Has this been handled yet? If not, perhaps showing the good and bad bytecode here would help trigger someone's brain into understanding the problem. On 11/22/05, Reinhold Birkenfeld <reinhold-birkenfeld-nospam at wolke7.net> wrote: > Hi, > > on my machine, "make test" hangs at test_colorsys. > > Careful investigation shows that when the bytecode is freshly generated > by "make all" (precisely in test___all__) the .pyc file is different from what a > direct call to "regrtest.py test_colorsys" produces. > > Curiously, a call to "regrtest.py test___all__" instead of "make test" produces > the correct bytecode. > > I can only suspect some AST bug here. > > Reinhold > > -- > Mail address is perfectly valid! > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org > -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4