On Nov 5, 2009, at 9:59 PM, [email protected] wrote: >> What happens when you do this in your Python? >> >> >>> float('+inf'), float('-inf'), float('nan') >> (inf, -inf, nan) >> >>> 1e300 * 1e300 >> inf >> >>> 1e300 * 1e300 * 0 >> nan > > only exceptions for string to float conversion:
Thanks. This is all now http://trac.cython.org/cython_trac/ticket/450 I'm sure we're not the first to deal with it. >>> File "C:\Josef\work-oth\Cython-0.12.alpha0\BUILD\run\cpp >>> \profile_test.pyd", line >>> 57, in profile_test >>> Failed example: >>> os.unlink(statsfile) >>> Exception raised: >>> Traceback (most recent call last): >>> File "C:\Programs\Python25\lib\doctest.py", line 1228, in __run >>> compileflags, 1) in test.globs >>> File "<doctest profile_test[11]>", line 1, in <module> >>> os.unlink(statsfile) >>> WindowsError: [Error 32] The process cannot access the file >>> because it is be >>> ing used by another process: 'c:\\docume~1\\carrasco\\locals~1\ >>> \temp\ >>> \tmpm6kkx5' > > This is a pretty common error on windows, in many packages temp files > don't get cleaned up because Windows still has an open file handle. > Many packages just skip the unlink on Windows and leave some tempfiles > on the system. I usually delete them manually every once in a while > >> >> That's a strange one. If os.fork is available (though it shouldn't be >> on Windows), could you try >> >> python runtests.py --no-fork profile_test > > I will run this tomorrow. No need, I bet the above explains it. I always wondered why Windows users periodically have to delete temp files... I've surrounded the unlink with a try...except block. > >> >>> ---------------------------------------------------------------------- >>> Ran 2950 tests in 1474.453s >>> >>> FAILED (failures=4, errors=14) >> >> Well, at least most of them passed :). Was that on a heavily loaded >> system, or is MingW just a really slow compiler? > > Heavy use, and at memory capacity, I guess a lot of swapping might > be done. > I only use MingW so I cannot compare, but building scipy or running > the full scipy test suite is usually the time for a coffee break. OK. It just took longer than I would have expected. - Robert _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
