Re: [Python-modules-team] Processed: Bug#936196 marked as pending in beautifulsoup4
Hi Sandro (2020.04.02_18:01:42_+) > Hey Stefano, we're not ready to drop python-bs4: > http://sandrotosi.me/debian/py2removal/python-bs4_1.svg -- all those > rdeps are gonna take a long time to be fixed, so please do not upload > yet. thanks I was going to mail you - they're all basically ready to go, except aseba-plugin-blockly (non-free, meh). I think soupsive, bs4, and lxml can all go together. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
Re: [Python-modules-team] Processed: Bug#936196 marked as pending in beautifulsoup4
Hi Sandro (2020.04.02_18:34:24_+) > > I think soupsive, bs4, and lxml can all go together. > > i'm not sure it's that easy: if you look at the level 2 diagram > http://sandrotosi.me/debian/py2removal/python-bs4_2.svg you see at > least inkscape and localize needs to be fixed before we can remove > python-lxml You're right. dak wasn't showing me that. inkscape 1.0 is probably still a few months away. I'll look at lokalize, those may be trivial to port. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#938756: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).
Hi Thomas (2020.04.21_21:20:16_+) > > But that still leaves the question of what to do about the dependency of > > pytest on pypy-funcsigs ? should pypy modules be removed from pytest and > > it's reverse-dependencies in the same way that regular python2 modules > > were? how feasible is that? are pypy-* packages only useful with python2 > > pypy or are they also useful with python3 pypy? Pretty much, yes. pypy itself (the python 2.7 pypy) will continue to exist for the foreseeable future, to support building pypy3. But we don't need to ship modules for it. I'd be pretty happy if we had working virtualenv, and nothing else. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#973082: confirmed
Hi Hans-Christoph (2021.02.01_10:27:12_+) > Do the tests pass with this patch? Yes. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#991195: appdirs: Friendly Fork: platformdirs
Hi Debian (2021.07.17_01:00:13_+) > Upstream there has been a friendly fork of appdirs to "platformdirs". > Assuming this is the future of the library, we should migrate debian > packages from appdirs to platformdirs, once it's in the archive. Uploaded to NEW, under the python-team: https://salsa.debian.org/python-team/packages/platformdirs SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#970158: pyparsing isn't Python 2 compatible: time to remove pypy support? (was: Bug#970158: Updating the pyparsing Uploaders list)
Hi Thomas (2022.01.26_10:34:13_+) > When building 3.0.7, I get: > > I: pybuild base:237: pypy setup.py clean > Traceback (most recent call last): > File "setup.py", line 8, in > from pyparsing import __version__ as pyparsing_version > File "/<>/pyparsing/__init__.py", line 100 > major: int > ^ > SyntaxError: invalid syntax > E: pybuild pybuild:367: clean: plugin distutils failed with: exit code=1: > pypy setup.py clean > > This feels like we need to drop pypy support for this package. Stefano, your > thoughts? How should this be handled? It can be dropped, we don't need to keep much Python 2.7 stack alive any more. I'm keeping the bare minimum for virtualenvs to function, and that doesn't require this. There is one reverse-dep, python-packaging, that should have it's 2.7 bits dropped, too. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272 ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
