pmxbot IRC Log Viewer

[08:21:44] <mitsuhiko> dstufft: it's a general community problem

[08:22:11] <mitsuhiko> and i'm as guilty as everybody else

[08:22:18] <mitsuhiko> click gained windows ci support a week ago

[08:22:44] <mitsuhiko> the first time i looked at osx packaging was two weeks ago

[09:25:09] <ztane> is there any way to make pip force install a package to a venv that also uses --system-site-packages

[09:25:23] <ztane> I need to *downgrade* 1 package ...

[09:25:35] <ztane> but I really also do not want to install numpy by hand in this venv

[09:26:42] <ztane> Collecting ply==3.6 Using cached ply-3.6.tar.gz

[09:26:42] <ztane> Installing collected packages: ply Running setup.py install for ply

[09:26:42] <ztane> Successfully installed ply-3.7

[09:26:46] <ztane> :D

[09:27:12] <ztane> and the ply-3.7 is in ubuntu dist-packages

[09:28:32] <mgedmin> there's a known bug where "successfully installed foo-VERSION" prints nonsensical versions that don't match whatever was actually installed

[09:28:57] <mgedmin> so maybe check the venv's site-packages by hand?

[09:29:05] <mgedmin> or try pip list/pip freeze?

[09:29:23] <mgedmin> I've no idea what happens if you have the same package in a venv and in the system, with --system-site-packages

[09:29:46] <mgedmin> presumably both end up on sys.path so whichever comes first wins?

[09:30:06] <ztane> it is the wrong version

[09:30:31] <ztane> I wonder if there is a way to link a single package from dist-packages

[09:30:36] <ztane> I guess not...

[09:30:51] <mgedmin> yes, manually, with ln -s

[09:30:57] <mgedmin> it reportedly works

[09:31:43] <ztane> ah I have lunch break so I could try compiling an egg out of numpy :D

[09:31:55] <ztane> or wheel or whatever would work

[09:46:58] <ztane> shit it didn't even work

[09:47:38] <ztane> (building bdist/bdist_egg/whatever for numpy)

[09:57:58] <mgedmin> do you have all the build dependencies?

[09:58:08] <mgedmin> apt-get build-dep python-numpy is a timesaver

[10:11:51] <mitsuhiko> does anyone know a way to compile python statically linked to openssl?

[12:52:39] <ztane> mgedmin: mhmm good point... will try later

[17:57:33] <zmanji> mitsuhiko: I once attempted and was not able to statically link to openssl. If you find out a way I think a lot of people would appreciate a gist/blogpost/tweet

[18:06:51] <elarson> mitsuhiko: do you develop on linux generally? I by "develop" I mean do you run linux on your desktop vs. some other os and dev via ssh on another machine

[18:07:11] <mitsuhiko> all my servers run linux but my development environment is osx and sometimes windows

[18:07:35] <mitsuhiko> haven't used linux on the desktop for years now

[18:42:37] <mitsuhiko> zmanji: i have the shittest of hacks now

[18:42:39] <mitsuhiko> step one: https://github.com/mitsuhiko/lektor/blob/master/gui/bin/compile-python-framework

[18:42:45] <mitsuhiko> step two: https://github.com/mitsuhiko/lektor/blob/master/gui/bin/make-openssl-relocatable

[18:42:49] <mitsuhiko> step three: https://github.com/mitsuhiko/lektor/blob/master/gui/bin/make-python-framework-relocatable

[18:43:06] <mitsuhiko> and obviously it only runs on mac

[18:43:10] <zmanji> jfc

[18:43:58] <mitsuhiko> tbh. install_name_tool + @rpath rewriting is great

[18:44:09] <mitsuhiko> one could totally write a tool that just walks binaries and auto bundles them

[18:44:16] <mitsuhiko> assuming they are all compiled against the right deployment target

[18:45:01] <ngoldbaum> mitsuhiko: do you think it might be possible to upload openssl wheels to pypi? One thing I struggled with recently is that under 10.11 apple no longer bundles the openssl headers, so it's impossible to build python from source with a working _ssl module.

[18:45:23] <mitsuhiko> ngoldbaum: that's what this is about

[18:45:23] <ngoldbaum> (unless you install openssl with e.g. a package manager)

[18:45:29] <mitsuhiko> it's worse than that

[18:45:37] <mitsuhiko> the python tarball is completely broken for building openssl

[18:45:43] <mitsuhiko> no configure option can fix it

[18:45:56] <mitsuhiko> but no, i'm not going to care about making wheels for this

[18:45:57] <ngoldbaum> somehow apple did it for their version of 2.7.10 in /usr/bin/python

[18:46:11] <ngoldbaum> mitsuhiko: fair enough

[18:46:35] <mitsuhiko> apple links against 0.9.8

[18:46:43] <mitsuhiko> if you have headers for that, you can do the same

[18:46:59] <mitsuhiko> but in this case i just unfucked all the things and built it myself

[18:47:06] <mitsuhiko> but this is for a very specific case where i want to ship python to users

[18:47:10] <ngoldbaum> right, this isn't for me but for a script that bootstraps python and a bunch of scientific libraries

[18:47:13] <ngoldbaum> yeah, makes sense

[18:47:16] <mitsuhiko> so my app comes with it's own self contained python

[18:48:16] <mitsuhiko> i also have a frankenversion of imagemagick in there

[19:09:25] <tdsmith> mitsuhiko: fwiw setting CPPFLAGS and LDFLAGS for the python build ought to let you build against openssl without modifying any files

[19:09:30] <tdsmith> which is pretty common in autotools-land

[19:10:04] <tdsmith> also delocate is a tool for auto-bundling libraries

[19:14:43] <my-generic-nickn> I'm in the process of adding my first package to PyPI. So far I have https://pypi.python.org/pypi/numpngw, but it does not show up in a search, either on the pypi web page or with "pip search".

[19:16:51] <tdsmith> how long has it been? i think i remember the search index is rebuilt periodically so you may have to wait a day or so but dstufft probably has a more definitive answer

[19:17:49] <my-generic-nickn> tdsmith: About an hour or so.

[19:42:02] <my-generic-nickn> By the way, is http://peterdowns.com/posts/first-time-with-pypi.html reasonably up-to-date? Where can I find documentation about using the [metadata] part of setup.cfg?

[19:45:09] <Ivoz> my-generic-nickn, the equivalent to description-file there is just to also use a long_description keyword in setup() of setup.py

[19:46:09] <Ivoz> you can find lots of info here https://packaging.python.org/en/latest/distributing/

[19:46:30] <Ivoz> and demo of long_description here https://github.com/pypa/sampleproject/blob/master/setup.py#L14-L29

[19:47:50] <my-generic-nickn> lvoz: Thanks. The "equivalence" of long_description and description-file is.. interesting. I have both.

[19:48:49] <Ivoz> mm, I'd suggest one or the other

[19:50:06] <my-generic-nickn> lvoz: I guess I don't understand who/what reads the [metadata]/description-file filename and how it is used.

[19:50:36] <Ivoz> basically it will appear on the project's pypi page

[19:50:40] <Ivoz> as the big description

[19:51:52] <my-generic-nickn> lvoz: So if I use the technique of reading the README file in setup.py and making it the long description, I don't need setup.cfg (since the only thing in there are the moment is the deifniotn of description-file).

[19:52:03] <Ivoz> yep

[19:54:33] <my-generic-nickn> OK, thanks.

[19:59:42] <my-generic-nickn> Hmmm... My README.md is pretty long, and includes links to PNG files on github. It will be interesting to see what the pypi site does with those.

[20:06:07] <mitsuhiko> tdsmith: does not work

[20:12:07] <tdsmith> mitsuhiko: really? https://gist.github.com/281fd14a49075a72c98b

[20:12:10] <tdsmith> built the _ssl extension fine

[20:12:17] <tdsmith> and it looks functional to me

[20:12:41] <mitsuhiko> tdsmith: what does otool -L on _ssl.so point to?

[20:13:22] <tdsmith> homebrew's openssl

[20:13:22] <tdsmith> https://gist.github.com/acf092078dca2fbec4d1

[20:13:35] <mitsuhiko> actually, probably works for you

[20:13:41] <mitsuhiko> i just saw your compile output

[20:13:44] <mitsuhiko> wonder why it does not for me

[21:19:14] <my-generic-nickn> OK, numpngw is now being found by "pip search numpngw". Woot.

Log file Viewer

Help | Karma | Search:

#pypa logs for Friday the 13th of November, 2015