Re: [Numpy-discussion] linux wheels coming soon

2016-04-17 Thread Olivier Grisel
I tried on trusty and is also picked
numpy-1.11.0-cp27-cp27mu-manylinux1_x86_64.whl using the system python
2.7 (in a virtualenv with pip 8.1.1):

>>> import pip
>>> pip.pep425tags.get_abi_tag()
'cp27mu'

Outside of the virtualenv I still have the pip version from ubuntu
trusty and it does cannot detect ABI tags:

$ /usr/bin/pip --version
pip 1.5.4 from /usr/lib/python2.7/dist-packages (python 2.7)

>>> import pip
>>> pip.pep425tags.get_abi_tag()
Traceback (most recent call last):
  File "", line 1, in 
AttributeError: 'module' object has no attribute 'get_abi_tag'

But we don't really care because manylinux1 wheels can only be
installed by pip 8.1 and later. Previous versions of pip should just
ignore those wheels and try to install from the source tarball
instead.

-- 
Olivier
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] linux wheels coming soon

2016-04-17 Thread Jens Nielsen
I have tested the new cp27m wheels and they seem to work great.

@Matthew I am using the:

```
sudo: required
dist: trusty

images mentioned here https://docs.travis-ci.com/user/ci-environment/. As
far as I can see you are doing:
sudo: false
dist: trusty

I had no idea such an image exist since it's not documented on
https://docs.travis-ci.com/user/ci-environment/

Anyway your tests runs with python 2.7.9 where as the sudo: requires ships
python 2.7.10 so it's clearly a different python version:

@Olivier Grisel this only applies to Travis's own home build versions of
python 2.7 on the Trusty running on google compute engine.
It ships it's own prebuild python version. I don't have any issues with the
stock versions on Ubuntu which pip tells me are indeed cp27mu.

It seems like the new cp27m wheels works as expected. Thanks a lot
Doing:

```
python -c "from pip import pep425tags;
print(pep425tags.is_manylinux1_compatible());
print(pep425tags.have_compatible_glibc(2, 5));
print(pep425tags.get_abi_tag())"
pip install --timeout=60 --no-index --trusted-host "
ccdd0ebb5a931e58c7c5-aae005c4999d7244ac63632f8b80e089.r77.cf2.rackcdn.com"
--find-links  "
http://ccdd0ebb5a931e58c7c5-aae005c4999d7244ac63632f8b80e089.r77.cf2.rackcdn.com/";
numpy scipy --upgrade
```
results in:

```
True
True
cp27m
Ignoring indexes: https://pypi.python.org/simple
Collecting numpy
  Downloading
http://ccdd0ebb5a931e58c7c5-aae005c4999d7244ac63632f8b80e089.r77.cf2.rackcdn.com/numpy-1.11.0-cp27-cp27m-manylinux1_x86_64.whl
(15.3MB)
100% || 15.3MB 49.0MB/s
Collecting scipy
  Downloading
http://ccdd0ebb5a931e58c7c5-aae005c4999d7244ac63632f8b80e089.r77.cf2.rackcdn.com/scipy-0.17.0-cp27-cp27m-manylinux1_x86_64.whl
(39.5MB)
100% || 39.5MB 21.1MB/s
Installing collected packages: numpy, scipy
  Found existing installation: numpy 1.10.1
Uninstalling numpy-1.10.1:
  Successfully uninstalled numpy-1.10.1
Successfully installed numpy-1.11.0 scipy-0.17.0
```
And all my tests pass as expected.
Thanks a lot for all the work.
Best
Jens

On Sun, 17 Apr 2016 at 11:05 Olivier Grisel 
wrote:

> I tried on trusty and is also picked
> numpy-1.11.0-cp27-cp27mu-manylinux1_x86_64.whl using the system python
> 2.7 (in a virtualenv with pip 8.1.1):
>
> >>> import pip
> >>> pip.pep425tags.get_abi_tag()
> 'cp27mu'
>
> Outside of the virtualenv I still have the pip version from ubuntu
> trusty and it does cannot detect ABI tags:
>
> $ /usr/bin/pip --version
> pip 1.5.4 from /usr/lib/python2.7/dist-packages (python 2.7)
>
> >>> import pip
> >>> pip.pep425tags.get_abi_tag()
> Traceback (most recent call last):
>   File "", line 1, in 
> AttributeError: 'module' object has no attribute 'get_abi_tag'
>
> But we don't really care because manylinux1 wheels can only be
> installed by pip 8.1 and later. Previous versions of pip should just
> ignore those wheels and try to install from the source tarball
> instead.
>
> --
> Olivier
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] linux wheels coming soon

2016-04-17 Thread Olivier Grisel
Thanks for the clarification, I read your original report too quickly.

I wonder why the travis maintainers built Python 2.7 with a
non-standard unicode option.

Edit (after googling): this is a known issue. The image with Python
2.7.11 will be fixed:

https://github.com/travis-ci/travis-ci/issues/5107

-- 
Olivier
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] linux wheels coming soon

2016-04-17 Thread Benjamin Root
Yeah! That's the bug I encountered! So, that would explain why this seems
to work fine now (I tried it out a bit on Friday on a CentOS6 system, but
didn't run the test suite).

Cheers!
Ben Root

On Sun, Apr 17, 2016 at 1:46 PM, Olivier Grisel 
wrote:

> Thanks for the clarification, I read your original report too quickly.
>
> I wonder why the travis maintainers built Python 2.7 with a
> non-standard unicode option.
>
> Edit (after googling): this is a known issue. The image with Python
> 2.7.11 will be fixed:
>
> https://github.com/travis-ci/travis-ci/issues/5107
>
> --
> Olivier
> ___
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> https://mail.scipy.org/mailman/listinfo/numpy-discussion
>
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion


Re: [Numpy-discussion] linux wheels coming soon

2016-04-17 Thread Nathaniel Smith
On Apr 17, 2016 10:47 AM, "Olivier Grisel"  wrote:
>
> Thanks for the clarification, I read your original report too quickly.
>
> I wonder why the travis maintainers built Python 2.7 with a
> non-standard unicode option.

Because for some reason cpython's configure script (in the now somewhat
ancient versions we're talking about) defaults to non-standard broken
Unicode support, and you have to explicitly override it if you want working
standard Unicode support.

I guess this made sense in like the 90s before people realized how unicode
was going to go down.

Same issue affects pyenv users (or used to, I think they might have just
fixed it [0]) and Enthought Canopy.

-n

[0] https://github.com/yyuu/pyenv/issues/257
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion