[Python-Dev] how important is setting co_filename for a module being imported to what __file__ is set to?

Brett Cannon brett at python.org
Mon Aug 31 18:27:49 CEST 2009

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.


More information about the Python-Dev mailing list