Menu
▾
▴
Re: [Numpy-discussion] RE: Python 2.2 seriously crippled for numerical computation?
|
From: Jochen <jo...@un...> - 2002-03-20 01:53:21
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 19 Mar 2002 20:20:36 -0500 Tim Peters wrote: Thanks for the quick answer. The problem is resolved. Tim> [jo...@bo...] >> [1] If it is in there, it doesn't work for me with current python cvs >> branch release22-maint. I still have to manually add -lieee. >> (RedHat-7.0 with current updates.) Tim> I don't know what "current" meant to you at the time you wrote this. About 20:00 (8:00pm) EST today, March 19. Tim> Tim> Michael Hudson did backport the patch into 2.2.1c1, which Tim> Tim> was released yesterday. So please try 2.2.1c1, and if you Tim> Tim> still have a problem, file a bug report about it on Tim> Tim> SourceForge. 2.2.1 final is expected in about a week. Well, changing cvs from release22-maint to r221c1 helps. That is, everything seems to work fine with the cvs sources tagged r221c1. Then, is it really necessary to mess up the cvs tags so much? Why isn't it possible to have a single python-2.2 branch which one could follow to get all the stuff that's incorporated into that version? [1] There are huge differences between release22-maint and r221c1, it seems from the number of patches applied when going from one to the other. But then some files are in the same (non-main) branch. ??? Thanks for all your work, and thank you for the quick help again. Greetings, Jochen - -- University of North Carolina phone: +1-919-962-4403 Department of Chemistry phone: +1-919-962-1579 Venable Hall CB#3290 (Kenan C148) fax: +1-919-843-6041 Chapel Hill, NC 27599, USA GnuPG key: 44BCCD8E -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6-cygwin-fcn-1 (Cygwin) Comment: Processed by Mailcrypt and GnuPG <http://www.gnupg.org/> iEYEARECAAYFAjyX6yYACgkQiJ/aUUS8zY76QwCdGZsJd1b+0qJ19LJ5TlvwI5fP kbcAniNe/5eiPnEUfGbddLCpyYD1+gmr =fLmk -----END PGP SIGNATURE----- |
