Importer / module loader for filelike objects produces uglystacktraces

N

Nebur

I've made an importer (experimental status) to load python modules
from archives, especially from AES encrypted ones.
( http://sourceforge.net/projects/py-archimporter )

I've followed the PEP 302 recipe (http://www.python.org/dev/peps/
pep-0302/).
The loader does set each modules __file__ attribute to a meaningful
string, similar to a real file name.

Still, any stacktrace of the application looks like that:
(...)
File "<string>", line 1530, in <module>
File "<string>", line 225, in __init__
File "<string>", line 423, in _
(...)
Filenames are "<string>" all over.
Does someone know what am importer has to do for better tracebacks ?
Ruben
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,995
Messages
2,570,236
Members
46,825
Latest member
VernonQuy6

Latest Threads

Top