So let me sum up: > Some Python building backends, eg. setuptools, explicitly allow > creating package with version `0.0.0` when the version used by a > project is not known. This was > [https://github.com/pypa/setuptools/issues/2329 discussed upstream] > with conclusion that it's an intended behavior. Upstream says that it is intended that packages are able to set their version to 0 or 0.0.0, but… > Based on discussion on python-devel mailing list there will be no way > to opt out from this change. There will be no possibility to package a > Python package with version `0`. … your proposed Change will fail those packages' build with no opt-out!? You cannot be serious! (Though actually, would %global __provides_exclude_from … together with a manual Provides: python3dist(…) = 0 not work?) A clear -1 to this Change as proposed. > We've never encountered a situation when packaging the version `0` was > the package maintainers intention. What if it is the *upstream* maintainer's intention? Are we now dictating versioning schemes on upstream projects, disallowing version numbers that upstream setuptools explicitly considers valid? Kevin Kofler _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
