On Sun, 2012-09-23 at 18:54 +0100, Nathaniel Smith wrote:
> On Sat, Sep 22, 2012 at 10:24 PM, Sebastian Berg
> wrote:
> > In case you are interested, the second (real odditiy), is caused by
> > ISFORTRAN and IS_F_CONTIGUOUS mixup, I have found three occurances where
> > I think ISFORTRAN should be
On Sat, Sep 22, 2012 at 1:18 PM, Ralf Gommers wrote:
> On Fri, Sep 21, 2012 at 11:39 PM, Nathaniel Smith wrote:
>> So the question is, how do we get a .egg-info? For the specific case
>> Ralf ran into, I'm pretty sure the solution is just that if you're
>> clever enough to do an in-place build an
On Sun, Sep 23, 2012 at 7:55 PM, Olivier Grisel
wrote:
> 2012/9/23 Olivier Grisel :
>>
>> The only clean solution for the collapsed base of numpy 1.7 I see
>> would be to replace the direct mmap.mmap buffer instance from the
>> numpy.memmap class to use a custom wrapper of mmap.mmap that would
>>
2012/9/23 Olivier Grisel :
>
> The only clean solution for the collapsed base of numpy 1.7 I see
> would be to replace the direct mmap.mmap buffer instance from the
> numpy.memmap class to use a custom wrapper of mmap.mmap that would
> still implement the buffer python API but would also store the
2012/9/23 Nathaniel Smith :
> On Sat, Sep 22, 2012 at 4:46 PM, Olivier Grisel
> wrote:
>> There is also a third use case that is problematic on numpy master:
>>
>> orig = np.memmap('tmp.mmap', dtype=np.float64, shape=100, mode='w+')
>> orig[:] = np.arange(orig.shape[0]) * -1.0 # negative markers
On Sat, Sep 22, 2012 at 4:46 PM, Olivier Grisel
wrote:
> There is also a third use case that is problematic on numpy master:
>
> orig = np.memmap('tmp.mmap', dtype=np.float64, shape=100, mode='w+')
> orig[:] = np.arange(orig.shape[0]) * -1.0 # negative markers to
> detect under / overflows
>
> a
On Sat, Sep 22, 2012 at 10:24 PM, Sebastian Berg
wrote:
> In case you are interested, the second (real odditiy), is caused by
> ISFORTRAN and IS_F_CONTIGUOUS mixup, I have found three occurances where
> I think ISFORTRAN should be replaced by the latter. Check also:
>
> https://github.com/seberg/n
On Sun, Sep 23, 2012 at 5:23 PM, 心如烛光 <275438...@qq.com> wrote:
> Hi,all.
> I have installed numpy and scipy step by step carefully as the
> instructions from website:http://www.scipy.org/Installing_SciPy/Mac_OS_X
> But still get many errors and warnings while it's building.
> (OSX lion 10.7.
Hi,all.
I have installed numpy and scipy step by step carefully as the
instructions from website:http://www.scipy.org/Installing_SciPy/Mac_OS_X
But still get many errors and warnings while it's building.
(OSX lion 10.7.4 /Xcode 4.5 /clang /gfortran4.2.3)
Do scipy and numpy must be built by g
In case you are interested, the second (real odditiy), is caused by
ISFORTRAN and IS_F_CONTIGUOUS mixup, I have found three occurances where
I think ISFORTRAN should be replaced by the latter. Check also:
https://github.com/seberg/numpy/commit/4d2713ce8f2107d225fe291f5da6c6a75436647e
Sebastian
On Sat, Sep 22, 2012 at 12:19:53PM -0600, Charles R Harris wrote:
> But you loose the pointer to the filename and the offset. In previous
> versions of numpy c.base used to be the np.memmap instance from which
> c is an array view. That allowed to make efficient pickling without
>
On Sat, Sep 22, 2012 at 12:30:46PM -0600, Charles R Harris wrote:
> As to the 1.7 release, I've been thinking we are violating the release
> early, release often maxim. Bugs trickle in at a constant rate and if we
> wait to fix them all we wait forever. So while it would be nice to h
12 matches
Mail list logo
