> > The intention was to introduce sharing of the filename object between > > code objects compiled from the same file (remember that every method > > is a separate code object). > > > > But I believe the sharing won't happen when the code is loaded from a > > bytecoded file instead, so it is indeed wasted efficiency. > > In 2.4, it would: strings that are interned when being marshalled will > get interned on unmarshalling. Aha! So maybe we should reconsider whether mwh's removal of the filename interning in the compiler should be reverted. --Guido van Rossum (home page: http://www.python.org/~guido/)
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