On Wed, Jul 21, 2010 at 2:03 AM, Mark Hammond <mhammond@...> wrote:
>> Nevertheless, this exception is in importing materials and some
>> advanced features that I am not using, so it should work. In fact, it
>> worked before.
> I'm not sure what you are trying to say here, but it seems clear this is
> your problem. You probably need to work out *why* the IOError is being
> raised and resolve that. Talking to the VPython people might be your best
I talked with them before, and they couldn't help. :(
What I was trying to say is that the importing of the module goes well
until some submodules that are seldom used. So, my workaround is
It is possible that in this case it is importing the module in a
Anyway, the name error is in a very basic command. If it is failing, I
bet a very small part of the module could be imported. I hope I have
explained myself better this time.
I will try again with VPython people. Thank you anyway.