[Numpy-discussion] 1.10.x is branched

Hi All, Numpy 1.10.x is branched. There is still some cleanup to do before the alpha release, but that should be coming in a couple of days. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-

[Numpy-discussion] mailmap update

Hi All, I'm trying to update the .mailmap file on github and could use some help. The current version seems common to both numpy and scipy, hence the crosspost. Here is what I've got so far. Alex Griffing ncsu.edu> alex ncsu.edu> Alex Griffing ncsu.edu> argriffing ncsu.edu> Alex Griffing nc

[Numpy-discussion] Branching 1.10 Sunday, Aug 2.

Hi All, Just a heads up. If anything absolutely needed has been left out, please make a noise. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] 1,10 and 1.11 releases

Hi All, I plan on branching 1.10 this next weekend and the `__numpy_ufunc__` work will be pushed off to 1.11. One of the things we discussed at SciPy 2015 was the need for a faster release cycle. If we are going to manage that we need to start planning now by picking a release manager, listing th

Re: [Numpy-discussion] Video meeting this week

Any of those times would work for me. On Mon, Jun 29, 2015 at 3:14 PM, Nathaniel Smith wrote: > On Mon, Jun 29, 2015 at 9:04 AM, Nathaniel Smith wrote: > > On Jun 26, 2015 2:32 AM, "Nathaniel Smith" wrote: > >> > >> Hi all, > >> > >> In a week and a half, this is happening: > >> > >> https

Re: [Numpy-discussion] Clarification sought on Scipy Numpy version requirements.

On Sun, Jun 21, 2015 at 11:49 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Sun, Jun 21, 2015 at 9:57 AM, Ralf Gommers > wrote: > >> >> >> On Sun, Jun 21, 2015 at 5:45 PM, Charles R Harris < >> charlesr.har...@gmail.com> wr

Re: [Numpy-discussion] Clarification sought on Scipy Numpy version requirements.

On Sun, Jun 21, 2015 at 9:57 AM, Ralf Gommers wrote: > > > On Sun, Jun 21, 2015 at 5:45 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Sun, Jun 21, 2015 at 9:31 AM, Ralf Gommers >> wrote: >> >>&g

Re: [Numpy-discussion] Clarification sought on Scipy Numpy version requirements.

On Sun, Jun 21, 2015 at 9:31 AM, Ralf Gommers wrote: > > > On Sun, Jun 21, 2015 at 5:13 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> >> On Sun, Jun 21, 2015 at 7:14 AM, Ralf Gommers >> wrote: >> >&

Re: [Numpy-discussion] Clarification sought on Scipy Numpy version requirements.

On Sun, Jun 21, 2015 at 7:14 AM, Ralf Gommers wrote: > > > On Fri, Jun 19, 2015 at 11:52 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Fri, Jun 19, 2015 at 3:05 PM, Sturla Molden >> wrote: >> >>> Charles

Re: [Numpy-discussion] Removal of Deprecated Keywords/functionality

On Sat, Jun 20, 2015 at 3:32 PM, Nathaniel Smith wrote: > On Jun 20, 2015 1:43 PM, "Charles R Harris" > wrote: > > > > Hi All, > > > > There are three long ago deprecations that I am not sure how to handle. > > > > keywords skiprows and m

Re: [Numpy-discussion] I can't tell if Numpy is configured properly with show_config()

On Sat, Jun 20, 2015 at 2:08 PM, Elliot Hallmark wrote: > Sebastian, in the slow virtual-env, _dotblas.so isn't there. I only have > _dummy.so > > On Sat, Jun 20, 2015 at 3:02 PM, Elliot Hallmark > wrote: > >> Well, here is the question that started this all. In the slow >> environment, blas s

[Numpy-discussion] Removal of Deprecated Keywords/functionality

Hi All, There are three long ago deprecations that I am not sure how to handle. - keywords skiprows and missing in genfromtxt, deprecated in 1.5. - keyword old_behavior (default False) in correlate. added in 1.5 at least, but default value changed later. The documentation says they wil

Re: [Numpy-discussion] Clarification sought on Scipy Numpy version requirements.

On Fri, Jun 19, 2015 at 3:05 PM, Sturla Molden wrote: > Charles R Harris wrote: > > > I'm looking to change some numpy deprecations into errors as well as > remove > > some deprecated functions. The problem I see is that > > SciPy claims to support Numpy >=

[Numpy-discussion] Clarification sought on Scipy Numpy version requirements.

Hi All, I'm looking to change some numpy deprecations into errors as well as remove some deprecated functions. The problem I see is that SciPy claims to support Numpy >= 1.5 and Numpy 1.5 is really, really, old. So the question is, does "support" mean compiles with earlier versions of Numpy ? If t

[Numpy-discussion] 1.10 release

Hi All, I plan to branch the 1.10 release next Monday. I expect this to be a difficult release, much time has passed since 1.9 and there have been significant enhancements/changes to masked arrays, structured array assigment, and recored arrays. In addition, most ufuncs no longer return `NotImplem

Re: [Numpy-discussion] Open CV 3.0 + NPY_RELAXED_STRIDES

On Wed, Jun 10, 2015 at 7:02 PM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote: > On Wed, Jun 10, 2015 at 5:53 PM, Jaime Fernández del Río < > jaime.f...@gmail.com> wrote: > >> I'm in the midst of a Python 3.5 + MSVS 2015 compilation frenzy. Today it >> was time for Open CV 3.0, where I fo

Re: [Numpy-discussion] NumPy + Python 3.5 + Windows + VS2015

On Tue, Jun 9, 2015 at 5:12 PM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote: > On Mon, Jun 8, 2015 at 3:11 PM, Jaime Fernández del Río < > jaime.f...@gmail.com> wrote: > >> I have just unsuccessfully tried to build numpy under Windows for Python >> 3.5, using the latest release candidate

Re: [Numpy-discussion] matmul needs some clarification.

On Thu, Jun 4, 2015 at 6:50 PM, Alexander Belopolsky wrote: > > On Wed, Jun 3, 2015 at 5:12 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> but is as good as dot right now except it doesn't handle object arrays. > > > > This is a fairl

Re: [Numpy-discussion] DEP: Deprecate boolean array indices with non-matching shape #4353

On Thu, Jun 4, 2015 at 6:26 PM, Charles R Harris wrote: > Hi All, > > I've not strong feelings one way or the other on this proposed deprecation > for numpy 1.10 and would like some feedback from interested users. > Umm, link is #4353 <https://github.com/numpy/n

[Numpy-discussion] DEP: Deprecate boolean array indices with non-matching shape #4353

Hi All, I've not strong feelings one way or the other on this proposed deprecation for numpy 1.10 and would like some feedback from interested users. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listin

Re: [Numpy-discussion] matmul needs some clarification.

On Wed, Jun 3, 2015 at 1:38 PM, Alexander Belopolsky wrote: > > On Sat, May 30, 2015 at 6:23 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> The problem arises when multiplying a stack of matrices times a vector. >> PEP465 defines this as appending

Re: [Numpy-discussion] matmul needs some clarification.

On Wed, Jun 3, 2015 at 2:25 PM, Stephan Hoyer wrote: > On Sat, May 30, 2015 at 3:23 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> The problem arises when multiplying a stack of matrices times a vector. >> PEP465 defines this as appending a '1&

[Numpy-discussion] matmul needs some clarification.

Hi All, The problem arises when multiplying a stack of matrices times a vector. PEP465 defines this as appending a '1' to the dimensions of the vector and doing the defined stacked matrix multiply, then removing the last dimension from the result. Note that in the middle step we have a stack of ma

Re: [Numpy-discussion] addition to numpy.i

On Tue, May 26, 2015 at 8:59 AM, Tom Krauss wrote: > Hi folks, > > After some discussion with Bill Spotz I decided to try to submit my new > typemap to numpy.i that allows in-place arrays of an arbitrary number of > dimensions to be passed in as a "flat" array with a single "size". > > To that en

Re: [Numpy-discussion] Two questions about PEP 465 dot product

On Fri, May 22, 2015 at 12:02 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Thu, May 21, 2015 at 7:06 PM, Alexander Belopolsky > wrote: > >> 1. Is there a simple expression using existing numpy functions that >> implements PEP 465 semantics

Re: [Numpy-discussion] Two questions about PEP 465 dot product

On Thu, May 21, 2015 at 7:06 PM, Alexander Belopolsky wrote: > 1. Is there a simple expression using existing numpy functions that > implements PEP 465 semantics for @? > > 2. Suppose I have a function that takes two vectors x and y, and a matrix > M and returns x.dot(M.dot(y)). I would like to

Re: [Numpy-discussion] Integral Equation Solver

On Tue, May 12, 2015 at 12:41 PM, Pierson, Oliver C wrote: > Hi All, > > Awhile back I had written some code to solve Volterra integral equations > (integral equations where one of the integration bounds is a variable). > The code is available on Github (https://github.com/oliverpierson/volter

Re: [Numpy-discussion] import scipy.linalg is hanging on Marvell armada 370

On Tue, May 5, 2015 at 1:52 PM, Alexander Brezinov < alexander.brezi...@mmbresearch.com> wrote: > Hello > > The import of scipy.linalg is hanging in DOUBLE_mutiply function > (BINARY_LOOP) in umath.so. After attaching the gdb and dumping the local > varibles the args are empty strings. Could you p

[Numpy-discussion] Weighted covariance.

The weighted covariance function in PR #4960 is evolving to the following, where frequency weights are `f` and reliability weights are `a`. Assume that the observations are in the columns of the observation matrix. the steps to compute the weighted covari

Re: [Numpy-discussion] 1.10 release again.

On Mon, Apr 6, 2015 at 5:59 PM, Nathaniel Smith wrote: > On Apr 6, 2015 2:01 PM, "Ralf Gommers" wrote: > > > > There are too many PRs marked as "1.10 blockers", I think the only real > blockers are: > > - __numpy_ufunc__ PRs (#4815, #4855) > > The main blocker here is figuring out how to coordin

Re: [Numpy-discussion] 1.10 release again.

On Mon, Apr 6, 2015 at 3:01 PM, Ralf Gommers wrote: > > > On Mon, Apr 6, 2015 at 9:22 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> Hi All, >> >> I'd like to mark current PR's for inclusion in 1.10. >> > > Good idea.

[Numpy-discussion] 1.10 release again.

Hi All, I'd like to mark current PR's for inclusion in 1.10. If there is something that you want to have in the release, please mention it here by PR #.I think new enhancement PR's should be considered for 1.11 rather than 1.10, but bug fixes will go in. There is some flexibility, of course, as th

Re: [Numpy-discussion] NPY_SEPARATE_COMPILATION and RELAXED_STRIDES_CHECKING

On Sun, Apr 5, 2015 at 4:37 AM, Sebastian Berg wrote: > On Fr, 2015-04-03 at 21:00 -0600, Charles R Harris wrote: > > Hi All, > > > > > > Just to raise the question if these two options should be removed at > > some point? The current default value for b

Re: [Numpy-discussion] NPY_SEPARATE_COMPILATION and RELAXED_STRIDES_CHECKING

On Fri, Apr 3, 2015 at 9:00 PM, Charles R Harris wrote: > Hi All, > > Just to raise the question if these two options should be removed at some > point? The current default value for both is 0, so we have separate > compilation and relaxed strides checking by default. > > O

[Numpy-discussion] NPY_SEPARATE_COMPILATION and RELAXED_STRIDES_CHECKING

Hi All, Just to raise the question if these two options should be removed at some point? The current default value for both is 0, so we have separate compilation and relaxed strides checking by default. Chuck ___ NumPy-Discussion mailing list NumPy-Disc

Re: [Numpy-discussion] IDE's for numpy development?

On Thu, Apr 2, 2015 at 7:46 AM, David Cournapeau wrote: > > > On Wed, Apr 1, 2015 at 7:43 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Wed, Apr 1, 2015 at 11:55 AM, Sturla Molden >> wrote: >> >>> C

Re: [Numpy-discussion] IDE's for numpy development?

On Wed, Apr 1, 2015 at 11:55 AM, Sturla Molden wrote: > Charles R Harris wrote: > > > I'd be > > interested in information from anyone with experience in using such an > IDE > > and ideas of how Numpy might make using some of the common IDEs easier. > &

[Numpy-discussion] IDE's for numpy development?

Hi All, In a recent exchange Mark Wiebe suggested that the lack of support for numpy development in Visual Studio might limit the number of developers attracted to the project. I'm a vim/console developer myself and make no claim of familiarity with modern development tools, but I wonder if such t

Re: [Numpy-discussion] Numpy where

On Fri, Mar 13, 2015 at 2:09 PM, Charles R Harris wrote: > > > On Fri, Mar 13, 2015 at 1:26 PM, Nathaniel Smith wrote: > >> On Thu, Mar 12, 2015 at 9:35 PM, Benjamin Root wrote: >> > I think the question is if scalars should be acceptable for the first >> &g

Re: [Numpy-discussion] Numpy where

On Fri, Mar 13, 2015 at 1:26 PM, Nathaniel Smith wrote: > On Thu, Mar 12, 2015 at 9:35 PM, Benjamin Root wrote: > > I think the question is if scalars should be acceptable for the first > > argument, not if it should be for the 2nd and 3rd argument. > > > > If scalar can be given for the first a

Re: [Numpy-discussion] Numpy 1.10

On Sun, Mar 8, 2015 at 3:43 PM, Ralf Gommers wrote: > > > On Sat, Mar 7, 2015 at 12:40 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> Hi All, >> >> Time to start thinking about numpy 1.10. >> > > Sounds good. Do we have a volu

[Numpy-discussion] Numpy where

Hi All, This is apropos gh-5582 dealing with some corner cases of np.where. The following are the current behavior >>> import numpy >>> numpy.where(True) # case 1 ... (array([0]),) >>> numpy.where(True, None, None) # case 2 ... array(None, dtype=object

Re: [Numpy-discussion] MKL ValueError: On entry to DLASCL parameter number 5 had an illegal value

On Tue, Mar 10, 2015 at 10:33 AM, wrote: > > I got a illegal value message using MKL on Windows 64 while running the > statsmodels test suite. > > Kevin is getting the same with more information, which indicates that it > might be numpy.linalg.svd > > https://github.com/statsmodels/statsmodels/is

Re: [Numpy-discussion] Would like to patch docstring for numpy.random.normal

On Mon, Mar 9, 2015 at 2:34 PM, Paul Hobson wrote: > I feel your pain. Making it worse, numpy.random.lognormal takes "mean" and > "sigma" as input. If there's ever a backwards incompatible release, I hope > these things will be cleared up. > There is a numpy 2.0 milestone ;) Chuck ___

Re: [Numpy-discussion] Numpy 1.10

On Mon, Mar 9, 2015 at 4:16 PM, Ralf Gommers wrote: > > > On Sun, Mar 8, 2015 at 10:43 PM, Ralf Gommers > wrote: > >> >> >> On Sat, Mar 7, 2015 at 12:40 AM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >> >>> Hi All, >&

Re: [Numpy-discussion] numpy array casting ruled not safe

On Sat, Mar 7, 2015 at 2:45 PM, Charles R Harris wrote: > > > On Sat, Mar 7, 2015 at 2:02 PM, Dinesh Vadhia > wrote: > >> This was originally posted on SO ( >> https://stackoverflow.com/questions/28853740/numpy-array-casting-ruled-not-safe) >> and it was

Re: [Numpy-discussion] numpy array casting ruled not safe

On Sat, Mar 7, 2015 at 2:02 PM, Dinesh Vadhia wrote: > This was originally posted on SO ( > https://stackoverflow.com/questions/28853740/numpy-array-casting-ruled-not-safe) > and it was suggested it is probably a bug in numpy.take. > > Python 2.7.8 |Anaconda 2.1.0 (32-bit)| (default, Jul 2 201

[Numpy-discussion] Numpy 1.10

Hi All, Time to start thinking about numpy 1.10. At the moment there are 21 blockers and 93 PRs. it would be good if we could prioritize the blockers and the PRs. It might be a good idea to also look at closing some of the aging PRs. These days it seems to be normal to have 20 or so PRs in progres

Re: [Numpy-discussion] numpy pickling problem - python 2 vs. python 3

On Fri, Mar 6, 2015 at 10:34 AM, Sebastian wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi all, > > As this also affects .npy files, which uses pickle internally, why can't > this be done by Numpy itself? This breaks backwards compatibility in a > very bad way in my opinion. >

Re: [Numpy-discussion] Adding keyword to asarray and asanyarray.

On Thu, Mar 5, 2015 at 10:02 PM, wrote: > On Thu, Mar 5, 2015 at 12:33 PM, Charles R Harris > wrote: > > > > > > On Thu, Mar 5, 2015 at 10:04 AM, Chris Barker > wrote: > >> > >> On Thu, Mar 5, 2015 at 8:42 AM, Benjamin Root wrote: > >&g

Re: [Numpy-discussion] appveyor CI

On Thu, Mar 5, 2015 at 5:38 PM, Robert McGibbon wrote: > From my experience, it's pretty easy, assuming you're prepared to pick up > some powershell. > Some useful resources are > > - Olivier Grisel's example. > https://github.com/ogrisel/python-appveyor-demo > - I made a similar example, using

Re: [Numpy-discussion] appveyor CI

On Thu, Mar 5, 2015 at 12:42 PM, Stefan van der Walt wrote: > Hi Chuck > > On 2015-03-05 10:09:08, Charles R Harris > wrote: > > Anyone familiar with appveyor <http://www.appveyor.com/>? Is > > this something we could use to test/build numpy on windows > >

[Numpy-discussion] appveyor CI

Anyone familiar with appveyor ? Is this something we could use to test/build numpy on windows machines? It is free for open source. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman

Re: [Numpy-discussion] Adding keyword to asarray and asanyarray.

On Thu, Mar 5, 2015 at 10:04 AM, Chris Barker wrote: > On Thu, Mar 5, 2015 at 8:42 AM, Benjamin Root wrote: > >> dare I say... datetime64/timedelta64 support? >> > > well, the precision of those is 64 bits, yes? so if you asked for less > than that, you'd still get a dt64. If you asked for 64 bi

[Numpy-discussion] Adding keyword to asarray and asanyarray.

Hi All, This is apropos gh-5634 , a PR adding a precision keyword to asarray and asanyarray. The PR description is The precision keyword differs from the current dtype keyword in the > following way. > >- It specifies a minimum precision. If the prec

Re: [Numpy-discussion] linalg.norm probems

On Tue, Mar 3, 2015 at 7:12 PM, Ralf Gommers wrote: > > > On Wed, Mar 4, 2015 at 1:34 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Tue, Mar 3, 2015 at 5:31 PM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: &

Re: [Numpy-discussion] linalg.norm probems

On Tue, Mar 3, 2015 at 5:31 PM, Charles R Harris wrote: > > > On Tue, Mar 3, 2015 at 5:21 PM, Jaime Fernández del Río < > jaime.f...@gmail.com> wrote: > >> On Tue, Mar 3, 2015 at 4:11 PM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >>

Re: [Numpy-discussion] linalg.norm probems

On Tue, Mar 3, 2015 at 5:21 PM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote: > On Tue, Mar 3, 2015 at 4:11 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> Hi All, >> >> This is with reference to issue #5626 >> <https:

[Numpy-discussion] linalg.norm probems

Hi All, This is with reference to issue #5626 . Currently linalg.norm converts the input like so `x = asarray(x)`. This can produce integer arrays, which in turn may create problems of overflow, or the failure of the abs functions for minimum values of

Re: [Numpy-discussion] [SciPy-User] Congratulations to Chris Barker...

On Mon, Mar 2, 2015 at 5:51 PM, Nathaniel Smith wrote: > On Mon, Mar 2, 2015 at 2:57 PM, Stephan Hoyer wrote: > > Indeed, congratulations Chris! > > > > Are there plans to write a vectorized version for NumPy? :) > > np.isclose isn't identical, but IIRC the only difference is the defaults. > > T

Re: [Numpy-discussion] ANN: NumPy 1.9.2 bugfix release

On Sun, Mar 1, 2015 at 2:05 PM, Julian Taylor wrote: > Hi, > > > We am pleased to announce the release of NumPy 1.9.2, a > bugfix only release for the 1.9.x series. > The tarballs and win32 binaries are available on sourceforge: > https://sourceforge.net/projects/numpy/files/NumPy/1.9.2/ > PyPI a

Re: [Numpy-discussion] dot and MKL memory

On Fri, Feb 27, 2015 at 9:02 AM, Mads Ipsen wrote: > Hi, > > If I build Python 2.7.2 and numpy-1.9.1 and run the following script > > import numpy > c = numpy.ones((50, 4)) > mat = numpy.identity(4) > r = numpy.dot(c, mat) > > the evaluation of the 'dot' increases the memory by app. 35 MB. >

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

On Wed, Feb 25, 2015 at 11:23 AM, Pauli Virtanen wrote: > 25.02.2015, 19:59, Pauli Virtanen kirjoitti: > > 25.02.2015, 07:11, Nathaniel Smith kirjoitti: > >> Not sure if this is a full GSoC but it would be good to get the > benchmarks > >> into the numpy repository, so we can start asking people

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

On Tue, Feb 24, 2015 at 10:15 AM, Julian Taylor < jtaylor.deb...@googlemail.com> wrote: > On 02/24/2015 05:41 PM, Charles R Harris wrote: > > > > > > On Mon, Feb 23, 2015 at 11:49 PM, Ralf Gommers > <mailto:ralf.gomm...@gmail.com>> wrote: > > > &g

Re: [Numpy-discussion] GSoC'15 - mentors & ideas

On Mon, Feb 23, 2015 at 11:49 PM, Ralf Gommers wrote: > Hi all, > > > On Fri, Feb 20, 2015 at 10:05 AM, Ralf Gommers > wrote: > >> Hi all, >> >> It's time to start preparing for this year's Google Summer of Code. There >> is actually one urgent thing to be done (before 19.00 UTC today), which is

Re: [Numpy-discussion] np.nonzero behavior with multidimensional arrays

On Mon, Feb 23, 2015 at 2:29 PM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote: > > > On Mon, Feb 23, 2015 at 12:12 PM, Julian Taylor < > jtaylor.deb...@googlemail.com> wrote: > >> On 23.02.2015 08:52, Jaime Fernández del Río wrote: >> > This was raised in SO today: >> > >> > >> http://sta

Re: [Numpy-discussion] One-byte string dtype: third time's the charm?

On Sun, Feb 22, 2015 at 3:40 PM, Aldcroft, Thomas < aldcr...@head.cfa.harvard.edu> wrote: > > > On Sun, Feb 22, 2015 at 2:52 PM, Nathaniel Smith wrote: > >> On Sun, Feb 22, 2015 at 10:21 AM, Aldcroft, Thomas >> wrote: >> > The idea of a one-byte string dtype has been extensively discussed twice

Re: [Numpy-discussion] One-byte string dtype: third time's the charm?

On Sun, Feb 22, 2015 at 12:52 PM, Nathaniel Smith wrote: > On Sun, Feb 22, 2015 at 10:21 AM, Aldcroft, Thomas > wrote: > > The idea of a one-byte string dtype has been extensively discussed twice > > before, with a lot of good input and ideas, but no action [1, 2]. > > > > tl;dr: Perfect is the

Re: [Numpy-discussion] Matrix Class

On Sat, Feb 14, 2015 at 12:36 PM, wrote: > On Sat, Feb 14, 2015 at 12:05 PM, cjw wrote: > > > > On 14-Feb-15 11:35 AM, josef.p...@gmail.com wrote: > >> > >> On Wed, Feb 11, 2015 at 4:18 PM, Ryan Nelson > >> wrote: > >>> > >>> Colin, > >>> > >>> I currently use Py3.4 and Numpy 1.9.1. However, I

Re: [Numpy-discussion] Silent Broadcasting considered harmful

On Sun, Feb 8, 2015 at 2:14 PM, Stefan Reiterer wrote: > Yeah I'm aware of that, that's the reason why I suggested a warning level > as an alternative. > Setting no warnings as default would avoid breaking existing code. > *Gesendet:* Sonntag, 08. Februar 2015 um 22:08 Uhr > *Von:* "Eelco Hoogen

Re: [Numpy-discussion] Datetime again

On Thu, Jan 29, 2015 at 12:55 AM, Eric Firing wrote: > On 2015/01/28 6:29 PM, Charles R Harris wrote: > > > > > > And as for "The 64 bits of long long really isn't enough and leads > > to all sorts of compromises". not long enough for what? I&#

Re: [Numpy-discussion] Datetime again

On Wed, Jan 28, 2015 at 6:13 PM, Chris Barker wrote: > Sorry not to notice this for a while -- I've been distracted by > python-ideas. (Nathaniel knows what I'm talking about ;-) ) > > I do like the idea of prototyping some DateTime stuff -- it really isn't > clear what's needed or how to do it

[Numpy-discussion] What should recfromcsv defaults be?

Hi All, This question comes apropos this bugfix #5495 that ensures that the default options get passed down the call chain. The current defaults are kwargs.setdefault("case_sensitive", "lower") kwargs.setdefault("names", True) kwargs.setdefau

Re: [Numpy-discussion] Datetime again

On Thu, Jan 22, 2015 at 8:08 AM, Charles R Harris wrote: > > > On Thu, Jan 22, 2015 at 7:54 AM, Nathaniel Smith wrote: > >> On Thu, Jan 22, 2015 at 2:51 PM, Charles R Harris >> wrote: >> > Hi All, >> > >> > I'm playing with the idea of bu

Re: [Numpy-discussion] Datetime again

On Thu, Jan 22, 2015 at 7:54 AM, Nathaniel Smith wrote: > On Thu, Jan 22, 2015 at 2:51 PM, Charles R Harris > wrote: > > Hi All, > > > > I'm playing with the idea of building a simplified datetime class on top > of > > the current numpy implementation

[Numpy-discussion] Datetime again

Hi All, I'm playing with the idea of building a simplified datetime class on top of the current numpy implementation. I believe Pandas does something like this, and blaze will (does?) have a simplified version. The reason for the new class would be to have an easier, and hopefully more portable, A

Re: [Numpy-discussion] Sorting refactor

On Fri, Jan 16, 2015 at 7:11 AM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote: > On Fri, Jan 16, 2015 at 3:33 AM, Lars Buitinck wrote: > >> 2015-01-16 11:55 GMT+01:00 : >> > Message: 2 >> > Date: Thu, 15 Jan 2015 21:24:00 -0800 >> > From: Jaime Fern?ndez del R?o >> > Subject: [Numpy-di

Re: [Numpy-discussion] The future of ndarray.diagonal()

On Thu, Jan 15, 2015 at 9:44 AM, Maniteja Nandana < maniteja.modesty...@gmail.com> wrote: > Hello everyone, > > I just wanted to highlight the point made by Charles, it would be great if > he would clarify any mistakes in the points that I put forward. > > Quoting the documentation, > > In version

Re: [Numpy-discussion] linspace handling of extra return

On Tue, Jan 13, 2015 at 7:02 PM, Benjamin Root wrote: > So, raise a ValueError when it used to return (mostly) correct results? > For some reason, I don't think people would appreciate that. > > Ben Root > On Jan 13, 2015 5:59 PM, "Chris Barker" wrote: > >> On Tue, Jan 13, 2015 at 7:23 AM, Benja

Re: [Numpy-discussion] Equality of dtypes does not imply equality of type kinds

On Mon, Jan 12, 2015 at 12:14 PM, Maniteja Nandana < maniteja.modesty...@gmail.com> wrote: > Hi, > > On Tue, Jan 13, 2015 at 12:03 AM, Alexander Belopolsky > wrote: > >> Consider this (on a 64-bit platform): >> >> >>> numpy.dtype('q') == numpy.dtype('l') >> True >> >> > >>> numpy.dtype('q').char

Re: [Numpy-discussion] diag, diagonal, ravel and all that

On Sun, Jan 4, 2015 at 1:44 AM, Ralf Gommers wrote: > > > On Sun, Jan 4, 2015 at 1:28 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Sat, Jan 3, 2015 at 4:54 PM, Sturla Molden >> wrote: >> >>> On 03/01/15 03:0

Re: [Numpy-discussion] diag, diagonal, ravel and all that

On Sat, Jan 3, 2015 at 4:54 PM, Sturla Molden wrote: > On 03/01/15 03:04, Charles R Harris wrote: > > > The diag, diagonal, and ravel functions have recently been changed to > > preserve subtypes. However, this causes lots of backward compatibility > > problems for mat

Re: [Numpy-discussion] The future of ndarray.diagonal()

On Sat, Jan 3, 2015 at 2:55 PM, Matthew Brett wrote: > Hi, > > On Thu, Jan 1, 2015 at 9:35 PM, Alexander Belopolsky > wrote: > > A discussion [1] is currently underway at GitHub which will benefit from > a > > larger forum. > > > > In version 1.9, the diagonal() method was changed to return a re

Re: [Numpy-discussion] diag, diagonal, ravel and all that

there a way to convincingly group these as > >> array operations vs matrix operations? > >> Personally I am puzzled by preserving subtype of > >> `diagonal` and > >> very especially of `ravel`. Has anyone requested this? > >> (I ca

Re: [Numpy-discussion] diag, diagonal, ravel and all that

On Sat, Jan 3, 2015 at 8:05 AM, Alan G Isaac wrote: > Would this really be practicality beating purity? > It would be nice to have know the principle governing this. > For example, is there a way to convincingly group these as > array operations vs matrix operations? > > Personally I am puzzled b

Re: [Numpy-discussion] Optimizing multi-tensor contractions in numpy

On Fri, Jan 2, 2015 at 7:45 PM, Daniel Smith wrote: > Hello everyone, > > I have been working on a chunk of code that basically sets out to provide > a single function that can take an arbitrary einsum expression and computes > it in the most optimal way. While np.einsum can compute arbitrary > e

[Numpy-discussion] diag, diagonal, ravel and all that

Hi All, The diag, diagonal, and ravel functions have recently been changed to preserve subtypes. However, this causes lots of backward compatibility problems for matrix users, in particular, scipy.sparse. One possibility for fixing this is to special case matrix and so that these functions continu

[Numpy-discussion] numpy developers

Hi All, I've invited Alex Griffing onto the team to be a numpy developer. He has been contributing fixes and reviews for a while and it is time to give him more opportunity to contribute. I think he will do well. Chuck ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] Changing np.ravel's return to be same array type as input array

On Sat, Dec 27, 2014 at 10:56 PM, Garrett Reynolds < garrettreynol...@gmail.com> wrote: > I made a pull request to change np.ravel so that it would return the same > array type (ndarray, matrix, masked array, etc.) as it took in. > > This would bring np.ravel in line with other functions. For exa

Re: [Numpy-discussion] simple reduction question

On Wed, Dec 24, 2014 at 10:29 AM, wrote: > > > On Wed, Dec 24, 2014 at 10:30 AM, Julian Taylor < > jtaylor.deb...@googlemail.com> wrote: > >> On 24.12.2014 16:25, Neal Becker wrote: >> > What would be the most efficient way to compute: >> > >> > c[j] = \sum_i (a[i] * b[i,j]) >> > >> > where a[i]

Re: [Numpy-discussion] Fast sizes for FFT

On Tue, Dec 23, 2014 at 7:32 PM, Robert McGibbon wrote: > Hey, > > The performance of fftpack depends very strongly on the array size -- > sizes that are powers of two are good, but also powers of three, five and > seven, or numbers whose only prime factors are from (2,3,5,7). For problems > that

[Numpy-discussion] g77

Hi All, Is there any reason to keep support for g77? The last release was in 2006 and gfortran has been available since 2005. I admit that there is no reason to drop current support, apart from getting rid of some code, so perhaps the question should be: how much work should we spend maintaining i

Re: [Numpy-discussion] GDB macros for numpy

On Sun, Nov 30, 2014 at 4:54 AM, David Cournapeau wrote: > Hi there, > > I remember having seen some numpy-aware gdb macros at some point, but > cannot find any reference. Does anyone know of any ? > What would numpy aware gdb macros be? Never heard of them. Chuck __

Re: [Numpy-discussion] packbits / unpackbits bugs or misfeatures?

On Sat, Nov 29, 2014 at 6:49 PM, Alan G Isaac wrote: > Six years ago Zachary Pincus wrote: > > it would kind of make more sense, at least to me, for > > unpackbits to return a boolean array, and packbits to take > > boolean arrays. I could try to look into fixing the code > > instead of the docs

Re: [Numpy-discussion] Scipy 0.15.0 beta 1 release

On Wed, Nov 26, 2014 at 6:59 AM, Julian Taylor < jtaylor.deb...@googlemail.com> wrote: > On 11/26/2014 02:19 PM, Charles R Harris wrote: > > > > > > On Wed, Nov 26, 2014 at 2:06 AM, Julian Taylor > > mailto:jtaylor.deb...@googlemail.com>> > > wrot

Re: [Numpy-discussion] Setting up a "newcomers" label on the issue tracker ?

On Wed, Nov 26, 2014 at 2:36 AM, Sebastian Berg wrote: > On Mi, 2014-11-26 at 08:44 +, David Cournapeau wrote: > > Hi, > > > > > > Would anybody mind if I create a label "newcomers" on GH, and start > > labelling simple issues ? > > We actually have an "easy fix" label, which I think had this

Re: [Numpy-discussion] Scipy 0.15.0 beta 1 release

On Wed, Nov 26, 2014 at 2:06 AM, Julian Taylor < jtaylor.deb...@googlemail.com> wrote: > On 11/26/2014 12:50 AM, Andrea Gavana wrote: > > > > On 25 November 2014 at 19:33, David Cournapeau > > wrote: > > > > > > > > On Tue, Nov 25, 2014 at 6:10 PM, Sturla Molden > >

Re: [Numpy-discussion] Implementation of tensor product and tensor contraction?

Take a look as einsum, it is quite good for such things. Chuck On Tue, Nov 25, 2014 at 9:06 PM, Yuxiang Wang wrote: > Dear all, > > I have been doing tensor algebra recently (for continuum mechanics) > and was looking into two common operations: tensor product & tensor > contraction. > > 1. Ten

Re: [Numpy-discussion] Problem with _dotblas.pyd when using Matplotlib for 3d plot

On Wed, Nov 19, 2014 at 3:03 PM, Mégardon Geoffrey < geoffrey.megar...@gmail.com> wrote: > Hi, > > In verbose mode, it stops at this line: > test_blasdot.test_dot_3args ... > > Ok, I will try with numpy and python :/ > Might want to file a bug report with Continuum Analytics. Plain old numpy wil

Re: [Numpy-discussion] Numpy 1.9.1, zeros and alignement

On Tue, Nov 18, 2014 at 11:20 AM, David Cournapeau wrote: > Hi, > > I have not followed closely the changes that happen in 1.9.1, but was > surprised by the following: > > x = np.zeros(12, "d") > assert x.flags.aligned # fails > > This is running numpy 1.9.1 built on windows with VS 2008. Is it e

<    1   2   3   4   5   6   7   8   9   10   >