ma, 2010-02-15 kello 00:38 +0100, Xavier Gnata kirjoitti:
> Ok!
> git clone git://github.com/pv/numpy-work.git
> git checkout origin/py3k
> NPY_SEPARATE_BUILD=1 python3.1 setup.py build
>
> but now it fails during the build:
>
> In file included from numpy/core/src/multiarray/buffer.c:14,
> from
Hi all,
I'm pleased to announce version 0.2 of pyfftw, a python module providing access
to the FFTW3 library.
New features:
- pyfftw can now create advanced plans (needs testing)
- provide location of fftw libraries at runtime with an environment variable
- better detection of fftw location at
Perhaps it's my inability to properly use openmp, but when working on
scikits.image on algorithms doing per-pixel manipulation with numpy arrays
(using Cython), i saw better performance using Python threads and releasing
the GIL than I did with openmp. I found the openmp overhead to be quite
large,
On Sun, Feb 14, 2010 at 17:38, Xavier Gnata wrote:
> BTW, is there a better place to discuss these "python3 only" related issues?
I suggest starting a new thread, but numpy-discussion is the right place.
--
Robert Kern
"I have come to believe that the whole world is an enigma, a harmless
enigm
Ok!
git clone git://github.com/pv/numpy-work.git
git checkout origin/py3k
NPY_SEPARATE_BUILD=1 python3.1 setup.py build
but now it fails during the build:
n file included from numpy/core/src/multiarray/buffer.c:14,
from numpy/core/src/multiarray/multiarraymodule_onefile.c:36:
numpy/core/src/multi
On Feb 14, 2010, at 12:02 PM, Charles R Harris wrote:
> Python 2.4
>
> ==
> ERROR: test_view_to_flexible_dtype (test_core.TestMaskedView)
> --
>
> Traceback (mos
Ok, to come back to the original question I have pushed a branch
"bugtracking.01.numpyops" to github.com/friedrichromstedt/upy. If you
want to inspect the problem with some closer look, please pull from
this repo, and run demo.py in the branch mentioned. Today's version
is tagged 10-02-14_GMT-22-
On Feb 14, 2010, at 3:58 PM, Stéfan van der Walt wrote:
> All ndfromtxt does is to force usemask to False (but usemask is False
> by default). This isn't documented, nor is it reflected by the name.
> What am I missing?
http://docs.scipy.org/doc/numpy/user/basics.io.genfromtxt.html#shortcut-func
On 14 February 2010 22:13, Pierre GM wrote:
> On Feb 14, 2010, at 9:27 AM, Stéfan van der Walt wrote:
>> On 14 February 2010 14:54, Pierre GM wrote:
>>> This backwards-incompatibility bugs me. Why don't we set dtype=None as the
>>> default for ndfromtxt & mafromtxt and tell people to use these f
On Feb 13, 2010, at 10:04 PM, David Carmean wrote:
> I'm just starting to work with masked arrays and I've found some behavior
> that
> definitely does not follow the Principle of Least Surprise:
A fuzzy concept ;)
>
> I've generated a 2-d array from a list of lists, where the elements are
>
On Feb 14, 2010, at 9:27 AM, Stéfan van der Walt wrote:
> On 14 February 2010 14:54, Pierre GM wrote:
>> This backwards-incompatibility bugs me. Why don't we set dtype=None as the
>> default for ndfromtxt & mafromtxt and tell people to use these functions
>> instead (I'm pretty sure nobody knew
On Sun, Feb 14, 2010 at 3:01 AM, Pierre GM wrote:
> It has been suggested (ticket #1262) to change the default dtype=float to
> dtype=None in np.genfromtxt. Any thoughts ?
+1
For my case, I didn't use the default behavior hardly at all.
Skipper
___
N
On Sun, Feb 14, 2010 at 11:38 AM, Charles R Harris <
charlesr.har...@gmail.com> wrote:
>
>
> On Sun, Feb 14, 2010 at 11:32 AM, Pauli Virtanen wrote:
>
>> Charles R Harris gmail.com> writes:
>> > - if (ap1->ob_type != ap2->ob_type) {
>> > + if (Py_TYPE(ap1) != Py_TYPE(ap2)) {
>> >
>> > Pauli fix
On Sun, Feb 14, 2010 at 11:32 AM, Pauli Virtanen wrote:
> Charles R Harris gmail.com> writes:
> > - if (ap1->ob_type != ap2->ob_type) {
> > + if (Py_TYPE(ap1) != Py_TYPE(ap2)) {
> >
> > Pauli fixed a lot of those. Did you remove the old build directory and
> all
> that stuff?
>
> I thought I fi
Charles R Harris gmail.com> writes:
> - if (ap1->ob_type != ap2->ob_type) {
> + if (Py_TYPE(ap1) != Py_TYPE(ap2)) {
>
> Pauli fixed a lot of those. Did you remove the old build directory and all
that stuff?
I thought I fixed all of those, but apparently missed that one. Builds fine for
me, but
Xavier Gnata gmail.com> writes:
> Well I ran git clone git://github.com/pv/numpy-work.git an hour ago (in
> an empty directory)
That will give you the master branch, which indeed does not contain any Py3
stuff. You need also to switch to the py3k branch:
git co origin/py3k
To see all availa
Python 2.4
==
ERROR: test_view_to_flexible_dtype (test_core.TestMaskedView)
--
Traceback (most recent call last):
File
"/home/numpybb/Buildbot/numpy/b13/numpy-
On 14 February 2010 14:54, Pierre GM wrote:
> This backwards-incompatibility bugs me. Why don't we set dtype=None as the
> default for ndfromtxt & mafromtxt and tell people to use these functions
> instead (I'm pretty sure nobody knew they existed, so we can break them
> without upsetting anyon
On Feb 14, 2010, at 7:47 AM, Neil Crighton wrote:
> Pierre GM gmail.com> writes:
>
>>
>> It has been suggested (ticket #1262) to change the default dtype=float to
> dtype=None in np.genfromtxt.
>> Any thoughts ?
>>
>
> I agree dtype=None should be default for the reasons given in the ticket.
Pierre GM gmail.com> writes:
>
> It has been suggested (ticket #1262) to change the default dtype=float to
dtype=None in np.genfromtxt.
> Any thoughts ?
>
I agree dtype=None should be default for the reasons given in the ticket.
How do we handle the backwards-incompatible change? A warning
On 14 February 2010 01:23, David Cournapeau wrote:
> I think that there should be absolutely no change whatsoever, for two reasons:
> - the release is in a few weeks, it is too late to change much. The
> whole datetime issue happened because the change came too late, I
> would hope that we avoid
Dag Sverre Seljebotn wrote:
> Pauli Virtanen wrote:
>> We will most likely have experimental py3 support in 2.0.
>>
>> If you, or someone else wishes to help bringing 2.0 to fully work
>> with Py3, now is a very good time to step up.
>>
> ...
>> Finally, try to write some PEP 3118 using code, a
Pauli Virtanen wrote:
> We will most likely have experimental py3 support in 2.0.
>
> If you, or someone else wishes to help bringing 2.0 to fully work with Py3,
> now is a very good time to step up.
>
...
> Finally, try to write some PEP 3118 using code, and check how it works. (You
> can use
On 02/13/2010 09:28 PM, Pauli Virtanen wrote:
> We will most likely have experimental py3 support in 2.0.
>
> If you, or someone else wishes to help bringing 2.0 to fully work with Py3,
> now is a very good time to step up.
>
> How to give a hand:
>
> 1. Get my latest py3 branch from http://github
On Sun, Feb 14, 2010 at 4:01 PM, Pierre GM wrote:
> It has been suggested (ticket #1262) to change the default dtype=float to
> dtype=None in np.genfromtxt. Any thoughts ?
>
Comments in the ticket make sense, and I don't see a downside. Type
inference should be done only once, so performance for
On Sun, Feb 14, 2010 at 2:17 AM, Charles R Harris
wrote:
> That's what I was looking for. I see that it works for python >= 2.4 with
> some work. Does it work for python 3.1 also?
I haven't tried, but a quick scan of the code makes me think it would
be pretty easy to port it to 3.1. It's all fai
On Sun, Feb 14, 2010 at 2:40 AM, David Goldsmith
wrote:
>
> Curious: how is sympy at deducing recursion relations and/or index
> functions? Reason: my first thought about Chuck's high-degree issue was
> that in such cases perhaps PrettyPoly (or __pretty__) could attempt to use
> summation notatio
It has been suggested (ticket #1262) to change the default dtype=float to
dtype=None in np.genfromtxt. Any thoughts ?
___
NumPy-Discussion mailing list
NumPy-Discussion@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion
28 matches
Mail list logo
