Re: [Numpy-discussion] Numpy 1.10.3 release.

[Ralf Gommers]

On Wed, Jan 6, 2016 at 8:30 AM, Ralf Gommers  wrote:

>
>
>
> On Mon, Jan 4, 2016 at 9:38 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>>
>>
>> The failed tests require pyrex, fortran, and swig. The refcount error
>> comes and goes, probably the test isn't very good.  Ralf, is there any
>> reason to keep the various extension building tests? They are very old.
>>
>
> There are f2py tests that are useful - if they fail then building anything
> else with f2py fails as well. However those are all in f2py/tests/ IRRC,
> not in distutils/tests.
>
>>
>> I don't know what the recommendation on using nosetests is,
>>
>
> Don't use it (it definitely gives test errors due to not having the
> knownfailure plugin), use either runtests.py or numpy.test().
>
>
>> but probably it is finding too many tests.
>>
>
> It's doing its job here in finding these though. It looks like these tests
> need either fixing (the extensions aren't built) or removing. I'll have a
> look tonight.
>

Should be fixed by https://github.com/numpy/numpy/pull/6955

`nosetests numpy` will still give test errors (6 right now), but only due
to not understanding KnownFailureException.

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

Re: [Numpy-discussion] Numpy 1.10.3 release.

[Ralf Gommers]

On Mon, Jan 4, 2016 at 9:38 PM, Charles R Harris 
wrote:
>
>
> The failed tests require pyrex, fortran, and swig. The refcount error
> comes and goes, probably the test isn't very good.  Ralf, is there any
> reason to keep the various extension building tests? They are very old.
>

There are f2py tests that are useful - if they fail then building anything
else with f2py fails as well. However those are all in f2py/tests/ IRRC,
not in distutils/tests.

>
> I don't know what the recommendation on using nosetests is,
>

Don't use it (it definitely gives test errors due to not having the
knownfailure plugin), use either runtests.py or numpy.test().


> but probably it is finding too many tests.
>

It's doing its job here in finding these though. It looks like these tests
need either fixing (the extensions aren't built) or removing. I'll have a
look tonight.

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

Re: [Numpy-discussion] Numpy 1.10.3 release.

[Charles R Harris]

On Sat, Jan 2, 2016 at 10:05 PM,  wrote:

> On Sat, Jan 2, 2016 at 4:47 PM, Charles R Harris
>  wrote:
> > Hi All,
> >
> > A significant segfault problem has been reported against Numpy 1.10.2
> and I
> > want to make a quick 1.10.3 release to get it fixed. Two questions
> >
> > What exactly is the release process that has been decided on? AFAIK, I
> > should just do a source release on Sourceforge, ping Matthew to produce
> > wheels for Mac and wait for him to put them on pypi, and then upload the
> > sources to pypi. No windows binaries are to be produced.
> > Is there anything else that needs fixing for 1.10.3?
>
>
> I'm running the 1.10.2 tests on Windows 10 in a virtualbox on Windows 8.1
> using Gohlke binary for MKL on a fresh Python 3.5
>
> This test
> "Test workarounds for 32-bit limited fwrite, fseek, and ftell ..."
> is taking a very long time. Is this expected?
>
>
> I get the following errors on Windows 10, and also on Windows 8.1
> Winpython 3.4 (except for the last "Unable to find vcvarsall.bat"
> because it's set up for compiling with mingw)
>
> Earlier I also got a ref count error message but I don't see it
> anymore, so maybe I messed up when trying Ctrl+C to kill the tests.
>
>
> ==
> ERROR: Failure: ImportError (cannot import name 'fib2')
> --
> Traceback (most recent call last):
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\failure.py",
> line 39, in runTest
> raise self.exc_val.with_traceback(self.tb)
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\loader.py",
> line 418, in loadTestsFromName
> addr.filename, addr.module)
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
> line 47, in importFromPath
> return self.importFromDir(dir_path, fqname)
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
> line 94, in importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
>   File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
> line 234, in load_module
> return load_source(name, filename, file)
>   File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
> line 172, in load_source
> module = _load(spec)
>   File "", line 693, in _load
>   File "", line 673, in _load_unlocked
>   File "", line 662, in exec_module
>   File "", line 222, in
> _call_with_frames_removed
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\numpy\distutils\tests\f2py_ext\tests\test_fib2.py",
> line 4, in 
> from f2py_ext import fib2
> ImportError: cannot import name 'fib2'
>
> ==
> ERROR: Failure: ImportError (cannot import name 'foo')
> --
> Traceback (most recent call last):
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\failure.py",
> line 39, in runTest
> raise self.exc_val.with_traceback(self.tb)
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\loader.py",
> line 418, in loadTestsFromName
> addr.filename, addr.module)
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
> line 47, in importFromPath
> return self.importFromDir(dir_path, fqname)
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
> line 94, in importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
>   File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
> line 234, in load_module
> return load_source(name, filename, file)
>   File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
> line 172, in load_source
> module = _load(spec)
>   File "", line 693, in _load
>   File "", line 673, in _load_unlocked
>   File "", line 662, in exec_module
>   File "", line 222, in
> _call_with_frames_removed
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\numpy\distutils\tests\f2py_f90_ext\tests\test_foo.py",
> line 4, in 
> from f2py_f90_ext import foo
> ImportError: cannot import name 'foo'
>
> ==
> ERROR: Failure: ImportError (cannot import name 'fib3')
> --
> Traceback (most recent call last):
>   File
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\failure.py",
> line 39, in runTest
> raise self.exc_val.with_traceback(self.tb)
>   File
> 

Re: [Numpy-discussion] Numpy 1.10.3 release.

[josef.pktd]

On Sun, Jan 3, 2016 at 12:05 AM,   wrote:
> On Sat, Jan 2, 2016 at 4:47 PM, Charles R Harris
>  wrote:
>> Hi All,
>>
>> A significant segfault problem has been reported against Numpy 1.10.2 and I
>> want to make a quick 1.10.3 release to get it fixed. Two questions
>>
>> What exactly is the release process that has been decided on? AFAIK, I
>> should just do a source release on Sourceforge, ping Matthew to produce
>> wheels for Mac and wait for him to put them on pypi, and then upload the
>> sources to pypi. No windows binaries are to be produced.
>> Is there anything else that needs fixing for 1.10.3?
>
>
> I'm running the 1.10.2 tests on Windows 10 in a virtualbox on Windows 8.1
> using Gohlke binary for MKL on a fresh Python 3.5
>
> This test
> "Test workarounds for 32-bit limited fwrite, fseek, and ftell ..."
> is taking a very long time. Is this expected?
>
>
> I get the following errors on Windows 10, and also on Windows 8.1
> Winpython 3.4 (except for the last "Unable to find vcvarsall.bat"
> because it's set up for compiling with mingw)
>
> Earlier I also got a ref count error message but I don't see it
> anymore, so maybe I messed up when trying Ctrl+C to kill the tests.
>
>
> ==
> ERROR: Failure: ImportError (cannot import name 'fib2')
> --
> Traceback (most recent call last):
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\failure.py",
> line 39, in runTest
> raise self.exc_val.with_traceback(self.tb)
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\loader.py",
> line 418, in loadTestsFromName
> addr.filename, addr.module)
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
> line 47, in importFromPath
> return self.importFromDir(dir_path, fqname)
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
> line 94, in importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
>   File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
> line 234, in load_module
> return load_source(name, filename, file)
>   File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
> line 172, in load_source
> module = _load(spec)
>   File "", line 693, in _load
>   File "", line 673, in _load_unlocked
>   File "", line 662, in exec_module
>   File "", line 222, in _call_with_frames_removed
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\numpy\distutils\tests\f2py_ext\tests\test_fib2.py",
> line 4, in 
> from f2py_ext import fib2
> ImportError: cannot import name 'fib2'
>
> ==
> ERROR: Failure: ImportError (cannot import name 'foo')
> --
> Traceback (most recent call last):
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\failure.py",
> line 39, in runTest
> raise self.exc_val.with_traceback(self.tb)
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\loader.py",
> line 418, in loadTestsFromName
> addr.filename, addr.module)
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
> line 47, in importFromPath
> return self.importFromDir(dir_path, fqname)
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
> line 94, in importFromDir
> mod = load_module(part_fqname, fh, filename, desc)
>   File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
> line 234, in load_module
> return load_source(name, filename, file)
>   File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
> line 172, in load_source
> module = _load(spec)
>   File "", line 693, in _load
>   File "", line 673, in _load_unlocked
>   File "", line 662, in exec_module
>   File "", line 222, in _call_with_frames_removed
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\numpy\distutils\tests\f2py_f90_ext\tests\test_foo.py",
> line 4, in 
> from f2py_f90_ext import foo
> ImportError: cannot import name 'foo'
>
> ==
> ERROR: Failure: ImportError (cannot import name 'fib3')
> --
> Traceback (most recent call last):
>   File 
> "c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\failure.py",
> line 39, in runTest
> raise self.exc_val.with_traceback(self.tb)
>   File 
> 

Re: [Numpy-discussion] Numpy 1.10.3 release.

[Charles R Harris]

On Sat, Jan 2, 2016 at 4:51 PM, Matthew Brett 
wrote:

> Hi,
>
> On Sat, Jan 2, 2016 at 9:47 PM, Charles R Harris
>  wrote:
> > Hi All,
> >
> > A significant segfault problem has been reported against Numpy 1.10.2
> and I
> > want to make a quick 1.10.3 release to get it fixed. Two questions
> >
> > What exactly is the release process that has been decided on? AFAIK, I
> > should just do a source release on Sourceforge, ping Matthew to produce
> > wheels for Mac and wait for him to put them on pypi, and then upload the
> > sources to pypi.
>
> You're welcome to ping me to do the Mac wheels, but I'd be even
> happier if you could have a go at triggering the build, to see if you
> can make it work:
>
> https://github.com/MacPython/numpy-wheels


Hmm... Since it needs to build off the tag to have the correct behavior, I
assume that that needs to be set explicitly. Also, it didn't look as if
your last pypi uploads were signed. Did you upload with twine?

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

[Numpy-discussion] Numpy 1.10.3 release.

[Charles R Harris]

Hi All,

A significant segfault problem has been reported against Numpy 1.10.2 and I
want to make a quick 1.10.3 release to get it fixed. Two questions


   - What exactly is the release process that has been decided on? AFAIK, I
   should just do a source release on Sourceforge, ping Matthew to produce
   wheels for Mac and wait for him to put them on pypi, and then upload the
   sources to pypi. No windows binaries are to be produced.
   - Is there anything else that needs fixing for 1.10.3?

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

Re: [Numpy-discussion] Numpy 1.10.3 release.

[Matthew Brett]

Hi,

On Sat, Jan 2, 2016 at 9:47 PM, Charles R Harris
 wrote:
> Hi All,
>
> A significant segfault problem has been reported against Numpy 1.10.2 and I
> want to make a quick 1.10.3 release to get it fixed. Two questions
>
> What exactly is the release process that has been decided on? AFAIK, I
> should just do a source release on Sourceforge, ping Matthew to produce
> wheels for Mac and wait for him to put them on pypi, and then upload the
> sources to pypi.

You're welcome to ping me to do the Mac wheels, but I'd be even
happier if you could have a go at triggering the build, to see if you
can make it work:

https://github.com/MacPython/numpy-wheels

Cheers,

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

Re: [Numpy-discussion] Numpy 1.10.3 release.

[Matthew Brett]

On Sun, Jan 3, 2016 at 12:01 AM, Charles R Harris
 wrote:
>
>
> On Sat, Jan 2, 2016 at 4:51 PM, Matthew Brett 
> wrote:
>>
>> Hi,
>>
>> On Sat, Jan 2, 2016 at 9:47 PM, Charles R Harris
>>  wrote:
>> > Hi All,
>> >
>> > A significant segfault problem has been reported against Numpy 1.10.2
>> > and I
>> > want to make a quick 1.10.3 release to get it fixed. Two questions
>> >
>> > What exactly is the release process that has been decided on? AFAIK, I
>> > should just do a source release on Sourceforge, ping Matthew to produce
>> > wheels for Mac and wait for him to put them on pypi, and then upload the
>> > sources to pypi.
>>
>> You're welcome to ping me to do the Mac wheels, but I'd be even
>> happier if you could have a go at triggering the build, to see if you
>> can make it work:
>>
>> https://github.com/MacPython/numpy-wheels
>
>
> Hmm... Since it needs to build off the tag to have the correct behavior, I
> assume that that needs to be set explicitly.

No, the build system uses a script I wrote to find the tag closest in
development history to master, by default - see :
http://stackoverflow.com/a/24557377/1939576

So, if you push a tag, then trigger a build, there's a good chance
that will do what you want.  If not, then you can set the tag or
commit explicitly at :

https://github.com/MacPython/numpy-wheels/blob/master/.travis.yml#L5

> Also, it didn't look as if your
> last pypi uploads were signed. Did you upload with twine?

I did yes - with a custom uploader script [1], but I guess it would be
better to download, sign, then upload again using some other mechanism
that preserves the signature.

Cheers,

Matthew

[1] https://github.com/MacPython/terryfy/blob/master/wheel-uploader
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Numpy 1.10.3 release.

[josef.pktd]

On Sat, Jan 2, 2016 at 4:47 PM, Charles R Harris
 wrote:
> Hi All,
>
> A significant segfault problem has been reported against Numpy 1.10.2 and I
> want to make a quick 1.10.3 release to get it fixed. Two questions
>
> What exactly is the release process that has been decided on? AFAIK, I
> should just do a source release on Sourceforge, ping Matthew to produce
> wheels for Mac and wait for him to put them on pypi, and then upload the
> sources to pypi. No windows binaries are to be produced.
> Is there anything else that needs fixing for 1.10.3?


I'm running the 1.10.2 tests on Windows 10 in a virtualbox on Windows 8.1
using Gohlke binary for MKL on a fresh Python 3.5

This test
"Test workarounds for 32-bit limited fwrite, fseek, and ftell ..."
is taking a very long time. Is this expected?


I get the following errors on Windows 10, and also on Windows 8.1
Winpython 3.4 (except for the last "Unable to find vcvarsall.bat"
because it's set up for compiling with mingw)

Earlier I also got a ref count error message but I don't see it
anymore, so maybe I messed up when trying Ctrl+C to kill the tests.


==
ERROR: Failure: ImportError (cannot import name 'fib2')
--
Traceback (most recent call last):
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\failure.py",
line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\loader.py",
line 418, in loadTestsFromName
addr.filename, addr.module)
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
line 47, in importFromPath
return self.importFromDir(dir_path, fqname)
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
line 94, in importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
line 234, in load_module
return load_source(name, filename, file)
  File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
line 172, in load_source
module = _load(spec)
  File "", line 693, in _load
  File "", line 673, in _load_unlocked
  File "", line 662, in exec_module
  File "", line 222, in _call_with_frames_removed
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\numpy\distutils\tests\f2py_ext\tests\test_fib2.py",
line 4, in 
from f2py_ext import fib2
ImportError: cannot import name 'fib2'

==
ERROR: Failure: ImportError (cannot import name 'foo')
--
Traceback (most recent call last):
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\failure.py",
line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\loader.py",
line 418, in loadTestsFromName
addr.filename, addr.module)
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
line 47, in importFromPath
return self.importFromDir(dir_path, fqname)
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
line 94, in importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
line 234, in load_module
return load_source(name, filename, file)
  File "c:\users\josef\appdata\local\programs\python\python35\lib\imp.py",
line 172, in load_source
module = _load(spec)
  File "", line 693, in _load
  File "", line 673, in _load_unlocked
  File "", line 662, in exec_module
  File "", line 222, in _call_with_frames_removed
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\numpy\distutils\tests\f2py_f90_ext\tests\test_foo.py",
line 4, in 
from f2py_f90_ext import foo
ImportError: cannot import name 'foo'

==
ERROR: Failure: ImportError (cannot import name 'fib3')
--
Traceback (most recent call last):
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\failure.py",
line 39, in runTest
raise self.exc_val.with_traceback(self.tb)
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\loader.py",
line 418, in loadTestsFromName
addr.filename, addr.module)
  File 
"c:\users\josef\appdata\local\programs\python\python35\lib\site-packages\nose\importer.py",
line 47, in importFromPath
return self.importFromDir(dir_path, fqname)