> > That was a purely altruistic proposal. I've already > discovered that sets are finalized and that some code that > works with dict emulating a set may not work with a set. It > will not make much difference for me if my proposal will be > implemented in 2.6 or even in 3.0, but the sooner it will > happen the fewer people will stumble on the same problem that > I did. I also feel that dummy allocated on the heap and the > free set list are complicating the code with no gain. > Can this not be resolved by carefully adjusting the order of finalization? If code can be bootstrapped it can be strootbapped. As a side note, is there a finalization order list for imported modules? Kristján
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