June 2, 2000
6:23 p.m.
Hey Numpy people! On Fri, 2 Jun 2000, Charles G Waldman wrote:
This seems to be fixed in the current CVS version. I suggest you either wait for the next release or grab the current version from CVS if this is really a problem for you.
I don't understand wich files I would need to take a new version from and wich command I have to issue to get a version of Numpy that correct the bug I just hit. Thanks for help. I would like my code to work with the next release. Jean-Bernard