> This has nothing to do with recent work. I am executing pytest from the
command line on Windows.
Mystery solved, and fixed at 16011ec6. The culprit was python3_test.py.
python3_test.py created the "a" and "b" files with module level code!
I found this file by brute force, deleting all files from the unittest
directory and then adding files back until the problem reappeared. The
problem did not happen during unit testing because `@test Python3 features`
does not import this file, it merely compiles it ast.parse. In contrast,
pytest actually imports the file.
This code has now been disabled with an `if 0:` statement, which retains
the code for ast.parse without doing anything harmful at import time. A
relatively small price to pay for making pytest work smoothly.
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
