Log file Viewer

[00:22:13] <_habnabit> if i'm using `pip install -d` to download a bunch of packages, is there a way to say 'ignore git+https:// in the requirements.txt' file? it fails on those when i'd like to just skip them

[00:22:50] <_habnabit> i'd rather not split the requirements.txt file into two, though i could do that

[00:46:47] <dstufft> _habnabit: uhhh

[00:46:58] <dstufft> _habnabit: if there's a way to skip it i'm not aware of one

[00:47:01] <_habnabit> dang

[00:47:07] <dstufft> probably you could use some sed and xargs

[00:47:16] <_habnabit> yeah, well :(

[00:47:18] <dstufft> (I think I just told you to go fuck yourself?)

[00:47:26] <wickman> pip install -r <(grep -v git+https requirements.txt) ? :P

[00:47:38] <dstufft> oh there you go

[00:47:44] <dstufft> you probably still need some xargs

[00:47:55] <dstufft> I don't think we accept requirements files on stdin

[00:47:55] <wickman> though dunno if pip will read from /dev/fd or whatever correctly

[00:47:58] <dstufft> though maybe we should

[00:48:27] <wickman> with open(foo) as fp: fp.readlines() works fine with something piped in from a subshell, at least on POSIX

[00:48:37] <wickman> only if you do like seek() or tell() will it freak out

[00:49:41] <_habnabit> this is in ansible, so this'll be a little more complicated......

[00:49:53] <_habnabit> maybe i'll go with the split requirements file

[00:50:03] <dstufft> _habnabit: you're aware you can include one req file in another yea?

[00:50:08] <_habnabit> yeah i know

[00:50:11] <dstufft> ok

[00:50:24] <dstufft> just make sure you knew that at least it'll still be one entry point to isntalling stuff

[00:50:25] <dstufft> :[

[00:50:27] <dstufft> oh wait

[00:50:30] <dstufft> you knowwww

[00:50:34] <dstufft> there's this one wierd option

[00:50:36] <_habnabit> so requirements.txt will be `-r downloadable-reqs.txt\ngit+http://....`

[00:50:40] <_habnabit> uh oh

[00:50:45] <wickman> install your requirements with this one weird old trick™

[00:50:49] <dstufft> that was deperecated forever ago and noone ever removed it afaik

[00:50:53] <_habnabit> hahaha

[00:50:55] <dstufft> I don't actually know what it does

[00:51:02] <dstufft> but it's called --skip-requirements-regex

[00:51:06] <_habnabit> wow

[00:51:09] <wickman> wat

[00:51:09] <_habnabit> is that even documented?

[00:51:12] <dstufft> nope!

[00:51:19] <dstufft> you probably don't want to use it

[00:51:22] <_habnabit> --skip-requirements-regex option requires an argument

[00:51:23] <dstufft> but if you really don't want two files

[00:51:24] <_habnabit> dang

[00:51:37] <dstufft> _habnabit: presuamably the regex you want to skip

[00:51:49] <_habnabit> oh, yeah, i was just commenting on that it actually is an option

[00:51:49] <wickman> dstufft: this is reminiscent of s/just call a function with arguments/just edit a text file/

[00:52:37] <dstufft> wickman: yea I want to remove it, I have no idea why it was added, or why it was silenced in the help output and undocumented, but it seems like thing that just makes things more confusing

[00:53:01] <_habnabit> i guess i won't use it then ;<

[00:53:15] <_habnabit> weird that it exists though

[00:53:21] <wickman> i could see it being useful if it was used to cull requirements pulled in transitively

[00:53:56] <dstufft> everything I know about it, I know because I saw it here https://github.com/pypa/pip/blob/develop/pip/cmdoptions.py#L141-L147

[00:54:07] <dstufft> I don't even know if it works anymore or if it bitrotted

[00:54:38] <dstufft> another weird option, you can specify the default VCS for editable installs, incase you get tired of typing git+ or something

[00:54:52] <_habnabit> if i put a -r in a requirements.txt file, where is the path relative to? the cwd?

[00:54:54] <wickman> whyyy

[00:55:11] <dstufft> _habnabit: I think it's relative to the file

[00:55:17] <_habnabit> oh, that's better

[00:55:17] <dstufft> lemme verify

[00:56:03] <dstufft> _habnabit: looks like it

[00:56:09] <_habnabit> dstufft, thanks

[00:56:30] <dstufft> every once in awhile a packaging tool does something reasonable.

[00:56:33] <_habnabit> yes!

[00:56:39] <dstufft> I bet it was an accident though!

[02:58:29] <weykent> i'm having some trouble getting pip to recognize my wheels. the wheel's name is 'sanpera-0.1.1.dev4-cp34-cp34m-linux_x86_64.whl' and on a linux x86_64 box i'm getting 'skipping ... because it is not compatible with this Python' in the pip output

[02:58:53] <weykent> i'm not even entirely clear what all the parts of the wheel filename mean

[02:59:16] <weykent> is there a way to get pip to explain in more detail what the incompatibility is?

[04:59:27] <weykent> well, i found http://legacy.python.org/dev/peps/pep-0425/ but it doesn't describe what the 'm' is in 'cp34m' afaict

[05:01:07] <dstufft> weykent: it means CPython was compiled with pymalloc

[05:01:40] <weykent> aha

[05:01:51] <dstufft> it's just a compile time option that changes the ABI of CPython

[05:02:10] <weykent> how can i tell if my python was compiled with pymalloc?

[05:04:58] <dstufft> python -m sysconfig | grep SOABI

[05:05:11] <weykent> thanks

[05:06:28] <weykent> man, what the heck. i don't know how, but it looks like installing python 3.4 from the same deb has resulted in pymalloc on one machine and no pymalloc on the other

[05:06:38] <weykent> i guess i'll purge and reinstall

[05:07:57] <weykent> apt-cache show lists the same SHA256, too

[05:09:01] <weykent> oh, duh. i'd installed python 3.4 from source previously and it was in ~/.local

[05:12:07] <weykent> yaaay, my wheels installed

[05:17:54] <weykent> what's the best way to maintain an internal fork of a project, version-number-wise? PEP-386 doesn't let me use an arbitrary suffix or infix to indicate 'this is a forked version', so i've just been making .dev version number releases on top of the existing version numbers

[05:18:09] <weykent> maybe i should just change the project name to projectname_internal or something

[05:18:25] <weykent> either way the package will only be available on the internal pypi

[05:23:12] <dstufft> PEP440 local version

[05:24:36] <weykent> oh!

[05:25:25] <weykent> so instead of 0.5.dev1, do 0.5-1 ?

[15:49:07] <mpj17> Good morning! Could someone please help me with an issue I am having using Twine to upload a package to PyPI? I am confused by an error:

[15:49:09] <mpj17> HTTPError: 403 Client Error: You are not allowed to edit 'gs.dmarc' package information

[15:49:13] <mpj17> I have registered, and Twine seems to authenticate fine. I cannot figure out what to do next.