Re: gmpy 1.01 rc near... anybody wanna test>

[EMAIL PROTECTED] wrote: > [EMAIL PROTECTED] wrote: > > What processor are you running? > > Drat, didn't see this before I left work. I'm fairly certain it was a > Pentium 4, definitely 1.7GHz, Win2000 and Python 2.3. > > So I thought I would run the test again on my home computers, > a Pentium 4 1

Re: gmpy 1.01 rc near... anybody wanna test>

[EMAIL PROTECTED] wrote: > What processor are you running? Drat, didn't see this before I left work. I'm fairly certain it was a Pentium 4, definitely 1.7GHz, Win2000 and Python 2.3. So I thought I would run the test again on my home computers, a Pentium 4 1.5 GHz WinXP Python 2.3 and a laptop w

Re: gmpy 1.01 rc near... anybody wanna test>

[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: ... > Excellent work guys! > > Not only is the divm() bug fixed but it looks like we got a > significant performance increase. Thanks! Alex -- http://mail.python.org/mailman/listinfo/python-list

Re: gmpy 1.01 rc near... anybody wanna test>

David Gutierrez <[EMAIL PROTECTED]> wrote: > Include me in your list, please. Uh, what list? If you mean gmpy-commits, you subscribe to it on gmpy.sf.net -- if you mean the general Python list, on www.python.org. Alex -- http://mail.python.org/mailman/listinfo/python-list

Re: gmpy 1.01 rc near... anybody wanna test>

What processor are you running? I only have Windows running on an old Pentium 3. It is easy for me to build a version that will running on almost any recent processor. I'm willing to try and override the CPU detection and make a processor specific build for you. I won't be able to test it, though.

Re: gmpy 1.01 rc near... anybody wanna test>

Alex Martelli wrote: > <[EMAIL PROTECTED]> wrote: > > > I've created Windows binaries for Python 2.3 and 2.4. It should be > > compatible with PentiumPro or later processors. > > Thanks! I hope to package up a release early next week, and to include > these. > > > Alex I downloaded the binaries a

Re: gmpy 1.01 rc near... anybody wanna test>

Include me in your list, please. David From: [EMAIL PROTECTED] (Alex Martelli) To: python-list@python.org Subject: Re: gmpy 1.01 rc near... anybody wanna test> Date: Fri, 11 Nov 2005 07:10:01 -0800 MIME-Version: 1.0 Received: from smtp-vbr7.xs4all.nl ([194.109.24.27]) by mc10-f5.hotmail.

Re: gmpy 1.01 rc near... anybody wanna test>

<[EMAIL PROTECTED]> wrote: > I've created Windows binaries for Python 2.3 and 2.4. It should be > compatible with PentiumPro or later processors. Thanks! I hope to package up a release early next week, and to include these. Alex -- http://mail.python.org/mailman/listinfo/python-list

Re: gmpy 1.01 rc near... anybody wanna test>

I've created Windows binaries for Python 2.3 and 2.4. It should be compatible with PentiumPro or later processors. They can be found at http://home.comcast.net/~casevh/ Case -- http://mail.python.org/mailman/listinfo/python-list

Re: gmpy 1.01 rc near... anybody wanna test>

Nick Craig-Wood <[EMAIL PROTECTED]> wrote: > I tested gmpy cvs as of now on Debian/testing/x86 with python2.3. It > compiled perfectly, ran all of its unit tests and also all my test > programs - Well done! Thanks! > My test program seemed to run at the same speed with both versions > (not supri

Re: gmpy 1.01 rc near... anybody wanna test>

I tested gmpy cvs as of now on Debian/testing/x86 with python2.3. It compiled perfectly, ran all of its unit tests and also all my test programs - Well done! My test program seemed to run at the same speed with both versions (not suprising really since both are using the same libgmp.so on the syst

Re: gmpy 1.01 rc near... anybody wanna test>

> > Will you be updating the information in setup.py file? > > Done, in the current CVS version. I will grab the CVS version and create installers. > > Which versions of Python do you want to support? > > I have tested gmpy with 2.3 and 2.4 on Mac, and those two and also 2.2 > on Linux. I think

Re: gmpy 1.01 rc near... anybody wanna test>

<[EMAIL PROTECTED]> wrote: ... > I made a successful installer for Windows using Mingw32 and Python 2.4. Great, thanks. > I needed to edit setup.py to list gmp as a required library. > > if sys.version.find('MSC')==-1: > gmpy_ext = Extension('gmpy', sources=['src/gmpy.c'], > # lib

Re: gmpy 1.01 rc near... anybody wanna test>

Alex Martelli wrote: > <[EMAIL PROTECTED]> wrote: > > > Everything works fine with v1.16. I'm sure I was doing something wrong. > > I shouldn't be testing that late at night. ;-) > > > > It looks like the warning about "tp_compare" has been fixed. > > I didn't touch tp_compare specifically, so the

Re: gmpy 1.01 rc near... anybody wanna test>

<[EMAIL PROTECTED]> wrote: > Everything works fine with v1.16. I'm sure I was doing something wrong. > I shouldn't be testing that late at night. ;-) > > It looks like the warning about "tp_compare" has been fixed. I didn't touch tp_compare specifically, so the fix must have been a side effect (

Re: gmpy 1.01 rc near... anybody wanna test>

Everything works fine with v1.16. I'm sure I was doing something wrong. I shouldn't be testing that late at night. ;-) It looks like the warning about "tp_compare" has been fixed. I will try to build a version for Windows, but that may take me a day or two. Thanks for the updates to gmpy! Case

Re: gmpy 1.01 rc near... anybody wanna test>

Alex Martelli wrote: > Steve Holden <[EMAIL PROTECTED]> wrote: >... > >>I tried compiling it with the MS free toolkit but the C compile >>complains about the absence of "gmp.h". Since I see such a header in my >>Cygwin installation I presume it's something that a full VC7 >>installation coul

Re: gmpy 1.01 rc near... anybody wanna test>

Steve Holden <[EMAIL PROTECTED]> wrote: ... > I tried compiling it with the MS free toolkit but the C compile > complains about the absence of "gmp.h". Since I see such a header in my > Cygwin installation I presume it's something that a full VC7 > installation could expect to be present. gmp

Re: gmpy 1.01 rc near... anybody wanna test>

Paul Rubin wrote: > [EMAIL PROTECTED] (Alex Martelli) writes: > > gmpy users able to download and build from sourceforge's cvs are > > encouraged to test the current CVS version. > > Oh cool, I wondered whether any gmpy maintenance was still going on. Only when I get g

Re: gmpy 1.01 rc near... anybody wanna test>

<[EMAIL PROTECTED]> wrote: > I downloaded and tried the CVS version. Division still didn't work as > expected. Now that's truly interesting... > >>> import gmpy > >>> gmpy.version() > '1.01' > >>> gmpy.mpz(9)//gmpy.mpz(4) > Traceback (most recent call last): > File "", line 1, in ? > TypeError

Re: gmpy 1.01 rc near... anybody wanna test>

[EMAIL PROTECTED] (Alex Martelli) writes: > gmpy users able to download and build from sourceforge's cvs are > encouraged to test the current CVS version. Oh cool, I wondered whether any gmpy maintenance was still going on. I'll see if I can give the new version a try. -- http://mail.python.org/m

Re: gmpy 1.01 rc near... anybody wanna test>

Alex Martelli wrote: > I have fixed almost all of the outstanding bugreports and feature > request for gmpy: divm doesn't leak memory any more, truediv and > floordiv are implemented for all types, etc -- in the current CVS > version (one thing I must still look at is divm's behavior when its args

Re: gmpy 1.01 rc near... anybody wanna test>

I downloaded and tried the CVS version. Division still didn't work as expected. >>> import gmpy >>> gmpy.version() '1.01' >>> gmpy.mpz(9)//gmpy.mpz(4) Traceback (most recent call last): File "", line 1, in ? TypeError: unsupported operand type(s) for //: 'mpz' and 'mpz' >>> from __future__ impor

gmpy 1.01 rc near... anybody wanna test>

I have fixed almost all of the outstanding bugreports and feature request for gmpy: divm doesn't leak memory any more, truediv and floordiv are implemented for all types, etc -- in the current CVS version (one thing I must still look at is divm's behavior when its args are not mutually prime). It