Author exarkun
Recipients arigo, exarkun, loewis, pitrou, zseil
Date 2009-01-05.17:11:08
SpamBayes Score 0.0147827
Marked as misclassified No
Message-id <1231175471.58.0.711115087308.issue1180193@psf.upfronthosting.co.za>
In-reply-to
Content
This is causing problems for me as well.  The attached patch no longer
applies cleanly to trunk.  I've attached an updated version which
addresses the conflicts.  The new behavior fixes the issues I have with
the current behavior.  It'd be great to have it applied.

> If code objects grew a __module__ attribute (which functions already
> have), wouldn't it be just a matter of falling back on 
> sys.modules[my_code_object.__module__].__file__ when
> my_code_object.co_filename points to a non-existent file?

It'd be nice if it wasn't necessary to check to see if co_filename
referred to an existing file.  Can we have a solution which creates one
definitive, correct way to determine the source file?
History
Date User Action Args
2009-01-05 17:11:12exarkunsetrecipients: + exarkun, loewis, arigo, zseil, pitrou
2009-01-05 17:11:11exarkunsetmessageid: <1231175471.58.0.711115087308.issue1180193@psf.upfronthosting.co.za>
2009-01-05 17:11:10exarkunlinkissue1180193 messages
2009-01-05 17:11:10exarkuncreate