On woensdag, juli 10, 2002, at 11:56 , Michael Hudson wrote: >> This won't work for one of the standard use cases: having multiple >> "build" subdirectories of the source directory (where you build for >> different platforms or some such). > > How so? It worked for my cron jobs last night, which build in this > fashion. You're right, of course. I was confusing this with the sys.path initialization code. I think there's absolutely nothing wrong with your solution. > >> And on the other question: as of a week ago setup.py is also >> being used >> to build at least some of the MacPython extension modules. > > Is this MacPython as built by CodeWarrior? I'm counting MacOS X as > unix when it's convenient to do so :) Correct. Over on the pythonmac-sig the use of "MacPython" is (for the time being) reserved to mean the CodeWarrior-built Python that will also run on OS9. MachoPython is used for the OSX-only unix Python. And, as I said (or try to say:-), "don't worry about MacPython builds, they'll continue to work. -- - Jack Jansen <Jack.Jansen@oratrix.com> http://www.cwi.nl/~jack - - If I can't dance I don't want to be part of your revolution -- Emma Goldman -
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