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
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?
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
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