Re: [Numpy-discussion] Numpy-vendor vcvarsall.bat problem.

2015-08-07 Thread Charles R Harris
On Fri, Aug 7, 2015 at 9:36 AM, Charles R Harris wrote: > So the problem comes from the has_cblas function > > def has_cblas(self): > # primitive cblas check by looking for the header > res = False > c = distutils.ccompiler.new_compiler() > tmpdir = tempfile.mk

Re: [Numpy-discussion] Numpy-vendor vcvarsall.bat problem.

2015-08-07 Thread Charles R Harris
So the problem comes from the has_cblas function def has_cblas(self): # primitive cblas check by looking for the header res = False c = distutils.ccompiler.new_compiler() tmpdir = tempfile.mkdtemp() s = """#include """ src = os.path.join(tmpdir,

Re: [Numpy-discussion] Numpy-vendor vcvarsall.bat problem.

2015-08-07 Thread Charles R Harris
On Fri, Aug 7, 2015 at 8:16 AM, Charles R Harris wrote: > > > On Fri, Aug 7, 2015 at 8:02 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Fri, Aug 7, 2015 at 3:33 AM, David Cournapeau >> wrote: >> >>> Which command exactly did you run to have that error ? Normally, the >

Re: [Numpy-discussion] Numpy-vendor vcvarsall.bat problem.

2015-08-07 Thread Charles R Harris
On Fri, Aug 7, 2015 at 8:02 AM, Charles R Harris wrote: > > > On Fri, Aug 7, 2015 at 3:33 AM, David Cournapeau > wrote: > >> Which command exactly did you run to have that error ? Normally, the code >> in msvc9compiler should not be called if you call the setup.py with the >> mingw compiler as e

Re: [Numpy-discussion] Numpy-vendor vcvarsall.bat problem.

2015-08-07 Thread Charles R Harris
On Fri, Aug 7, 2015 at 3:33 AM, David Cournapeau wrote: > Which command exactly did you run to have that error ? Normally, the code > in msvc9compiler should not be called if you call the setup.py with the > mingw compiler as expected by distutils > I'm running numpy-vendor which is running wine

Re: [Numpy-discussion] Numpy-vendor vcvarsall.bat problem.

2015-08-07 Thread Jaime Fernández del Río
On Fri, Aug 7, 2015 at 2:33 AM, David Cournapeau wrote: > Which command exactly did you run to have that error ? Normally, the code > in msvc9compiler should not be called if you call the setup.py with the > mingw compiler as expected by distutils > FWIW, the incantation that works for me to com

Re: [Numpy-discussion] Shared memory check on in-place modification.

2015-08-07 Thread srean
I got_misled_by (extrapolated erroneously from) this description of temporaries in the documentation http://docs.scipy.org/doc/numpy/user/basics.indexing.html#assigning-values-to-indexed-arrays ,,,])]" ... new array is extracted from the original (as a temporary) containing the values at 1, 1, 3,

Re: [Numpy-discussion] Numpy-vendor vcvarsall.bat problem.

2015-08-07 Thread David Cournapeau
Which command exactly did you run to have that error ? Normally, the code in msvc9compiler should not be called if you call the setup.py with the mingw compiler as expected by distutils On Fri, Aug 7, 2015 at 12:19 AM, Charles R Harris wrote: > > > On Thu, Aug 6, 2015 at 5:11 PM, Charles R Harri

Re: [Numpy-discussion] Shared memory check on in-place modification.

2015-08-07 Thread Sebastian Berg
On Fr, 2015-08-07 at 13:14 +0530, srean wrote: > Wait, when assignments and slicing mix wasn't the behavior supposed to > be equivalent to copying the RHS to a temporary and then assigning > using the temporary. Is that a false memory ? Or has the behavior > changed ? As long as the behavior is wel

Re: [Numpy-discussion] Shared memory check on in-place modification.

2015-08-07 Thread srean
Wait, when assignments and slicing mix wasn't the behavior supposed to be equivalent to copying the RHS to a temporary and then assigning using the temporary. Is that a false memory ? Or has the behavior changed ? As long as the behavior is well defined and succinct it should be ok On Tuesday, Ju