[Python-modules-team] Bug#946810: python3-commonmark-py: update the source url in watch to match the currently supported repo

Package: python3-commonmark-bkrs Version: 0.5.4+ds-4 Severity: wishlist Dear Maintainer, The watch file of the package points to the old repository (rolandshoemaker/CommonMark-py): https://salsa.debian.org/python-team/modules/commonmark- bkrs/blob/master/debian/watch But that repository clearly

[Python-modules-team] Bug#946619: python3-pylint-django: Re-enable the tests after pylint 2.5 has been released.

Package: python3-pylint-django Version: 2.0.11-1 Severity: wishlist As explained in #945426, pylint 2.4 has removed the unit tests from the package installation and the test functional classes have only been re-introduced in the package in pylint 2.5 so for now I'll disable the unit tests and

[Python-modules-team] Bug#936422: django-tables: Python2 removal in sid/bullseye

Hi Matthias, I was surprised to receive this mail as I thought that migration had already been done but it turns out that the doc package was still depending on python-doc instead of python3-doc. I'll upload the new version shortly. Thanks, Joseph

[Python-modules-team] Bug#934271: #934271: patch integrated!

Control: tags ! + pending Control: forwarded ! https://github.com/vinayak-mehta/tablib/pull/374 Hi Mathieu, Thanks for the report and sorry for the late reply. I've uploaded the latest version of python-tablib and included your patch. I also forwarded your patch to upstream to hopefully get it

[Python-modules-team] Bug#933921: src:python-tablib: Unsafe use of yaml.load()

Hi, Thanks Scott for the report. Tomas: the repository in Openstack was archived long ago because it was ported to https://salsa.debian.org/python-team/modules/python-tablib The module is used by other packages than openstack (like django-tables if I remember correctly), so could you please hold

[Python-modules-team] Bug#918340: pylint-django build depends on python3-factory-boy that is currently not in buster

FYI, the new version of factory-boy is on the ftp-master queue. This will solve itself in the next few days. I'll close it once the package reaches testing. Cheers, Joseph ___ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net

[Python-modules-team] Bug#918340: pylint-django build depends on python3-factory-boy that is currently not in buster

Hi Adrian, Thanks for the report. I was hoping to get a quick answer from https://github.com/FactoryBoy/factory_boy/issues/552 to push the new version of factory-boy without patching but I'll probably try to update the package and add the patch for python 3.7 that has been already merged so that

[Python-modules-team] Bug#910318: factory-boy: do you mind if I upload the new version and fix the FTBS?

Hi Brian, One of my packages needs factory-boy to be able to run properly (see #918340). Do you mind if I upload the latest version of factory-boy and add the subset of the relevant patch that fixes the compatibility with python 3.7? (the part about factory/utils.py in

[Python-modules-team] Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

Note that I'm having trouble with the latest release right now (see https://github.com/PyCQA/pylint-django/issues/215) so I won't upload it today. But I should be able to get that fixed shortly. ___ Python-modules-team mailing list

[Python-modules-team] Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

Control: tags -1 + fixed-upstream Reading through the changes of 2.0.1 to 2.0.5 of pylint-django, it seems that this change has already been dealt with in the latest version. See:

[Python-modules-team] Bug#917717: pylint-django: FTBFS: dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.7 returned exit code 13

Control: tags -1 - fixed Control: tags -1 + patch Hi guys, Thanks Lucas for the report. Sorry for the late reply, I was out of the country with very limited internet access. Thanks Emmanuel for the quick patch. Notes for next time: * Please use meaningful commit messages, especially when

[Python-modules-team] Bug#869194: awscli failing to upload empty files on => due to python-s3transfer

Control: reassign -1 python-s3transfer Control: forwarded -1 https://github.com/boto/s3transfer/pull/102 Reassigning this bug to python-s3transfer as it is the one that will be patch to support the missing argument. Upstream issues:

[Python-modules-team] Addition in lintian to warn about debian/pyversions file

Hi guys, FYI I am requesting a new lintian tag to warn about the presence of the debian/pyversions file as it is supposed to be obsolete since dh_python2 [1]. According to the policy[2], we are supposed to use the X-Python3-Version field in debian/control to specify the version now. Please let

Re: [Python-modules-team] Mass-commit fix of lintian ancient-python-version-field

Hi, On Fri, May 11, 2018 at 1:10 AM, Ondrej Novy wrote: > Are we sure it's completely safe to remove it globally? Also, it's written in the python policy to do so: https://wiki.debian.org/Python/Policy "Another note: if there is a debian/pycompat file, you must launch

Re: [Python-modules-team] Mass-commit fix of lintian ancient-python-version-field

Hi, On Fri, May 11, 2018, 1:10 AM Ondrej Novy wrote: > no problem, so just remove that file? > > > https://github.com/onovy/onovy-mass/commit/2c24adf1ecd8fc934328f69c75b2b2d9256ee3c9 > > Are we sure it's completely safe to remove it globally? > This file has been deprecated

Re: [Python-modules-team] Mass-commit fix of lintian ancient-python-version-field

On Thu, May 10, 2018 at 4:29 AM, Ondrej Novy wrote: > Removing Python 2 version: <= 2.7 (thus all) > Removing Python 3 version: <= 3.4 (older than jessie) > > Any objections? Thanks for doing that Ondřej, maybe we could delete the pycompat file when exists at the same time (in a

[Python-modules-team] Bug#896429: python*-django-tables2: django_tables2 fails to import => usage problem???

I just saw that that there was a discussin on #896429 (I was looking at #896396). > I wonder whether we can draw anything useful from these bugs before > closing them. > > For one thing, you cannot use autopkgtest-pkg-python on these modules as is. > So yeah, for django this may make sense, but

[Python-modules-team] Bug#896429: python*-django-tables2: django_tables2 fails to import => usage problem???

Control: severity -1 minor Control: tag -1 + moreinfo Hi The error message you posted seems pretty explicit: it seems you're missing some configuration apparently: django.core.exceptions.ImproperlyConfigured: Requested setting DEFAULT_INDEX_TABLESPACE, but settings are not