2009/1/12 Alan G Isaac :
> This would really involve the following.
> Create a searchable database of citations
> and an interface for adding to it.
> Unique keys would be generated by your
> algorithm of choice when an entry is added.
> Authors would be asked to use only references
> in the databa
On Sun, Jan 11, 2009 at 20:23, Neal Becker wrote:
> Robert Kern wrote:
>
>
>>
>> That's a fair point. However, given the wider range of issues that you
>> had in trying to get memmap to work with your device, perhaps we
>> should just state that the memmap class is intended for the common use
Robert Kern wrote:
>
> That's a fair point. However, given the wider range of issues that you
> had in trying to get memmap to work with your device, perhaps we
> should just state that the memmap class is intended for the common use
> case of regular files. The detection of the existing fil
On Sun, Jan 11, 2009 at 15:13, Bryan Cole wrote:
>
>> > However, also note
>> > that with ndarray's rich comparisons, such membership testing will
>> > fail with ndarrays, too.
>>
>> This poses a similarly big problem. I can't understand this behaviour
>> either:
>
> OK, I can now. After equality
On 1/11/2009 4:13 PM Stéfan van der Walt apparently wrote:
> Thank you for your feedback. Yes, this is a problem. In a way,
> RestructuredText is partially to blame for not providing numerical
> citation markup.
I do not agree.
I cannot think of any bibliography tool that uses
numerical citati
> > However, also note
> > that with ndarray's rich comparisons, such membership testing will
> > fail with ndarrays, too.
>
> This poses a similarly big problem. I can't understand this behaviour
> either:
OK, I can now. After equality testing each item, the result must be cast
to bool. This is
Hi Alan
2009/1/11 Alan G Isaac :
> The docstring standard at
> http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines#docstring-standard
> suggests a citation reference format that is not compatible
> with reStructuredText. Quoting from
> http://docutils.sourceforge.net/docs/ref/rst/res
The docstring standard at
http://projects.scipy.org/scipy/numpy/wiki/CodingStyleGuidelines#docstring-standard
suggests a citation reference format that is not compatible
with reStructuredText. Quoting from
http://docutils.sourceforge.net/docs/ref/rst/restructuredtext.html#citations:
Citat
> >
> > What's the consensus on this? Is the current dtype behaviour broken?
>
> It's suboptimal, certainly. Feel free to fix it.
Thankyou.
> However, also note
> that with ndarray's rich comparisons, such membership testing will
> fail with ndarrays, too.
This poses a similarly big problem.
On Sun, Jan 11, 2009 at 03:41, Bryan Cole wrote:
> Dtype objects throw an exception if compared for equality against other
> objects. e.g.
>
import numpy
numpy.dtype('uint32')==1
> Traceback (most recent call last):
> File "", line 1, in
> TypeError: data type not understood
>
> A
Dtype objects throw an exception if compared for equality against other
objects. e.g.
>>> import numpy
>>> numpy.dtype('uint32')==1
Traceback (most recent call last):
File "", line 1, in
TypeError: data type not understood
>>>
After some googling, I think python wisdom (given in the Python do
11 matches
Mail list logo
