[Python-Dev] confusing exec error message in 3.0 (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Fri Aug 29 03:39:01 CEST 2008
- Previous message: [Python-Dev] confusing exec error message in 3.0
- Next message: [Python-Dev] confusing exec error message in 3.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Steven D'Aprano wrote:
I don't think M.file should lie and say it was loaded from a file that it wasn't loaded from. It's useful to be able to look at a module and see what file it was actually loaded from.
On the other hand, it could be useful to be able to find the source file for a module, regardless of whether it was loaded from a .py, .pyc or .pyo.
Maybe there should be a source attribute for that?
Or is os.path.splitext(M.file)[0] + ".py" considered good enough for that?
-- Greg
- Previous message: [Python-Dev] confusing exec error message in 3.0
- Next message: [Python-Dev] confusing exec error message in 3.0
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]