Le 2020-01-16 15:10, Felix Schwarz a écrit :
Am 16.01.20 um 13:37 schrieb Nicolas Mailhot via devel:
If we start messing with the Python tree it would be nice to put each
shared
python component in a separate zip/xz/whatever, and allow versioning
those
archives
(ie use the highest semver zip present unless the code explicitely
requests
another version, and this version is available on the filesystem)
That would heal the breach between venv users and Fedora/rpm. We’re
alienating
a lot of users, because un-versioned python components, do not permit
the
version divergence, some third party software requires
Could you give a specific example? Even though my $DAYJOB is mostly
about
working with Python I don't have a clue which "un-versioned python
components"
you are referring to.
Right now we (in Fedora) deploy things like
/usr/lib/pythonxx/site-packages/something
That means only one something may exist on-disk at a given time. Python
users workaround this with venvs and blame rpm and Fedora for making a
single something possible.
Accommodating component versioning would mean deploying
/usr/lib/pythonxx/site-packages/something-semver.zip
Regards,
--
Nicolas Mailhot
_______________________________________________
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
