Maybe a bit off topic but still something that could be potentially interesting and useful is that we could/should start compiling all these "bugs" and turn them into unit tests so that future proofing is handled.
Not sure if for a IDE like spyder Travis (now that the move to github seems inminent) could provide some sort of testing in this direction. I will start scrapping all these "bugs" in the wiki for the moment. Cheers On Tuesday, October 7, 2014 5:44:06 PM UTC+2, Adrian Klaver wrote: > > On 10/06/2014 08:51 AM, Patrick Leinenkugel wrote: > > Yes, I definitely used the same python distribution. > > What perhaps is of interest to you is that I experienced different > > tolerances in the Python IDLE of producing these arrays (3-5 arrays), > > while with Spyder, it was either one or a maximum of two arrays, that > > could be created. So in all cases, I was able to create a higher number > > of arrays with IDLE than with Spyder. Now, with the 64-bit version, I > > have no problems creating a large number of arrays also in Spyder. > > My guess is that this is related to this thread: > > https://groups.google.com/forum/#!topic/spyderlib/PoOig4rf43c > > You might to file an issue: > > https://code.google.com/p/spyderlib/issues/list > > > Cheers, > > Patrick > > > > -- > Adrian Klaver > [email protected] <javascript:> > -- You received this message because you are subscribed to the Google Groups "spyder" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/spyderlib. For more options, visit https://groups.google.com/d/optout.
