Re: Request to join Python Modules Team
On Fri, Apr 10, 2020 at 6:22 PM Sao I Kuan wrote: > > On Fri, Apr 10, 2020 at 6:16 PM Sao I Kuan wrote: > > > > Hiya o/, > > > > I would like to join the Python Modules Team. > > > > I'm a newcomer into Debian from this March, and doing the packaging > > which is COVID-19 related, with COVID-19 Biohackathon[0]. > > > > [0] https://lists.debian.org/debian-devel-announce/2020/03/msg00010.html > > > > Now I'm trying to packaging the new python application idseq-bench[1] > > (which will be team-maintained inside debian-med), which needs a > > module smart_open[2]. I think [2] could be team maintained inside > > DPMT. > > > > [1] https://github.com/chanzuckerberg/idseq-bench > > [2] https://github.com/RaRe-Technologies/smart_open > > > > I read the Debian Python Policy[3]. > > > > [3] https://www.debian.org/doc/packaging-manuals/python-policy/ > > I now found and accept the DPMT Policy[4]. My Salsa handle is @sikuan-guest. > > [4] > https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst Ping o/ Or am I missing any necessary information? My Salsa handle was changed to @sikuan. Thank you! Sincerely, Sao I Kuan saoik...@gmail.com
Re: Request to join Python Modules Team
On Fri, Apr 10, 2020 at 6:16 PM Sao I Kuan wrote: > > Hiya o/, > > I would like to join the Python Modules Team. > > I'm a newcomer into Debian from this March, and doing the packaging > which is COVID-19 related, with COVID-19 Biohackathon[0]. > > [0] https://lists.debian.org/debian-devel-announce/2020/03/msg00010.html > > Now I'm trying to packaging the new python application idseq-bench[1] > (which will be team-maintained inside debian-med), which needs a > module smart_open[2]. I think [2] could be team maintained inside > DPMT. > > [1] https://github.com/chanzuckerberg/idseq-bench > [2] https://github.com/RaRe-Technologies/smart_open > > I read the Debian Python Policy[3]. > > [3] https://www.debian.org/doc/packaging-manuals/python-policy/ I now found and accept the DPMT Policy[4]. My Salsa handle is @sikuan-guest. [4] https://salsa.debian.org/python-team/tools/python-modules/-/blob/master/policy.rst Thank you! Sincerely, Sao I Kuan saoik...@gmail.com
Request to join Python Modules Team
Hiya o/, I would like to join the Python Modules Team. I'm a newcomer into Debian from this March, and doing the packaging which is COVID-19 related, with COVID-19 Biohackathon[0]. [0] https://lists.debian.org/debian-devel-announce/2020/03/msg00010.html Now I'm trying to packaging the new python application idseq-bench[1] (which will be team-maintained inside debian-med), which needs a module smart_open[2]. I think [2] could be team maintained inside DPMT. [1] https://github.com/chanzuckerberg/idseq-bench [2] https://github.com/RaRe-Technologies/smart_open I read the Debian Python Policy[3]. [3] https://www.debian.org/doc/packaging-manuals/python-policy/ Thank you! Sincerely, Sao I Kuan saoik...@gmail.com
Re: Questions about including tests/ directory into package
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 > Depends: @, python3-all, python3-pytest > > The goal of autopkgtests is to test the installed package, when > autopkgtest starts running it defaults to starting in the extracted > copy of the source package. > > The goal is to make sure you test the copy in /usr/lib/python*/dist- > packages. So I assumed if cd-ed into the tests directory the package > source module wouldn't be available to the test runner. > > I did make the assumption that none of the tests messed with the python > path to look in the parent directory... Thanks, Diane. I tried with your given example, it really helped. A lot of appreciates. Thanks for your kind and deep explanation. Sincerely, Sao I Kuan saoik...@gmail.com
Questions about including tests/ directory into package
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 files are located in tests/ directory, but seems this directory is excluded during packaging. I have no idea how to include this tests/ directory. 1. Please let me know is there any variable for including the specific file/directory. 2. Why and when the tests/ directory excluded? I tried to find the logic in dh-python [2], but failed. [2] https://salsa.debian.org/python-team/tools/dh-python 3. Is this a correct approach for including the excluded test materials? Always appreciates. Sincerely, Sao I Kuan saoik...@gmail.com
