[Numpy-discussion] [SciPy-Dev] ANN: Numpy 1.6.0 beta 1
ralf.gommers at googlemail.com
Wed Mar 23 13:25:11 EDT 2011
On Wed, Mar 23, 2011 at 6:00 PM, Bruce Southey <bsouthey at gmail.com> wrote:
> On 03/23/2011 11:38 AM, Ralf Gommers wrote:
>> On Wed, Mar 23, 2011 at 5:29 PM, Bruce Southey<bsouthey at gmail.com> wrote:
>>> On 03/23/2011 11:07 AM, Ralf Gommers wrote:
>>>> I am pleased to announce the availability of the first beta of NumPy
>>>> 1.6.0. Due to the extensive changes in the Numpy core for this
>>>> release, the beta testing phase will last at least one month. Please
>>>> test this beta and report any problems on the Numpy mailing list.
>>>> Sources and binaries can be found at:
>>>> For (preliminary) release notes see below.
>>> Python 3.1 failed to build it due to import error of _inspect module and
>>> Python2.4 failed 'test_iterator.test_iter_broadcasting_errors'. Yet all
>>> tests passed on Python versions 2.5, 2.6 and 2.7.
>>> PS I do want to go through the bugs I indicated but I have not found
>>> sufficient time.
>>> Python3.1 error:
>>> Traceback (most recent call last):
>>> File "setup.py", line 201, in<module>
>>> File "setup.py", line 178, in setup_package
>>> from numpy.distutils.core import setup
>>> line 22, in<module>
>>> import numpy.distutils.ccompiler
>>> line 15, in<module>
>>> from numpy.distutils.exec_command import exec_command
>>> line 58, in<module>
>>> from numpy.compat import open_latin1
>>> line 11, in<module>
>>> import _inspect
>>> ImportError: No module named _inspect
>> This is strange. I checked that numpy/compat/_inspect.py is present in
>> the tarball. What build command did you use, and can you give the
>> complete output of that command?
>> NumPy-Discussion mailing list
>> NumPy-Discussion at scipy.org
> Yes, I know that it is there and not sure what is missing!
> The typical way:
> $python3.1 setup.py build
It runs 2to3, but then for some reason decides not to use the output
of that on your system. Is that failing each time? If so, can you look
just above where it is failing, and see what's going on before/after
switching the path. Relevant code is:
old_path = os.getcwd()
Just inserting some print statements to look at os.getcwd() before and
after and at sys.path may tell you what's going on.
> Also I know that it builds with Python3.1 and Python 3.2 with the latest git
> pull! But I have update nose before I can test it.
More information about the NumPy-Discussion