On Aug 29, 6:11 pm, "Diez B. Roggisch" <[EMAIL PROTECTED]> wrote:
> > That will mean that there will be no (easy?) way to determine after the
> > import whether the module was imported from a source file or a compiled
> > file. I've suggested that the original justification for the patch no
> > lon
> That will mean that there will be no (easy?) way to determine after the
> import whether the module was imported from a source file or a compiled
> file. I've suggested that the original justification for the patch no
> longer applies, and that the secondary purpose of the patch is better
> solve
On 29 Aug 2008 15:21:53 GMT, Steven D'Aprano <[EMAIL PROTECTED]> wrote:
On the python-dev mailing list, a question has be raised about a change
to module.__file__ in Python 3.
http://www.gossamer-threads.com/lists/python/dev/674923#674923
In Python 2.x, m.__file__ is the name of the file that t
On the python-dev mailing list, a question has be raised about a change
to module.__file__ in Python 3.
http://www.gossamer-threads.com/lists/python/dev/674923#674923
In Python 2.x, m.__file__ is the name of the file that the module was
imported from. That file might end with .py, .pyc, .pyo, o
