Petr Viktorin wrote:
> Indeed, there's a disconnect here. The old Pythons are intended for
> *upstream* development/testing.
Your explanation does not solve the inherent contradiction between:
>> churchyard (in the FESCo tracker):
>> | These packages are not intended to be used as dependencies for other
>> | packages (such as we have some "compat" packages when another package
>> | needs an older version of a library), hence we want to stop people from
>> | requiring them
and:
>> Nick Coghlan (in this thread):
>>> The addition of these packages to Fedora means that as soon as you do
>>> "dnf install tox", those runtimes are all brought in automatically via
>>> Recommends
>> I would also like to point out that if you have these suffixed Python
>> versions installed, some build scripts may be accidentally picking up
>> those instead of the recommended default versions of Python.
>
> Do you mean Fedora build scripts here?
I mean build scripts in upstream tarballs, which can also end up in our
packages (and cause problems when building outside of mock), but which can
also be used directly by people.
Kevin Kofler
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
