Hi, >My understanding is that sphinx no more support Python as well >(this is the excuse from the uptream maintainer):
hm, perhaps upstream. In Debian, the consensus was to keep Python 2 working for old things until some time after the release AIUI. >if sphinx still supports Python 2 in Buster, >then it makes sense to make nbsphin supporting Python 2 in Buster. OK. Perhaps it’s not too much effort, and then, after the unfreeze, things can get de-python2-ised in a controlled way (reversely down the dependency tree from leaf packages down to libraries). I didn’t check to see how often it’s still used in Depends or B-D (UDD might know), but perhaps just before the freeze is a bit tight to introduce deep changes, especially as, in my experience, not all upstreams are fast enough to adopt. >Ok, I will have a look this week end. Thanks! bye, //mirabilos -- <ch> you introduced a merge commit │<mika> % g rebase -i HEAD^^ <mika> sorry, no idea and rebasing just fscked │<mika> Segmentation <ch> should have cloned into a clean repo │ fault (core dumped) <ch> if I rebase that now, it's really ugh │<mika:#grml> wuahhhhhh _______________________________________________ Python-modules-team mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
