Log file Viewer

[04:27:24] <tdsmith> hmmm, installing setuptools 16.0 using its setup.py with python 3.5.0b1 is failing with "error in setuptools setup command: Invalid environment marker: sys_platform=='win32'"

[04:29:50] <tdsmith> on darwin

[08:56:59] <[Tritium]> Will warehouse, when its done, support browsing the repository?

[08:59:07] <ronny> [Tritium]: what do you mean by "browsing the repository" ?

[09:02:42] <[Tritium]> if you go to pypi.python.org, you actually can click around and get catagorized listings of every project of a certian criteria

[09:02:52] <[Tritium]> so...that

[09:04:00] <ronny> [Tritium]: as far as i understood thats required for warehouse to replace pypi

[18:03:07] <doismellburning> ionelmc: "the rewrite"?

[18:05:50] <doismellburning> ah I've just read https://github.com/pypa/virtualenv/pull/697

[18:33:45] <tdsmith> I think I don't understand this pip output: https://gist.github.com/7958b19ca46f0013e10d -- why is pip uninstalling numpy 1.9.2 and replacing it with numpy 1.9.2?

[18:34:13] <dstufft> tdsmith: because you typed --force-reinstall

[18:34:31] <tdsmith> oh

[18:34:46] <tdsmith> didn't expect that to propagate but i guess i should have

[18:34:48] <tdsmith> sorry~

[18:35:11] <dstufft> tdsmith: no worries!

[18:35:32] <dstufft> generally our options apply to the entire set of things to be installed

[18:35:45] <tdsmith> yeah, makes sense

[18:35:48] <dstufft> unless they explicitly accept a name

[18:35:54] <dstufft> like --no-binary projecy1,project2

[18:37:03] <tdsmith> 3.5b1 is breaking all of my toys

[18:37:30] <dstufft> lol

[18:37:42] <dstufft> I should probably go run the pip tests on that

[18:38:32] <tdsmith> setuptools doesn't install from sdist and numpy won't import

[18:44:59] <warner> dstufft: hey, random question for you

[18:45:48] <warner> dstufft: in the python packaging world, can I generally assume that "setup.py" commands will be run from the same directory as the setup.py file? i.e. os.getcwd() == os.path.dirname(__file__) ?

[18:45:48] <holmser> anyone know how to add a trusted host into the pip config file?

[18:47:14] <warner> holmser: I'm guessing add "[install]\ntrusted-host=HOSTNAME\n" into ~/.pip/pip.conf?

[18:50:16] <pjdelport> warner: I think you can rely on that; otherwise countless setup.py's doing open('README.rst') would be breaking.

[18:50:24] <warner> ok, good

[18:50:32] <warner> there's code in Versioneer that needs a rule like that

[18:51:10] <warner> thanks

[18:51:18] <pjdelport> warner: But you could always do dirname(__file__) to be safer, probably.

[18:52:04] <warner> the actual issue is that Versioneer works by having setup.py "import versioneer", and then versioneer.py looks at os.getcwd() to find itself (and the setup.cfg that configures it)

[18:52:45] <warner> and if you're doing "setup.py install" or "develop" and one of your dependencies also uses Versioneer, then it will also do an "import versioneer", and since it's all happening in the same python process (with the same global module table), it'll get the wrong versioneer.py

[18:53:04] <warner> which means I can't use __file__ inside versioneer.py to correctly find the matching setup.cfg

[18:53:12] <warner> but I think os.getcwd() is safe

[20:44:26] <dstufft> warner: theortically people might run a setup.py script outside of the current directory

[20:45:03] <dstufft> warner: but pip won't, because too many projects break if os.getcwd() isn't the same dir that has setup.py