[Python-modules-team] python-dateutil 2.8.1-4 MIGRATED to testing

2020-04-25 Thread Debian testing watch 
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 will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] toolz 0.9.0-1.1 MIGRATED to testing

2020-04-25 Thread Debian testing watch 
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 receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] python-dynaconf 2.2.3-2 MIGRATED to testing

2020-04-25 Thread Debian testing watch 
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 day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] pyxdg 0.26-3 MIGRATED to testing

2020-04-25 Thread Debian testing watch 
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
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] microsoft-authentication-extensions-for-python 0.2.1-1 MIGRATED to testing

2020-04-25 Thread Debian testing watch 
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 happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] flask 1.1.2-1 MIGRATED to testing

2020-04-25 Thread Debian testing watch 
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
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] python-structlog 20.1.0-1 MIGRATED to testing

2020-04-25 Thread Debian testing watch 
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 will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] celery-batches 0.2-2 MIGRATED to testing

2020-04-25 Thread Debian testing watch 
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 you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958848: [Pkg-privacy-maintainers] Bug#958848: pytest (build-)depends on pypy-funcsigs which the maintainer would like to get rid of.

2020-04-25 Thread Chris Lamb 
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 src:vanguards can be used to use the
Python 3.x testsuite instead:

--- a/debian/control
+++ b/debian/control
@@ -8,8 +8,9 @@ Build-Depends: debhelper (>= 11),
dh-python,
pypy,
pypy-setuptools,
+  python3-pytest ,
+  python3-stem ,
pypy-stem (>= 1.6.0-3.1),
-   pypy-pytest,
pypy-ipaddress
 Standards-Version: 4.1.5
 Vcs-Browser: https://salsa.debian.org/pkg-privacy-team/vanguards

--- a/debian/rules
+++ b/debian/rules
@@ -5,3 +5,6 @@
 
 override_dh_installsystemd:
dh_installsystemd --no-enable --no-start
+
+override_dh_auto_test:
+   dh_auto_test -- --system=custom --test-args='cd {build_dir}; python3 -m 
pytest $(CURDIR)/tests'

… but I'm not sure the "python3" in the dh_auto_test line is right.
"{interpreter}" there is replaced with pypy). This also assumes that
running PyPy at runtime will have identical behaviour as Python 3.x.

Enjoy...


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958764: Bug#958764: closed by Scott Kitterman (re: python3-pip: debundled _vendor packaging approach breaks usage of pip in environments)

2020-04-25 Thread Scott Kitterman 
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
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] python-injector_0.18.3-1_amd64.changes is NEW

2020-04-25 Thread Debian FTP Masters 
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 please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processing of python-injector_0.18.3-1_amd64.changes

2020-04-25 Thread Debian FTP Masters 
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,

Your Debian queue daemon (running on host usper.debian.org)

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958764: closed by Scott Kitterman (re: python3-pip: debundled _vendor packaging approach breaks usage of pip in environments)

2020-04-25 Thread Paul Ivanov 
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 with a pip upstream developer on IRC and his view is that what pipx 
> is doing is not supported by upstream:
>
> >  dstufft: If an program external to pip tries to use one of pip's
> > vendored libraries directsly (e.g. from pip._vendor.six import iteritems)
> > this won't work on Debian because we don't put the wheels in the pip
> > package tree (they are in /usr/share/python-wheels).  From your point of
> > view upstream, if another package is doing such a thing are they
> > unreasonably mucking about in pip internals and if it breaks it's their
> > problem or is it something reasonable that they should be able to rely on
> > and we should try to support?
> >  ScottK: upstrem does not support people importing pip internals
> > /vendored libs 
> >  we moved *everything* into a _ directory just to make this obvious

Pipx is not importing pip internals. Pipx is simply using pip.
The way pipx is doing this is by adding the site-packages of a
working pip installation in it's ~/.local/pipx/shared folder to
the sys.path of the environments that it manages in various
~/.local/pipx/venvs folders

Pipx is trying to save from having a copy of pip in each of its
venvs. This works if the pip on the path is the  wheel as
published on PyPI, or as the vendored code with the debundled
wheels in the  pip/_vendor directory, with the debundled wheels
in the pip/_vendor directory. But this does not work with the
logic patched in Debian's packaging that points the debundled
wheels to the sys.prefix + "/share/python-wheels" , because the
sys.prefix for each of the venvs is different and will not have
copies of the vendored code.

So the question to follow up with Donald and PyPA folks is
something like: "should pip be usable by adding the site packages
of a working installation to the sys.path of another
environment?" And similarly, "should a repackaged pip wheel work
standalone" - because the pip wheel in /usr/share/python-wheels
cannot be used the same way as a regular pip wheel, it is not
standalone, and it requires making the debundled wheels which are
assumed to be on the sys.prefix + share/python-wheels

> It may be that this pipx bug is only apparent on Debian and its derivatives 
> because we rely on the pip unbundle logic, but what pipx is doing is 
> unsupported upstream, so I don't think we can support it either.

Again, I believe it's the additional modification to the unbundle
logic, namely that the vendored wheels will be in sys.prefix +
share/python-wheels directory *instead* of the pip/_vendor
directory that is causing this behaviour.

> Sorry I didn't have a more positive answer.

I appreciate that, thank you for your time and efforts.

best,
pi

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958852: texlive-base/extra breaks jupyter-sphinx-theme autopkgtest: Builder name pickle not registered or available through entry point

2020-04-25 Thread Hilmar Preuße 
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 with only packages from testing. In tabular form:
> 
I'm not 100% sure if it is the fault of TL 2020. Please note that at the
same time sphinx 2.4.3 was uploaded. And you'll notice that the last
successful run was w/ sphinx 1.8.5, meanwhile it fails w/ sphinx 2.4.3.

Hence I suspect an incompatibility of jupyter-sphinx-theme & sphinx,
which is quite unrelated to TeX Live.

Hilmar
-- 
sigfault
#206401 http://counter.li.org



signature.asc
Description: OpenPGP digital signature
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] python-rx_3.1.0-1_amd64.changes is NEW

2020-04-25 Thread Debian FTP Masters 
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.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html
 or https://ftp-master.debian.org/backports-new.html for *-backports

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processing of python-rx_3.1.0-1_amd64.changes

2020-04-25 Thread Debian FTP Masters 
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 on host usper.debian.org)

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958852: texlive-base/extra breaks jupyter-sphinx-theme autopkgtest: Builder name pickle not registered or available through entry point

2020-04-25 Thread Paul Gevers 
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: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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 with only packages from testing. In tabular form:

   passfail
texlive-base   from testing2020.20200417-1
texlive-extra  from testing2020.20200417-1
jupyter-sphinx-theme   from testing0.0.6+ds1-9
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of texlive-base and
texlive-extra to testing [1]. Due to the nature of this issue, I filed
this bug report against all three packages. Can you please investigate
the situation and reassign the bug to the right package?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
texlive-base/2020.20200417-1. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=texlive-base

https://ci.debian.net/data/autopkgtest/testing/amd64/j/jupyter-sphinx-theme/5144210/log.gz

* pickle *
make -C demo pickle BUILDDIR=build/build-pickle
make[1]: Entering directory
'/tmp/autopkgtest-lxc.c4x56q58/downtmp/autopkgtest_tmp/examples/demo'
sphinx-build -b pickle -d build/build-pickle/doctrees   source
build/build-pickle/pickle
Running Sphinx v2.4.3

Sphinx error:
Builder name pickle not registered or available through entry point
make[1]: *** [Makefile:64: pickle] Error 2
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.c4x56q58/downtmp/autopkgtest_tmp/examples/demo'
make: *** [Makefile:51: build-demo] Error 2
autopkgtest [19:21:54]: test perform-demo: ---]



signature.asc
Description: OpenPGP digital signature
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processed: texlive-base/extra breaks jupyter-sphinx-theme autopkgtest: Builder name pickle not registered or available through entry point

2020-04-25 Thread Debian Bug Tracking System 
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 versions texlive-base/2020.20200417-1.
> found -1 texlive-extra/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 versions texlive-extra/2020.20200417-1.
> found -1 jupyter-sphinx-theme/0.0.6+ds1-9
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 versions jupyter-sphinx-theme/0.0.6+ds1-9.

-- 
958852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958852
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958848: pytest (build-)depends on pypy-funcsigs which the maintainer would like to get rid of.

2020-04-25 Thread peter green 

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) would like 
to get rid of the python-funcsigs source package completely rather than simply 
removing cpython 2 support from it.

pypy-pytest depends on and the pytest source package build-depends on the 
pypy-funcsigs package. I am assuming that removing the dependency on this 
package would mean dropping the pypy-pytest binary package.

checking reverse dependencies with dak reveals.

# Broken Build-Depends:
python-atomicwrites: pypy-pytest
python-pluggy: pypy-pytest
python-py: pypy-pytest
setuptools-scm: pypy-pytest
vanguards: pypy-pytest
wcwidth: pypy-pytest

most of these seem to be python module packages that are maintained by the 
python modules team and build pypy modules to directly or indirectly support 
pypy-pytest.

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?

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#938756: Bug#937769: getting python-linecache2/python-traceback2 fixes into testing (FAO traceback2, funcsigs nipype and numba maintainers).

2020-04-25 Thread peter green 

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 will need 
to drop it's python2 packages.

Though in fact, I already worked on that, but stopped, also because
unittest2 FTBFS when I try building it on my laptop. So I've pushed it
in its normal Git repo [1] under a py2-removal branch. If anyone has
some time available to look at it, that'd be nice (I currently don't...).

It appears that this was fixed in a NMU, but the NMU changes were never 
imported into the packaging repository, once I imported the NMU changes the 
package built fine here.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958827: marked as done (setuptools-scm: autopkgtest failure.)

2020-04-25 Thread Debian Bug Tracking System 
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 has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
958827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958827
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

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 setuptools-scm from migrating to testing (where it 
is needed to fix an uninstallable build-dependencies issue).

I think Sandro removed the wrong file, he should have removed 
debian/tests/testsuite2 but actually removed debian/tests/testsuite.

--- End Message ---
--- Begin Message ---
Source: setuptools-scm
Source-Version: 3.4.3+really3.3.3-4
Done: Sandro Tosi 

We believe that the bug you reported is fixed in the latest version of
setuptools-scm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 958...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated setuptools-scm package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-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: 958827
Changes:
 setuptools-scm (3.4.3+really3.3.3-4) unstable; urgency=medium
 .
   * debian/tests
 - remove testsuite2, restore testsuite, fixes a failure with autopkgtest;
   Closes: #958827
Checksums-Sha1:
 aff2b31ddb5c0aae388b2bdac796df8dbadee4f8 2586 
setuptools-scm_3.4.3+really3.3.3-4.dsc
 e7c4e48ba9549a0d5373abb24b9ced6d27bc2849 5240 
setuptools-scm_3.4.3+really3.3.3-4.debian.tar.xz
 dd4d099beacd9172be7acbc8a7aac8698ddb645d 10517 
setuptools-scm_3.4.3+really3.3.3-4_amd64.buildinfo
Checksums-Sha256:
 5495f8b4613fafdda6bcc58f4605ab62f5dee59242768ce70a48065e3a2d9147 2586 
setuptools-scm_3.4.3+really3.3.3-4.dsc
 a1ee3def513d3f3077410814b8ac117960c8032b09c9c0616bee9d3ff2c582d5 5240 
setuptools-scm_3.4.3+really3.3.3-4.debian.tar.xz
 3457cec914f3bae7acfd6a734f9b32910e91f88133f6f641d25f01d77f54d6cc 10517 
setuptools-scm_3.4.3+really3.3.3-4_amd64.buildinfo
Files:
 612b75934caf801befbf133b2fcef6c9 2586 python optional 
setuptools-scm_3.4.3+really3.3.3-4.dsc
 998113128662ac680df4ec0b56756b0b 5240 python optional 
setuptools-scm_3.4.3+really3.3.3-4.debian.tar.xz
 9d7986d72de8c1b472d79fd121d67e5d 10517 python optional 
setuptools-scm_3.4.3+really3.3.3-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl6kdT8ACgkQh588mTgB
qU/vvA/+OlySP2tDwse7vSFt2l2kjjU0TlP1/85y2ARzRZ9H9KM5amOA6CYw1Q8P
gQqLBi1DH6YJLdITxRX5IzlHBUqcF9ZookmiJx0mhLq7xDMvv0YNYYzMBs+3jhTM
8cf612x2FxOVyMcpVmylDtiKycMsG8SfMQHBkbDJvfQF8FkYz2Zjv1kuPCkZcaia
2L16bL3xDGHdYvu6YXQvNlyC1EQvAm8m45t5WVR8KWdCwP75b6V8dGgqSzHCFp7c
KlKG+qId+Kzw/y8i89Nl/ttKxpKKlnLIXgffBdFqeZSEb5PB3ih4OyG4GAeSNpwK
5kEv5kiLE7oS1t4rG1xdVIQ6/zf8iUj4okyWPUVyEjQdnhwKJD1+cxK0Y5tsBe78
k6r2c7vw5DuyAZfrVGTgClXbLFm9Pk/tHHrDLLWMvnkx9dSb9QSxcKYyBoSHcLEe
ui2/vHUb6pQ6njZ3MqElymyEstlDCl9T7Iwj8TboKCReJkRJCygGk2j3Vmc1PwyQ
nn39TwanTG0tI7WlJU838x+jt4vINsElO8+Q6ZwzLEYa1tbq0qQNpA17NJHxpYc8
frfIhdfo/Jn5EzZEQLQTELSuT6wB0sxIZ5s9d+7S1TIEFIHnxdHOi75vNxvH8Iyj
RgPo/7m1L2VpiwFhGmEGGUlYIoaY+Dcb1T1++QLCSq/PKQGr53U=
=UftL
-END PGP SIGNATURE End Message ---
___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] setuptools-scm_3.4.3+really3.3.3-4_source.changes ACCEPTED into unstable

2020-04-25 Thread Debian FTP Masters 


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: 958827
Changes:
 setuptools-scm (3.4.3+really3.3.3-4) unstable; urgency=medium
 .
   * debian/tests
 - remove testsuite2, restore testsuite, fixes a failure with autopkgtest;
   Closes: #958827
Checksums-Sha1:
 aff2b31ddb5c0aae388b2bdac796df8dbadee4f8 2586 
setuptools-scm_3.4.3+really3.3.3-4.dsc
 e7c4e48ba9549a0d5373abb24b9ced6d27bc2849 5240 
setuptools-scm_3.4.3+really3.3.3-4.debian.tar.xz
 dd4d099beacd9172be7acbc8a7aac8698ddb645d 10517 
setuptools-scm_3.4.3+really3.3.3-4_amd64.buildinfo
Checksums-Sha256:
 5495f8b4613fafdda6bcc58f4605ab62f5dee59242768ce70a48065e3a2d9147 2586 
setuptools-scm_3.4.3+really3.3.3-4.dsc
 a1ee3def513d3f3077410814b8ac117960c8032b09c9c0616bee9d3ff2c582d5 5240 
setuptools-scm_3.4.3+really3.3.3-4.debian.tar.xz
 3457cec914f3bae7acfd6a734f9b32910e91f88133f6f641d25f01d77f54d6cc 10517 
setuptools-scm_3.4.3+really3.3.3-4_amd64.buildinfo
Files:
 612b75934caf801befbf133b2fcef6c9 2586 python optional 
setuptools-scm_3.4.3+really3.3.3-4.dsc
 998113128662ac680df4ec0b56756b0b 5240 python optional 
setuptools-scm_3.4.3+really3.3.3-4.debian.tar.xz
 9d7986d72de8c1b472d79fd121d67e5d 10517 python optional 
setuptools-scm_3.4.3+really3.3.3-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl6kdT8ACgkQh588mTgB
qU/vvA/+OlySP2tDwse7vSFt2l2kjjU0TlP1/85y2ARzRZ9H9KM5amOA6CYw1Q8P
gQqLBi1DH6YJLdITxRX5IzlHBUqcF9ZookmiJx0mhLq7xDMvv0YNYYzMBs+3jhTM
8cf612x2FxOVyMcpVmylDtiKycMsG8SfMQHBkbDJvfQF8FkYz2Zjv1kuPCkZcaia
2L16bL3xDGHdYvu6YXQvNlyC1EQvAm8m45t5WVR8KWdCwP75b6V8dGgqSzHCFp7c
KlKG+qId+Kzw/y8i89Nl/ttKxpKKlnLIXgffBdFqeZSEb5PB3ih4OyG4GAeSNpwK
5kEv5kiLE7oS1t4rG1xdVIQ6/zf8iUj4okyWPUVyEjQdnhwKJD1+cxK0Y5tsBe78
k6r2c7vw5DuyAZfrVGTgClXbLFm9Pk/tHHrDLLWMvnkx9dSb9QSxcKYyBoSHcLEe
ui2/vHUb6pQ6njZ3MqElymyEstlDCl9T7Iwj8TboKCReJkRJCygGk2j3Vmc1PwyQ
nn39TwanTG0tI7WlJU838x+jt4vINsElO8+Q6ZwzLEYa1tbq0qQNpA17NJHxpYc8
frfIhdfo/Jn5EzZEQLQTELSuT6wB0sxIZ5s9d+7S1TIEFIHnxdHOi75vNxvH8Iyj
RgPo/7m1L2VpiwFhGmEGGUlYIoaY+Dcb1T1++QLCSq/PKQGr53U=
=UftL
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processing of setuptools-scm_3.4.3+really3.3.3-4_source.changes

2020-04-25 Thread Debian FTP Masters 
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 (running on host usper.debian.org)

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processed: Bug#958827 marked as pending in setuptools-scm

2020-04-25 Thread Debian Bug Tracking System 
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

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958827: setuptools-scm: autopkgtest failure.

2020-04-25 Thread peter green 

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 setuptools-scm from migrating to testing (where it 
is needed to fix an uninstallable build-dependencies issue).

I think Sandro removed the wrong file, he should have removed 
debian/tests/testsuite2 but actually removed debian/tests/testsuite.

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] python-jsonrpc-server_0.3.4-1_source.changes REJECTED

2020-04-25 Thread Debian FTP Masters 


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.


___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processing of python-jsonrpc-server_0.3.4-1_amd64.changes

2020-04-25 Thread Debian FTP Masters 
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 daemon (running on host usper.debian.org)

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processing of python-jsonrpc-server_0.3.4-1_source.changes

2020-04-25 Thread Debian FTP Masters 
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,

Your Debian queue daemon (running on host usper.debian.org)

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processed: notfound 958816 in python-pip/20.0.2-5

2020-04-25 Thread Debian Bug Tracking System 
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.
-- 
958816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processed: reassign 958816 to pipx

2020-04-25 Thread Debian Bug Tracking System 
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 request to alter fixed versions of bug #958816 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
958816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Processed: cloning 958764

2020-04-25 Thread Debian Bug Tracking System 
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 } [python3-pip] 
python3-pip: debundled _vendor packaging approach breaks usage of pip in 
environments
Bug reopened
Ignoring request to alter fixed versions of bug #958816 to the same values 
previously set
> retitle -1 "pipx makes unsupported use of pip internals"
Bug #958816 [python3-pip] python3-pip: debundled _vendor packaging approach 
breaks usage of pip in environments
Changed Bug title to '"pipx makes unsupported use of pip internals"' from 
'python3-pip: debundled _vendor packaging approach breaks usage of pip in 
environments'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
958764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958764
958816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958764: marked as done (python3-pip: debundled _vendor packaging approach breaks usage of pip in environments)

2020-04-25 Thread Debian Bug Tracking System 
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 packaging approach breaks usage of pip 
in environments
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
958764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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 3.8)

$ pip3 install pipx
...succeeds

$ export PATH=~/.local/bin:$PATH
$ pipx --version
0.15.1.3

$ pipx install cowsay
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 193, in _run_module_as_main
return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 86, in _run_code
exec(code, run_globals)
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/__main__.py", line 16, in 
from pip._internal.cli.main import main as _main  # isort:skip # noqa
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/cli/main.py", line 10, in 
from pip._internal.cli.autocompletion import autocomplete
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/cli/autocompletion.py", line 9, in 
from pip._internal.cli.main_parser import create_main_parser
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/cli/main_parser.py", line 7, in 
from pip._internal.cli import cmdoptions
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/cli/cmdoptions.py", line 24, in 
from pip._internal.exceptions import CommandError
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/exceptions.py", line 10, in 
from pip._vendor.six import iteritems
ModuleNotFoundError: No module named 'pip._vendor.six'


This was raised in a pipx issue [0] and in investigating it, I tracked it
down to the DEBUNDLE logic that gets patched to point to the python-wheels
folder.

Whereas with pip's code upstream (both vendored and debundled), adding the
site-packages folder containing a working version of pip will result in a being
able to use pip, this is not the case for Debian.

For pip as it is currently packaged in Debian, one has to also include all of
the wheels that get added to the path after importing pip._vendor. See an
example of such an approach in [1].

Would it be possible to keep the expected functionality provided by pip as
released upstream, perhaps by symlinking the wheels into the pip._vendor
directory?


0. https://github.com/pipxproject/pipx/issues/386
1. https://github.com/pipxproject/pipx/pull/388

best,
pi



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-pip depends on:
ii  ca-certificates 20190110
ii  python-pip-whl  20.0.2-5
ii  python3 3.8.2-3
ii  python3-distutils   3.8.2-2
ii  python3-setuptools  45.2.0-1
ii  python3-wheel   0.34.2-1

Versions of packages python3-pip recommends:
ii  build-essential  12.8
ii  python3-dev  3.8.2-3

python3-pip suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 24 Apr 2020 23:37:13 -0700 Paul Ivanov  wrote:
> 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.
...
> 
> from pip._vendor.six import iteritems
> ModuleNotFoundError: No module named 'pip._vendor.six'
> 
> 
> This was raised in a pipx issue [0] and in investigating it, I tracked it
> down to the DEBUNDLE logic that gets patched to point to the python-wheels
> folder.
> 
> Whereas with pip's code upstream (both vendored and debundled), adding the
> site-packages folder containing

[Python-modules-team] Bug#937823: python-hypothesis: Python2 removal in sid/bullseye

2020-04-25 Thread Emmanuel Arias 
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
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#949762: Please update hypothesis package to >= 5.1

2020-04-25 Thread Ole Streicher 
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
upgrade to 5.1 now? This starts to block upgrading the whole astropy
chain now.

Thanks

Ole

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team

[Python-modules-team] Bug#958764: python3-pip: debundled _vendor packaging approach breaks usage of pip in environments

2020-04-25 Thread Paul Ivanov 
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 3.8)

$ pip3 install pipx
...succeeds

$ export PATH=~/.local/bin:$PATH
$ pipx --version
0.15.1.3

$ pipx install cowsay
Traceback (most recent call last):
  File "/usr/lib/python3.8/runpy.py", line 193, in _run_module_as_main
return _run_code(code, main_globals, None,
  File "/usr/lib/python3.8/runpy.py", line 86, in _run_code
exec(code, run_globals)
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/__main__.py", line 16, in 
from pip._internal.cli.main import main as _main  # isort:skip # noqa
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/cli/main.py", line 10, in 
from pip._internal.cli.autocompletion import autocomplete
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/cli/autocompletion.py", line 9, in 
from pip._internal.cli.main_parser import create_main_parser
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/cli/main_parser.py", line 7, in 
from pip._internal.cli import cmdoptions
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/cli/cmdoptions.py", line 24, in 
from pip._internal.exceptions import CommandError
  File "/home/dummy/.local/pipx/shared/lib/python3.8/site-
packages/pip/_internal/exceptions.py", line 10, in 
from pip._vendor.six import iteritems
ModuleNotFoundError: No module named 'pip._vendor.six'


This was raised in a pipx issue [0] and in investigating it, I tracked it
down to the DEBUNDLE logic that gets patched to point to the python-wheels
folder.

Whereas with pip's code upstream (both vendored and debundled), adding the
site-packages folder containing a working version of pip will result in a being
able to use pip, this is not the case for Debian.

For pip as it is currently packaged in Debian, one has to also include all of
the wheels that get added to the path after importing pip._vendor. See an
example of such an approach in [1].

Would it be possible to keep the expected functionality provided by pip as
released upstream, perhaps by symlinking the wheels into the pip._vendor
directory?


0. https://github.com/pipxproject/pipx/issues/386
1. https://github.com/pipxproject/pipx/pull/388

best,
pi



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-pip depends on:
ii  ca-certificates 20190110
ii  python-pip-whl  20.0.2-5
ii  python3 3.8.2-3
ii  python3-distutils   3.8.2-2
ii  python3-setuptools  45.2.0-1
ii  python3-wheel   0.34.2-1

Versions of packages python3-pip recommends:
ii  build-essential  12.8
ii  python3-dev  3.8.2-3

python3-pip suggests no packages.

-- no debconf information

___
Python-modules-team mailing list
Python-modules-team@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team