From: James M. <mu...@pi...> - 2010-07-14 14:02:24
|
Gary and Rhett, I had this problem a couple of years ago when I was teaching a course where I wanted to use scipy and visual. IIRC at that time I solved it by rebuilding visual against the installed enthought python There were a few issues in the make file that I needed tinker with, but it wasn't hard - at that time. It was certainly easier than figuring out the install issues. Then I could distribute my own installer for those students in my class who had macs. Of course using the other part of pylab, matplotlib, and visual together never worked for me. On windows, the pythonxy distribution comes with numpy, scipy, matplotlib, and visual, so for students on that platform, it was easy to say just install pythonxy. Unfortunately, pythonxy doesn't have an OS-X version. -Jim On Jul 14, 2010, at 8:35 AM, Rhett Allain wrote: > Gary, > > I have essentially the same problem. The workaround I use is that if I launch VIDLE (in the VPython folder), it can find the vpython stuff - but it doesn't find the enthought stuff. If I launch some other IDLE, then it doesn't find the visual module. > > The bad part of this solution is that I can't use the visual module and the pylab module at the same time. > > Rhett > > > > On Wed, Jul 14, 2010 at 12:08 AM, Bruce Sherwood <bas...@nc...> wrote: > /Library/Frameworks/Python.framework/Versions/Current/bin/python is indeed the expected location for the Python executor, so that doesn't seem to be the problem, at least not in any simple sense. I use Apple PackageMaker to build the Mac VPython installer, and I know nothing about its criteria for recognizing the presence of Python 2.6. > > You made me realize that the Mac and Windows download pages at vpython.org were out of date, as they offered Python 2.6.4. After checking that the VPython installers for Mac and Windows are happy with Python 2.6.5, I've updated vpython.org to offer Python 2.6.5. > > Nor had I realized that now Python 2.7 is the standard release, so I need to build against that. > > Bruce Sherwood > > On Tue, Jul 13, 2010 at 8:47 PM, Gary Pajer <gar...@gm...> wrote: > I'm installing software on a new MacBook. I'm not yet very facile with Macs. > > I have python 2.6.5 from python.org installed, but the vpython installer says that I have to install python 2.6 before it will proceed. I think the problem may be that python is not installed in it's default location. Python was installed as part of the Enthought Python Distribution, which installs python and a bunch of other stuff that I use. The python executable ended up being > > /Library/Frameworks/Python.framework/Versions/Current/bin/python > > 1. Is this indeed *not* the default location for a "regular" installation of python? > 2. If it is not, is that possibly the cause of my problem? > 3. Can I fix it by > a. creating a symbolic link somewhere (what would it be?) > b. or telling vpython where to look for python (set an environment variable?) > 4. Or am I wrong, and the problem lies somewhere else? > > Thanks, > gary > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > Visualpython-users mailing list > Vis...@li... > https://lists.sourceforge.net/lists/listinfo/visualpython-users > > > > > -- > ================ > Rhett Allain, Ph.D. > Associate Professor of Physics > Department of Chemistry and Physics > Southeastern Louisiana University > ra...@se... > http://scienceblogs.com/dotphysics > ================ > <ATT00001..txt><ATT00002..txt> |