From: M H. <air...@ho...> - 2012-08-27 00:01:01
|
First, thanks for the help. I was kind of excited to see that their was a namespace conflict, ultimately thinking it would be an easy fix. So, I renamed the file to something more obscure and and tried to run through PyCharm again (I actually created a new file, copied and pasted, then deleted the vis.py- rather than just renaming the file). At least I'm getting somewhere, as the error is different, lol. This is the error that I got: C:\Python32\python.exe C:/Users/airspoon/PycharmProjects/goo/vp002.pyImportError: numpy.core.multiarray failed to importTraceback (most recent call last): File "C:/Users/airspoon/PycharmProjects/goo/vp002.py", line 1, in <module> from visual import * File "C:\Python32\lib\site-packages\visual\__init__.py", line 1, in <module> from .visual_all import * File "C:\Python32\lib\site-packages\visual\visual_all.py", line 1, in <module> from vis import version File "C:\Python32\lib\site-packages\vis\__init__.py", line 3, in <module> from .cvisual import (vector, dot, mag, mag2, norm, cross, rotate,SystemError: initialization of cvisual raised unreported exception And for what it's worth, this is the code that was copied and pasted from the vPython website: from visual import * floor = box (pos=(0,0,0), length=4, height=0.5, width=4, color=color.blue)ball = sphere (pos=(0,4,0), radius=1, color=color.red)ball.velocity = vector(0,-1,0)dt = 0.01 while 1: rate (100) ball.pos = ball.pos + ball.velocity*dt if ball.y < ball.radius: ball.velocity.y = abs(ball.velocity.y) else: ball.velocity.y = ball.velocity.y - 9.8*dt All other 3rd party libraries that I've used with Python seem to be working correctly, so I doubt the issue is with my Python distro. Can anyone make sense of those error messages? Again, thanks for all of the help. > Date: Sun, 26 Aug 2012 14:34:55 -0700 > Subject: Re: [Visualpython-users] Is there anyway to uninstall vPython? > From: kir...@gm... > To: cos...@wa... > CC: air...@ho...; vis...@li... > > Yeah sounds like some bad luck in terms of namespace collisions. > They're still quite possible. > > I'm deep into PyCharm / virtualenv issues (or maybe it's just that I'm > not deep enough), but none seem to involve VPython, other than the > fact it's sad there's no pip install route (or at least I couldn't > find it). > > Kirby |