Re: Re: python-team: New branch

Re: Re: python-team: New branch

[Sharlatan Hellseher]

[-- Attachment #1: Type: text/plain, Size: 129 bytes --]


Hi,

I've pulled and initiated local rebuild for

   guix build -P 2 python-astropy

I'll push any fixes if it failes.

--
Oleg

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

Re: python-team: New branch

[Ricardo Wurmus]

Sharlatan Hellseher <sharlatanus@gmail.com> writes:

> I've pulled and initiated local rebuild for
>
>    guix build -P 2 python-astropy
>
> I'll push any fixes if it failes.

Thank you!

I've just rebased python-team on top of master, because Maxim just
pushed some changes to python-tox etc to the master branch.

-- 
Ricardo

Re: python-team: New branch

[Ricardo Wurmus]

Ricardo Wurmus <rekado@elephly.net> writes:

> I've just rebased python-team on top of master, because Maxim just
> pushed some changes to python-tox etc to the master branch.

Perhaps prematurely I rebased python-team on top of rust-team to benefit
from upgrades needed for pydantic.  When rust-team is rebased on top of
master we should rebase once more to restore all the fixes to Python
packages that have since been pushed to the master branch.

-- 
Ricardo

Re: python-team: New branch

[Sharlatan Hellseher]

Hi,

Ricardo and Maxim do you have any list of packages you are about to
refresh/fix on python-team?
I've finished with Astro update for this month and may provide my time
for python-team.

Thanks,
Oleg

Re: python-team: New branch

[Efraim Flashner]

[-- Attachment #1: Type: text/plain, Size: 890 bytes --]

On Sat, Dec 21, 2024 at 09:33:31PM +0100, Ricardo Wurmus wrote:
> Ricardo Wurmus <rekado@elephly.net> writes:
> 
> > I've just rebased python-team on top of master, because Maxim just
> > pushed some changes to python-tox etc to the master branch.
> 
> Perhaps prematurely I rebased python-team on top of rust-team to benefit
> from upgrades needed for pydantic.  When rust-team is rebased on top of
> master we should rebase once more to restore all the fixes to Python
> packages that have since been pushed to the master branch.

I've put in a request for merge for rust-team.  Currently it is behind
mesa-updates, which is the current branch waiting to merge.

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

python-team: New branch

[Ricardo Wurmus]

Hi Guix,

I'm CC'ing the python-team.

Since the merge of the python-team branch we've seen a bunch of
new build failures to popular packages.  I've started work to repair
some of the damage.

I think we should start a new python-team branch where we build out
important upgrades and fixes.  I'd like to aim for merging that new
branch before the end of the year, so let's try to restrict ourselves to
important fixes only.

If there is more time we should also consider upgrading these packages:

    python-typing-extensions
    python-virtualenv
    python-platformdirs
    python-colorama
    python-chardet

(I patched out version checks in python-tox to avoid upgrading, but I
think we should not do that habitually.)

Unless anyone objects I'll destroy and recreate the python-team branch
with my commits tonight.

-- 
Ricardo

Re: python-team: New branch

[Ricardo Wurmus]

Ricardo Wurmus <rekado@elephly.net> writes:

> If there is more time we should also consider upgrading these packages:
>
>     python-typing-extensions
>     python-virtualenv
>     python-platformdirs
>     python-colorama
>     python-chardet
>
> (I patched out version checks in python-tox to avoid upgrading, but I
> think we should not do that habitually.)

I have upgraded the above packages, too.

> Unless anyone objects I'll destroy and recreate the python-team branch
> with my commits tonight.

I've pushed the branch.  Please add your fixes there.  Let's try to get
this merged soon.  The goal here is to reduce the number of recently
introduced build failures significantly.

-- 
Ricardo

Re: python-team: New branch

[Maxim Cournoyer]

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

> Hi Guix,
>
> I'm CC'ing the python-team.
>
> Since the merge of the python-team branch we've seen a bunch of
> new build failures to popular packages.  I've started work to repair
> some of the damage.
>
> I think we should start a new python-team branch where we build out
> important upgrades and fixes.  I'd like to aim for merging that new
> branch before the end of the year, so let's try to restrict ourselves to
> important fixes only.
>
> If there is more time we should also consider upgrading these packages:
>
>     python-typing-extensions
>     python-virtualenv
>     python-platformdirs
>     python-colorama
>     python-chardet
>
> (I patched out version checks in python-tox to avoid upgrading, but I
> think we should not do that habitually.)

I have a Python mass update branch I've been developing, holding it back
because I kept finding breakage (whether caused by my changes or
already there).  There's now 200 commits in it, including an update to
virtualenv and typing extensions, along Python build systems
improvements.

I'll try getting it a bit further in terms of packages breakage then
send it for review.  If you'd rather see it already and work on a
wip-python-team branch, I could submit it already in its more rough
form.

-- 
Thanks,
Maxim

Re: python-team: New branch

[Ricardo Wurmus]

Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> I have a Python mass update branch I've been developing, holding it back
> because I kept finding breakage (whether caused by my changes or
> already there).  There's now 200 commits in it, including an update to
> virtualenv and typing extensions, along Python build systems
> improvements.

There's a good chance there will be significant overlap with the
python-team branch in its current state.

> I'll try getting it a bit further in terms of packages breakage then
> send it for review.  If you'd rather see it already and work on a
> wip-python-team branch, I could submit it already in its more rough
> form.

If you could clean it up and push the parts that do not touch the Python
build system you could push those commits to python-team.  Let's delay
the build system changes this time around.

-- 
Ricardo

Re: python-team: New branch

[Maxim Cournoyer]

Hi Ricardo,

Ricardo Wurmus <rekado@elephly.net> writes:

> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>> I have a Python mass update branch I've been developing, holding it back
>> because I kept finding breakage (whether caused by my changes or
>> already there).  There's now 200 commits in it, including an update to
>> virtualenv and typing extensions, along Python build systems
>> improvements.
>
> There's a good chance there will be significant overlap with the
> python-team branch in its current state.
>
>> I'll try getting it a bit further in terms of packages breakage then
>> send it for review.  If you'd rather see it already and work on a
>> wip-python-team branch, I could submit it already in its more rough
>> form.
>
> If you could clean it up and push the parts that do not touch the Python
> build system you could push those commits to python-team.  Let's delay
> the build system changes this time around.

Note that I've updated the packages in (gnu packages python-build),
including setuptools, which means near full Python world rebuild anyway.
I think my changes may be better for python-team-next, if the next cycle
is to be as short as possible.

-- 
Thanks,
Maxim