Log file Viewer

[06:20:13] <ronny> what setuptools version starts to ship the setuptoolsversion object?

[06:20:51] <Arfrever> Check them all :) .

[06:36:43] <mgedmin> yay, back to 503 errors, time to clear cookies :/

[12:19:07] <pjdelport> Quick question: is there a way to save or see the build log when using "pip wheel"?

[12:19:57] <pjdelport> (For example, to see what library features were detected by packages like Pillow.)

[12:24:16] <mgedmin> hm, maybe https://pip.pypa.io/en/latest/reference/pip.html#file-logging ?

[12:28:56] <pjdelport> mgedmin: That only seems to save pip's own output; no further details.

[12:37:33] <nanonyme> Hey, it looks like when calling python -mpip freeze on Windows through subprocess.check_output, it makes the parent terminal yellow. What gives?

[12:41:51] <pjdelport> Is there a reason why pip wheel supports --build-option, but pip install doesn't?

[12:59:31] <dstufft> pjdelport: adding some -vvvs might get you that output

[13:00:06] <dstufft> and the reason is because ``pip install`` doesn't call build, it calls install so it gets a different flag (Yea this is kinda crappy in general)

[13:00:30] <pjdelport> Aha

[13:01:34] <pjdelport> dstufft: Yeah, i was trying to get it to pass stuff to build-ext for Pillow, but it turns out that --build-option doesn't do that anyway.

[13:01:57] <pjdelport> dstufft: One -v seems to do the trick, yeah!

[13:45:37] <nanonyme> dstufft, any idea?

[13:46:01] <nanonyme> I didn't spot any --no-colors or whatever option

[13:46:57] <dstufft> nanonyme: I don't know anything about the Windows terminal, we do use colors (and specifically the yellow color) but everyplace we use it we should also be resetting the colors after we're done via colorama

[13:47:11] <pjdelport> Darn.

[13:47:30] <pjdelport> Is there a sane way to do "find-links = ~/.cache/pip-wheelhouse" in your pip.conf?

[13:47:35] <nanonyme> dstufft, well, in this case pip is not writing directly to terminal but instead to a pipe

[13:48:15] <dstufft> nanonyme: does your pipe have a pty? (does a pty make sense on Windows?) the colors should be disabled if it's not a pty

[13:48:20] <dstufft> it might be a problem with subprocess

[13:48:21] <dstufft> er

[13:48:24] <dstufft> with subprocessing pip

[13:48:38] <dstufft> pjdelport: um, does that no work? Maybe it needs a normalize too

[13:48:53] <nanonyme> Afaik pty isn't really a concept on Windows

[13:49:42] <pjdelport> dstufft: That gives me an error and traceback; the exception is:

[13:49:42] <pjdelport> MissingSchema: Invalid URL u'~/.cache/pip-wheelhouse': No schema supplied. Perhaps you meant http://~/.cache/pip-wheelhouse?

[13:50:00] <nanonyme> dstufft, also isn't pty and pipe pretty much exclusive anyway?

[13:50:19] <nanonyme> My guess would be whatever is used to detect pty doesn't work correctly on Windows

[13:50:44] <nanonyme> This isn't *that* big a deal, just a funny side-effect I noticed when writing a build script

[13:51:02] <dstufft> https://github.com/pypa/pip/blob/develop/pip/utils/logging.py#L91-L93

[13:51:18] <dstufft> that whole function is what we use to determine if we should color or not

[13:51:55] <pjdelport> dstufft: Should i file a bug for that?

[13:52:01] <dstufft> pjdelport: probably yea

[13:54:24] <dstufft> nanonyme: do you have a TERM == "ANSI" set by any chance?

[13:54:41] <nanonyme> dstufft, http://bugs.python.org/issue18553

[13:54:54] <nanonyme> dstufft, isatty looks broken on Windows

[13:55:34] <nanonyme> It clearly is returning True even for things that aren't tty's

[13:56:02] <dstufft> nanonyme: file an issue please so we don't forget it

[13:56:29] <nanonyme> This is normally fine but it means you might sometimes want to override the decision

[13:56:54] <nanonyme> I'd expect 99% people call pip, it's through an actual terminal

[13:57:39] <nanonyme> s/an API/a public API/

[13:58:47] <nanonyme> install, freeze and uninstall are things you might actually want to do in build automation :)

[13:59:02] <dstufft> nanonyme: an issue for a --no-color is reasonable too :)

[13:59:27] <nanonyme> Yeah

[14:18:33] <nanonyme> dstufft, you can consider the latter bug more of a feature request

[14:49:13] <mgedmin> what are __init__$py.class files and why are they in my virtualenvs?

[14:50:02] <dstufft> sounds like some jython

[14:51:05] <mgedmin> heh, zope.event-4.0.3.tar.gz ships this file

[15:49:56] <ysionneau> Hi! I have AttributeError: install_layout when using setup.py can someone help? thx http://pastebin.com/CCDkff3C

[15:50:14] <ysionneau> setup.py is this one: https://github.com/m-labs/artiq/blob/master/setup.py

[16:00:50] <ysionneau> This setup.py was working before ... I tried to revert the last commit which modified it but still same error

[16:34:14] <ysionneau> hum ok, after removing $HOME/.local/bin and $HOME/.local/lib my problem is fixed

[16:41:39] <ronny> dstufft: i think i found a setuptools/pip bug, even when i require setuptools>=12 a wheel install will succeed

[16:42:27] <ronny> hmm, who is actually responsible ^^

[17:41:55] <ronny> dstufft: nm, solved it kind of