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] Windows build/distribute plan & MingwPy funding

[Matthew Brett]

Hi,

On Mon, Jan 4, 2016 at 5:35 PM, Erik Bray  wrote:
> On Sat, Jan 2, 2016 at 3:20 AM, Ralf Gommers  wrote:
>> Hi all,
>>
>> You probably know that building Numpy, Scipy and the rest of the Scipy Stack
>> on Windows is problematic. And that there are plans to adopt the static
>> MinGW-w64 based toolchain that Carl Kleffner has done a lot of work on for
>> the last two years to fix that situation.
>>
>> The good news is: this has become a lot more concrete just now, with this
>> proposal for funding: http://mingwpy.github.io/proposal_december2015.html
>>
>> Funding for phases 1 and 2 is already confirmed; the phase 3 part has been
>> submitted to the PSF. Phase 1 (of $1000) is funded by donations made to
>> Numpy and Scipy (through NumFOCUS), and phase 2 (of $4000) by NumFOCUS
>> directly. So a big thank you to everyone who made a donation to Numpy, Scipy
>> and NumFOCUS!
>>
>> I hope that that proposal gives a clear idea of the work that's going to be
>> done over the next months. Note that the http://mingwpy.github.io contains a
>> lot more background info, description of technical issues, etc.
>>
>> Feedback & ideas very welcome of course!
>>
>> Cheers,
>> Ralf
>
> Hi Ralph,
>
> I've seen you drop hints about this recently, and am interested to
> follow this work.  I've been hired as part of the OpenDreamKit project
> to work, in large part, on developing a sensible toolchain for
> building and distributing Sage on Windows.  I know you've been
> following the thread on that too.  Although the primary goal there is
> "whatever works", I'm personally inclined to focus on the mingwpy /
> mingw-w64 approach, due in large part with my past success with the
> MinGW 32-bit toolchain.  (I personally have a desire to improve
> support for building with MSVC as well, but that's a less important
> goal as far as the funding is concerned.)
>
> So anyways, please keep me in the loop about this, as I will also be
> putting effort into this over the next year as well.  Has there been
> any discussion about setting up a mailing list specifically for this
> project?

Yes, it exists already, but not well advertised :
https://groups.google.com/forum/#!forum/mingwpy

It would be great to share work.

Cheers,

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

Re: [Numpy-discussion] deprecate random.random_integers

[Robert Kern]

On Sun, Jan 3, 2016 at 11:51 PM, G Young  wrote:
>
> Hello all,
>
> In light of the discussion in #6910, I have gone ahead and deprecated
random_integers in my most recent PR here.  As this is an API change (sort
of), what are people's thoughts on this deprecation?

I'm reasonably in favor. random_integers() with its closed-interval
convention only exists because it existed in Numeric's RandomArray module.
The closed-interval convention was broadly been considered to be a mistake
introduced early in the stdlib random module and rectified with the
introduction and promotion of random.randrange() instead.

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

[Numpy-discussion] 1.10.3 release tomorrow, 1.11.x branch this month.

[Charles R Harris]

Hi All,

I'm going to attempt a 1.10.3 release tomorrow to address the segfault
reported in #6922 .

I'd also like to branch 1.11.x sometime this month, hopefully around Jan 18
(two weeks from now). There are some unresolved issues, in particular
__numpy_ufunc__, but there is plenty of accumulated material and I'd like
to get something out before the tinder buildup constitutes a fire hazard.
Releases generate plenty of sparks and it would be good if the 1.11.0
release was less flamable than the 1.10 release was. I will take a look
through the current bug fix PRs with intent to merge as many as possible
before the branch, but enhancements will not be a high priority except for
a couple that have been sitting ready in the queue for awhile. If there are
some enhancements that you think need to be in the release, mention them
here.

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

Re: [Numpy-discussion] Building master issues on Windows

[Jaime Fernández del Río]

On Tue, Jan 5, 2016 at 3:15 AM, G Young  wrote:

> Hello all,
>
> I've recently encountered issues building numpy off master on Windows in
> which setup.py complains that it can't find the Advapi library in any
> directories (which is an empty list).  I scanned the DLL under System32 and
> ran /sfc scannow as Administrator, and both came up clean.  Is anyone else
> encountering (or can reproduce) this issue, or is it just me?  Any
> suggestions about how to resolve this problem?
>

Can you give more details on your setup?

Jaime

(\__/)
( O.o)
( > <) Este es Conejo. Copia a Conejo en tu firma y ayúdale en sus planes
de dominación mundial.
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
https://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Building master issues on Windows

[G Young]

Hello all,

I've recently encountered issues building numpy off master on Windows in which 
setup.py complains that it can't find the Advapi library in any directories 
(which is an empty list).  I scanned the DLL under System32 and ran /sfc 
scannow as Administrator, and both came up clean.  Is anyone else encountering 
(or can reproduce) this issue, or is it just me?  Any suggestions about how to 
resolve this problem?

Thanks!

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

Re: [Numpy-discussion] Windows build/distribute plan & MingwPy funding

[Erik Bray]

On Sat, Jan 2, 2016 at 3:20 AM, Ralf Gommers  wrote:
> Hi all,
>
> You probably know that building Numpy, Scipy and the rest of the Scipy Stack
> on Windows is problematic. And that there are plans to adopt the static
> MinGW-w64 based toolchain that Carl Kleffner has done a lot of work on for
> the last two years to fix that situation.
>
> The good news is: this has become a lot more concrete just now, with this
> proposal for funding: http://mingwpy.github.io/proposal_december2015.html
>
> Funding for phases 1 and 2 is already confirmed; the phase 3 part has been
> submitted to the PSF. Phase 1 (of $1000) is funded by donations made to
> Numpy and Scipy (through NumFOCUS), and phase 2 (of $4000) by NumFOCUS
> directly. So a big thank you to everyone who made a donation to Numpy, Scipy
> and NumFOCUS!
>
> I hope that that proposal gives a clear idea of the work that's going to be
> done over the next months. Note that the http://mingwpy.github.io contains a
> lot more background info, description of technical issues, etc.
>
> Feedback & ideas very welcome of course!
>
> Cheers,
> Ralf

Hi Ralph,

I've seen you drop hints about this recently, and am interested to
follow this work.  I've been hired as part of the OpenDreamKit project
to work, in large part, on developing a sensible toolchain for
building and distributing Sage on Windows.  I know you've been
following the thread on that too.  Although the primary goal there is
"whatever works", I'm personally inclined to focus on the mingwpy /
mingw-w64 approach, due in large part with my past success with the
MinGW 32-bit toolchain.  (I personally have a desire to improve
support for building with MSVC as well, but that's a less important
goal as far as the funding is concerned.)

So anyways, please keep me in the loop about this, as I will also be
putting effort into this over the next year as well.  Has there been
any discussion about setting up a mailing list specifically for this
project?

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