[Jeremy] > I just noticed that a make install prints out a bunch of warnings > about .py files it is compiling. Yes, JimF noticed that within the last week too, and it threw him off track (me too). Meant to mention it. Of course it's not a problem on Windows -- no make there to make make problems <wink>. Irrelevantly, the damaged files test_future.py is trying to import should not have been named with a "test_" prefix (maybe a "bad_" prefix instead), and then there would have been no need to add them to the NOTTEST list in regrtest.py either. Could the Unix makefile be taught not to compile the supposed-to-fail .py files? Would that be easier if all the supposed-to-fail files were renamed to something other than test_*.py?
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