Log file Viewer

[13:56:24] <nicksloan> On Debian, should I get pip and virtualenv from the debian repos, or install virtualenv from pip, (and pip from...? get-pip.py maybe?)

[13:56:40] <nicksloan> Regarding Python 2.7

[14:26:59] <sbraz> nicksloan: repos sound good

[14:39:36] <nicksloan> sbraz: someone in #python brought up the concern of an outdated pip

[14:39:37] <dstufft> nicksloan: The answer is... it depends :) Theoretically the ones from the repo will interact better with their packaging system (e.g. no fighting over what version is installed and what not), but the flip side is it is often an older version, and often times their patching breaks in strange ways.

[14:40:37] <nicksloan> dstufft: that was my original concern with the repo approach.

[14:46:09] <nicksloan> Then the question is what is the best way to install pip on production? Running get-pip.py seems a bit less than ideal, since I'm so careful about getting everything else as wheels from our private pypi mirror.

[14:50:24] <dstufft> nicksloan: you can use get-pip.py to install from a private server

[14:54:12] <nicksloan> oh yeah! I forgot that get-pip.py contains (rather than downloads) pip.

[15:08:34] <dstufft> nicksloan: yea, I mean it also downloads pip too, but you can pass any of the options you pass to pip to get-pip.py

[15:08:42] <dstufft> so that it'll download from your server instead of PyPI

[15:15:17] <nicksloan> dstufft: oh, I see. So it uses the hardcoded pip to install the latest pip, which can optionally be hosted on our own servers

[15:15:27] <dstufft> nicksloan: yea

[16:19:21] <floppym> dstufft: The caching issue on files.pythonhosted.org -- does that eventually fix itself, or do you always have to manually purge it when files start erroneously 404-ing?

[18:39:10] <jaraco> I see jaraco.clipboard is stale on Warehouse (https://pypi.org/project/jaraco.clipboard/) (should be 1.3)

[18:39:23] <jaraco> Is that something that will correct itself or does it require manual intervention?

[18:40:33] <jaraco> Also, I just noticed that pypi.io now seems to redirect to pipi.org. Is that intentional and preferred? Which should I use when publishing a link?

[18:44:59] <Wooble> jaraco: no idea about the staleness, but .org is new and preferred.

[18:45:31] <Wooble> (the .io address was used because .org wasn't available. The PSF bought it from the old owner)

[20:51:02] <jaraco> dstufft: Normally I wouldn’t ping you about an issue like this, but I’ve made several references to the latest jaraco.clipboard, so I’d like if the latest info showed on warehouse.

[20:51:33] <jaraco> jaraco.clipboard still shows v1.2 for me in warehose, but v1.3 in pypi.python.org