Log file Viewer
#pypa logs for Tuesday the 24th of March, 2015
[05:53:56] <tdsmith> explicit linkages to libpython / Python frameworks on OS X mean you can't build against e.g. system python and import from e.g. homebrew python because it segfaults the interpreter
[11:25:43] <fladd> hi there, quick question: Can PIP install .exe installers? Like easy_install can do?
[11:29:55] <Wooble> It's certainly odd that they provide wheels for OS X, for which it's easy to get a sane build system, and not for windows :/
[11:33:02] <fladd> what happens if I define a link to http://www.lfd.uci.edu/~gohlke/pythonlibs/ in dependency_links? Will those be preferred by PIP, or will PIP still try to build numpy on Windows?
[11:34:04] <dstufft> it prefers the newest version that matches your version specifier, then it prefers wheels, then it finally prefers sdists, then it fails
[11:36:08] <fladd> and i assume there is no way I could tell pip with an option to install, that it should ignore source?
[11:36:44] <dstufft> not currently, there's an open issue for it. Of course you can do something like pip install numpy==1.9.2 mythingthatdependonnumpy
[11:39:15] <dstufft> No, you can't put the == inside of an extra, you'd have to specify it seperately
[11:40:36] <fladd> maybe the easier solution is to write an install python script, which just downloads all dependencies from various sources I define and then installs that...
[11:48:57] <fladd> well, if the biggest python packages don't support it, it is not there yet. Same as with Python 3...
[11:49:35] <fladd> we have a rather simple package we want to make available on PyPi, but even that is not possible
[11:51:17] <dstufft> That's not a problem with PyPI, that's a problem with Numpy. I dunno why they aren't releasing Wheels for Windows, Wheels themselves work fine on Windows, many other projects are releasing them (and gohlke's page shows they work for Numpy too). It might have something to do with them wanting to provide different options for things like SSE2 vs SSE3 or something, I dunno.
[11:51:50] <fladd> if big package maintainers do not see the value of putting their compiled code (which they have for windows, there are installers!) into PyPI, it seems to me that they don't see PyPI as a proper way to distribute their code
[11:52:58] <mgedmin> imagine you're a maintainer of a popular package; it's built with a system of jury-rigged scripts
[11:53:17] <mgedmin> now pip/pypi introduces a new feature (wheels), but you're afraid to touch your scripts
[11:53:38] <dstufft> eh, Wheels are a fairly newish thing. and there are a lot of package maintainers. Often times getting new things to happen is more a matter of inertia than not feeling like they aren't suitable (as mgedmin is saying)
[11:55:58] <dstufft> http://pythonwheels.com/ shows support for Wheels on PyPI for the top 360 (in terms of download #s), it's roughly 35% or so. Pretty decent considering it's new and some of these things haven't seen releases in years
[11:57:24] <dstufft> Some of those also don't have wheels because for compiled code, building wheels requires access to a Windows machine, and some folks may not want to do that
[12:51:15] <ionelmc> like a custom package index (devpi looked pretty interesting) or some custom install thingy (just put the wheels in a dir and use pip install --find-links
[18:23:40] <jessamyn_> I'm mostly using py3 now, so I put it first on my path. What tos9 said will work if you don't want to do that.
[18:28:13] <jessamyn_> tos9: you are right, and I didn't do that, and now I"m trying to figure out exactly what I *did* do
[18:28:21] <mgedmin> when you activate a virtualenv created with python3 it ends up putting a 'python' executable in from of your $PATH that runs Python 3
[18:35:46] <jessamyn_> tos9: I aliased mkvirtualenv to 'mkvirtualenv --python=/usr/local/bin/python3'
[20:04:54] <tos9> pip is refusing to install a tarball that it just downloaded via pip install --download
[20:05:28] <tos9> saying that no versions match, when there's a mylib-latest.tar.gz which it just downloaded from the URL -- it doesn't appear that passing --pre makes it happy either.
[20:19:41] <ronny> dstufft: it seems the communication of pypa to the outside world needs to be improved
[20:20:07] <ronny> having a discussion with the sqlalchemy author atm, hes pointing out many issues that confuse the hell out of everyone
[20:24:48] <dstufft> tos9: how are you trying to instal it, by directly referencing the tarball or by indirect reference?
[20:26:01] <ronny> dstufft: btw, is there any reason why twine puts up more metadata than setup.py bdist_wheel upload
[20:30:31] <ronny> agronholm: well, there is a reason why im working on a tool that removes setup.py from the developers hands
[20:30:52] <tos9> dstufft: my URL didn't have that info in it, how hsould I know what version that tarball is
[20:31:08] <tos9> dstufft: well it did in the URL itself, and in the resulting filename. I guess that's the answer.
[20:31:23] <ronny> agronholm: codename gumby elf, code hopefully at the end of the week, my recovery from the sinus op is stopping my work
[20:31:49] <dstufft> tos9: there's no way to know ahead of time when --download is going to give you no.. though i'm surprised it gave you a mylib-latest.tar.gz
[20:32:16] <tos9> (that URL is in my requirements file. And now I want to install the resulting tarball)