On Mon, Aug 31, 2009 at 08:10, Antoine Pitrou<solipsis at pitrou.net> wrote: > Benjamin Peterson <benjamin <at> python.org> writes: >> >> > Why can't we simply make co_filename a writable attribute instead of > inventing >> > some complicated API? >> >> Because code objects are supposed to be a immutable hashable object? > > Right, but co_filename is used neither in tp_hash nor in tp_richcompare. I didn't suggest this since I assumed co_filename was made read-only for a reason back when the design decision was made. But if the original safety concerns are not there then I am happy to simply change the attribute to writable. -Brett
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