Thomas Wouters wrote: > > On Tue, Aug 07, 2001 at 12:57:03AM -0400, Tim Peters wrote: > > > I've noted before that we're fast running out of this kind of thing (meaning > > big features discussed for a long time). Perhaps a formal notion of > > interface, some flavor of optional static typing, and major tweaks to the > > numeric model, will still occur, but that's "about it" for semantic features > > that have been discussed forever. > > Let's not forget 'free threading', which is another one of those 'generally > benificial' features that will break code. Is that true? I thought that you would have to ASK to use free threading in a particular program. I'm discussing threading models with our internal Perl guys and I'm curious about one thing: what prevents a person from running two non-communicating Python interpreters in two threads? What kind of data is shared between interpeters? -- Take a recipe. Leave a recipe. Python Cookbook! http://www.ActiveState.com/pythoncookbook
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