>> Basically the 'wrap' mode for handling out-of-bounds indexing in
>> ndimage functions is completely broken. The test suite tests for the
>> wrong behavior.
>>
>
> Ah, we are talking about numpy 1.5, not scipy. You should raise this issue
> over on the scipy-dev list.
My bad. Sorry for the noi
On Mon, Jul 26, 2010 at 7:54 PM, Kurt Smith wrote:
> On Mon, Jul 26, 2010 at 10:58 AM, Ralf Gommers
> wrote:
> > Hi all,
> >
> > For numpy 1.5.0 no one has yet said they have urgent changes that need to
> go
> > in. If you do, please reply with the what and why. If nothing big has to
> go
> > in
On 7/26/2010 8:18 PM, Skipper Seabold wrote:
> np.linalg.det(np.array([[2]]))
> #2.0
>
> which should either fail or if not, then I think np.linalg.det should
> handle scalars and scalars as 1d arrays
It should not fail, because it follows from standard definitions.
(E.g., it is the base case of a
On Mon, Jul 26, 2010 at 10:58 AM, Ralf Gommers
wrote:
> Hi all,
>
> For numpy 1.5.0 no one has yet said they have urgent changes that need to go
> in. If you do, please reply with the what and why. If nothing big has to go
> in, I propose the following release schedule:
>
> Aug 1 : beta 1
> Aug 15
On Mon, Jul 26, 2010 at 4:51 PM, Alan G Isaac wrote:
> On 7/26/2010 8:22 PM, Joshua Holbrook wrote:
>> imo, the determinant of a scalar should be defined as itself, based on
>> the definition of the determinant.
>
> What definition do you have in mind?
>
> Alan Isaac
>
>
>
> __
On 7/26/2010 8:22 PM, Joshua Holbrook wrote:
> imo, the determinant of a scalar should be defined as itself, based on
> the definition of the determinant.
What definition do you have in mind?
Alan Isaac
___
NumPy-Discussion mailing list
NumPy-Discuss
On Mon, Jul 26, 2010 at 6:22 PM, Joshua Holbrook wrote:
> On Mon, Jul 26, 2010 at 4:18 PM, Skipper Seabold
> wrote:
> > On Mon, Jul 26, 2010 at 7:38 PM, Charles R Harris
> > wrote:
> >>
> >>
> >> On Mon, Jul 26, 2010 at 5:05 PM, Skipper Seabold
> >> wrote:
> >>>
> >>> On Mon, Jul 26, 2010 at 5:
On Mon, Jul 26, 2010 at 4:18 PM, Skipper Seabold wrote:
> On Mon, Jul 26, 2010 at 7:38 PM, Charles R Harris
> wrote:
>>
>>
>> On Mon, Jul 26, 2010 at 5:05 PM, Skipper Seabold
>> wrote:
>>>
>>> On Mon, Jul 26, 2010 at 5:48 PM, Alan G Isaac wrote:
>>> > On 7/26/2010 12:45 PM, Skipper Seabold wrot
On Mon, Jul 26, 2010 at 7:38 PM, Charles R Harris
wrote:
>
>
> On Mon, Jul 26, 2010 at 5:05 PM, Skipper Seabold
> wrote:
>>
>> On Mon, Jul 26, 2010 at 5:48 PM, Alan G Isaac wrote:
>> > On 7/26/2010 12:45 PM, Skipper Seabold wrote:
>> >> Right now np.linalg.det does not handle scalars or 1d (scal
On Mon, Jul 26, 2010 at 5:05 PM, Skipper Seabold wrote:
> On Mon, Jul 26, 2010 at 5:48 PM, Alan G Isaac wrote:
> > On 7/26/2010 12:45 PM, Skipper Seabold wrote:
> >> Right now np.linalg.det does not handle scalars or 1d (scalar) arrays.
> >
> > I don't have a real opinion on changing this, but I
On Mon, Jul 26, 2010 at 5:48 PM, Alan G Isaac wrote:
> On 7/26/2010 12:45 PM, Skipper Seabold wrote:
>> Right now np.linalg.det does not handle scalars or 1d (scalar) arrays.
>
> I don't have a real opinion on changing this, but I am curious
> to know the use case, as the current behavior seems
U
On 7/26/2010 12:45 PM, Skipper Seabold wrote:
> Right now np.linalg.det does not handle scalars or 1d (scalar) arrays.
I don't have a real opinion on changing this, but I am curious
to know the use case, as the current behavior seems
a) correct and b) to provide an error check.
Cheers,
Alan
On Mon, Jul 26, 2010 at 01:52:06PM -0700, Matthew Brett wrote:
> http://old.nabble.com/numpydoc-broken-by-latest-sphinx-td28896476.html
> http://projects.scipy.org/numpy/ticket/1489
Darn, I should have googled :(
Thanks,
Gaël
___
NumPy-Discussion maili
Hi,
> I just wanted to mention that numpydoc is broken with the latest sphinx
> release. I had a quick look, but could find how to solve the problem, so
> I am just pointing it out here:
For reference in case anyone is searching...
http://old.nabble.com/numpydoc-broken-by-latest-sphinx-td2889647
Hi there,
I just wanted to mention that numpydoc is broken with the latest sphinx
release. I had a quick look, but could find how to solve the problem, so
I am just pointing it out here:
The trace is:
# Sphinx version: 1.0b2+/3fed33465259
# Docutils version: 0.6 release
# Jinja2 version: 2.3.1
T
All,
I'm teaching myself how to subclass ndarrays in C (not in Cython, just plain
C). It's slowly coming together, but I'm now running into a problem: I need to
overwrite __getitem__ and I'm not sure how to do it. I was thinking about using
my own function instead of array_as_mapping.mp_subscrip
Right now np.linalg.det does not handle scalars or 1d (scalar) arrays.
It first tests that an array is 2d, then if it is square. This seems
redundant to me.
This currently works
In [20]: np.linalg.det([[1]])
Out[20]: 1.0
but
In [21]: np.linalg.det([1])
LinAlgError: 1-dimensional array given.
Tue, 27 Jul 2010 00:26:51 +0800, Ralf Gommers wrote:
[clip]
> > > Also, Ralf has the Git ID in format "rgommers<...email...>", but I
> > > guess that's correct?
>
> My checkout failed so can't check this, but that looks a little odd. My
> .gitconfig is normal:
> user]
> name = rgommers
> em
On Mon, Jul 26, 2010 at 5:16 PM, David wrote:
> On 07/26/2010 05:44 PM, Pauli Virtanen wrote:
> > Mon, 26 Jul 2010 13:57:36 +0900, David Cournapeau wrote:
> >> I have finally prepared and uploaded a test repository containing numpy
> >> code:
> >>
> >> http://github.com/numpy/numpy_svn
>
Hmm, th
On Mon, Jul 26, 2010 at 11:58 AM, Ralf Gommers
wrote:
> Hi all,
>
> For numpy 1.5.0 no one has yet said they have urgent changes that need to go
> in. If you do, please reply with the what and why. If nothing big has to go
> in, I propose the following release schedule:
>
> Aug 1 : beta 1
> Aug 15
Hi all,
For numpy 1.5.0 no one has yet said they have urgent changes that need to go
in. If you do, please reply with the what and why. If nothing big has to go
in, I propose the following release schedule:
Aug 1 : beta 1
Aug 15: rc 1
Aug 22: rc 2
Aug 29: release
Please note that the branch has
Pauli Virtanen-3 wrote:
>
> That's a bug. It apparently implicitly encodes the Unicode string you
> pass in to UTF-8, instead of trying to encode in ASCII and fail, like it
> does on Python 2:
>
Thanks! Should I file a bug report?
Cheers,
Tom
--
View this message in context:
http://old.n
2010/7/26 bruno Piguet
>
> - I'm thinking of using something like np.array(f.read(),
> dtype=some_type).
>
Actually :
data=np.fromstring(f.read(), dtype=some_type, count=-1)
Bruno.
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://
Hi all,
I've got some code which basically does :
f = open (path, 'rb')
header = f.read (some_length)
data = np.fromfile (f, dtype= some_type, count=-1)
In order to process compressed files, I switched the open sequence to :
if (plain):
f = open (path, 'rb')
else:
f
Pauli Virtanen writes:
>> Returning a *right* identity for an operation that is otherwise a *left*
>> fold is very odd, no matter how you slice it. That is what looks like
>> special casing...
>
> I think I see your point now.
I know this is unlikely to happen, since it would break things for a
Hi list,
is there a way to compute the weighted median or the weighted percentile
http://en.wikipedia.org/wiki/Percentile#Weighted_Percentile
with numpy or scipy? I only found the "scoreatpercentile" function in
scipy.stat, and the "median" functions of scipy.stat and numpy, but they
both dont al
On 07/26/2010 05:44 PM, Pauli Virtanen wrote:
> Mon, 26 Jul 2010 13:57:36 +0900, David Cournapeau wrote:
>> I have finally prepared and uploaded a test repository containing numpy
>> code:
>>
>> http://github.com/numpy/numpy_svn
>
> Some observations based on a quick look:
>
> 1)
>
> $ git branch -
Mon, 26 Jul 2010 13:57:36 +0900, David Cournapeau wrote:
> I have finally prepared and uploaded a test repository containing numpy
> code:
>
> http://github.com/numpy/numpy_svn
Some observations based on a quick look:
1)
$ git branch -r
origin/maintenance/1.1.x_5227
origin/maintenance/1.5.x
28 matches
Mail list logo
