PMXBOT Log file Viewer

Help | Karma | Search:

#pypa logs for Thursday the 11th of August, 2016

(Back to #pypa overview) (Back to channel listing) (Animate logs)
[08:49:19] <brechtm_> What's the recommended way to prevent a package from installing on an unsupported Python version?
[08:52:06] <brechtm_> Are the "Programming Language :: Python" trove classifiers used in any way for checking compatibility?
[08:55:09] <mgedmin> I believe dashboards like https://python3wos.appspot.com/ use those to detect compatibility
[08:55:17] <mgedmin> pip install itself currently doesn't check trove classifiers
[09:03:07] <brechtm_> I can add a sys.version_info check in setup.py for sdist installs.
[09:03:28] <brechtm_> However, I haven't yet found a way to prevent installation of a wheel on an unsupported Python version.
[09:03:46] <brechtm_> pip will refuse to install my py3 wheel on Python 2.x, but not on the unsupported 3.3
[09:04:10] <brechtm_> Bah. This should be basic.
[09:04:11] <xafer> brechtm_: this should be included in pip 8.2
[09:04:25] <brechtm_> xafer: good to hear that!
[09:04:36] <brechtm_> But what to do in the meantime?
[09:04:39] <xafer> You'll need to define: https://github.com/pypa/setuptools/pull/631
[09:06:44] <brechtm_> I don't suppose there's a solution for wheel installs, since no code is being executed?
[09:08:07] <xafer> Yup, this will require pip 8.2
[09:49:05] <brechtm_> xafer: ok... the next best thing is to check the python version on import then
[10:49:36] <new_student> Hi! What is recommended way of moving ~/.cache/pip to a different location?
[10:49:54] <mgedmin> I'd expect symlinks to work
[10:50:17] <new_student> Is there some parameter in the pip.conf file which I can exploit?
[10:50:18] <mgedmin> I'd also expect pip to pay attention to XDG environment variables
[10:50:41] <mgedmin> ... I should stop answering questions when I don't know the answer
[10:51:04] <new_student> I did come across PIP_DOWNLOAD_CACHE but it isn't working for me.
[10:51:23] <new_student> and https://github.com/pypa/pip/issues/1871
[10:56:55] <mgedmin> why do you want to move ~/.cache/pip elsewhere?
[10:58:34] <new_student> mgedmin, because it is on NFS.
[10:58:48] <new_student> And the locking doesn't work correctly
[10:58:51] <mgedmin> ouch
[11:00:00] <new_student> what would you recommend? sure I could symlink, but would it still solve the locking issue/
[11:14:40] <mgedmin> maybe?
[11:30:55] <dstufft> new_student: XDG directories on linux are supported yes, or PIP_CACHE_DIR env, or cache-dir= in pip.conf
[11:58:17] <new_student> dstufft: Yes, that changes the cache dir, however the lock is still at $HOME/.cache/pip/selfcheck.json.lock
[11:59:29] <dstufft> new_student: hm, looking at the code, it appears we accidently made it so you can't change the location of that particular file
[11:59:32] <dstufft> new_student: file a bug?
[11:59:41] <dstufft> it should respect cache dir like everything else does
[12:01:28] <dstufft> gotta go
[12:01:38] <new_student> will do
[12:07:10] <new_student> How do I write --disable-pip-version-check to pip.conf ?
[12:07:51] <xafer> disable_pip_version_check = 1 in pip.conf ?
[12:08:47] <new_student> disable-pip-version-check=true worked
[18:46:30] <nanonyme> dstufft, blääh. It breaks backwards and forwards compatibility
[18:47:18] <nanonyme> dstufft, or can a mirror support PEP 503 and not break old pip?
[18:49:02] <nanonyme> I guess I need to go talk with our IT to see if they accept to change the mirror
[18:49:30] <nanonyme> If they don't, I'll probably need to drop pip altogether and figure something else out
[18:50:43] <nanonyme> Can't really rely on a specific version to be usable forever, can I?
[19:56:26] <nanonyme> Which would be really sad since I've been spending lengthy amounts of explaining how Python packaging now works reasonably sanely and how people should migrate from easy_install to pip just to have PEP 503 break things
[22:53:44] <dstufft> nanonyme: you can support post and pre PEP 503 with the same mirror
[22:54:31] <dstufft> nanonyme: in fact, bandersnatch does just that