Basically I suspect we've either got an import bug or (more likely IMHO) a documentation bug, but I don't want to file on sf until I know exactly what the problem is, and I'm reluctant to use too much bandwidth on python-dev, which I know to be a busy list.
The background is visible in the Python-list archives starting at
http://mail.python.org/pipermail/python-list/2005-January/262148.html
Of course it's possible that a savvy developer can just tell me what the problem is by reading that thread.
If not, being a bear of little brain I need help from someone who is used to running debugging interpreters and can see exactly what's going on - my debugging system is fine for Python source, but has no insight into the interpreter code itself.
Since I'm not currently subscribed to python-dev an email response (or, better, a follow-up on the c.l.py thread) would be appreciated if you can solve this problem.
I'm happy to send full code off-list (or on-list, come to that) to anybody who can assist.
regards Steve -- Meet the Python developers and your c.l.py favorites Come to PyCon!!!! http://www.python.org/pycon/2005/ Steve Holden http://www.holdenweb.com/
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
