Re: [Numpy-discussion] axis parameter for count_nonzero

for help as *@juliantaylor* pointed out. The *scipy* library has dealt with this problem as well in its *sparse* modules, so that is also a useful resource. Feedback on this issue would be much appreciated! Thanks! On Sun, May 22, 2016 at 1:36 PM, G Young <gfyoun...@gmail.com>

Re: [Numpy-discussion] broadcasting for randint

maintainers* so as to help get this merged! Thanks! On Tue, Jun 7, 2016 at 1:23 PM, G Young <gfyoun...@gmail.com> wrote: > There seems to be a push in my PR now for using Tempita as a way to solve > this issue with the ad-hoc templating. However, before I go about > attempting this, it

Re: [Numpy-discussion] broadcasting for randint

, 2016 at 3:04 AM, G Young <gfyoun...@gmail.com> wrote: > Just wanted to ping the mailing list again in case this email (see below) > got lost in your inboxes. Would be great to get some feedback on this! > Thanks! > > On Sun, May 22, 2016 at 2:15 AM, G Young <gfyoun...@g

Re: [Numpy-discussion] broadcasting for randint

Just wanted to ping the mailing list again in case this email (see below) got lost in your inboxes. Would be great to get some feedback on this! Thanks! On Sun, May 22, 2016 at 2:15 AM, G Young <gfyoun...@gmail.com> wrote: > Hi, > > I have had a PR <https://github.com/num

Re: [Numpy-discussion] axis parameter for count_nonzero

@juliantaylor* pointed out. The *scipy* library has dealt with this problem as well in its *sparse* modules, so that is also a useful resource. On Sun, May 22, 2016 at 1:35 PM, G Young <gfyoun...@gmail.com> wrote: > 1) Correction: The PR was not written with small arrays in m

Re: [Numpy-discussion] axis parameter for count_nonzero

to be a large technical brick wall up against such an implementation. So suggestions about how to move the code into C would be welcome too! On Sun, May 22, 2016 at 10:32 AM, Ralf Gommers <ralf.gomm...@gmail.com> wrote: > > > On Sun, May 22, 2016 at 3:05 AM, G Young <gfyoun..

Re: [Numpy-discussion] broadcasting for randint

Hi, I have had a PR open for quite some time now that allows arguments to broadcast in *randint*. While the functionality is fully in-place and very robust, the obstacle at this point is the implementation. When the *dtype* parameter was added to

Re: [Numpy-discussion] axis parameter for count_nonzero

Hi, I have had a PR open (first draft can be found here ) for quite some time now that adds an 'axis' parameter to *count_nonzero*. While the functionality is fully in-place, very robust, and actually

Re: [Numpy-discussion] linux wheels coming soon

Actually, conda pip will install the wheels that you put up. The good news is: they all (by which I mean *numpy* and *scipy* both on 2.7 and 3.5) pass! On Thu, Apr 14, 2016 at 7:26 PM, Matthew Brett wrote: > Hi, > > On Thu, Apr 14, 2016 at 11:11 AM, Benjamin Root

Re: [Numpy-discussion] linux wheels coming soon

Matthew, you are correct. A lot of things happened with random integer generation recently (including deprecating random_integers), but I believe those warnings should be squashed in the up and coming version of SciPy from what I remember. On Mon, Apr 4, 2016 at 6:47 PM, Matthew Brett

Re: [Numpy-discussion] fromnumeric.py internal calls

s. > Perhaps it's worth testing this change against third party array libraries > that implement their own array like classes? Off the top of my head, maybe > scipy, pandas, dask, astropy, pint, xarray? > On Wed, Feb 24, 2016 at 3:40 AM G Young <gfyoun...@gmail.com> wrote: > &g

Re: [Numpy-discussion] fromnumeric.py internal calls

Hello all, I have PR #7325 up that changes the internal calls for functions in *fromnumeric.py* from positional arguments to keyword arguments. I made this change for two reasons: 1) It is consistent with the external function signature 2) The

Re: [Numpy-discussion] making "low" optional in numpy.randint

Your statement is a little self-contradictory, but in any case, you shouldn't worry about random_integers getting removed from the code-base. However, it has been deprecated in favor of randint. On Wed, Feb 17, 2016 at 11:48 PM, Juan Nunez-Iglesias wrote: > Also fwiw, I

Re: [Numpy-discussion] making "low" optional in numpy.randint

t; > On Mi, 2016-02-17 at 20:48 +, Robert Kern wrote: > > > On Wed, Feb 17, 2016 at 8:43 PM, G Young <gfyoun...@gmail.com> > > > wrote: > > > > > > > Josef: I don't think we are making people think more. They're > > > > all > > &

Re: [Numpy-discussion] making "low" optional in numpy.randint

6 at 8:48 PM, Robert Kern <robert.k...@gmail.com> wrote: > On Wed, Feb 17, 2016 at 8:43 PM, G Young <gfyoun...@gmail.com> wrote: > > > Josef: I don't think we are making people think more. They're all > keyword arguments, so if you don't want to think about them, then

Re: [Numpy-discussion] making "low" optional in numpy.randint

hub.com/numpy/numpy/issues/6790> and the PR's that followed so that you have a better understanding as to why this 'weird' behavior was chosen. On Wed, Feb 17, 2016 at 8:30 PM, Alan Isaac <alan.is...@gmail.com> wrote: > On 2/17/2016 12:28 PM, G Young wrote: > >> Perhaps, but

Re: [Numpy-discussion] making "low" optional in numpy.randint

...@gmail.com> wrote: > On Wed, Feb 17, 2016 at 1:37 PM, <josef.p...@gmail.com> wrote: > > > > > > On Wed, Feb 17, 2016 at 10:01 AM, G Young <gfyoun...@gmail.com> wrote: > >> > >> Hello all, > >> > >> I have a PR open here tha

Re: [Numpy-discussion] making "low" optional in numpy.randint

Perhaps, but we are not coding in Haskell. We are coding in Python, and the standard is that the endpoint is excluded, which renders your point moot I'm afraid. On Wed, Feb 17, 2016 at 5:10 PM, Alan Isaac wrote: > On 2/17/2016 11:46 AM, Robert Kern wrote: > >> some at

Re: [Numpy-discussion] making "low" optional in numpy.randint

Actually, it has already been deprecated because I did it myself. :) On Wed, Feb 17, 2016 at 4:46 PM, Robert Kern wrote: > On Wed, Feb 17, 2016 at 4:40 PM, Alan Isaac wrote: > > > > Behavior of random integer generation: > > Python randint[a,b]

Re: [Numpy-discussion] making "low" optional in numpy.randint

Hello all, I have a PR open here that makes "low" an optional parameter in numpy.randint and introduces new behavior into the API as follows: 1) `low == None` and `high == None` Numbers are generated over the range `[lowbnd, highbnd)`, where `lowbnd =

Re: [Numpy-discussion] building NumPy with gcc if Python was built with icc?!?

I'm not sure about anyone else, but having been playing around with both gcc and icc, I'm afraid you might be out of luck. Is there any reason why you can't use a Python distribution built with gcc? On Tue, Feb 16, 2016 at 7:39 PM, BERGER Christian wrote: > Hi All, >

Re: [Numpy-discussion] Fwd: Windows wheels for testing

I've actually had test failures on occasion (i.e. when I run "numpy.test()") with his builds but overall, they are quite good. Speaking of MKL, for anyone who uses conda, does anyone know if it is possible to link the "mkl" package to the numpy source? My first guess is no since the description

Re: [Numpy-discussion] Fwd: Windows wheels for testing

AFAIK the vcvarsall.bat error occurs when your MSVC directories aren't properly linked in your system registry, so Python cannot find the file. This is not a numpy-specific issue, so I certainly would agree that that failure is not blocking. Other than that, this build contains the mingw32.lib

Re: [Numpy-discussion] Building Numpy with OpenBLAS

rgeted to build numpy with OpenBLAS. > > Carl > > 2016-01-27 16:01 GMT+01:00 Ralf Gommers <ralf.gomm...@gmail.com>: > >> >> >> On Wed, Jan 27, 2016 at 3:51 PM, G Young <gfyoun...@gmail.com> wrote: >> >>> I don't need it at this point. I'm

Re: [Numpy-discussion] Building Numpy with OpenBLAS

Hello all, I'm trying to update the documentation for building Numpy from source, and I've hit a brick wall in trying to build the library using OpenBLAS because I can't seem to link the libopenblas.dll file. I tried following the suggestion of placing the DLL in numpy/core as suggested here

Re: [Numpy-discussion] Building Numpy with OpenBLAS

t;> >>> One very helpful tool in diagnosing dll problems is dependency walker: >>> http://www.dependencywalker.com/ >>> >>> It may be that your openblas has a dependency that it can't load for >>> some reason. Dependency walker works on .pyd files as well as .dll

Re: [Numpy-discussion] Building Numpy with OpenBLAS

y helpful tool in diagnosing dll problems is dependency walker: > http://www.dependencywalker.com/ > > It may be that your openblas has a dependency that it can't load for some > reason. Dependency walker works on .pyd files as well as .dll files. > > Hth, > Michael > > On

Re: [Numpy-discussion] Building Numpy with OpenBLAS

file, called the import library. The .dll is used at > runtime, not at link time. This is different from *nix, where the .so > serves both purposes. The link you posted mentions import files, so I hope > this is helpful information. > > Best, > Michael > > On Wed, Jan 27, 2016

Re: [Numpy-discussion] Appveyor Testing Changes

wrote: > > > On Tue, Jan 26, 2016 at 2:13 AM, G Young <gfyoun...@gmail.com> wrote: > >> Ah, yes, that is true. That point had completely escaped my mind. In >> light of this, it seems that it's not worth the while then to completely >> switch over to pip +

Re: [Numpy-discussion] Appveyor Testing Changes

Hello all, I currently have a branch on my fork (not PR) where I am experimenting with running Appveyor CI via Virtualenv instead of Conda. I have build running here . What do people think of using Virtualenv (as we do on Travis)

Re: [Numpy-discussion] Appveyor Testing Changes

10:50 PM, Nathaniel Smith <n...@pobox.com> wrote: > On Mon, Jan 25, 2016 at 2:37 PM, G Young <gfyoun...@gmail.com> wrote: > > Hello all, > > > > I currently have a branch on my fork (not PR) where I am experimenting > with > > running Appveyor CI via Virt

Re: [Numpy-discussion] Appveyor Testing Changes

be expanded, though I'm not sure how prudent that is given how slow Appveyor tests run. Greg On Tue, Jan 26, 2016 at 12:13 AM, Bryan Van de Ven <bry...@continuum.io> wrote: > > > On Jan 25, 2016, at 5:21 PM, G Young <gfyoun...@gmail.com> wrote: > > > > With regards to

Re: [Numpy-discussion] Behavior of np.random.uniform

Of the methods defined in *numpy/mtrand.pyx* (excluding helper functions and *random_integers*, as they are all related to *randint*), *randint* is the only other function with *low* and *high* parameters. However, it enforces *high* > *low*. Greg On Tue, Jan 19, 2016 at 1:36 PM, Benjamin Root

Re: [Numpy-discussion] Behavior of np.random.uniform

; on both ends, so order doesn't matter, though if it raises for b<a, then > that's a precedent we could follow. > > (Sorry, on a phone, can't check) > > CHB > > > > On Jan 19, 2016, at 6:21 AM, G Young <gfyoun...@gmail.com> wrote: > > Of the metho

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

Hello all, Turns out I needed to do a complete re-installation of essentially everything that was involved in my Numpy setup. Now everything is working just fine! Cheers, Greg On Tue, Jan 5, 2016 at 7:45 AM, G Young <gfyoun...@gmail.com> wrote: > Sure. I'm running Windows 7 wi

[Numpy-discussion] Building master issues on Windows

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

Re: [Numpy-discussion] deprecate random.random_integers

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?

Re: [Numpy-discussion] dtype random.rand

Hello, Issue #6790 had requested the enhancement of adding the dtype argument to both random.randint and random.rand. With #6910 merged in, that addresses the first half of the request. What do people think

[Numpy-discussion] Fwd: Python 3.3 i386 Build

I accidentally subscribed to the defunct discussion mailing list, so my email got rejected the first time I sent to the active mailing list. My question is in the forwarded email below: -- Forwarded message -- From: G Young <gfyoun...@gmail.com> Date: Mon, Dec 14, 2015 at 3