Hi Ricardo, Ricardo Wurmus <rek...@elephly.net> writes:
> Maxim Cournoyer <maxim.courno...@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
