Re: Python 3.4 and ensurepip (rehashed, long)
- Original Message - > TL;DR: Let's re-enable the ensurepip module in Python 3.4, and possibly >address some usability issues. We should descend en masse on Montreal and >stage a revolt at Pycon. :) > > Python 3.4 has an `ensurepip` module[1] which implements the specification in > PEP 453 regarding the explicit bootstrapping of pip in Python > installations[2]. > This is promoted as a boon to users, especially on platforms without OS > provided package managers, i.e. not Debian. > > The PEP makes some recommendations for downstreams[3], which we do not > currently adopt, and maybe shouldn't fully. Our current Python 3.4 package > disables ensurepip at build time. In case you're interested how Fedora will approach this problem, please see this mail on Fedora's python-devel from me [1]. (Yeah, I'm Fedora's python maintainer and I'm eavesdropping here ;)) Basically, we'll add runtime deps on setuptools and pip to python3 package, so systemwide "python3 -m ensurepip" won't actually do anything, since setuptools and pip will already be there. In virtualenv, our custom "rewheel" script (see the referenced mail for more info/links) will repack the system setuptools and pip to wheels archives and install them into the virtualenv. I've been discussing this with Nick Coghlan quite extensively and he generally likes the approach, so we'll probably be trying to push it upstream for Python 3.5 (our patch is general, so it should work on any distro or even with vanilla upstream ensurepip). I'll be glad to discuss this/answer all questions that might arise about our approach. I'd really love to see it as a general cross-distro approach. Regards, Slavek Kabrda. [1] https://lists.fedoraproject.org/pipermail/python-devel/2014-March/000580.html -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1705317061.4464846.1395305607001.javamail.zim...@redhat.com
Re: Python 3.4 and ensurepip (rehashed, long)
Le 20/03/14 09:53, Bohuslav Kabrda a écrit : I'll be glad to discuss this/answer all questions that might arise about our approach. I'd really love to see it as a general cross-distro approach. Thanks for your post As Mageia packager, I'm interested to join this kind of discussion. I didn't had time yet to look in details your work, but it seems very interesting. -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532af98d.3080...@espelida.com
Re: Python 3.4 and ensurepip (rehashed, long)
Thanks for following up here, and welcome to the list! I lurk on the Fedora list via Gmane, but I don't think I have posting privileges there. Responding a bit out of order. On Mar 20, 2014, at 04:53 AM, Bohuslav Kabrda wrote: >I'll be glad to discuss this/answer all questions that might arise about our >approach. I'd really love to see it as a general cross-distro approach. I agree that a cross-platform approach is best, if possible. This may not be the best place to hash something out though, since we probably won't reach many other platforms (even Linux-based ones). Maybe python-dev or the pypa-dev list? I have a number of questions and issues with the downstream recommendations of PEP 453. If you'll be at Pycon, that might also be a good place to discuss. >Basically, we'll add runtime deps on setuptools and pip to python3 package, Doesn't that introduce a dependency cycle? If so, does that bother you? I don't particularly like it for Debian, but for Ubuntu it's a bigger problem because python-pip is in universe so it would require a MIR to pull that into main and avoid a cross-pocket dependency (on top of the dependency cycle it would introduce). >so systemwide "python3 -m ensurepip" won't actually do anything, since >setuptools and pip will already be there. With a reliable way to say "we are not in a virtualenv", I wouldn't mind if on Debian, a systemwide `python3 -m ensurepip` would recommend installing the python3-pip if it's not installed, much like command-not-found will do. It could also discourage the use of pip for the system Python (when --user is not given). Do Fedora users often want to pip install random PyPI packages into the system Python? >In virtualenv, our custom "rewheel" script (see the referenced mail for more >info/links) will repack the system setuptools and pip to wheels archives and >install them into the virtualenv. I've been discussing this with Nick >Coghlan quite extensively and he generally likes the approach, so we'll >probably be trying to push it upstream for Python 3.5 (our patch is general, >so it should work on any distro or even with vanilla upstream ensurepip). What will rewheeling prefer when: * bundled ones are newer than system ones? * newer versions are available on PyPI? * --upgrade is given? Does using --system-site-packages affect rewheeling? I'm not sure what we would do if we wanted avoided the dependency cycle, and pip/setuptools wasn't yet installed system wide. Cheers, -Barry signature.asc Description: PGP signature
Re: Python 3.4 and ensurepip (rehashed, long)
On Thu, Mar 20, 2014 at 5:40 AM, Barry Warsaw wrote: > I: Should we follow Fedora? > > Fedora is discussing some of these issues too[6]. Looks like one of their > devs created an rpm->wheel conversion script so that if you pip install a > package from the archive, it'll get the rpm, convert it to a while and install > it in the virtual environment (IIUC). I don't much like that, so I don't > suggest we take that approach. Side-note: DEP-11 should make it possible to do something like this in Debian to get the python-foo Debian package installed: apt-get install --component python:foo https://wiki.debian.org/DEP-11 -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAKTje6HcYST8stEcE51vWdDjgfAh2XQo66N6Nw=ccytpay7...@mail.gmail.com
Re: Hello, I'd like to join the team
[Jason Gerard DeRose, 2014-03-19] > > [Jason Gerard DeRose, 2013-12-30] > >> Hello, I'd like to join the Debian Python Modules Team. > > > > Please create an account on Alioth.debian.org and send me your username. > > Sorry, lost track of this email. My Alioth username is jderose (well, > jderose-guest currently it seems). welcome! :) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645 signature.asc Description: Digital signature
Packaging review
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I am working on packaging a python application along with its dependencies. This is my first shot at official Debian packages, so would appreciate any comments on my work! The modules are in the "debian" branches of: python-pocr https://github.com/rvandegrift/pyocr python-pyinsane https://github.com/rvandegrift/pyinsane python-nltk https://github.com/rvandegrift/nltk paperwork https://github.com/rvandegrift/paperwork NLTK already has had some packaging work in progress - I haven't heard back from the latest volunteer on it's RFP, so I'm not sure if that's something I'd hope to submit. Thanks for the help, Ross -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlMrinMACgkQMlMoONfO+HATmwCgkNoR7swlCS86uFkVKexQRqc0 RcgAn283ZxQoIv1iTRufyzW5pRKDkTDV =tvvQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532b8a75.5010...@kallisti.us
