Re: Retire Python 3.8 from Fedora 42+?
On Thu, Nov 21, 2024 at 11:13 PM Miro Hrončok via python-devel wrote: > > Hey Pythonistas, > > - Python 3.8 reached upstream End of Life 2024-10-07. > - RHEL 8 Python 3.8 Stream has been retired since May 2023. > - Debian buster had Python 3.7, bullseye has 3.9. > - Ubuntu 20.04 LTS (Focal Fossa) has Python 3.8. > - Standard support ends April 2025. > > Fedora 42 release date is April 2025. > > Hence I think we should retire Python 3.8 from Fedora 42+ Do it! Will you file a Change Proposal like https://fedoraproject.org/wiki/Changes/RetirePython3.7 ? Fabio -- ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org 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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Let's drop /usr/local/lib(64)/python3.X/site-packages once and for all
On Tue, Dec 3, 2024 at 7:03 PM Miro Hrončok via python-devel wrote: > > Hello Pythonistas. > > > tl;dr I wonder if we should get rid of the last downstream-only patch in > Fedora's Python, > the one responsible for /usr/local/lib(64)/python... installation location. > The removal would bring us closer to upstream, but perhaps cause a regression > for our users. > I propose to adapt PEP 668 (Marking Python base environments as “externally > managed”) instead. We shouldn't cater to ancient / broken tutorials and / or use cases that have always been "wrong" for all eternity, IMO. virtualenvs have existed in some shape or form for almost two decades (the venv module was added in Python 3.3 - in 2012!) - people should just use those. So I say "do it". If you make this a Change proposal, I'd vote +1 on it. Fabio -- ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org 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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
Re: Neuro SIG Python packaging strategy change
On Tue, Jul 8, 2025 at 12:51 PM Ankur Sinha via python-devel wrote: > > We've started to orphan packages and add them to the pytest testing > framework. You can see this in the PR. So far we've not run into a > package that is not installable/usable via pip on py3.12. I need to run > checks with other supported python versions. I'm trying to figure out if > that's something that can be passed as a parameter to the pytests too: I use `tox` for this purpose, it works great (we use it for the rust2rpm / cargo2rpm upstream tests). For example, here's the configuration for rust2rpm: https://pagure.io/fedora-rust/rust2rpm/blob/main/f/tox.ini#_1-16 With that configuration, running `tox p` runs the default tests for the defined environments in parallel (in this case, running `pytest` in parallel in venvs with py311, py312, py313, py314 interpreters, respectively). Fabio -- ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org 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/python-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
