pmxbot IRC Log Viewer

[06:32:33] <mgedmin> which version of setuptools added pep-426 environment marker support?

[06:36:16] <mgedmin> wow, 0.7, that's _old_

[06:36:33] <mgedmin> "There should probably be a PEP with a firmer spec before the feature should be considered suitable for use."

[06:36:36] <mgedmin> was there a spec?

[06:59:17] <ronny> mgedmin: i assume short for specification

[06:59:47] <mgedmin> right, but I don't think anyone wrote a spec?

[06:59:53] <mgedmin> PEP 426 defines the syntax for environment markers

[07:00:21] <mgedmin> but the syntax of putting them into extas_require after a ':' is not documented in any spec, I think?

[07:10:02] <ronny> mgedmin: thats a setuptools hack

[07:10:20] <mgedmin> ... yes

[11:04:44] <mgedmin> hey, I can't create virtualenvs on a self-compiled python3.5

[11:05:04] <mgedmin> virtualenv 13.0.1

[11:05:50] <mgedmin> https://gist.github.com/mgedmin/6339f8cf91f74e84026c

[11:05:58] <mgedmin> this is probably something bad with my local environment?

[11:06:05] <mgedmin> but virtualenv -p python3.4 works

[11:06:30] <mgedmin> (python3.4 is not self-built, tho; it comes from ppa:fkrull/deadsnakes)

[11:06:46] <mgedmin> (no what am I saying, 3.4 is from the ubuntu repos)

[11:09:55] <mgedmin> pip uninstall enum34 fixes this

[11:10:31] <mgedmin> why do I have enum34 installed in my "tools" venv? I DON'T KNOW

[11:10:48] <mgedmin> pip uninstall enum34 doesn't tell me what other packages it breaks ;(

[11:14:13] <mgedmin> ok, fixed that

[11:14:23] <mgedmin> now I get 'error in check-manifest setup command: Invalid environment marker: python_version=="2.6"'

[11:15:00] <mgedmin> why is this an invalid environment marker? and why does the error only show up on python 3.5.0b1?

[11:15:17] <ronny> dstufft: enum34 is massively broken and should fail on python3 but instead breaks python3, can it be removed from pypi unless the author fixes it?

[11:21:24] <mgedmin> no, that sounds like a bad idea

[11:21:54] <mgedmin> it would be better if virtualenv -p python3.4 did not put python2.7/site-packages on sys.path

[11:22:43] <mgedmin> and in fact https://github.com/pypa/virtualenv/pull/697 would fix that, but it's a big change

[11:25:18] <mgedmin> that 'invalid env marker: python_version=="2.6"'? happens during pip install from an sdist, but only on cpython 3.5.0b1

[11:25:28] <mgedmin> during "python setup.py egg_info"

[11:25:35] <mgedmin> bug in setuptools?

[11:26:25] <ronny> mgedmin: what version of setuptools?

[11:26:44] <mgedmin> 16.0

[11:27:10] <mgedmin> oh look https://bitbucket.org/pypa/setuptools/issue/388/install-from-sdist-fails-on-python-350b1

[11:29:45] <jhermann> any known problem with pip7 and metadata versions and/or namespace packages?

[11:30:08] <jhermann> i have a Jenkins job where py.test doesn'T find its "py" (which still is a namesapce package i think)

[11:30:18] <jhermann> fallback to pip6 fiexes it

[11:30:40] <jhermann> manual "easy_install py" fixes it too

[11:31:28] <jhermann> pip freeze and yolk generate different lists in a pip7 install (i.e. metadata differences are likely)

[11:41:15] <mgedmin> jhermann, cannot reproduce (virtualenv -p python3.4 /tmp/py34; /tmp/py34/bin/pip install pytest; /tmp/py34/bin/py.test -> starts to search for tests in .)

[11:41:29] <mgedmin> pip 7.0.1

[11:41:48] <mgedmin> uh, lemme try on 2.7

[11:42:12] <jhermann> wel, works on my trusty too, but fails in jenkins on wheezy

[11:42:14] <mgedmin> also works

[11:42:47] <jhermann> some stupid minute difference, as usual, but not sure what it is

[11:57:05] <jhermann> ok, no wonder, something installs setuptools-0.6c11 over my update to 16.0

[12:02:08] <mgedmin> haha

[12:02:10] <mgedmin> buildout?

[12:04:16] <jhermann> nope, I sued -UI with the initial update commands

[12:04:35] <jhermann> get I should drop the -I, that leaves the stoneage setuptools lying around and active

[12:05:01] <jhermann> droping the -I deletes the egg (and leaves the pth, but that points to the egg that'S gone)

[12:05:19] <jhermann> so then the 16.0 version gets atualyl used

[12:05:40] <jhermann> *guess I

[12:23:53] <mgedmin> oh my

[12:29:54] <jhermann> the old packaging mess has a wide reach ;)

[12:43:27] <mgedmin> ... did I find a CPython bug? https://bitbucket.org/pypa/setuptools/issue/388/install-from-sdist-fails-on-python-350b1#comment-18390886

[12:56:47] <mgedmin> why oh

[12:57:36] <mgedmin> make that "supported 2.4 when that code was written"

[13:59:51] <ionelmc> some brave people using 3.5 ... xD

[14:05:52] <Wooble> using, or testing under? :)

[14:51:22] <ionelmc> Wooble: suffering under? xD

[14:52:58] <tdsmith> mgedmin: thanks for tracking that down!

Log file Viewer

Help | Karma | Search:

#pypa logs for Wednesday the 27th of May, 2015