FYI: The status of the python-dateutil source package
in Debian's testing distribution has changed.
Previous version: 2.8.1-3
Current version: 2.8.1-4
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
FYI: The status of the toolz source package
in Debian's testing distribution has changed.
Previous version: 0.9.0-1
Current version: 0.9.0-1.1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
FYI: The status of the python-dynaconf source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 2.2.3-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a
FYI: The status of the pyxdg source package
in Debian's testing distribution has changed.
Previous version: 0.26-1
Current version: 0.26-3
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
FYI: The status of the microsoft-authentication-extensions-for-python source
package
in Debian's testing distribution has changed.
Previous version: 0.1.3-3
Current version: 0.2.1-1
--
This email is automatically generated once a day. As the installation of
new packages into testing
FYI: The status of the flask source package
in Debian's testing distribution has changed.
Previous version: 1.1.1-2
Current version: 1.1.2-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will receive
FYI: The status of the python-structlog source package
in Debian's testing distribution has changed.
Previous version: 18.1.0-2
Current version: 20.1.0-1
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you
FYI: The status of the celery-batches source package
in Debian's testing distribution has changed.
Previous version: (not in testing)
Current version: 0.2-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
Hi Peter,
> vanguards on the other hand is an application which I assume relies on
> pytest for it's testsuite.
>
> So I guess the question is whether it is worth keeping this pile of
> pypy modules around to support the testsuite of one application?
I believe the following patch to
I do have something that might address this, but I'm reluctant to promise
anything until I test it.
Scott K
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
binary:python3-injector is NEW.
binary:python3-injector is NEW.
source:python-injector is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so
python-injector_0.18.3-1_amd64.changes uploaded successfully to localhost
along with the files:
python-injector_0.18.3-1.dsc
python-injector_0.18.3.orig.tar.gz
python-injector_0.18.3-1.debian.tar.xz
python-injector_0.18.3-1_amd64.buildinfo
python3-injector_0.18.3-1_all.deb
Greetings,
Thanks for looking into this, Scott!
> Maintaining symlink farms is inherently difficult and unreliable. Debian
> used
> to use a similar approach to support multiple python2 versions and it never
> worked well. I would be reluctant to use such an approach.
Ok, makes sense.
> I checked
Am 25.04.2020 um 22:10 teilte Paul Gevers mit:
Hi Paul,
> With recent uploads of texlive-base and texlive-extra the autopkgtest of
> jupyter-sphinx-theme fails in testing when that autopkgtest is run with
> the binary packages of texlive-base and texlive-extra from unstable. It
> passes when run
binary:python3-rx is NEW.
binary:python3-rx is NEW.
source:python-rx is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.
python-rx_3.1.0-1_amd64.changes uploaded successfully to localhost
along with the files:
python-rx_3.1.0-1.dsc
python-rx_3.1.0.orig.tar.gz
python-rx_3.1.0-1.debian.tar.xz
python-rx_3.1.0-1_amd64.buildinfo
python3-rx_3.1.0-1_all.deb
Greetings,
Your Debian queue daemon (running
Source: texlive-base, jupyter-sphinx-theme, texlive-extra
Control: found -1 texlive-base/2020.20200417-1
Control: found -1 texlive-extra/2020.20200417-1
Control: found -1 jupyter-sphinx-theme/0.0.6+ds1-9
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User:
Processing control commands:
> found -1 texlive-base/2020.20200417-1
Bug #958852 [src:texlive-base, src:jupyter-sphinx-theme, src:texlive-extra]
texlive-base/extra breaks jupyter-sphinx-theme autopkgtest: Builder name pickle
not registered or available through entry point
Marked as found in
Package: pytest
Version: 4.6.9-3
x-debbugs-cc: vangua...@packages.debian.org
As discussed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937769 the
maintainer of the python-funcsigs source package (which builds the
python-funcsigs, python3-funcsigs and pypy-funcsigs binary packages)
On 21/04/2020 22:20, Thomas Goirand wrote:
So, if I'm following correctly, what you seem to propose, is to remove
Python 2 from unittest2. If that's the case, then I agree with such a
plan. I just didn't dare to do it yet.
Yes, whichever approach is taken to dealing with funcsigs, unittest2
Your message dated Sat, 25 Apr 2020 17:48:57 +
with message-id
and subject line Bug#958827: fixed in setuptools-scm 3.4.3+really3.3.3-4
has caused the Debian Bug report #958827,
regarding setuptools-scm: autopkgtest failure.
to be marked as done.
This means that you claim that the problem
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 25 Apr 2020 13:24:15 -0400
Source: setuptools-scm
Architecture: source
Version: 3.4.3+really3.3.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Sandro Tosi
Closes:
setuptools-scm_3.4.3+really3.3.3-4_source.changes uploaded successfully to
localhost
along with the files:
setuptools-scm_3.4.3+really3.3.3-4.dsc
setuptools-scm_3.4.3+really3.3.3-4.debian.tar.xz
setuptools-scm_3.4.3+really3.3.3-4_amd64.buildinfo
Greetings,
Your Debian queue daemon
Processing control commands:
> tag -1 pending
Bug #958827 [src:setuptools-scm] setuptools-scm: autopkgtest failure.
Added tag(s) pending.
--
958827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: setuptools-scm
Version: 3.4.3+really3.3.3-3
x-debbugs-cc: mo...@debian.org
The setuptools-scm autopkgtest is failing with.
badpkg: debian/tests/testsuite does not exist
autopkgtest [19:02:59]: ERROR: erroneous package: debian/tests/testsuite does
not exist
This is preventing the new
Source-only uploads to NEW are not allowed.
binary:python3-jsonrpc-server is NEW.
source:python-jsonrpc-server is NEW.
===
Please feel free to respond to this email if you don't understand why
your files were rejected, or if you upload new files which address our
concerns.
DELAYED/1-day/python-jsonrpc-server_0.3.4-1_amd64.changes is already present on
target host:
python-jsonrpc-server_0.3.4-1_amd64.buildinfo
Either you already uploaded it, or someone else came first.
Job python-jsonrpc-server_0.3.4-1_amd64.changes removed.
Greetings,
Your Debian queue
python-jsonrpc-server_0.3.4-1_source.changes uploaded successfully to localhost
along with the files:
python-jsonrpc-server_0.3.4-1.dsc
python-jsonrpc-server_0.3.4.orig.tar.gz
python-jsonrpc-server_0.3.4-1.debian.tar.xz
python-jsonrpc-server_0.3.4-1_amd64.buildinfo
Greetings,
Processing commands for cont...@bugs.debian.org:
> notfound 958816 python-pip/20.0.2-5
Bug #958816 [python3-pip] "pipx makes unsupported use of pip internals"
No longer marked as found in versions python-pip/20.0.2-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Processing commands for cont...@bugs.debian.org:
> reassign 958816 pipx
Bug #958816 [python3-pip] "pipx makes unsupported use of pip internals"
Bug reassigned from package 'python3-pip' to 'pipx'.
Ignoring request to alter found versions of bug #958816 to the same values
previously set
Ignoring
Processing commands for cont...@bugs.debian.org:
> clone 958764 -1
Bug #958764 {Done: Scott Kitterman } [python3-pip]
python3-pip: debundled _vendor packaging approach breaks usage of pip in
environments
Bug 958764 cloned as bug 958816
> reopen -1
Bug #958816 {Done: Scott Kitterman }
Your message dated Sat, 25 Apr 2020 10:34:02 -0400
with message-id <58839866.iLgyPFC6jr@sk-desktop>
and subject line re: python3-pip: debundled _vendor packaging approach breaks
usage of pip in environments
has caused the Debian Bug report #958764,
regarding python3-pip: debundled _vendor
Hi Sandro,
pypy-hypothesis was not removed. I am preparing a new upstream release
to close ##949762, and fail for pypy.
I will push the drop pypy support to salsa.
Could you review it, please?
Cheers,
Emmanuel
___
Python-modules-team mailing list
Hi Emanuel,
On Sat, 25 Jan 2020 08:59:00 -0300 Emmanuel Arias wrote:
> Hypothesis from >= 5.0.0 version drop Python 2 support. So, I think we
> should wait on Debian until
> python-hypothesis remove the Python2 support.
Since there is no more a Python2 package for hyptothesis, could I ask to
Package: python3-pip
Version: 20.0.2-5
Severity: normal
Dear Maintainer,
Some tools that use pip rely on being able to use it by adding its installed
location to the path of their environments.
One example is pipx.
$ pip3 --version
pip 20.0.2 from /usr/lib/python3/dist-packages/pip (python
35 matches
Mail list logo
