Also note that the problem only occurs when trying to build a unix-Python out-of-the-box on MacOSX. If you're building a Carbon Python from the MacPython sources (something very few people can do right now:-) the executable isn't called "python". And when a real MacOSX-Python will be done it'll have all the nifty packaging stuff that will also make sure that there's nothing called "python" in the toplevel folder. And the two workarounds (1-Use a UFS filesystem, 2-Put a ".exe" extension in the Makefile) work fine for the mean time. -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm
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