On Mon, 7 Jun 1999, Skip Montanaro wrote: > True enough, but as Guido pointed out, enabling threads by default would > immediately make the Mac a second-class citizen. Test cases and demos would > eventually find their way into the distribution that Mac users could not > run, etc., etc. It may not account for a huge fraction of the Python > development seats, but it seems a shame to leave it out in the cold. I'm not sure I buy that argument. There are already thread demos in the current directory, and no one complains. The windows builds are already threaded by default, and it's not caused any problems that I know of. Think of it like enabling the *new* module. =) > Has there been an assessment of how hard it would be to add thread > support to the Mac? That's an interesting question, especially since ActiveState lists it as a machine w/ threads and w/o fork(). --david
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