On Feb 23, 3:27 pm, [EMAIL PROTECTED] wrote: > On Feb 23, 12:00 pm, [EMAIL PROTECTED] wrote: > ... > > > > > + gmpy is looking pretty unmaintained (dead) to me (newest update of > > > > cvs 10 months ago). > > > I worked withAlex Martelli(gmpy's maintainer) to fix a bug found by > > mensanator. With Alex's permission, I released it as gmpy 1.04a. Alex > > has not updated cvs with the fix. > > Heh, I see why one might get that impression -- I'm in the process of > moving gmpy from sourceforge (where I find it harder and harder, and > ever more problematic, to work) to code.google.com 's new hosting > facility -- gmpy 1.02 prerelease (more updated than that "1.04a", and > particularly including your fix, Case) is already available > athttp://code.google.com/p/gmpy/but I have made no official > announcement yet (partly because what's available is yet limited: > sources, and binaries for Python 2.3, 2.4 and 2.5 but only for MacOSX > 10.4 on Macs with intel processors)... building binaries for Windows > (not having a Windows machine or development system) or Universal > binaries for the Mac (due to problems building Universal versions of > the underlying GMP in its latest, 4.2 incarnation... I'm running out > of PPC-based Macs, and have none left with MaxOSX 10.3...) is much > more problematic for me. > > To call this (Google Code) release 1.02, with a "1.04" (?) out from > another source, may be confusing, but I'd rather not "force" the > number upwards > > I do have one new co-owner on the Google Code "version" of gmpy (Chip > Turner, once author of a similar GMP wrapper for perl, now a Python > convert and a colleague of mine) but I suspect that won't make the > building of Windows (and Universal Mac) binaries much easier. If > anybody who has easy access to Microsoft's MSVC++.NET (and is willing > to try building GMP 4.2 with/for it), or a PPC Mac with XCode > installed (possibly with MacOSX 10.3...), wants to volunteer to build > "the missing binaries" for the platforms that the current owners of > gmpy can't easily support, we could complete, test and release the > definitive 1.02, and move on with the development (I could get > enthusiastic about this again, if I could develop just the sources, > and the binaries for the one architecture I really use -- Macs w/intel > -- rather than strive each time with binaries for architectures that > are quite a pain for me...!-). > > Anybody who's interested in helping out is welcome to mail me and/or > use the "wiki" and "issues" entry of the Google Code gmpy site... > > Thanks, > > Alex
I can keep building gmpy for Windows. I actually use MINGW since getting GMP compiled under MSVC is "challanging". I should be able to build new binaries for Windows this weekend. And I would be happy to point everyone to a real release. casevh -- http://mail.python.org/mailman/listinfo/python-list
