I've uploaded a specially-built Linux (RHEL 6.5 and 6.6) wheel of numpy to a local devpi install. It uses openblas instead of atlas, and is partially statically linked to reduce the number of rpm's we need to install (static linking was not my decision). Also, this wheel works with our local CPython 2.7 installs; our old Linuxes come with CPython 2.5, so we can't just use yum on the Linux side. Things seem good on the Linux side. But although we have our production and pre-production environments on Linux, we do our development and initial testing on OS/X systems. That's perhaps a little odd, but it mostly works. Both have CPython 2.7.something, so they're mostly close for our purposes. Anyway, on the OS/X side, we can no longer install the pypi version of numpy on OS/X without first unsetting our PIP_TRUSTED_HOST and PIP_INDEX_URL variables. Is this business as usual? I didn't upload an OS/X binary. It seems the Linux binary is making devpi give up on obtaining an OS/X binary before trying pypi. Thanks!
On Mon, Apr 27, 2015 at 13:12 -0700, Dan Stromberg wrote:
I've uploaded a specially-built Linux (RHEL 6.5 and 6.6) wheel of numpy to a local devpi install. It uses openblas instead of atlas, and is partially statically linked to reduce the number of rpm's we need to install (static linking was not my decision). Also, this wheel works with our local CPython 2.7 installs; our old Linuxes come with CPython 2.5, so we can't just use yum on the Linux side.
Things seem good on the Linux side.
But although we have our production and pre-production environments on Linux, we do our development and initial testing on OS/X systems. That's perhaps a little odd, but it mostly works. Both have CPython 2.7.something, so they're mostly close for our purposes.
Anyway, on the OS/X side, we can no longer install the pypi version of numpy on OS/X without first unsetting our PIP_TRUSTED_HOST and PIP_INDEX_URL variables.
Is this business as usual?
I didn't upload an OS/X binary. It seems the Linux binary is making devpi give up on obtaining an OS/X binary before trying pypi.
Thanks!
I think you need to use the pypi_whitelist setting on your index because once you upload X to the index, pypi.python.org will not be asked for X until you set pypi_whitelist=X ("=*" to allow everything). See http://doc.devpi.net/latest/userman/devpi_indices.html#modifying-the-pypi-wh... holger
-- You received this message because you are subscribed to the Google Groups "devpi-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to devpi-dev+...@googlegroups.com. To post to this group, send email to devp...@googlegroups.com. Visit this group at http://groups.google.com/group/devpi-dev. For more options, visit https://groups.google.com/d/optout.
-- about me: http://holgerkrekel.net/about-me/ contracting: http://merlinux.eu
On Monday, April 27, 2015 at 1:26:12 PM UTC-7, holger krekel wrote:
I've uploaded a specially-built Linux (RHEL 6.5 and 6.6) wheel of numpy to a local devpi install. It uses openblas instead of atlas, and is
On Mon, Apr 27, 2015 at 13:12 -0700, Dan Stromberg wrote: partially
statically linked to reduce the number of rpm's we need to install (static linking was not my decision). Also, this wheel works with our local CPython 2.7 installs; our old Linuxes come with CPython 2.5, so we can't just use yum on the Linux side.
Things seem good on the Linux side.
But although we have our production and pre-production environments on Linux, we do our development and initial testing on OS/X systems. That's perhaps a little odd, but it mostly works. Both have CPython 2.7.something, so they're mostly close for our purposes.
Anyway, on the OS/X side, we can no longer install the pypi version of numpy on OS/X without first unsetting our PIP_TRUSTED_HOST and PIP_INDEX_URL variables.
Is this business as usual?
I didn't upload an OS/X binary. It seems the Linux binary is making devpi give up on obtaining an OS/X binary before trying pypi.
Thanks!
I think you need to use the pypi_whitelist setting on your index because once you upload X to the index, pypi.python.org will not be asked for X until you set pypi_whitelist=X ("=*" to allow everything).
See
http://doc.devpi.net/latest/userman/devpi_indices.html#modifying-the-pypi-wh...
The doc seemed to say this was about something else, but I tried and it worked well; now our OS/X systems can get numpy and scipy without needing to build our own or something. Thanks!
participants (2)
-
Dan Stromberg -
holger krekel