Running DeVIDE on windowxp 64bit

17 views
Skip to first unread message

Simon Su

unread,
Oct 21, 2009, 9:54:56 AM10/21/09
to devide-users
Hi All,

I downloaded and installed DeVIDE for winxp 64 bit on my laptop. Once
installed, I get two icons on the desktop; "DeVIDE" and "DeVIDE no-
itk".

However, when I click on DeVIDE, or run dre.cmd from a cmd window, I
get the following.

C:\Program Files\DeVIDE-RE>dre.cmd
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "C:\Program Files\DeVIDE-RE\\dre.py", line 7, in <module>
import ConfigParser
ImportError: No module named ConfigParser


Any thoughts?

Thank you much

Simon

Charl Botha

unread,
Oct 21, 2009, 10:56:24 AM10/21/09
to devide...@googlegroups.com
Dear Simon,

2009/10/21 Simon Su <newsgr...@gmail.com>:

I just started up my clean Windows XP64 virtual test machine, but
could not reproduce this behaviour.

Could you send me the output of "dre python -v" ?

Did the installation run to completion without any errors?

Thanks,
Charl

Simon Su

unread,
Oct 21, 2009, 11:33:43 AM10/21/09
to devide...@googlegroups.com
Dear Charl,

The installation completed successfully. No error reported. Here is the output. I am suspecting other packages that I have installed on the machine is conflicting with DeVIDE's run time environment. Are there environment variables that are assumed?

Thanks,
Simon


C:\Program Files\DeVIDE-RE>dre python -v

'import site' failed; use -v for traceback
Traceback (most recent call last):
  File "C:\Program Files\DeVIDE-RE\\dre.py", line 7, in <module>
    import ConfigParser



Charl Botha

unread,
Oct 21, 2009, 11:36:46 AM10/21/09
to devide...@googlegroups.com
2009/10/21 Simon Su <newsgr...@gmail.com>:

> The installation completed successfully. No error reported. Here is the
> output. I am suspecting other packages that I have installed on the machine
> is conflicting with DeVIDE's run time environment. Are there environment
> variables that are assumed?

1. It looks like you might have forgotten the attachment, or the
mailing list is filtering them out.
2. DeVIDE doesn't make any assumptions, although it could be that
another package is setting up certain variables that are causing the
devide init to fail. The output of "dre python -v" would help to see
if this is the case. Is it possible for you to try on a different
machine or even better under a different account?

Simon Su

unread,
Oct 21, 2009, 11:39:51 AM10/21/09
to devide...@googlegroups.com
here is the message



C:\Program Files\DeVIDE-RE>dre python -v
'import site' failed; use -v for traceback
Traceback (most recent call last):
  File "C:\Program Files\DeVIDE-RE\\dre.py", line 7, in <module>
    import ConfigParser

Sorry it got cut....

Charl Botha

unread,
Oct 21, 2009, 11:47:46 AM10/21/09
to devide...@googlegroups.com
2009/10/21 Simon Su <newsgr...@gmail.com>:

> C:\Program Files\DeVIDE-RE>dre python -v
> 'import site' failed; use -v for traceback
> Traceback (most recent call last):
>   File "C:\Program Files\DeVIDE-RE\\dre.py", line 7, in <module>
>     import ConfigParser
>
> Sorry it got cut....

Oh durn, it didn't get cut, I wasn't looking carefully enough.
Usually these tracebacks are quite long, in your case, it doesn't even
get far enough to show a proper traceback.

Do you have another machine or (not as good a test) another account available?

You should also see in DeVIDE-RE\python\Lib somewhere the site.py (I
just checked in the installer). This means that somehow the DRE
python (called from dre.cmd) is being confused probably by globally
set paths.

What happens if you go to DeVIDE-RE\python and then manually run
python? Does that startup? If so, can you type "import site" ?

See you tomorrow,
Charl

Simon Su

unread,
Oct 21, 2009, 12:01:44 PM10/21/09
to devide...@googlegroups.com
Dear Charl,

I will try it on another machine then.... yes probably the python setting on the system is messing things up. I have at least 2 different python version installed together with VisIt, Paraview, and a few others packages on the machine. I got some error when I do import site

C:\Program Files\DeVIDE-RE\python>python.exe

'import site' failed; use -v for traceback
Python 2.6.2 (r262:71605, Apr 14 2009, 22:46:50) [MSC v.1500 64 bit (AMD64)] on
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import site

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: No module named site
>>>


Thanks.
Simon

Simon Su

unread,
Oct 21, 2009, 12:18:05 PM10/21/09
to devide...@googlegroups.com
Dear Charl,

I have another winxp 32bit machine and I installed DeVIDE on it and it just worked right from installation. I do believe now all that python variable on the system is probably messing up DeVIDE's path.

Any way we can unset some of those variables in the DeVIDE run script?

Thanks,
Simon

Charl Botha

unread,
Oct 22, 2009, 3:40:12 AM10/22/09
to devide...@googlegroups.com
Dear Simon,

2009/10/21 Simon Su <newsgr...@gmail.com>:


> I have another winxp 32bit machine and I installed DeVIDE on it and it just
> worked right from installation. I do believe now all that python variable on
> the system is probably messing up DeVIDE's path.
>
> Any way we can unset some of those variables in the DeVIDE run script?

Thank you very much for checking on a different machine.

Yes, it would indeed be great if the DRE python would disregard this
type of existing setting. Could you try the following three things
for me on your 64bit Windows machine and report back on the output?

DeVIDE-RE\python> python -E (this should ignore all PYTHON* env variables)

Also the following:

python -s
(this will ignore user-specific site startup)

And finally the following:

python -S
(this will suppress automatic import site)

I believe that this last one solves our problem. At the moment, the
DRE Python is also importing your existing python site-packages, and
that is obviously not the idea. If this third statement
(DeVIDE-RE\python> python.exe -S) works, please modify dre.cmd as
follows:

Change this line:
"%~dp0\python\python.exe" "%~dp0\dre.py" %1 %2 %3 %4 %5 %6 %7 %8 %9

into this:
"%~dp0\python\python.exe" -S "%~dp0\dre.py" %1 %2 %3 %4 %5 %6 %7 %8 %9

If this works for you, I'll fix it in SVN (so the next release will
have the new behaviour), and also add a FAQ for now.

Thanks for helping to diagnose this!
Charl

Reply all
Reply to author
Forward
0 new messages