Aaargh, I think I've found out what the problem is. I'm using framework builds on MacOSX. I have two experimental builds of Python 3.1 around, plus a standard one installed in /Library. It's picking up the version of Python.framework in /Library/Frameworks instead of the one in the local build directory that python.exe was explicitly linked with. Now I'm confused about why my *other* experimental build worked -- the one I've been using for yield-from and codef -- because it should have suffered from the same problem. And when I tried to use it again just now, it did indeed not work. Does anyone know if there's a way to tell Apple's linker to use a framework from a specific location and not go looking anywhere else? In the meantime, I think I'll switch to a non-framework build for this project. -- Greg
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