Log file Viewer

[03:30:37] <gsnedders> dstufft: given I spoke to you about this ages, FWIW https://gsnedders.github.io/python-marker-test/results.html has some vague summary of what supports what markers

[03:30:48] <gsnedders> s/ages/ages ago/

[03:33:59] <gsnedders> interestingly this goes against what https://github.com/pypa/packaging/issues/70 says

[17:06:37] <aagbds> I'm using pip in a virtualenv with a pip.conf in the virtualenv. Is there a way to specify a relative directory the pip cache dir? For instance, something like `cache-dir = ./.cache` or `cache-dir = $VIRTUAL_ENV/.cache`? It seems that pip doesn't expand the environment variable and creates a literal `$VIRTUAL_ENV` directory in every directory where `pip install` is called.

[17:07:12] <dstufft> aagbds: I don't think so no

[17:14:13] <aagbds> I'm running in a CI environment where I don't necessarily know where the virtualenv will be created, so creating a cache relative to the pip.conf would be ideal. I guess the only solution is to use PIP_CACHE_DIR env variable

[17:38:46] <dstufft> aagbds: fwiw the cache should be safe to share between virtual environments.. are you seeing a behavior where it isn't?

[17:51:11] <aagbds> dstufft: Potentially with prebuilt wheels we self-publish... say uwsgi built with python2.7.6 and it being installed from cache in a virtualenv with python2.7.11

[17:58:03] <ionelmc> aagbds: patch version differences should not change the binaries

[17:58:32] <ionelmc> iow they are binary compatible

[19:09:52] <frewsxcv_> dstufft: did pip break compatibility with wheels between 7.1.2 and the latest version?

[19:10:58] <dstufft> frewsxcv_: shouldn't have no, what are you seeing?

[19:13:30] <frewsxcv_> dstufft: Skipping file:///opt/localpackages/numpy-1.11.1rc1-cp27-cp27mu-linux_x86_64.whl because it is not compatible with this Python

[19:13:39] <frewsxcv_> error in 7.1.2, but works in latest version

[19:13:51] <dstufft> frewsxcv_: oh, that's because of the SOABI

[19:14:00] <dstufft> so

[19:14:19] <dstufft> CPython 2.7 doesn't expose a SOABI, so previously we just said "hey, it's just a cp27, that's it's SOABI"

[19:14:33] <dstufft> but that's a lie, because CPython has different compile options that affect the ABI

[19:15:00] <dstufft> later versions of pip and wheel emulate the Python 3 SOABI on 2.7, by detecting the compile flags at runtime

[19:15:12] <dstufft> hence, that wheel got detected as a cp27mu SOABI

[19:15:25] <frewsxcv_> what is SO in SOABI?

[19:15:42] <frewsxcv_> nevermind, shared object

[19:15:46] <dstufft> but of course, the old pip's don't know about that, so it is only looking for a SOABI of ``cp27`

[19:20:43] <frewsxcv_> dstufft: what is "mu" in "cp27mu"

[19:21:14] <dstufft> m stands for pymalloc

[19:21:18] <dstufft> and u is uh, wide unicode

[19:22:56] <frewsxcv_> cool, thanks