Re: Removal of Python 2?
Hi Ryan, > Python 2 is no longer supported, but the Tauthon project [1] is > continuing support and backporting features from Python 3. We should Didn't know about Tauthon, thanks for the pointer! > consider packaging Tauthon in Guix and updating packages to depend on Yes, that sounds like an interesting strategy to explore. One potential obstacle is that most of the Python2-dependent package are out of maintenance as well. But then, many of them don't need any maintenance. If we introduce Tauthon, we should probably untie its dependents from the Python (3) version, i.e. stop deriving them from Python 3 package definitions. The latter will ever more evolve in an incompatible way. Cheers, Konrad.
Re: Removal of Python 2?
Hi Ludo and Simon, Ludovic Courtès writes: > What we could do is start removing ‘python2-’ packages, especially those > with a non-negligible maintenance cost (numpy, scipy, matplotlib, etc.). > We can move them to the Guix-Past channel if there’s interest. Yes, that sounds like a good plan. With the long-term goal of moving python2 itself to guix-past, if it ever ceases to be an important dependency (which I am not yet convinced of). > The attached script lists unused ‘python2-’ leaf packages: ... > Are these good candidates for removal? These and more: once they are removed, there will be a new set of leaf packages. It might be worth checking if there is a Python 3 equivalent before removing a library. But in the majority of cases there is. zimoun writes: > Starting with e13ab46c2052609c4ad792aeb304a752b50d034e, I remove the > broken leaf Python2 packages. I find them using "guix weather" and > "guix refresh -l". More are coming. ;-) It certainly makes sense to remove broken packages, but for the rest I'd say guix-past is a better destination than the trashcan. Cheers, Konrad
Re: Removal of Python 2?
Hi, On Wed, 23 Jun 2021 at 17:27, Ludovic Courtès wrote: > What we could do is start removing ‘python2-’ packages, especially those > with a non-negligible maintenance cost (numpy, scipy, matplotlib, etc.). > We can move them to the Guix-Past channel if there’s interest. Starting with e13ab46c2052609c4ad792aeb304a752b50d034e, I remove the broken leaf Python2 packages. I find them using "guix weather" and "guix refresh -l". More are coming. ;-) Cheers, simon
Re: Removal of Python 2?
Hi, Konrad Hinsen skribis: >> Python 2 is dead, dead, dead like the parrot and end-of-prolonged life >> as of more than 1 1/2 years. Anyhow, there might still be quite some >> software not ported to Python 3 after 10 years. So I'm afraid we need to >> keep Python 2. > > At this time, more than 2500 packages still depend on Python 2, and > that's not just Python libraries. The list includes packages such as > TeXlive, LLVM, Rust, OpenJDK, Calibre, OCaml, qemu, etc. > > For many of these packages, Python 2 is used only as part of the build > procedure. Which is run in a highly protective sandbox. So I don't think > we need to worry much about having Python 2 in Guix. To discourage > people from installing it by accident, we could make it a hidden > package. I agree. What we could do is start removing ‘python2-’ packages, especially those with a non-negligible maintenance cost (numpy, scipy, matplotlib, etc.). We can move them to the Guix-Past channel if there’s interest. The attached script lists unused ‘python2-’ leaf packages: --8<---cut here---start->8--- $ guix repl -- unused-python2-packages.scm | wc -l 288 --8<---cut here---end--->8--- Are these good candidates for removal? Thoughts? Ludo’. (use-modules (gnu packages) (guix) (guix graph) (guix scripts graph)) (define all (fold-packages cons '() #:select? (const #t))) (with-store store (let ((back-edges (run-with-store store (node-back-edges %bag-node-type all (define (unused-python2? package) (and (string-prefix? "python2-" (package-name package)) (zero? (node-reachable-count (list package) back-edges (for-each (lambda (package) (when (unused-python2? package) (format #t "~a~%" (package-name package all)))
Re: Removal of Python 2?
On Tuesday, June 22nd, 2021 at 6:53 AM, Hartmut Goebel wrote: > Am 06.06.21 um 21:44 schrieb Lars-Dominik Braun: > > > 3. Determine the fate of Python 2, which is probably broken through this > > > > patch set. Shall we remove it entirely? Is it worth to keep support? > > Python 2 is dead, dead, dead like the parrot and end-of-prolonged life > > as of more than 1 1/2 years. Anyhow, there might still be quite some > > software not ported to Python 3 after 10 years. So I'm afraid we need to > > keep Python 2. Python 2 is no longer supported, but the Tauthon project [1] is continuing support and backporting features from Python 3. We should consider packaging Tauthon in Guix and updating packages to depend on it. The Python project has promised there will never be a Python 2.8 release [2] but considering the huge body of extant Python 2 code, if we can get consensus within Guix I think there would be value in continuing to support python2 packages via Tauthon. [1] https://github.com/naftaliharris/tauthon [2] https://www.python.org/dev/peps/pep-0404/
Re: Removal of Python 2?
Hi Hartmut, > Python 2 is dead, dead, dead like the parrot and end-of-prolonged life > as of more than 1 1/2 years. Anyhow, there might still be quite some > software not ported to Python 3 after 10 years. So I'm afraid we need to > keep Python 2. At this time, more than 2500 packages still depend on Python 2, and that's not just Python libraries. The list includes packages such as TeXlive, LLVM, Rust, OpenJDK, Calibre, OCaml, qemu, etc. For many of these packages, Python 2 is used only as part of the build procedure. Which is run in a highly protective sandbox. So I don't think we need to worry much about having Python 2 in Guix. To discourage people from installing it by accident, we could make it a hidden package. Cheers, Konrad.
Removal of Python 2?
Am 06.06.21 um 21:44 schrieb Lars-Dominik Braun: 3) Determine the fate of Python 2, which is probably broken through this patch set. Shall we remove it entirely? Is it worth to keep support? Python 2 is dead, dead, dead like the parrot and end-of-prolonged life as of more than 1 1/2 years. Anyhow, there might still be quite some software not ported to Python 3 after 10 years. So I'm afraid we need to keep Python 2. Other opinions? -- Regards Hartmut Goebel | Hartmut Goebel | h.goe...@crazy-compilers.com | | www.crazy-compilers.com | compilers which you thought are impossible |
