From: Daπid <dav...@gm...> - 2010-07-20 23:38:38
|
Hello. I am working over Windows XP and I am trying to compile some scripts based on VPython, but when I try to execute the exe version, I get: Traceback (most recent call last): File "show_scene.py", line 5, in <module> NameError: name 'display' is not defined display() is a basic command in VPython to create a window. Plus, the script alone works perfectly. Of course, the original .py script, before Py2exe works great without raising errors. The five first lines, until the crash are: 1· try: from visual import * 2· except IOError: pass 3· 4· 5· scene=display() Trying to figure how to solve it, I remembered some VPython scripts I compiled some months ago, that were functional; but when I try to run them, I get similar errors. In this same computer, they ran perfectly some months ago. I don't remember doing any big modification in the OS (appart from the security updates), nor touching the Python installation (although this should work anyway). More testing brings more weird results. Testing both old and new scripts in another similar computer, the old one works great (as it should), but the new one still says the same error. Anyone has any idea on why is it happening and how to solve? Thank you very much. David. P.D.: if anyone needs the complete scritps, just ask for them; I don't have any problem in publishing them. |
From: Mark H. <ski...@gm...> - 2010-07-20 23:56:55
|
On 21/07/2010 9:38 AM, Daπid wrote: > Hello. > > I am working over Windows XP and I am trying to compile some scripts > based on VPython, but when I try to execute the exe version, I get: > > Traceback (most recent call last): > File "show_scene.py", line 5, in<module> > NameError: name 'display' is not defined > > > display() is a basic command in VPython to create a window. Plus, the > script alone works perfectly. Of course, the original .py script, > before Py2exe works great without raising errors. The five first > lines, until the crash are: > > 1· try: from visual import * > 2· except IOError: pass > 3· > 4· > 5· scene=display() I'd guess your import is throwing an IOError. Mark |
From: Daπid <dav...@gm...> - 2010-07-21 00:01:01
|
On Wed, Jul 21, 2010 at 1:56 AM, Mark Hammond <ski...@gm...> wrote: > I'd guess your import is throwing an IOError. VPython always throw it with Py2exe, so I have to silent it with the try. 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. |
From: Stef M. <ste...@gm...> - 2010-07-21 21:05:16
|
On 21-07-2010 02:00, Daπid wrote: > On Wed, Jul 21, 2010 at 1:56 AM, Mark Hammond <ski...@gm...> wrote: >> I'd guess your import is throwing an IOError. > VPython always throw it with Py2exe, so I have to silent it with the > try. 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. > watch the exceptions py2exe is given you, then include the special files explictly (even if you don't need them) This is the code I use for one of the first Vpython versions 5: if Include_VPython : print '*** Include VPython ***' Data_Files.append ( ( r'visual', glob.glob ( r'P:\Python\Lib\site-packages\visual\*.tga' ))) cheers, Stef |
From: Mark H. <mha...@sk...> - 2010-07-21 00:04:08
|
On 21/07/2010 10:00 AM, Daπid wrote: > On Wed, Jul 21, 2010 at 1:56 AM, Mark Hammond<ski...@gm...> wrote: >> I'd guess your import is throwing an IOError. > > VPython always throw it with Py2exe, so I have to silent it with the > try. But obviously a side-effect of that is that the imports aren't happening, so you aren't getting the symbols you desire - hence your NameError. > 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 hope. Cheers, Mark |
From: Daπid <dav...@gm...> - 2010-07-21 00:19:47
|
On Wed, Jul 21, 2010 at 2:03 AM, Mark Hammond <mha...@sk...> 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 > hope. 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 habitually correct. It is possible that in this case it is importing the module in a different order? 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. Regards, David. |