On 3 December 2016 at 05:40, Toshio Kuratomi <a.bad...@gmail.com> wrote: > On Dec 1, 2016 6:58 AM, "Petr Viktorin" <pvikt...@redhat.com> wrote: >> Problems with upstreams getting setup.py wrong should be treated as >> upstream bugs and treated accordingly: reported as pull requests, or, as the >> last resort, by a Fedora-specific patch to setup.py. > > Note that fedora will have to carry more patches to setup.py's (but > hopefully of limited durations and pretty trivial). Upstream versioned > requirements often don't match with distro packages because we backport to > work around bugs in compatible manners while upstream simply requires newer > versions that have the bugs fixed. > > Not a showstopper by any means; just something to be aware of.
Depending on how deep people want to dive into that aspect, it may even make sense to start using the "Local version identifier" feature in PEP 440 to expose RPM release numbers to Python level tooling: https://www.python.org/dev/peps/pep-0440/#local-version-identifiers Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
