Log file Viewer

[06:10:52] <s_edrik> If anyone stumbles upon the same issue that I was having this is the source of it https://github.com/pypa/pip/issues/3

[06:11:11] <s_edrik> the fix mentioned in the latest comment worked for me

[14:42:28] <J1m> getting (503): backend read error trying to register a new release w PyPI

[14:44:34] <J1m> although despite the non-200 responses, my package update got published.

[15:07:58] <[Tritium]> pypi.pythonp.org is falling down. :(

[15:10:08] <elarson> [Tritium]: is pythonp.org a typo?

[15:10:28] <[Tritium]> yes

[15:11:01] <elarson> just making sure!

[15:15:37] <[Tritium]> hmm

[15:15:45] <[Tritium]> I wonder if i should file a feature request...

[15:16:59] <[Tritium]> on posix, the shell handels wildcard expansion. On windows, the shell expects the application to handel wildcard expansion. Pip could detect that it is on windows and do the expansion itself if it looks like someone is doing pip install *.whl

[22:13:26] <Jasper> Does anybody know why we might be seeing an error when trying to install packages?

[22:13:27] <Jasper> https://paste.fedoraproject.org/373127/64731902/

[22:13:31] <Jasper> AttributeError: 'Requirement' object has no attribute 'project_name'

[22:13:46] <Jasper> Google tells us stuff about Salt, but we're not using Salt.

[22:27:23] <dstufft> Jasper: Debian (or Ubuntu) needs to update it's pip or it needs to patch it to work with the newer version of setuptools

[22:27:37] <dstufft> I think

[22:27:51] <Jasper> dstufft, what can I do in the mean time to unbreak my stuff

[22:28:02] <dstufft> use pip from PyPI I guess

[22:28:32] <Jasper> time to add `pip install --upgrade pip` to my Dockerfile

[22:28:40] <Jasper> Anything else?

[22:29:13] <dstufft> that should be it I think

[22:30:16] <Jasper> Is there an upstream bug I can follow?

[22:31:20] <dstufft> I don't think any bug exists in pip itself, pip bundles setuptools so it's not possible for setuptools upgrades to break pip, Debian unbudles setuptools (and then rebundles it) and they used a version of pip together with a version of setuptools that doesn't work I think

[22:31:41] <dstufft> IOW I think this is because of Debuntu's patches

[22:34:11] <Jasper> Debian / Ubuntu bug, sorry, not an upstream bug.

[22:34:13] <Jasper> Meant to say downstream.

[22:35:28] <dstufft> I don't remember offhand. I think I talked to Barry about it at one point, but I don't remember if there was a bug for it or not

[23:56:11] <mitsuhiko> dstufft: fun fact. when you upload a release by accident, and you delete it (in pypi), then when automatic release hiding is enabled, the entire project disappears

[23:56:18] <mitsuhiko> until you make the old release visible again

[23:56:26] <mitsuhiko> my /pypi/Werkzeug page was gone for a few days apparently

[23:56:40] <dstufft> mitsuhiko: yea, this is part of why Warehouse elminiates the entire concept of hidden releases

[23:56:45] <mitsuhiko> (happened because i accidentally put a dev release up due to that 500 internal server thing)

[23:56:56] <mitsuhiko> yeah. figured i'm not going to make a bug report fo rthis