[EMAIL PROTECTED] wrote on 08/09/2005 17:53:40: > Hi Ben, > > Thanks for tirelessly reporting Windows failures :-) > Which exact Windows are you using, BTW? >
That's alright :) I wish I could do more to actually fix the issues, but by the time I get home from work a can barely stand to even look at a computer if you know what I mean! I'll stop reporting errors / questions if it gets too tiresome for you all. For your information i'm running PyPy on cygwin on XP Pro, which probably exercises a slightly different set of issues to straight windows. P.S Do you have any plans to make annotation/translation more robust, as it seems it is very easy to introduce SomeObjectness without knowing, and even of annotation succeeds, successful translation is not guaranteed (or am I talking rubbish?) Cheers, Ben > The link failures should be resolved. They are due to the unsetenv() > built-in missing on Windows, but still present in os.py -- faked, > implemented in pure Python as os.setenv(xxx, ''). This caused all parts > of the translation to assume that there was an unsetenv() built-in, but > the C include files at the end didn't actually define it because CPython > doesn't define HAVE_UNSETENV. > > The rounding errors are more tricky. We could of course just use an "is > almost equal" comparison, but still we are a bit clueless (though > Christian is digging). > > > Armin > _______________________________________________ > pypy-dev@codespeak.net > http://codespeak.net/mailman/listinfo/pypy-dev > > _______________________________________________ pypy-dev@codespeak.net http://codespeak.net/mailman/listinfo/pypy-dev
