Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #12546
| Path | csiph.com!3.eu.feeder.erje.net!feeder.erje.net!news.albasani.net!tahina.priv.at!bofh.it!news.nic.it!robomod |
|---|---|
| From | Stefano Rivera <stefanor@debian.org> |
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Python Wheel Related Policy Change |
| Date | Thu, 30 Apr 2020 23:50:02 +0200 |
| Message-ID | <A1pea-38B-5@gated-at.bofh.it> (permalink) |
| References | <A183E-11c-5@gated-at.bofh.it> <A1kev-a3-37@gated-at.bofh.it> <A1mgi-1nf-23@gated-at.bofh.it> <A1o8q-2w2-7@gated-at.bofh.it> |
| X-Original-To | Scott Kitterman <debian@kitterman.com> |
| X-Mailbox-Line | From debian-python-request@lists.debian.org Thu Apr 30 21:49:33 2020 |
| Old-Return-Path | <stefano@rivera.za.net> |
| X-Amavis-Spam-Status | No, score=-6.252 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, CAPINIT=0.5, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FOURLA=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no |
| X-Policyd-Weight | using cached result; rate: -4.6 |
| Dkim-Signature | v=1; a=ed25519-sha256; c=relaxed/simple; d=debian.org; i=@debian.org; q=dns/txt; s=satie-ed25519.stefanor.user; t=1588283360; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : content-transfer-encoding : in-reply-to : from; bh=NQgwOLnWag0S5X9hT5eg8xQn/c86HeQVxu5QgARASf8=; b=aGsZPJZPkzo/ybKlPhnPX5bCpmZruxmUc4f4QUzTGuVsaqmQZxYElp++OMFhWrIL3QeAc MtO8JUajJQKyr4GCw== |
| Dkim-Signature | v=1; a=rsa-sha256; c=relaxed/simple; d=debian.org; i=@debian.org; q=dns/txt; s=satie-rsa.stefanor.user; t=1588283360; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : content-transfer-encoding : in-reply-to : from; bh=NQgwOLnWag0S5X9hT5eg8xQn/c86HeQVxu5QgARASf8=; b=CkxUjRSvmwgOWmSoTH0ytmY6TalRc008V7m+InGnW2oYQdzfIBQcHgBxdBq3YcbiE4tVf jNGWEZULU9SoEqxJ58ednhG9oLGal/csESmtJjAN4KlZt+/z7JTOpPxTPHfSyjoQehbiwWY OE+FZJFqUshgLFgIb8ddu4M1cRHUYNB/DNvum236jyKdRN5TL5s6sBD9VdKq6uJgdItzA2B UazZwGzU4xWzxN3iU4HdpNW22EZ9JzpjL2EQee2huooVLSCDpcV1OSNM5k6+7H1h1V7ywzX EN9bSumRguJDWA9wzWhYYolpXyAa73MyHjoXBnXOo+B8LS2nxbAZoBtKPgig== |
| Mail-Followup-To | Scott Kitterman <debian@kitterman.com>, debian-python@lists.debian.org |
| MIME-Version | 1.0 |
| Content-Type | text/plain; charset=utf-8 |
| Content-Disposition | inline |
| Content-Transfer-Encoding | quoted-printable |
| X-Gpg-Public-Key | http://www.rivera.za.net/stefano.gpg |
| User-Agent | NeoMutt/20180716 |
| X-Mailing-List | <debian-python@lists.debian.org> archive/latest/18230 |
| List-ID | <debian-python.lists.debian.org> |
| List-URL | <https://lists.debian.org/debian-python/> |
| List-Archive | https://lists.debian.org/msgid-search/20200430214920.2wvyzpl6htsxaeop@satie.tumbleweed.org.za |
| Approved | robomod@news.nic.it |
| Lines | 85 |
| Organization | linux.* mail to news gateway |
| Sender | robomod@news.nic.it |
| X-Original-Cc | debian-python@lists.debian.org |
| X-Original-Date | Thu, 30 Apr 2020 21:49:20 +0000 |
| X-Original-Message-ID | <20200430214920.2wvyzpl6htsxaeop@satie.tumbleweed.org.za> |
| X-Original-References | <2045632.ZOD33WiUoI@sk-desktop> <7982820.PtiXLErMFD@sk-desktop> <20200430183223.g72jzsvaqd32etae@satie.tumbleweed.org.za> <13020274.iKOWmRv0R3@sk-desktop> |
| Xref | csiph.com linux.debian.maint.python:12546 |
Show key headers only | View raw
Hi Scott (2020.04.30_20:33:59_+0000) > > That seems reasonable, although if we're going down that road, it > > probably makes no sense for any of them to be universal. > > If we were talking about maintaining this for multiple release cycles with > lots of version divergence, I would agree. Let's not do more than we have to > until python2 is gone (whether it is before bullseye or after). I suspect pypy (2.7) will probably be around post-bullseye, unless somebody funds pypy to migrate rpython to python 3. But yeah, we can change strategy later, if appropriate. > As a result, one could add some kind of py2 flag to dirtbike to tell it to look > in /usr/lib/python2.7/dist-packages and make a 'universal' wheel from there. > It could then rename the files from py2.py3-none-any.whl to py2-none-any.whl. > The bonus Tag in the WHEEL file shouldn't hurt anything. > > They key is I think we can do this without actually running python2, we just > need to be able to install python-setuptools/pkg-resources. That should be > supportable ~as long as python2.7 is in the archive. Yep, that sounds good. > Agreed. As long as pip supports python2, we should try. Worst case we can > tell people to find their own interpreter and do a --download install with > setuptools pinned to 44.0.0 (that approach doesn't need ipaddr because they'll > get the upstream pip in the virtualenv too. When we get to the download route: pip can parse Requires-Python, and it looks like virtualenv uses the system pip to download pip, so the pinning shouldn't be necessary, I think. > > So, the options are: > > 1. pin pip dependencies at versions that support py2, forever. Obviously > > this is a no-go. > > 2. Ship py2 and py3 wheels. > > 2.1. package the py2 weels with dirtbike. This requires bringing back > > python-wheel, or more work on dirtbike. > > 2.2. Ship static py2 wheels (like we did pre-dirtbike). It's not like > > upstream is continuing development... > > 3. Let virtualenv always download pip from pypi for py2. Only ship py3 > > wheels. > > > > The easy options here are 2.2 and 3. > > 2.1a Where needed package 'py2' wheels with dirtbike running python3. Ah, yeah. Still requires keeping py2 source packages whenever a library in the pip dependency stack drops py2 support. But if they move slowly, that's fine. > 2.2 is using sourceless binaries, so I think it's got DFSG issues. We need > the preferred form of modification and a bdist_wheel is not that. They could be bdist_wheeled at build time, within a single source package. > I think 2.1a would be nice if someone can manage it. We'll need to support 3 > eventually. I plan to implement 3 as an option when I upload pip 20.1 and > virtualenv 2.0.18. Not necessarily. 2.2 is equivalent to 3, but without hitting PyPI. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Python Wheel Related Policy Change Scott Kitterman <debian@kitterman.com> - 2020-04-30 05:30 +0200
Re: Python Wheel Related Policy Change Matthias Klose <doko@debian.org> - 2020-04-30 09:30 +0200
Re: Python Wheel Related Policy Change Scott Kitterman <debian@kitterman.com> - 2020-04-30 12:00 +0200
Re: Python Wheel Related Policy Change Scott Kitterman <debian@kitterman.com> - 2020-04-30 18:30 +0200
Re: Python Wheel Related Policy Change Stefano Rivera <stefanor@debian.org> - 2020-04-30 20:40 +0200
Re: Python Wheel Related Policy Change Scott Kitterman <debian@kitterman.com> - 2020-04-30 22:40 +0200
Re: Python Wheel Related Policy Change Stefano Rivera <stefanor@debian.org> - 2020-04-30 23:50 +0200
Re: Python Wheel Related Policy Change Scott Kitterman <debian@kitterman.com> - 2020-05-01 00:30 +0200
Re: Python Wheel Related Policy Change Scott Kitterman <debian@kitterman.com> - 2020-05-01 22:50 +0200
Re: Python Wheel Related Policy Change Nicholas D Steeves <nsteeves@gmail.com> - 2020-05-01 23:10 +0200
csiph-web