ome cases I
> believe (when printing is not done through our work in numpyos.c). I
> will still check that the test works, at least.
Thanks!
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.sc
http://scipy.org/scipy/numpy/ticket/1008
http://codereview.appspot.com/22054
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
pparently doesn't track dependencies to the
*.inc.src files.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
mpy side. I know zip about sphinx extensions, so I don't expect
> to be able to suggest a fix myself.
>
> (I am assuming that the doc subdirectory in svn *should* be
> buildable--am I correct?)
Yes. But not necessarily with Sphinx 0.6.dev.
--
Pauli Virtanen
___
t the nonpropagating versions of `amax` and `amin` called `nanmax`
and `nanmin`? But these are functions, not array methods.
What does the `f` in the beginning of `fmax` and `fmin` stand for?
--
Pauli Virtanen
___
Numpy-discussion mailing list
Num
is O. and Dag,
> especially), I'd appreciate it if you could read over the pages to
> ensure everything is actually correct.
I wonder if it would make sense to redirect the page here:
http://docs.scipy.org/doc/numpy/reference/arrays.interface.html
so that it would be easier
g' SVN url that doesn't
work any more in its config.
- The FreeBSD_64 slave (+ maybe others) has a wrong Numpy test stanza in
its Makefile, so tests won't run.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@s
x/issue/81/
but I think Ctrl+C is not a requirement for triggering it. Did you get
this error from a clean build?
> There are also some errors on mac os x about too many opened files
> (which can be alleviated by running the make html again, but obviously,
> that's not great). I don&#
Tue, 10 Mar 2009 18:22:12 +, Pauli Virtanen wrote:
> Tue, 10 Mar 2009 15:27:32 +0900, David Cournapeau wrote:
>> For the upcoming 1.3.0 release, I would like to distribute the (built)
>> documentation in some way. But first, I need to be able to build it :)
>
> Yep, bu
we should follow Python here, otherwise unnecessary confusion may
arise.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Wed, 11 Mar 2009 16:20:47 +0900, David Cournapeau wrote:
> On Wed, Mar 11, 2009 at 3:22 AM, Pauli Virtanen wrote:
[clip]
>> Sphinx 0.5.1 worksforme, and on two different Linux machines (and
>> Python versions), so I doubt it's somehow specific to my setup.
>
> Yes, it
d, specify the Codereview site issue number to the upload:
python upload.py -i 12345
so that the new version of the patch is marked as an improved version of
the old one.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scip
ff suffix. Maybe this can be fixed.
- Inline comments in patches would be nice, as in codereview.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
TA : True
> WRITEABLE : True
> ALIGNED : True
> UPDATEIFCOPY : False
>>>> (a+1).flags
> C_CONTIGUOUS : True
> F_CONTIGUOUS : False
> OWNDATA : True
> WRITEABLE : True
> ALIGNED : True
> UPDATEIFCOPY : False
New numpy arrays are by default in C-orde
Tue, 17 Mar 2009 15:25:37 +0200, Stéfan van der Walt wrote:
> Pauli,
>
> 2009/2/14 Pauli Virtanen :
>> It seems that the buildbot.scipy.org is not picking up the changes in
>> Numpy trunk.
>>
>> I'd guess this could be some issue with SVNPoller. At leas
ands... I wonder if these would be worth the
trouble.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Tue, 17 Mar 2009 15:25:37 +0200, Stéfan van der Walt wrote:
> 2009/2/14 Pauli Virtanen :
>> It seems that the buildbot.scipy.org is not picking up the changes in
>> Numpy trunk.
>>
>> I'd guess this could be some issue with SVNPoller. At least it doesn't
p
info = np.finfo(np.longcomplex)
print "eps:", info.eps, info.eps.dtype
print "tiny:", info.tiny, info.tiny.dtype
print "log10:", np.log10(info.tiny), np.log10(info.tiny/info.eps)
Thanks!
--
Pauli Virtanen
___
Numpy-disc
Wed, 18 Mar 2009 09:26:29 +0200, Stéfan van der Walt wrote:
> 2009/3/17 Pauli Virtanen :
>> Ok, it seems like this the issue with no updates is now sorted out:
>>
>> http://buildbot.scipy.org/waterfall?show_events=false
>>
>> and the buildbot gets the chang
t;
> Where in the docs is it supposed to go?
New file routines.testing.rst would perhaps be the best place.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
pass through them. I invite other people who have the
reviewer permissions to check my judgment.
Comments or suggestions?
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Sun, 22 Mar 2009 03:14:50 +0200, Stéfan van der Walt wrote:
> Hi Pauli
>
> 2009/3/22 Pauli Virtanen :
>> Previously, I did the cherry-picking just by reading through the full
>> patch, but now I added a feature to the doc wiki that allows to
>> parallelize t
Sun, 22 Mar 2009 14:37:28 +0200, Stéfan van der Walt wrote:
> 2009/3/22 Pauli Virtanen :
>>> There is a small problem, in that when I click on any function is
>>> shows that it is set to "No", with the option to change to "Yes" --
>>> even when t
is to fix the precision
> test to use a hardwired range of values, I don't think testing the
> extreme small values is necessary to check the power series expansion.
> But I have been leaving that fixup to Pauli.
I'll do just
-2)
z**101
Do you get a crash at some point?
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Mon, 23 Mar 2009 19:55:17 +, Pauli Virtanen wrote:
> Mon, 23 Mar 2009 13:22:29 -0600, Charles R Harris wrote: [clip]
>> PPC stores long doubles as two doubles. I don't recall exactly how the
>> two are used, but the result is that the numbers aren't in the form
gn and multiple longdoubles and take the square root
> but not use the power '**'.
> >>> y=np.longdouble(2)
> >>> y
> 2.0
> >>> y**1
> 2.0
> >>> y**2
> crash
Ok, this looks a bit tricky, I have no id
way to do it, it can wait.
Done, r6717.
Sorry about the long time it took to get this fixed...
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
om there it directly
seems to go to _basic_longdouble_pow, where it calls npy_pow, which calls
system's powl. (Like so on my system, verified with gdb.)
I don't see branches testing for exponent 1, so this probably means that
the crash occurs inside powl?
--
Pauli Virtanen
__
th.mpf('3e-9')
>>> print (mpmath.atanh(p) - p)*1e27
9.0001681879956480095820042512435586643130912
I'll relax the test tolerance to allow for this...
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
n-working patterns.
> =
> version_pattern = r'Pathscale(TM) Compiler Suite: Version (?P[^\s]*)'
> =
Possibly like so:
version_pattern = r'PathScale\(TM\) Compiler Suite: Version (?P[^\s]*)'
You need the escapes to avoid the first
s probably best answered by the documentation:
http://docs.python.org/library/re.html
In short, the (?P<...>) construct defines a named group.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy
port it and some other doc fixes to 1.3.x tomorrow (if no
objections):
git://github.com/pv/numpy-work.git work-1.3.x
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
torizing the list constructor:
>>> a = np.empty((5,), dtype=np.object_)
>>> a.fill([])
>>> a = np.frompyfunc(list,1,1)(a)
>>> a
array([[], [], [], [], []], dtype=object)
>>> a[0].append('foo')
>>> a
array([['foo'], [], [],
23, I get an exception:
{{{
Traceback (most recent call last):
File "", line 1, in
File ".../numpy-1.4.0.dev-py2.5-linux-x86_64.egg/numpy/lib/io.py", line
436, in loadtxt
raise IOError('End-of-file reached before encountering
use a real file, that is).
Could you test this with Numpy SVN version (or the 1.3 beta).
It's very likely the bug is this one:
http://projects.scipy.org/numpy/ticket/908
and it has already been fixed.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
of ifft in the "Guide to NumPy" book is probably
incorrect:
>>> np.fft.ifft([1,0,0,0])
array([ 0.25+0.j, 0.25+0.j, 0.25+0.j, 0.25+0.j])
whereas that of the online reference guide is correct. (To avoid
confusion between the different docs, i
Fri, 27 Mar 2009 09:20:09 -0400, josef.pktd wrote:
[clip: numpy.random.exponential docstring]
> I changed this a while ago in the documentation editor, but it hasn't
> been merged yet to the source docstring
It is merged, but I forgot to regenerate the mtrand.c file.
--
Pau
t there ought to
be no API changes in the .ZZ, so we'd like docs for newer versions
(possibly containing updates etc.) be labelled as compatible with all
XX.YY. versions.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@s
py/browser/trunk/numpy/lib/io.py#L243
and use a copy of it in your code temporarily. The function is fairly
small.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
k you should open a ticket for this.
The data seems to be in a different order in the index array and in the
data array returned by `find_duplicates`.
It is intended that find_duplicates guarantees that the returned indices
correspond to the returned values?
Another question: the 'recfunc
t.
I think the test is now fixed in trunk:
http://projects.scipy.org/numpy/changeset/6827
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Sphinx >= 0.6. It should now be fixed in Numpy trunk.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Wed, 08 Apr 2009 09:59:50 +0200, Gael Varoquaux kirjoitti:
> On Wed, Apr 01, 2009 at 08:40:15PM +0000, Pauli Virtanen wrote:
>> It was an incompatibility of Numpy's autosummary extension and Sphinx
>> >= 0.6. It should now be fixed in Numpy trunk.
>
> autosum
ll together, as rebasing tends to move also the "trunk"
bookmark around.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
>>> z[0] = 'x'
>>> x
'xbcde'
>>> y
'xbcde'
>>> hash(x)
-1332677140
>>> hash("abcde")
-1332677140
Hashing breaks, and the assumed immutability of strings causes nonlocal
effects
rst time this has been discussed on this ML, but the
last discussion did not (IIRC) lead to any conclusions. (But I think it
was established that detecting when views really overlap is a problem
with no cheap solution. So walking up ->base pointers or comparing ->data
pointers seemed nea
t;> used to build the numpy binaries).
>>
>> cheers,
>>
>> David
>
> numpy compiles fine with mingw, but I never managed to build an egg. I'm
> not able to get the --compiler=mingw32 to be recognized.
I think it might work if you separate the compiling and bdist_egg steps:
setupegg.py build --compiler=mingw32 bdist_egg
Does this help?
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Wed, 15 Apr 2009 16:36:09 -0400, josef.pktd wrote:
[clip]
> Is there a list of gotchas for working with views that might produce
> unexpected results?
I don't think there is. Also, the reference manual would probably need a
separate section about views.
--
Pau
lesome
cases and raise a warning. (The user can silence these, if the behavior
is really relied on.) I don't know what is the performance impact of
Python warnings, though.
The alternative is to have really good documentation on views...
--
Pauli Virtanen
___
Wed, 15 Apr 2009 15:27:21 -0600, Charles R Harris wrote:
> I'm going to move the docstrings from mtrand.pyx to add_newdocs.py. Will
> this require any fixes to the doc editor so that the docs don't get
> readded to mtrand?
Go ahead, nothing should break.
to get me to the site?
I don't see this. Can you try emptying your browser's cache?
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Hi,
buildbot.scipy.org says:
Service Temporarily Unavailable
The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later.
--
Pauli Virtanen
___
Numpy
most equal
(mismatch 100.0%)
x: array([ 2.+1.j, 1.+2.j], dtype=complex64)
y: array([ 7.22953510+1.74995685j, 10.88255692+1.7498703j ],
dtype=complex64)
--
Ran 2034 tests in 41.154s
FAILED (KNOWNFAIL=1, failures=2)
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Sat, 18 Apr 2009 13:19:39 -1000, Eric Firing wrote:
[clip]
> This is a real pain. What is the simplest work-around?
apt-get install libatlas3gf-base
export LD_LIBRARY_PATH=/usr/lib/atlas
Or, just uninstall libatlas3gf-sse2 in favor of the *-base version.
--
Pauli Virta
xplain these issues in depth.
If you want to ensure no-copy, assign to shape:
a.shape = (6,)
> Another remark against reshape:
> OWNDATA flag is False, even if b is a copy !
Apparently, reshape first copies to a contiguous array and then reshapes.
This could be simplified.
be confusing at times.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Wed, 22 Apr 2009 15:12:20 -0400, josef.pktd wrote:
> On Wed, Apr 22, 2009 at 2:37 PM, Pauli Virtanen wrote:
[clip]
>> If you want to ensure no-copy, assign to shape:
>>
>> a.shape = (6,)
[clip]
> Is the difference between assigning to the attribute and using the
This would limit our responsibility to just ensuring that our Nose
extensions work with all relevant Nose versions.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
imized Atlas libraries shipped with Ubuntu 9.04 are broken:
https://bugs.launchpad.net/bugs/363510
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
isting the branches, would help this.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
cision.
The only thing that does not work is integration, since it seems to
force-cast to float:
>>> np.polyint(p)
poly1d([ 0., 1., 3., 0.])
This is a bug in itself, since poly1d could well have complex
coefficients.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
will work fine with minor changes, so I see no
reason not to make sure we're consistent with duck typing.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Fri, 24 Apr 2009 19:04:50 +, Pauli Virtanen wrote:
> Well, Numpy's poly1d will work fine with minor changes, so I see no
> reason not to make sure we're consistent with duck typing.
polyint fixed in r6883, there doesn't seem anything else to fix:
>>> import
0],
[0, 0, 0, ..., 0, 0, 0],
[0, 0, 0, ..., 0, 0, 0]], dtype=object)
The trick is to create an universal function out of the object
constructor, and feed it initializer data. Works for any classes.
I'm undecided whether it'd be a good idea to add a specialized routine
fo
es
> that could then be merged.
I don't think broken trunk has often been a significant problem in Numpy
in the past. Anyway, feature branches are good, and we have the
buildbot.scipy.org, so there's no reason not to check it after committin
Fri, 08 May 2009 11:45:51 +0400, Ilya A. Kozyreff kirjoitti:
> $ python setup.py install --prefix=/nethome/ia/usr/
>
> $ python -c 'import numpy; numpy.test()'
[clip]
> ImportError: No module named numpy
[clip]
> What I do wrong?
http://docs.python.org/install/index.html#modifying-python-s-search
http://trac-hacks.org/ticket/3233
I applied the patch from the ticket; I think password resets should work
now, so you can try using your old accounts again.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.
eat with structured arrays copied for speed.
> --
[clip]
Buildbot can't. I'd suggest removing your build/ directory and
rebuilding, to see if it's caused by some file not rebuilding properly.
Otherwise,
Mon, 11 May 2009 16:22:37 +0200, Nils Wagner kirjoitti:
> On Mon, 11 May 2009 14:05:13 + (UTC)
> Pauli Virtanen wrote:
>> Mon, 11 May 2009 14:06:07 +0200, Nils Wagner kirjoitti:
>>> Can someone reproduce the following failure ? I am using
>>>>>&g
Wed, 13 May 2009 13:18:45 -0700, David J Strozzi kirjoitti:
[clip]
> Many of you probably know of the interpreter yorick by Dave Munro. As a
> Livermoron, I use it all the time. There are some built-in functions
> there, analogous to but above and beyond numpy's sum() and diff(), which
> are quite
re
doing. Preparing a self-contained code example could help here, at least
this would make pinpointing where the error is more easy.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
manual/yorick_46.php#SEC46
http://yorick.sourceforge.net/manual/yorick_47.php#SEC47
I must say that I don't see many functions missing in Numpy...
David (Strozzi): are these the functions you meant? Are there more?
--
Pauli Virtanen
___
Nump
Hi,
Sat, 16 May 2009 16:01:00 +0300, Quilby wrote:
[clip]
> http://www.scipy.org/doc/numpy_api_docs/numpy.linalg.linalg.html#lstsq
[clip]
Could we take these old Endo-generated docs down, and make the URL
redirect to docs.scipy.org?
I believe they are more harmful than helpful...
--
Pa
Sat, 16 May 2009 14:02:34 +, Pauli Virtanen wrote:
> Hi,
>
> Sat, 16 May 2009 16:01:00 +0300, Quilby wrote: [clip]
>> http://www.scipy.org/doc/numpy_api_docs/numpy.linalg.linalg.html#lstsq
> [clip]
>
> Could we take these old Endo-generated docs down, and ma
ms to work differently from asarray.
This may actually be a bug in matplotlib; perhaps you should ask the
people on the matplotlib lists if this is really the intended behavior.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.
that this doesn't get forgotten.
Thanks,
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
sdos/programming/news/yorick.10
.. [2] http://www.scilab.org/platform/index_platform.php?page=history
.. [3] http://en.wikipedia.org/wiki/GNU_Octave#History
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.s
x[1,:].copy()
>
> If not, please advise.
Yes, it should be x[1,:].copy(). Please feel free to correct it.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Thu, 21 May 2009 01:45:54 -0700, dmitrey wrote:
> I have updated numpy to latest '1.4.0.dev7008', but the bug still
> remains.
> I use KUBUNTU 9.04, compilers - gcc (using build-essential), gfortran.
Worksforme on Ubuntu 9.04, on python2.6 and python2.5. Should be the same
p
Thu, 21 May 2009 09:26:18 +, Pauli Virtanen wrote:
> Thu, 21 May 2009 01:45:54 -0700, dmitrey wrote:
>
>> I have updated numpy to latest '1.4.0.dev7008', but the bug still
>> remains.
>> I use KUBUNTU 9.04, compilers - gcc (using build-essential), gfortran.
memory fragmentation. Also, you should check that
you don't have an ulimit set for virtual/RSS memory.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
ding empty files:
http://projects.scipy.org/numpy/ticket/1115
which is maybe related.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Thu, 21 May 2009 10:54:21 -0700, Grant Kelly wrote:
> It's an immutable page. Can someone who already has access make the
> edit?
Umm, are you sure? I don't see any ACL's on the page. (Though you need to
register an account on the wiki before editing.
OTOH, implements the pickle protocol, and will unwrap non-
array objects so that all their attributes etc. are exposed in the hdf5
file and can be read by non-Python applications.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@s
ar 0 when I checked it.
What do you mean by "nowhere near"? What does the following output for
you:
>>> np.arctanh(np.array([1e-5 + 1e-5j], np.complex64))
array([ 9.9975e-06 +9.9975e-06j], dtype=complex64)
--
Pauli Virtanen
t maybe RClass should be a private
> class. Also a name like RowConcatenator (it is a subclass of
> AxisConcatenator) would make more sense. I'm not sure this change is
> worth the trouble though.
I think the RClass is a private imple
Sun, 24 May 2009 19:21:59 +, Pauli Virtanen wrote:
> Sun, 24 May 2009 14:29:30 -0400, Ralf Gommers wrote:
>
>> Hi all,
>>
>> I'm documenting the index_tricks module and am unsure how to handle r_
>> and related objects. r_ is an instance of RClass, th
h the C-side stuff is in place.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
) -> [1,2]
fromstring("1,2,x,4", sep=",", count=5) -> ValueError
fromstring("1,2,x,4", sep=",", count=5, strict=False) -> [1,2]
Fromfile would always behave the same way as `fromstring(file.read())`.
In the above, " " in sep would equal the regexp \w+, and binary data
implied by sep='' would be interpreted in the same way it would if first
converted to comma-separated text.
Can you think of any other alternatives? (Let's forget the names of
the new keyword arguments for the present, and assume they have
perfectly fitting names.)
I'd vote for (e) if the slate was clean, but since it's not:
+1 for (a) or (b)
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
e dictionary interface for the NpzFile class. Any comments as to
> whether this is a good/bad idea, or about the specific implementation?
+0
I don't see any drawbacks, and the implementation looks good.
--
Pauli Virtanen
___
Numpy-discussion
Wed, 03 Jun 2009 16:05:51 -0400, David Warde-Farley wrote:
> On 2-Jun-09, at 3:06 PM, Pauli Virtanen wrote:
>
>> +0
>>
>> I don't see any drawbacks, and the implementation looks good.
>
> Thanks Pauli. I realized I was missing values() and itervalues() (thou
as Python warnings instead of printing them to
stderr.
***
I added this to 0.7.1-notes.rst.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
[clip]
>
> Should I open a ticket for that?
Please do, the current behavior doesn't seem correct.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
onsiderably more work than just
representing the binary data. Also, I doubt that this would be very
useful: representing large amounts of data as text is not efficient. I
also think few people have interest in this feature.
--
Pauli Virtanen
___
Nump
rst file, eg.,
http://docs.scipy.org/numpy/docs/numpy-docs/reference/routines.set.rst/
in order to be included in the final documentation.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
ly go here:
http://docs.scipy.org/numpy/docs/numpy-docs/reference/c-api.array.rst/#array-iterators
Probably as a new subsection.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
ize.py in Numpy's SVN that should report the
status, but it's currently broken.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
const @type@ tmp = x - y;
>
> is -inf or not. And if it is, just to return -inf.
That's not the correct fix.
Anyway, fixed in r7059.
--
Pauli Virtanen
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
On 2009-06-19, Nils Wagner wrote:
> Is this a known failure ?
> I am using 1.4.0.dev7069
Check the tickets:
http://projects.scipy.org/numpy/ticket/1108
Cause is not known yet, but that bug most likely has been around for a long
time.
--
Pauli Vi
701 - 800 of 1087 matches
Mail list logo
