[Christian Tismer] > ... > I know of many companies (all my Stackless customers, for > instance), who would *never* switch to a Python version that > needs the GC. What relationship does Stackless have with user code creating cycles among Python objects? I don't see any. One thing getting overlooked here is how many newer C-level Python objects register with GC, due to that so many new features end up creating reference cycles. For example, create a new-style class and you've created cycles. If you have a customer who disables cyclic GC, they'll have to avoid other newer features too, or endure leaks.
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