[Tim' > I'm seeing three seemingly unrelated failures on Windows ... > but every one of them *is* trying to import something with a name of > the form "test.XYZ". Ring a bell to anyone? Well, you've all failed me again <wink>. This turned out to be pilot error: I was running from my build directory, and it turned out I had a "test.py" file in there. So any sort of "import test.whatever" picked up that first. I have no idea where it came from, and staring at the contents didn't help because it also turned out it was empty (0 bytes). Removing test.py didn't help either. That's when I discovered test.pyc. The good news is that I remembered to delete test.pyo too before wasting another hour <0.9 wink>. some-days-suck-ly y'rs - tim
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