On Jan 5, 2005, at 18:49, Martin v. Löwis wrote: > Jack Jansen wrote: >> The "new" solution is basically to go back to the Unix way of >> building an extension: link it against nothing and sort things out >> at runtime. Not my personal preference, but at least we know that >> loading an extension into one Python won't bring in a fresh copy of >> a different interpreter or anything horrible like that. > > This sounds good, except that it only works on OS X 10.3, right? > What about older versions? Older versions do not support this feature and have to deal with the way things are as-is. Mac OS X 10.2 is the only supported version that suffers this consequence, I don't think anyone has supported Python on Mac OS X 10.1 in quite some time. -bob
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