[09:46:35] <fang> I am install scipy on centos 6, got error: openblas_lapack_info: libraries openblas not found
[09:47:19] <fang> already latest version blas-devel-3.2.1-4.el6.x86_64 lapack-devel-3.2.1-4.el6.x86_64
[10:09:39] <dstufft> fang: hard to say, it's going to be specific to scipy's setup.py
[15:18:13] <tos9> Any of you fine people have experience both with running devpi and with running package installs straight out of an S3 bucket, and have an opinion on the two
[15:18:35] <tos9> (It would appear devpi doesn't support S3 as a storage backend.)
[16:12:25] <ronny> tos9: devpi was originated as a *local network* tool
[16:12:38] <ronny> tos9: however as faras i can tell controbutions and/or commisions are welcome
[16:20:50] <tos9> ronny: Yeah, I know :), there's an existing ticket, but devpi's source is a bit complex, and also I'm just generally looking for why I might want to use it at this point.
[16:21:06] <tos9> So I'd rather not invest the effort until I figure out whether I actually *want* to use it.
[16:59:07] <tos9> I don't really see any compelling features if the use case is storing packages for release, wh[Cich I guess is what I'm asking.
[16:59:27] <tos9> Maybe your answer is that in fact that's not what people use it for though.
[17:08:39] <ronny> tos9: the usualge is local cache, developer controlled release testing pipelines and so on
[19:44:55] <tdsmith> while i'm in a blogging mood, a note on building python extension modules on os x outside of distutils: http://blog.tim-smith.us/2015/09/python-extension-modules-os-x/
[19:45:05] <tdsmith> tl;dr: use -undefined dynamic_lookup instead of -lpython