PMXBOT Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Saturday the 2nd of January, 2016

(Back to #pypa-dev overview) (Back to channel listing) (Animate logs)
[02:33:43] <pmxbot> jaraco pushed 1 commit to setuptools (https://bitbucket.org/pypa/setuptools/) :
[02:33:44] <pmxbot> Move extern.packaging into a package to enable package-relative imports to resolve propertly. Ref #229.
[12:05:17] <pumpkinseed> The packaging guide should probably stop referring to the distutils documentation for what is included by default (w/o a MANIFEST.in) since setuptools doesn't include data_files if you do sdist.
[20:03:00] <xafer> dstufft: any opinion on https://github.com/pypa/pip/pull/3295 to easily have https://landscape.io/github/xavfernandez/pip feedbacks ?
[20:03:30] <dstufft> seems fine to me
[20:05:39] <xafer> and since you're here, I'd love to have #pypa-dev on https://botbot.me/ for when pmxbot gets sick
[20:05:51] <dstufft> I sent them a request
[20:05:53] <dstufft> never heard back
[20:06:05] <xafer> :-/
[20:13:32] <xafer> Do you have any planning for pip 8 ?
[20:17:29] <dstufft> xafer: hopefully soon
[20:17:36] <dstufft> that;s about it
[20:27:35] <xafer> k, soon as in january ?
[20:29:10] <dstufft> xafer: probably yea
[20:32:09] <pmxbot> jaraco pushed 4 commits to setuptools (https://bitbucket.org/pypa/setuptools/) :
[20:32:10] <pmxbot> Create a PEP 302 importer for managing conditional import of vendored packages from the 'extern' namespace. This technique avoids the use of 'imp' and works even when setuptools is installed as a zipped egg. Ref #229.
[20:32:10] <pmxbot> Make VendorImporter more generic
[20:32:10] <pmxbot> Pop the module off the stack, preventing the 'Version' class from having a different manifestation in packaging than in pkg_resources.
[20:32:10] <pmxbot> Combine separate VendorImporters into a single one in pkg_resources.extern
[20:33:38] <xafer> Concerning https://github.com/pypa/pip/issues/1087 I was thinking one could maybe host all the last pip versions in bootstrap.pypa.io ? Something like "get-pip-1.5.6.py", "get-pip-6.1.1.py", etc ?
[20:34:40] <dstufft> https://github.com/pypa/pip/pull/2393#issuecomment-90476770 is probably how I Would do it tbh
[20:36:24] <xafer> well the issue is that get-pip.py contains latest pip which old python versions can not run
[20:37:27] <dstufft> oh
[20:37:28] <dstufft> right
[20:37:42] <xafer> or we could also state that we have no interest in supporting such use case and closing this issue :)
[20:42:31] <dstufft> I don't personally have much interest in it, but I Wouldn't block someone solving it if they did they work
[20:44:59] <xafer> Me neither, but I'd like pip to have less open issues :o
[20:51:01] <dstufft> I'm fine closing it with a "unless someone steps up to make this happen, it's unlikely any of the pip core are going to do anything to support this use case"
[20:51:06] <dstufft> anyways, gotta go :D
[20:51:44] <xafer> ok, bye :)
[21:25:51] <pmxbot> jaraco pushed 2 commits to setuptools (https://bitbucket.org/pypa/setuptools/) :
[21:25:51] <pmxbot> Based on experimentation, the canonical module name needs to be in sys.modules on Python prior to 3.3, but must be omitted on Python 3.3 and later.
[21:25:51] <pmxbot> Add some docstrings
[21:36:32] <pmxbot> jaraco pushed 1 commit to setuptools (https://bitbucket.org/pypa/setuptools/) :
[21:36:32] <pmxbot> Extract variable for extant name. Add comment about the hack.