Autopkgtest issues blocking python3.8 as default transition

2020-03-20 Thread Scott Kitterman
I've gone through and statused the issues currently listed on the package tracker for python3-defaults migration that are autopkgtest related [1]. I stuffed it into a pastebin [2]. I'm open to suggestions about where better to maintain such a list. If you ever want python3.8 as default

Re: Where can I find packages that need a maintainer?

2020-03-20 Thread Paul Wise
On Thu, Feb 13, 2020 at 1:25 AM Pablo Mestre wrote: > With the desire to continue contributing I would like to know where I > can find other packages that need a maintainer. The WNPP data (specifically RFA, O bugs) list packages needing a new maintainer: https://www.debian.org/devel/wnpp/

Re: When should I drop python2 support for python-linecache2 & python-traceback2 (therefore, unittest2, mock, sphinx, pytest... and the rest of the Python 2 world if I pull this string until end...)

2020-03-20 Thread Sandro Tosi
> python-fixture (the binary) is gone, therefore we have #952130 and > #952127. I've been reluctant to remove Py2 support from these, because > unittest2 needs it, and this would break a lot of packages (including, > indirectly, stuff like sphinx, pytest, etc.). you can remove them when

When should I drop python2 support for python-linecache2 & python-traceback2 (therefore, unittest2, mock, sphinx, pytest... and the rest of the Python 2 world if I pull this string until end...)

2020-03-20 Thread Thomas Goirand
Hi, python-fixture (the binary) is gone, therefore we have #952130 and #952127. I've been reluctant to remove Py2 support from these, because unittest2 needs it, and this would break a lot of packages (including, indirectly, stuff like sphinx, pytest, etc.). What is it that the team suggests at

Re: Questions about including tests/ directory into package

2020-03-20 Thread Sandro Tosi
> packages=find_packages("src"), > > Setuptools will only find "tinyalign" under the "src" folder, as a > python module to package, which is why that's the only thing that is > going to be packaged. > > IMO, the best approach to this problem is to convince upstream to move > their tests folder

Re: Questions about including tests/ directory into package

2020-03-20 Thread Thomas Goirand
On 3/19/20 7:22 AM, Sao I Kuan wrote: > Hi, > > I'm newcomer to Debian packaging, and trying to add the autopkgtest > test script into python-tinyalign[1]. > > [1] https://salsa.debian.org/med-team/python-tinyalign > > And now I'm facing a (maybe simple) problem. > > The upstream test

Re: Where can I find packages that need a maintainer?

2020-03-20 Thread Pablo Mestre
Thanks, i will take a look... El 2/24/20 a las 4:24 AM, Paul Wise escribió: > On Thu, Feb 13, 2020 at 1:25 AM Pablo Mestre wrote: > >> I recently started as a maintainer of a package for Debian which is >> currently awaiting approval to be reintroduced into the repositories. [1] > In case you

Joining the team and RFS

2020-03-20 Thread Juhani Numminen
Hi, I'd like to join the Debian Python Modules Team to maintain a new python module called pysol_cards. It is a dependency of pysolfc and freecell-solver. The role of the pysol_cards module seems to be mainly to share code between those two. Packaging is ready for review and upload, please see

Re: Questions about including tests/ directory into package

2020-03-20 Thread Sao I Kuan
On Fri, Mar 20, 2020 at 2:38 AM Diane Trout wrote: > The way I solved that problem in a similar package was this > > Test-Command: set -e > ; for py in $(py3versions -r 2>/dev/null) > ; do cd tests > ; echo "Testing with $py in $(pwd):" > ; http_proxy= $py -m pytest -v --pyargs > ; done >