Re: Prefered way to RFS
Thanks! Is this something that could be added here? https://wiki.debian.org/Python/GitPackaging#Sponsoring.2C_mentoring.2C_reviewing On 04.12.2019 18:42, Louis-Philippe V??ronneau wrote: If you are part of the DPMT or the PAPT, you can modify a package directly. If not, Merge Requests are accepted but since very few people have receive those notifications, sometimes it takes time to have them merged. For the sponsoring part, I've found that adding your requests to the topic of the #debian-python IRC channel on OFTC works really well. You can also send emails to this list. Cheers,
Re: pytest help needed
On Wed, 4 Dec 2019, Andreas Tille wrote:
Hi,
I try to prepare the latest git commit from upstream of python-pbcore[1].
Unfortunately the build time test fails with:
...
dh_auto_test
I: pybuild base:217: python3.8 setup.py test
running pytest
running egg_info
writing pbcore.egg-info/PKG-INFO
writing dependency_links to pbcore.egg-info/dependency_links.txt
writing entry points to pbcore.egg-info/entry_points.txt
writing requirements to pbcore.egg-info/requires.txt
writing top-level names to pbcore.egg-info/top_level.txt
reading manifest file 'pbcore.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
/usr/lib/python3.8/distutils/dist.py:274: UserWarning: Unknown distribution
option: 'test_requires'
warnings.warn(msg)
warning: no files found matching '*.txt'
writing manifest file 'pbcore.egg-info/SOURCES.txt'
running build_ext
ERROR: usage: setup.py [options] [file_or_dir] [file_or_dir] [...]
setup.py: error: unrecognized arguments: -n --dist=loadscope --cov=./pbcore
--cov-report=xml:coverage.xml
inifile: /build/python-pbcore-1.7.1+git20191121.7947eb7+dfsg/pytest.ini
rootdir: /build/python-pbcore-1.7.1+git20191121.7947eb7+dfsg
E: pybuild pybuild:341: test: plugin custom failed with: exit code=4: python3.8
setup.py test
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.8 3.7"
returned exit code 13
...
Those arguments are mentioned in pytest.ini which reads:
[pytest]
markers =
pbtestdata: requires the 'PacBioTestData' package to be installed
internal_data: requires access to internal data on
'/pbi/dept/secondary/siv/testdata'
constools: requires 'pbindex', 'samtools' and 'pbmerge' in PATH
addopts =
-v -n auto --dist=loadscope --durations=20 --junitxml=nosetests.xml
--cov=./pbcore --cov-report=xml:coverage.xml
Any hints what options I should use instead?
I think you also need pytest plugins xdist and cov (Debian packages
python3-pytest-xdist and python3-pytest-cov).
Scott
Re: pytest help needed
Why are you running tests via PYBUILD_SYSTEM=custom
PYBUILD_TEST_ARGS="{interpreter} setup.py test"? Is the pytest one not
working?
--
WBR, wRAR
signature.asc
Description: PGP signature
pytest help needed
Hi,
I try to prepare the latest git commit from upstream of python-pbcore[1].
Unfortunately the build time test fails with:
...
dh_auto_test
I: pybuild base:217: python3.8 setup.py test
running pytest
running egg_info
writing pbcore.egg-info/PKG-INFO
writing dependency_links to pbcore.egg-info/dependency_links.txt
writing entry points to pbcore.egg-info/entry_points.txt
writing requirements to pbcore.egg-info/requires.txt
writing top-level names to pbcore.egg-info/top_level.txt
reading manifest file 'pbcore.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
/usr/lib/python3.8/distutils/dist.py:274: UserWarning: Unknown distribution
option: 'test_requires'
warnings.warn(msg)
warning: no files found matching '*.txt'
writing manifest file 'pbcore.egg-info/SOURCES.txt'
running build_ext
ERROR: usage: setup.py [options] [file_or_dir] [file_or_dir] [...]
setup.py: error: unrecognized arguments: -n --dist=loadscope --cov=./pbcore
--cov-report=xml:coverage.xml
inifile: /build/python-pbcore-1.7.1+git20191121.7947eb7+dfsg/pytest.ini
rootdir: /build/python-pbcore-1.7.1+git20191121.7947eb7+dfsg
E: pybuild pybuild:341: test: plugin custom failed with: exit code=4: python3.8
setup.py test
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.8 3.7"
returned exit code 13
...
Those arguments are mentioned in pytest.ini which reads:
[pytest]
markers =
pbtestdata: requires the 'PacBioTestData' package to be installed
internal_data: requires access to internal data on
'/pbi/dept/secondary/siv/testdata'
constools: requires 'pbindex', 'samtools' and 'pbmerge' in PATH
addopts =
-v -n auto --dist=loadscope --durations=20 --junitxml=nosetests.xml
--cov=./pbcore --cov-report=xml:coverage.xml
Any hints what options I should use instead?
Kind regards
Andreas.
[1] https://salsa.debian.org/med-team/python-pbcore
--
http://fam-tille.de
Prefered way to RFS
Hi, Is there any preferred way to RFS? Merge request, just push to the repo and mail this list or something else? I guess that uploading a package to mentors.debian isn't of much use since we are using salsa? Thanks, H??vard
Re: RFS: python-traits
On Wed, Dec 04, 2019 at 09:23:56AM -0500, Scott Talbert wrote: > > Please fix that and I will sponsor this. > > Done. Uploaded! > > Also are you interested in python-traitsui package? It would be nice to > > get it ported to Python 3 or removed. > > Yes, I was planning to work on that package next. Thanks! Feel free to ping me directly about it. -- Dmitry Shachnev signature.asc Description: PGP signature
Joining the DPMT Team
Hi all, I have been working in the PAPT Team for quite some time and found that it's not really easy to be working under PAPT without DPMT access, since fixes for Python applications would often require changes in Python libraries. Can anyone add me into the DPMT Team? My Salsa account is @byang. Thanks very much in advance! Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Re: RFS: python-traits
On Wed, 4 Dec 2019, Dmitry Shachnev wrote:
Hi,
Can someone please do an upload of python-traits? I did an update to the
latest upstream release, plus various minor fixes. I didn't remove Python 2
support yet as there are still a few rdeps.
https://salsa.debian.org/python-team/modules/python-traits
- The changelog entry from 4.6.0-1 upload is missing.
- You added ${sphinxdoc:Depends}, but none of the packages contains any .html
files, so that substitution variable is undefined. Please either build and
ship the documentation, or remove that variable and python3-sphinx from
Build-Depends.
Please fix that and I will sponsor this.
Done.
Also are you interested in python-traitsui package? It would be nice to get
it ported to Python 3 or removed.
Yes, I was planning to work on that package next.
Scott
Lintian warning for this issue (Was: autopkgtest-pkg-python fails if package name is python-pyMODULENAME)
On Fri, Nov 29, 2019 at 12:02:44PM +0100, Andreas Tille wrote: > > I've opened > > https://salsa.debian.org/cpython-team/python3-defaults/merge_requests/2 > > to clarify this. Comments welcome, particularly if you don't think my > > proposed change reflects consensus. > > Thanks. This is more clear. I just uploaded with python3-pubsub to new. BTW, I think the issue deserves a lintian warning: package-name-different-than-loadable-python-module or something like this. Kind regards, Andreas. -- http://fam-tille.de
Re: RFS: python-traits
Hi Scott!
On Wed, Dec 04, 2019 at 12:07:36AM -0500, Scott Talbert wrote:
> Hi,
>
> Can someone please do an upload of python-traits? I did an update to the
> latest upstream release, plus various minor fixes. I didn't remove Python 2
> support yet as there are still a few rdeps.
>
> https://salsa.debian.org/python-team/modules/python-traits
- The changelog entry from 4.6.0-1 upload is missing.
- You added ${sphinxdoc:Depends}, but none of the packages contains any .html
files, so that substitution variable is undefined. Please either build and
ship the documentation, or remove that variable and python3-sphinx from
Build-Depends.
Please fix that and I will sponsor this.
Also are you interested in python-traitsui package? It would be nice to get
it ported to Python 3 or removed.
--
Dmitry Shachnev
signature.asc
Description: PGP signature
