As part of a discussion on a pip issue, it was noted that if pip
depends on distlib for installer capabilities (e.g., locators, wheel
installation, version and requirement parsing and matching, etc) then
the user needs distlib installed as well as pip. That shouldn't be an
issue for an end user,
It would be great to maintain and install pkg_resources separately. The
idea has come up before, including the idea of just putting pkg_resources
in the system library without the rest of setuptools (it will stay on pypi
now - pip install pkg_resources)
On Mar 9, 2013 1:29 PM, Paul Moore
On 10 Mar 2013 10:16, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Paul Moore p.f.moore at gmail.com writes:
Would it be worth considering splitting distlib into two separate
parts - one that is intended solely for writers of installers and
similar tools, and another for runtime support
On Sat, Mar 9, 2013 at 8:14 PM, Nick Coghlan ncogh...@gmail.com wrote:
On 10 Mar 2013 10:16, Vinay Sajip vinay_sa...@yahoo.co.uk wrote:
Paul Moore p.f.moore at gmail.com writes:
Would it be worth considering splitting distlib into two separate
parts - one that is intended solely for
On Mar 7, 2013, at 11:40 PM, Matt Behrens askedre...@gmail.com wrote:
After doing some research tonight on storing/accessing passwords in the OSX
Keychain
(http://asktherelic.com/2013/03/07/storing-command-line-passwords-in-keychain/),
I was curious why the .pypirc doesn't support
