search

ratalaika / angel-engine

Automatically exported from code.google.com/p/angel-engine
0 stars 0 forks source link

IntroGame gives Python import errors on execution #25

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Download and unpack the source code.
2. Open the solution in Visual Studio.
3. Build the solution.
4. Run without debugging.

What is the expected output? What do you see instead?
The IntroGame seems to give two errors in the console when it is executed.
 I get an error string stating "'import site' failed; use -v for
traceback", followed by several more lines of traceback errors caused by a
bad import (specifically "import new" from angel.py during its import in
start.py).

What version of the product are you using? On what operating system? Is it
a downloaded distribution or from SVN?
I am using the stable Angel-2.0 from the zip file.  I am attempting to
build and run it on Windows Server 2003 using Visual Studio 2008 on a dual
CPU Intel Xeon x86 2.0GHz with 2 gigs of RAM.  I have the latest DirectX
SDK installed (November 2008).

Please provide any additional information below.
N/A

Original issue reported on code.google.com by johnatho...@gmail.com on 2 Mar 2009 at 2:03

GoogleCodeExporter commented 9 years ago 
You indicated you were no longer seeing this? I can't reproduce on my end, and 
can't
imagine that it's related to the differences in VS. Unless you're still seeing 
it,
I'm going to close this. 

(Sorry, somehow put this comment on a different issue originally. Lousy tabs.)

Original comment by lieseg...@gmail.com on 2 Mar 2009 at 7:18

GoogleCodeExporter commented 9 years ago 
I still have it in the 2.0 version, but not your branch.  I'm not sure what 
changed,
but something made it disappear (if I get curious enough I may run some diffs 
and see
if I can figure it out).  At least its noted if someone else has any problems.

Original comment by johnatho...@gmail.com on 2 Mar 2009 at 7:36

GoogleCodeExporter commented 9 years ago 
There have been lots of miscellaneous bug fixes I've been doing in my branch, 
but
this is never one I came across. In any event, glad to know it's fixed. :-)

Original comment by lieseg...@gmail.com on 2 Mar 2009 at 7:38