Re: Joining the team
Hi Sebastiaan, Il 23/12/22 14:16, Sebastiaan Couwenberg ha scritto: Please add sebastic to the team on Salsa, I'd like to help by pushing commits for packages maintained in the team that are part of the dependency chain of the packages I help maintain. Case in point: python-numpy-groupies (#1026885) I have read and accept the team policy. Kind Regards, Bas I have some work done for numpy_groupies in https://salsa.debian.org/antonio.valentino/numpy-groupies. cheers -- Antonio Valentino
Re: Please add me to the salsa project
Hi Michael (2023.01.07_15:25:31_+) > please add me to the python-team/packages salsa project. > > I would like to maintain my python-related packages there. Added. Welcome! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Joining the team
Hi Sebastiaan (2022.12.23_13:16:38_+) > Please add sebastic to the team on Salsa, I'd like to help by pushing > commits for packages maintained in the team that are part of the dependency > chain of the packages I help maintain. Added, welcome! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Joining the team to maintain pydrive
Hi Sebastien (2022.12.09_12:18:38_+) > I would like to add pydrive [1] to Debian (I'm currently maintaining it for > Ubuntu as a opt-depends of deja-dup to be able to back-up on gdrive). I > think it makes sense for it to be under the python team umbrella. > I might occasionally contribute to updates or fixes on desktop components > maintained by the team. Added. Welcome to the team! SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Re: Requset to join team
Hi اوبونتو (2022.12.07_13:29:03_+) > I want to join Debian Python team to maintain python-fire package. Hi, thanks for your interest in joining the Python team. Please read the team policy: https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst#joining-the-team SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Please add me to the salsa project
Hi, please add me to the python-team/packages salsa project. I would like to maintain my python-related packages there. My salsa user account is mbanck. I have read and accept the team policy. Michael
Re: Python 3.11 for bookworm?
On Sat, 07 Jan 2023 at 10:23:19 +0200, Andrius Merkys wrote:
> If I may, I would as well be grateful if someone could give a look at:
>
> #1023972 [src:python-ase] FTBFS with Python 3.11 due to
> pathlib.Path.__enter__() deprecation
>
> I have no idea how to fix this and the upstream is silent.
My first thought on seeing this was: why were Path objects a context
manager in the first place? What would that mean?
Looking at the code in python3.10 and python3.11 pathlib, it seems the
reason this is deprecated is indeed that it didn't make sense:
def __enter__(self):
# In previous versions of pathlib, __exit__() marked this path as
# closed; subsequent attempts to perform I/O would raise an IOError.
# This functionality was never documented, and had the effect of
# making Path objects mutable, contrary to PEP 428.
# In Python 3.9 __exit__() was made a no-op.
# In Python 3.11 __enter__() began emitting DeprecationWarning.
# In Python 3.13 __enter__() and __exit__() should be removed.
warnings.warn("pathlib.Path.__enter__() is deprecated and scheduled "
"for removal in Python 3.13; Path objects as a context "
"manager is a no-op",
DeprecationWarning, stacklevel=2)
return self
def __exit__(self, t, v, tb):
pass
So the solution seems to be that if your package contains this:
with some_path_object:
do_stuff(some_path_object)
replace it with:
do_stuff(some_path_object)
and if it contains:
with Path(...) as my_path:
do_stuff(my_path)
replace with:
my_path = Path(...)
do_stuff(my_path)
I hope that should be a relatively straightforward change.
smcv
Re: Python 3.11 for bookworm?
Hello, On 2023-01-07 10:05, Andreas Tille wrote: Am Thu, Jan 05, 2023 at 01:57:43PM +0100 schrieb Thomas Goirand: Please share it in this list! #1023965 [src:pandas] pandas FTBFS with Python 3.11 as supported version #1024031 [src:numba] numba FTBFS with Python 3.11 as supported version If I may, I would as well be grateful if someone could give a look at: #1023972 [src:python-ase] FTBFS with Python 3.11 due to pathlib.Path.__enter__() deprecation I have no idea how to fix this and the upstream is silent. Best, Andrius
Re: Python 3.11 for bookworm?
Hi Thomas, Am Thu, Jan 05, 2023 at 01:57:43PM +0100 schrieb Thomas Goirand: > > This has since already been discussed here: the final decision was to "at > least try 3.11", which is exactly what we're doing. I admit I was not at site and may be I missunderstood what was finally decided. From my perspective this "at least try" is that we are actually trying by having 3.11 as additional supported version which has triggered quite some work. We are approaching the Transition and Toolchain Freeze in 5 days[1]. Given that switching default Python is a transition I wonder how you can assume that this is the right time to suggest this. I would not have been that astonished if you would have done so say at first December last year. But now its absolutely clear that a migration (with the "option" to revert which will cause extra work) will pour sand into the gears of the release process. > FYI, I'm down with only 2 major bugs (I don't mind much if the other 3 RC > bugs push the 3 affected packages away from the release, it's just a "would > be nice" thing ATM): That's a nice situation for the field you are working in. > > If I would create a list mine whould be way longer. > > Please share it in this list! #1023965 [src:pandas] pandas FTBFS with Python 3.11 as supported version #1024031 [src:numba] numba FTBFS with Python 3.11 as supported version These packages have a sufficient amount of rdepends and usually trigger lots of other autopkgtest failures in other packages which will keep them out of testing for quite some time. We could need all helping hands to fix these ... all noise that will happen afterwards will keep the relevant teams busy enough. > > We are constantly beaten by removal from testing warnings > > even with Python3.11 as an option and sometimes we simply need to remove > > that option as a temporary means for bookworm. > > Same over here. It's finally looking good for me after 2 months of heavy > efforts. You mean you are fixing Python 3.10 manually in some packages diverging what will be default Python? > > No better solution but better timing which means after bookworm release. > > I've read *many* people saying it would be disappointing for them to see > their package removed because of Python 3.11. Well, please consider that it > would also be very disappointing to *not* have Python 3.11 for those who > managed constantly fix issues for it. I can understand that we can never satisfy the needs of everybody. My main problem is the extremely unfortunate timing that is happening now. > The timing was exactly what was discussed during Debconf: it's very annoying > that this year, upstream Python release was one month late... we're only > trying to deal with it. I do not remember that the scchedule was discussed. * Add 3.11 as a supported Python3 version was done in python3-defaults (3.10.6-2) at Fri, 11 Nov 2022 11:10:31 +0200. At 12. December Graham suggested on the behalf of the release team[2] to switch to 3.11. If we would have acted upon this at that very time I would have considered this quite dense but the last chance to consider this in line with the "lets try" attempt discussed at DebConf. Bug #1026825: python3.11 as default filed right before (21.12.) a series of holidays in the region of the world where lots of developers will typically reduce their activity which is closely followed by the first freeze step is IMHO something else. Since I realised that the transition was started[3] our discussion is a bit useless. I just want to explain the motivation why I sounded "astonished" since you said that you do not understood astonishment since we are following the suggested plan. Kind regards Andreas. [1] https://release.debian.org/testing/freeze_policy.html [2] https://lists.debian.org/debian-python/2022/12/msg00074.html [3] https://release.debian.org/transitions/html/python3.11-default.html -- http://fam-tille.de
