Re: Packaging the "next" Python

[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 
>>        "0mpbb6hkzdphyin861ywqnxibh5i4gjl5vvxdyralz6ngk2vr16r"))
>>        (patches (search-patches 
>>        "python-3-deterministic-build-info.patch"
>>                                 "python-3.13-fix-tests.patch"
>>                                 "python-3-hurd-configure.patch"))))))
>> ```
>
> Does this not work?
>
> --8<---------------cut here---------------start------------->8---
> (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-patches 
>        "python-3-deterministic-build-info.patch"
>                                 "python-3.13-fix-tests.patch"
>                                 "python-3-hurd-configure.patch"))))))
> --8<---------------cut here---------------end--------------->8---

Unfortunately, no. First, it doesn’t inherit the `name`, so the package is not
found, then there is a problem with the hash, the inherited one being used?!

I’ll just drop inheritance all together and write a package definition from
scratch as in was suggested, even if it involves a **lot** of code duplication.

-- 
Tanguy