Re: Packaging the "next" Python

2025-03-02 Thread Leo Famulari
On Sat, Mar 01, 2025 at 12:02:57PM +0100, Tanguy Le Carrour wrote: > On Thu Feb 27, 2025 at 7:39 PM CET, Ricardo Wurmus wrote: > > Even though you may feel pressured to write a verbose version of this > > package > > variant after reading the messages here, I think it's a perfectly situation > > f

Re: Packaging the "next" Python

2025-03-01 Thread dannym
Hi Tanguy, I tried this (define-public python-3.13 (package (inherit python-3.12) (version "3.13.2") (source (origin (inherit (package-source python-3.12)) (sha256 (base32 "0mpbb6hkzdphyin861ywqnxibh5i4gjl5vvxdyralz6ngk2vr16r")) (patches (search-pa

Re: Packaging the "next" Python

2025-03-01 Thread Tanguy Le Carrour
Hi Ricardo, On Thu Feb 27, 2025 at 7:39 PM CET, Ricardo Wurmus wrote: > Even though you may feel pressured to write a verbose version of this package > variant after reading the messages here, I think it's a perfectly situation > for inheritance. There is nothing wrong with use of inheritance fo

Re: Packaging the "next" Python

2025-02-27 Thread Ricardo Wurmus
Felix Lechner via "Development of GNU Guix and the GNU System distribution." writes: On Thu, Feb 27 2025, Leo Famulari wrote: I always recommend against using inheritance Yes, it's like a disease! Please make the use of inheritance illegal in package declarations except in approved case

Re: Packaging the "next" Python

2025-02-27 Thread Tanguy Le Carrour
Hi Ricardo, On Thu Feb 27, 2025 at 3:05 PM CET, Ricardo Wurmus wrote: > Hi Tanguy, > >> ```scheme >> (define-public python-3.13 >> (package >> (inherit python-3.12) >> (version "3.13.2") >> (source >> (origin >>(sha256 (base32 >>"0mpbb6hkzdphyin861ywqnxibh5i4gj

Re: Packaging the "next" Python

2025-02-27 Thread Tanguy Le Carrour
Hi Felix, On Thu Feb 27, 2025 at 3:14 PM CET, Felix Lechner wrote: > On Thu, Feb 27 2025, Leo Famulari wrote: > >> I always recommend against using inheritance > > Yes, it's like a disease! Please make the use of inheritance illegal in > package declarations except in approved cases. > > In all

Re: Packaging the "next" Python

2025-02-27 Thread Tanguy Le Carrour
Hi Leo, On Thu Feb 27, 2025 at 2:39 PM CET, Leo Famulari wrote: > On Thu, Feb 27, 2025, at 08:33, Tanguy Le Carrour wrote: >> I have a working package definition for 3.13, but I’m struggling with >> the inheritance >> mechanism. I had to copy over from 3.12 the 300+ lines of `(arguments >> …)`

Re: Packaging the "next" Python

2025-02-27 Thread Development of GNU Guix and the GNU System distribution.
Hi Leo, On Thu, Feb 27 2025, Leo Famulari wrote: > I always recommend against using inheritance Yes, it's like a disease! Please make the use of inheritance illegal in package declarations except in approved cases. In all circumstances, however, later package versions should never inherit from

Re: Packaging the "next" Python

2025-02-27 Thread Ricardo Wurmus
Hi Tanguy, ```scheme (define-public python-3.13 (package (inherit python-3.12) (version "3.13.2") (source (origin (sha256 (base32 "0mpbb6hkzdphyin861ywqnxibh5i4gjl5vvxdyralz6ngk2vr16r")) (patches (search-patches "python-3-deterministic-build-info.

Re: Packaging the "next" Python

2025-02-27 Thread Leo Famulari
On Thu, Feb 27, 2025, at 08:33, Tanguy Le Carrour wrote: > I have a working package definition for 3.13, but I’m struggling with > the inheritance > mechanism. I had to copy over from 3.12 the 300+ lines of `(arguments > …)` to > make it work, even if I didn’t change a single line of it!? That so