Re: [Numpy-discussion] Deprecating `numpy.iterable`

Oh wow, yeah, there are tons of uses: https://github.com/search?q=%22np.iterable%22=simplesearch=Code=%E2%9C%93 Meh, I dunno, maybe we're stuck with it. It's not a major maintenance burden at least. -n On Thu, Feb 11, 2016 at 10:25 AM, Stephan Hoyer wrote: > We certainly

Re: [Numpy-discussion] Deprecating `numpy.iterable`

Huh... matplotlib could use that! We have been using our own internal function left over from the numerix days, I think. Ben Root On Thu, Feb 11, 2016 at 2:12 PM, Nathaniel Smith wrote: > Oh wow, yeah, there are tons of uses: > >

Re: [Numpy-discussion] Deprecating `numpy.iterable`

It appears that deprecating `numpy.iterable` would be counterproductive. I have reverted my PR to just making the return value an actual `bool` instead of an `int`. On Thu, Feb 11, 2016 at 2:54 PM, Benjamin Root wrote: > Huh... matplotlib could use that! We have been using

[Numpy-discussion] Build fortran extension on Windows with gfortran and MSVC

Hi! It seems that on Windows + Python-3.5 fortran extensions cannot be built anymore with f2py and mingw32 compilers, because of new MSVC. Here is the short description of the errors one gets:

Re: [Numpy-discussion] Build fortran extension on Windows with gfortran and MSVC

Hi, On 11 February 2016 at 15:40, Marek Wojciechowski wrote: > It seems that on Windows + Python-3.5 fortran extensions cannot be built > anymore with f2py and mingw32 compilers, because of new MSVC. Here is the > short description of the errors one gets: > Off-topic, but

Re: [Numpy-discussion] Hook in __init__.py to let distributors patch numpy

+1. This seems nicer than patching __init__.py itself, in that it is much more transparent. Good idea. Michael On Thu, Feb 11, 2016 at 7:19 PM Matthew Brett wrote: > Hi, > > Over at https://github.com/numpy/numpy/issues/5479 we're discussing > Windows wheels. > > On

[Numpy-discussion] Hook in __init__.py to let distributors patch numpy

Hi, Over at https://github.com/numpy/numpy/issues/5479 we're discussing Windows wheels. On thing that we would like to be able to ship Windows wheels, is to be able to put some custom checks into numpy when you build the wheels. Specifically, for Windows, we're building on top of ATLAS BLAS /

Re: [Numpy-discussion] Build fortran extension on Windows with gfortran and MSVC

Dnia czwartek, 11 lutego 2016 16:40:22 Marek Wojciechowski pisze: > Hi! > > It seems that on Windows + Python-3.5 fortran extensions cannot be built > anymore with f2py and mingw32 compilers, because of new MSVC. Here is the > short description of the errors one gets: > >

Re: [Numpy-discussion] Build fortran extension on Windows with gfortran and MSVC

Dnia czwartek, 11 lutego 2016 16:23:23 Jose Gomez-Dans pisze: > Hi, > > On 11 February 2016 at 15:40, Marek Wojciechowski wrote: > > It seems that on Windows + Python-3.5 fortran extensions cannot be built > > anymore with f2py and mingw32 compilers, because of new MSVC. Here

Re: [Numpy-discussion] Deprecating `numpy.iterable`

We certainly can (and probably should) deprecate this, but we can't remove it for a very long time. np.iterable is used in a lot of third party code. On Wed, Feb 10, 2016 at 7:09 PM, Joseph Fox-Rabinovitz < jfoxrabinov...@gmail.com> wrote: > I have created a PR to deprecate `np.iterable` >