Brett Cannon wrote: > > > The idea is that there be a separate Python interpreter per web > > > browser page instance. > > > I think there may be scaling issues there. JavaScript isn't doing that > > is it, do you know? As well, that doesn't seem like it would translate > > well to sharing execution between separate chrome windows in a > > non-browser XUL/Mozilla-based app. > > And if you don't think it is going to scale, how do you think it should > be done? That was an ignorant response (I haven't read what you've suggested and really though about it). Sorry for the unsubstantiated babbling. To Bob's question on how much interpreter state *is* there: I don't know. Have you done any measuring of that, Brett? Trent -- Trent Mick trentm at activestate.com
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