Christopher Barker wrote:
> Hi folks,
>
> This isn't really a numpy question, and I'm doing this with regular old
> python, but I figure you are the folks that would know this:
>
> How do I get python to make a distinction between -0.0 and 0.0? IN this
> case, I'm starting with user input, so:
Darren Dale wrote:
> I'm not a core numpy developer and don't want to step on anybody's
> toes here. But I was wondering if anyone had considered approaching
> the Python Software Foundation about support to help get numpy working
> with python-3?
What kind of support are you talking about? Develo
David Cournapeau wrote:
> No, and it never will. Parallel builds requires to build with
> dependency handling. Even make does not handle it well: it works most
> of the time by accident, but there are numerous problems (try for
> example building lapack with make -j8 on your 8 cores machine - it
>
David Cournapeau wrote:
> It is said in the email that this is reserved to the python project, and
> prominent python projects like Twisted and Django. Would it be ok to try
> to be qualified as a prominent python project as well ?
Give it some time. Nobody - not even the Python core devs - have a
David Cournapeau schrieb:
> Do you only need numpy or also scipy ? If you only need numpy, it is
> relatively straightforward because you don't need BLAS/LAPACK nor any
> fortran compiler. You should use the Visual Studio compiler, though: VS
> 2005 for python 2.5 or VS 2008 for python 2.6 - mingw
Andrew Dalke wrote:
> There are a few things that Python-the-language guarantees are singleton
> objects which can be compared correctly with "is". Those are:
>
>True, False, None
The empty tuple () and all interned strings are also guaranteed to be
singletons. String interning is used to o
Ondrej Certik wrote:
> Are we able to provide an actual patch to Python that implements this?
> If so, then I am.
> Imho the proposal should come with an actual patch, otherwise it's
> difficult to judge it.
Your better off with writing a PEP first. In order to implement the
proposal you've to ma
Andrew Dalke wrote:
> When would this "with float ... " considered valid?
[long posting]
Oh h... what have I done ... *g*
Slow down, please. For now there are no concrete plans what-so-ever to
implement the feature in the near future. Some developers have expressed
their interest in a way to a
Ondrej Certik wrote:
> Ok, in the current state, you don't know either what's going to
> happen. If you write
>
> In [1]: x/2*3/4
>
> you have no idea what the result is going to be, you need to analyze
> x.__div__() and start from there. But if you write
>
> In [2]: 1/2*3/4
>
> currently you
Andrew Dalke wrote:
> Or write B \circledast C ? (Or \oast?) Try using Google to search
> for that character.
>>> unicodedata.lookup('CIRCLED ASTERISK OPERATOR')
'⊛'
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.o
Pauli Virtanen wrote:
> To clarify this again: *no* features of C99 were used. The C99 specs were
> only used as a guideline to what behavior we want of complex math
> functions, and I wrote tests for this, and marked failing ones as skipped.
Got it.
> However, it turned out that different test
Charles R Harris wrote:
> I believe C99 was used as a guide to how complex corner cases involving
> +/-0, +/-inf, etc. should behave. However, it doesn't look possible to make
> that behaviour portable without a lot of work and it probably isn't worth
> the trouble. At the moment the failing tests
David Cournapeau wrote:
> The current trunk has 14 failures on windows (with mingw). 12 of them
> are related to C99 (see ticket 869). Can the people involved in recent
> changes to complex functions take a look at it ? I think this is high
> priority for 1.2.0
I'm asking just out of curiosity. Wh
Robert Kern wrote:
> Yes, we know that. The concern I was addressing was the time overhead
> for creating the new dict object every time an ndarray gets
> instantiated. Most of these dict objects would be unused, so we would
> be wasting a substantial amount of time. If you push off the creation
>
Robert Kern wrote:
> I think you could make the dictionary created lazily on the first getattr().
In order to make it work you have to reserve space for a PyObject*
pointer for the instance dict somewhere in your type definition. It's
going to increase the size of every object by 4 bytes on a 32
Stuart Brorson schrieb:
> Hi --
>
> Sorry to be a pest with corner cases, but I found another one.
[...]
Mark and I spent a *lot* of time in fixing those edge cases in Python
2.6 and 3.0. We used the C99 standard as template. I recommend that you
look at our code.
Christian
___
Robin schrieb:
> If I try to allocate something too big for the available memory I
> often get a MemoryError exception. However, in other situations,
> Python memory use continues to grow until the machine falls over. I
> was hoping to understand the difference between those cases. From what
> I've
Matthieu Brucher schrieb:
> Hi,
>
> As I've said, you must start by compiling Python with VC++ 8, that means
> using the 2.6 alpha.
Negative Houston
Python 2.6 and 3.0 are using VS 2008 aka VC 9.0
Christian
___
Numpy-discussion mailing list
Numpy-dis
Stuart Brorson wrote:
> math.pow(0, -1)
>> Traceback (most recent call last):
>> File "", line 1, in
>> ValueError: math domain error
>
> Why isn't this one inf?
The standard says return inf and raise a divide-by-zero floating point
exception. Since we can't do both in Python we sticked to
Stuart Brorson wrote:
> I have been poking at the limits of NumPy's handling of powers of
> zero. I find some results which are disturbing, at least to me.
> Here they are:
[SNIPP]
Please checkout Mark Dickinson's and my trunk-math branch of Python 2.6.
We have put lots of effort into fixing ed
David Cournapeau wrote:
> Do you have a link to the related python ML discussion by any chance ?
No, I'm sorry. It was a private chat between between Guido, Martin and
me during the release phase of Python 3.0a2.
The MSDN website has some articles about SxS DLLs though. I had to read
about ten ar
Matthieu Brucher wrote:
> When Visual Studio 2008 will be used, there might be a way of using the
> manifest files (that were created for a similar purpose).
> For the moment, All I know is that you must put the dll in the
> Windows/system32 folder or somewhere in the PATH.
That's not enough for s
Hello!
The Python core developers are currently working on several improvements
for floats and the math module. Since you are "power users" I like to
get your opinion and suggestions on several patches:
http://bugs.python.org/issue1534 -- sys.float_info [done]
http://bugs.python.org/issue1580 --
23 matches
Mail list logo
