Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.python > #12222 > unrolled thread

Updating pip

Back to article view | Back to linux.debian.maint.python

Contents

  Updating pip Scott Kitterman <debian@kitterman.com> - 2020-01-24 20:10 +0100
    Re: Updating pip Matthias Klose <doko@debian.org> - 2020-01-24 20:30 +0100
    Re: Updating pip Håvard Flaget Aasen <haavard_aasen@yahoo.no> - 2020-01-24 21:00 +0100
    Re: Updating pip Scott Kitterman <debian@kitterman.com> - 2020-01-25 00:40 +0100
    Re: Updating pip "Diego M. Rodriguez" <diego@moreda.io> - 2020-01-25 13:40 +0100
    Re: Updating pip Fabrice BAUZAC-STEHLY <noon@mykolab.com> - 2020-01-26 23:10 +0100

#12222 — Updating pip

[Multipart message — attachments visible in raw view] — view raw

I started looking into updating pip to the current release because I knew it 
would take awhile and we need to do it at some point.  Merging our changes 
into the new upstream release turned out to be somewhat less challenging that 
I had feared (alternately it wasn't and I messed it up).  I've pushed the 
results of that effort to salsa.

The next step is to deal with all the packages that pip vendors and we 
unvendor.  There are quite a few packages that need updating to a sufficient 
version for the new pip:

Needs packaging:
pep517

Needs upgrade:
CacheControl
contextlib2
distro
ipaddress (python2 only)
msgpack
packaging
progress
pyparsing
pytoml
idna
urllib3

I'm not going to be able to deal with all that by myself, so this is a request 
for team members to step up and look at updating these packages.  I have not 
checked which of these are DPMT maintained, so in some cases the action may be 
to work with the maintainer to update their package.

I would suggest that people who decide to work on one of the above reply to 
this message so we don't end up with people doing duplicate works.

Thanks,

Scott K


Here's the full list:

appdirs==1.4.3 have 1.4.3
CacheControl==0.12.6 have 11.7.2
colorama==0.4.3 have 0.4.3
contextlib2==0.6.0 have 0.5.5
distlib==0.3.0 have 0.3.0
distro==1.4.0 have 1.3.0
html5lib==1.0.1 have 1.0.1
ipaddress==1.0.23 have 1.0.17  # Only needed on 2.6 and 2.7
msgpack==0.6.2 have 0.5.6
packaging==20.1 have 19.1.2
pep517==0.7.0 Missing (not packaged)
progress==1.5 have 1.2
pyparsing==2.4.6 have 2.4.2
pytoml==0.1.21 have 0.1.2
requests==2.22.0 have 2.22.0
certifi==2019.11.28 have 2019.11.28
chardet==3.0.4 have 3.0.4
idna==2.8 have 2.6
urllib3==1.25.7 have 1.25.6
retrying==1.3.3 have 1.3.3
setuptools==44.0.0 have 44.0.0
six==1.14.0 have 1.14.0
webencodings==0.5.1 have 0.5.1

[toc] | [next] | [standalone]

#12223

On 24.01.20 20:00, Scott Kitterman wrote:
> I started looking into updating pip to the current release

thanks for doing that.

> packaging

the recent version is in the archive but ftbfs.  it's a dh-python issue.

Matthias

[toc] | [prev] | [next] | [standalone]

#12224

> 
> I'm not going to be able to deal with all that by myself, so this is a request
> for team members to step up and look at updating these packages.  I have not
> checked which of these are DPMT maintained, so in some cases the action may be
> to work with the maintainer to update their package.
> 
> I would suggest that people who decide to work on one of the above reply to
> this message so we don't end up with people doing duplicate works.
> 

I can begin with distro and pyparsing.

H�vard

[toc] | [prev] | [next] | [standalone]

#12225

[Multipart message — attachments visible in raw view] — view raw

On Friday, January 24, 2020 2:00:36 PM EST Scott Kitterman wrote:
> The next step is to deal with all the packages that pip vendors and we
> unvendor.  There are quite a few packages that need updating to a sufficient
> version for the new pip:
> 
> Needs packaging:
> pep517

I am taking care of this.

...
> 
> I would suggest that people who decide to work on one of the above reply to
> this message so we don't end up with people doing duplicate works.

Scott K

[toc] | [prev] | [next] | [standalone]

#12226

[Multipart message — attachments visible in raw view] — view raw

On 1/24/20 8:00 PM, Scott Kitterman wrote:
> I would suggest that people who decide to work on one of the above reply to 
> this message so we don't end up with people doing duplicate works.

I can work on bumping "progress".

Best,
-- 
Diego M. Rodriguez

[toc] | [prev] | [next] | [standalone]

#12228

Hello,

Scott Kitterman writes:

> There are quite a few packages that need updating to a sufficient
> version for the new pip:
> [...]
> contextlib2

As you may know, I'm still a newbie in the Debian contribution world but
trying to learn.  I have worked to upgrade contextlib2, what do you
think:

Update the upstream branch:
https://salsa.debian.org/python-team/modules/contextlib2/merge_requests/2

Update the master branch:
https://salsa.debian.org/python-team/modules/contextlib2/merge_requests/3

As I'm not confident, I have created these two merge requests.  If you
believe I should do differently to submit such changes, I'd be happy to
learn!

Thanks!

Best regards

--
Fabrice BAUZAC-STEHLY
PGP 015AE9B25DCB0511D200A75DE5674DEA514C891D

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.python

csiph-web