On 20 September 2007 07:23, Mike MacFerrin wrote:
> I'm a grad student in a Compiler Tools course, and (as part of the course)
> we're compiling a subset of the Python language down to C, and from there
> to x86 Assmebly. Our code has to pass a lengthy series of test-suites for
> correctness (comparing the output of our compiled C Code with that of
> native Python code), and I stumbled across what seems to be a quirky bug in
> Cygwin Python 2.5.1 (the most recent install).
> Any suggestions or workarounds?
Can you roll back your install? 2.4.3 doesn't reproduce the problem.
cheers,
DaveK
--
Can't think of a witty .sigline today....
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
