Menu
▾
▴
visualpython-users
|
From: Gary P. <gar...@gm...> - 2010-07-14 02:47:58
|
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 |
|
From: Bruce S. <bas...@nc...> - 2010-07-14 05:08:58
|
/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.orgwere 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 > > |
|
From: Rhett A. <ra...@se...> - 2010-07-14 13:01:15
|
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.orgwere 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 ================ |
|
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> |
|
From: Gary P. <gar...@gm...> - 2010-07-14 14:03:20
|
On Wed, Jul 14, 2010 at 8:35 AM, Rhett Allain <ra...@se...> 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 > How did you install Vpython? In my case, the Mac installer won't run. -g > > > > 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 > ================ > > > ------------------------------------------------------------------------------ > 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 > > |
|
From: Rhett A. <ra...@se...> - 2010-07-14 14:28:33
|
Gary, I just followed the instructions on vpython.org and it worked fine. Rhett On Wed, Jul 14, 2010 at 8:31 AM, Gary Pajer <gar...@gm...> wrote: > On Wed, Jul 14, 2010 at 8:35 AM, Rhett Allain <ra...@se...> 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 >> > > How did you install Vpython? In my case, the Mac installer won't run. > -g > > >> >> >> >> 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 >> ================ >> >> >> ------------------------------------------------------------------------------ >> 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 ================ |
|
From: Gary P. <gar...@gm...> - 2010-07-14 14:35:05
|
OK. To be clear about my situation: the installer starts but will not perform the installation. -g On Wed, Jul 14, 2010 at 10:28 AM, Rhett Allain <ra...@se...> wrote: > Gary, > > I just followed the instructions on vpython.org and it worked fine. > > Rhett > > > On Wed, Jul 14, 2010 at 8:31 AM, Gary Pajer <gar...@gm...> wrote: > >> On Wed, Jul 14, 2010 at 8:35 AM, Rhett Allain <ra...@se...> 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 >>> >> >> How did you install Vpython? In my case, the Mac installer won't run. >> -g >> >> >>> >>> >>> >>> 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 >>> ================ >>> >>> >>> ------------------------------------------------------------------------------ >>> 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 > ================ > > > ------------------------------------------------------------------------------ > 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 > > |
|
From: James M. <mu...@pi...> - 2010-07-14 14:35:45
|
I took a look and the file distribution.dist inside the vpython installer contains the lines
if(!(system.files.fileExistsAtPath('/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6') == true)) {
my.result.title = 'Need Python 2.6 from python.org';
my.result.message = 'Python 2.6 from python.org must be installed before installing VPython.';
my.result.type = 'Fatal';
return false;
}
So it isn't looking for Current, it is looking for a specific python.
So, if you also install the python 2.6 from python.org, this file will exist and the visual installer will work and you will be in the same setup as Rhett. You will have two versions of python, one with visual and one with all the enthought libraries.
-Jim
On Jul 14, 2010, at 9:31 AM, Gary Pajer wrote:
> On Wed, Jul 14, 2010 at 8:35 AM, Rhett Allain <ra...@se...> 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
>
> How did you install Vpython? In my case, the Mac installer won't run.
> -g
>
>
>
>
> 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
> ================
>
> ------------------------------------------------------------------------------
> 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
>
>
> <ATT00001..txt><ATT00002..txt>
|
|
From: Gary P. <gar...@gm...> - 2010-07-14 15:15:46
|
On Wed, Jul 14, 2010 at 10:35 AM, James Mueller <mu...@pi...> wrote:
> I took a look and the file distribution.dist inside the vpython installer
> contains the lines
>
> if(!(system.files.fileExistsAtPath('/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6')
> == true)) {
> my.result.title = 'Need Python 2.6 from python.org';
> my.result.message = 'Python 2.6 from python.org must be installed
> before installing VPython.';
> my.result.type = 'Fatal';
> return false;
> }
>
> So it isn't looking for Current, it is looking for a specific python.
>
> So, if you also install the python 2.6 from python.org, this file will
> exist and the visual installer will work and you will be in the same setup
> as Rhett. You will have two versions of python, one with visual and one
> with all the enthought libraries.
>
> -Jim
>
AHA!!!
There's a typo in the Enthought distribution. The directory that should be
called "2.6" is actually called "6.2"
But simply renaming that directory causes other problems. I'll report it to
the Enthought people.
>
> On Jul 14, 2010, at 9:31 AM, Gary Pajer wrote:
>
> On Wed, Jul 14, 2010 at 8:35 AM, Rhett Allain <ra...@se...> 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
>>
>
> How did you install Vpython? In my case, the Mac installer won't run.
> -g
>
>
>>
>>
>>
>> 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
>> ================
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
> <ATT00001..txt><ATT00002..txt>
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
>
|
|
From: James M. <mu...@pi...> - 2010-07-14 15:43:37
|
No, this is exactly what they want. 6.2 is the version of the Enthought distribution. It doesn't agree with the python version, so perhaps this is a bad choice on their part, but I don't think they would consider it a bug.
-Jim
On Jul 14, 2010, at 11:15 AM, Gary Pajer wrote:
>
>
> On Wed, Jul 14, 2010 at 10:35 AM, James Mueller <mu...@pi...> wrote:
> I took a look and the file distribution.dist inside the vpython installer contains the lines
>
> if(!(system.files.fileExistsAtPath('/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6') == true)) {
> my.result.title = 'Need Python 2.6 from python.org';
> my.result.message = 'Python 2.6 from python.org must be installed before installing VPython.';
> my.result.type = 'Fatal';
> return false;
> }
>
> So it isn't looking for Current, it is looking for a specific python.
>
> So, if you also install the python 2.6 from python.org, this file will exist and the visual installer will work and you will be in the same setup as Rhett. You will have two versions of python, one with visual and one with all the enthought libraries.
>
> -Jim
>
>
> AHA!!!
>
> There's a typo in the Enthought distribution. The directory that should be called "2.6" is actually called "6.2"
> But simply renaming that directory causes other problems. I'll report it to the Enthought people.
>
>
>
>
>
> On Jul 14, 2010, at 9:31 AM, Gary Pajer wrote:
>
>> On Wed, Jul 14, 2010 at 8:35 AM, Rhett Allain <ra...@se...> 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
>>
>> How did you install Vpython? In my case, the Mac installer won't run.
>> -g
>>
>>
>>
>>
>> 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
>> ================
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>>
>> <ATT00001..txt><ATT00002..txt>
>
>
> ------------------------------------------------------------------------------
> 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
>
>
|
|
From: Gary P. <gar...@gm...> - 2010-07-14 15:56:06
|
You're right. Here's a snippet of my conversation with them:
----------------------------------------------------------
> The Mac EPD installer has a directory named
>
> /Library/Frameworks/Python.framework/Versions/6.2
>
> But the Vpython installer checks to see if exists:
>
> /Library/Frameworks/Python.framework/Versions/2.6
>
> I rather suspect that the "6.2" is a typo. Simply renaming the directory
> name doesn't work ... stuff doesn't get found.
No, the "6.2" refers to the EPD version, not the python version. It
sounds like Vpython is either hardcoded to look at that dir, rather
than use sys.prefix, or you're using the system python to install it.
--------------------------------------------------
So the ball is back in Vpython's court: the installer should look for
sys.prefix ???
On Wed, Jul 14, 2010 at 11:43 AM, James Mueller <mu...@pi...> wrote:
> No, this is exactly what they want. 6.2 is the version of the Enthought
> distribution. It doesn't agree with the python version, so perhaps this is
> a bad choice on their part, but I don't think they would consider it a bug.
>
> -Jim
>
> On Jul 14, 2010, at 11:15 AM, Gary Pajer wrote:
>
>
>
> On Wed, Jul 14, 2010 at 10:35 AM, James Mueller <mu...@pi...> wrote:
>
>> I took a look and the file distribution.dist inside the vpython installer
>> contains the lines
>>
>> if(!(system.files.fileExistsAtPath('/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6')
>> == true)) {
>> my.result.title = 'Need Python 2.6 from python.org';
>> my.result.message = 'Python 2.6 from python.org must be installed
>> before installing VPython.';
>> my.result.type = 'Fatal';
>> return false;
>> }
>>
>> So it isn't looking for Current, it is looking for a specific python.
>>
>> So, if you also install the python 2.6 from python.org, this file will
>> exist and the visual installer will work and you will be in the same setup
>> as Rhett. You will have two versions of python, one with visual and one
>> with all the enthought libraries.
>>
>> -Jim
>>
>
>
> AHA!!!
>
> There's a typo in the Enthought distribution. The directory that should be
> called "2.6" is actually called "6.2"
> But simply renaming that directory causes other problems. I'll report it
> to the Enthought people.
>
>
>
>
>
>>
>> On Jul 14, 2010, at 9:31 AM, Gary Pajer wrote:
>>
>> On Wed, Jul 14, 2010 at 8:35 AM, Rhett Allain <ra...@se...> 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
>>>
>>
>> How did you install Vpython? In my case, the Mac installer won't run.
>> -g
>>
>>
>>>
>>>
>>>
>>> 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
>>> ================
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> 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
>>>
>>>
>> <ATT00001..txt><ATT00002..txt>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>
>
|
|
From: Bruce S. <bas...@nc...> - 2010-07-14 16:29:36
|
This is very helpful. Thanks much! So I need to find out (or someone needs to tell me) how to get PackageMaker to look for an installed Python, not a python.org Python. Bruce Sherwood On Wed, Jul 14, 2010 at 8:35 AM, James Mueller <mu...@pi...> wrote: > I took a look and the file distribution.dist inside the vpython installer > contains the lines > > if(!(system.files.fileExistsAtPath('/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6') > == true)) { > my.result.title = 'Need Python 2.6 from python.org'; > my.result.message = 'Python 2.6 from python.org must be installed > before installing VPython.'; > my.result.type = 'Fatal'; > return false; > } > > So it isn't looking for Current, it is looking for a specific python. > > So, if you also install the python 2.6 from python.org, this file will > exist and the visual installer will work and you will be in the same setup > as Rhett. You will have two versions of python, one with visual and one > with all the enthought libraries. > > -Jim > > On Jul 14, 2010, at 9:31 AM, Gary Pajer wrote: > > On Wed, Jul 14, 2010 at 8:35 AM, Rhett Allain <ra...@se...> 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 >> > > How did you install Vpython? In my case, the Mac installer won't run. > -g > > >> >> >> >> 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 >> ================ >> >> >> ------------------------------------------------------------------------------ >> 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 >> >> > <ATT00001..txt><ATT00002..txt> > > > > > ------------------------------------------------------------------------------ > 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 > > |
|
From: Steve S. <st...@sp...> - 2010-07-14 17:23:51
Attachments:
PackageMakerScreenSnapz001.jpg
|
I'd love to help... but I'm leaving town for two weeks in the morning and have too much going on to be much use today. I guess you'll need to cook up a python script to check sys.prefix and/or sys.version_info. The trouble is that you'll need to install stuff into a directory that you won't really know until you fire up python and check these values. You may need to install in a 'staging' area (/ tmp ?) and then move the packages to the target 'site-packages' folder once you know where they belong. There are several places you can inject scripts that should be callable under different circumstances... but it sounds like it could get complicated. ;-) -steve |
|
From: Bruce S. <bas...@nc...> - 2010-07-14 16:47:34
|
This suggests that I should make available an optional VPython installer that checks for a Python being available but not check for the version at all, leaving it to the person doing the installing the responsibility for having an appropriate level of Python installed. Gary, as a test you might install VPython on the standard Python 2.6 (maybe on a different Mac) and save a copy of the files that go into site-packages, then on your Enthought machine just copy those files into site-packages. If the Enthought Python is in fact an instance of Python 2.6, this should work. If you do this experiment, please let me know, as I don't have an Enthought installation to try this on myself. Bruce Sherwood On Wed, Jul 14, 2010 at 9:55 AM, Gary Pajer <gar...@gm...> wrote: > You're right. Here's a snippet of my conversation with them: > > ---------------------------------------------------------- > > The Mac EPD installer has a directory named > > > > /Library/Frameworks/Python.framework/Versions/6.2 > > > > But the Vpython installer checks to see if exists: > > > > > /Library/Frameworks/Python.framework/Versions/2.6 > > > > I rather suspect that the "6.2" is a typo. Simply renaming the directory > > name doesn't work ... stuff doesn't get found. > > No, the "6.2" refers to the EPD version, not the python version. It > sounds like Vpython is either hardcoded to look at that dir, rather > than use sys.prefix, or you're using the system python to install it. > -------------------------------------------------- > > So the ball is back in Vpython's court: the installer should look for > sys.prefix ??? > > > > On Wed, Jul 14, 2010 at 11:43 AM, James Mueller <mu...@pi...> wrote: > >> No, this is exactly what they want. 6.2 is the version of the Enthought >> distribution. It doesn't agree with the python version, so perhaps this is >> a bad choice on their part, but I don't think they would consider it a bug. >> >> -Jim >> >> >> >> |
|
From: Gary P. <gar...@gm...> - 2010-07-14 17:02:32
|
I'll do as you ask as soon as I can get to it. In the meantime, note that there is also a python variable that holds information about the python version: sys.version_info (there are probably other similar variables). So with yet more work the version could be checked. -g On Wed, Jul 14, 2010 at 12:47 PM, Bruce Sherwood <bas...@nc...> wrote: > This suggests that I should make available an optional VPython installer > that checks for a Python being available but not check for the version at > all, leaving it to the person doing the installing the responsibility for > having an appropriate level of Python installed. Gary, as a test you might > install VPython on the standard Python 2.6 (maybe on a different Mac) and > save a copy of the files that go into site-packages, then on your Enthought > machine just copy those files into site-packages. If the Enthought Python is > in fact an instance of Python 2.6, this should work. > > If you do this experiment, please let me know, as I don't have an Enthought > installation to try this on myself. > > Bruce Sherwood > > > On Wed, Jul 14, 2010 at 9:55 AM, Gary Pajer <gar...@gm...> wrote: > >> You're right. Here's a snippet of my conversation with them: >> >> ---------------------------------------------------------- >> > The Mac EPD installer has a directory named >> > >> > /Library/Frameworks/Python.framework/Versions/6.2 >> > >> > But the Vpython installer checks to see if exists: >> >> > >> > /Library/Frameworks/Python.framework/Versions/2.6 >> > >> > I rather suspect that the "6.2" is a typo. Simply renaming the >> directory >> > name doesn't work ... stuff doesn't get found. >> >> No, the "6.2" refers to the EPD version, not the python version. It >> sounds like Vpython is either hardcoded to look at that dir, rather >> than use sys.prefix, or you're using the system python to install it. >> -------------------------------------------------- >> >> So the ball is back in Vpython's court: the installer should look for >> sys.prefix ??? >> >> >> >> On Wed, Jul 14, 2010 at 11:43 AM, James Mueller <mu...@pi...> wrote: >> >>> No, this is exactly what they want. 6.2 is the version of the Enthought >>> distribution. It doesn't agree with the python version, so perhaps this is >>> a bad choice on their part, but I don't think they would consider it a bug. >>> >>> -Jim >>> >>> >>> >>> > > > ------------------------------------------------------------------------------ > 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 > > |
|
From: James M. <mu...@pi...> - 2010-07-14 17:03:08
|
Bruce, It is actually a little worse. When I dealt with this two years ago, an additional problem was that the numpy that came with enthought was different from the one in the visual package. So, after installing visual, the extra packages in the Enthought distribution like scipy would crash; if I went back to enthought's numpy, then visual would crash. I finally found it easier to install the enthought distribution and then build visual using the enthought numpy. -Jim On Jul 14, 2010, at 12:47 PM, Bruce Sherwood wrote: > This suggests that I should make available an optional VPython installer that checks for a Python being available but not check for the version at all, leaving it to the person doing the installing the responsibility for having an appropriate level of Python installed. Gary, as a test you might install VPython on the standard Python 2.6 (maybe on a different Mac) and save a copy of the files that go into site-packages, then on your Enthought machine just copy those files into site-packages. If the Enthought Python is in fact an instance of Python 2.6, this should work. > > If you do this experiment, please let me know, as I don't have an Enthought installation to try this on myself. > > Bruce Sherwood > > On Wed, Jul 14, 2010 at 9:55 AM, Gary Pajer <gar...@gm...> wrote: > You're right. Here's a snippet of my conversation with them: > > ---------------------------------------------------------- > > The Mac EPD installer has a directory named > > > > /Library/Frameworks/Python.framework/Versions/6.2 > > > > But the Vpython installer checks to see if exists: > > > > > /Library/Frameworks/Python.framework/Versions/2.6 > > > > I rather suspect that the "6.2" is a typo. Simply renaming the directory > > name doesn't work ... stuff doesn't get found. > > No, the "6.2" refers to the EPD version, not the python version. It > sounds like Vpython is either hardcoded to look at that dir, rather > than use sys.prefix, or you're using the system python to install it. > -------------------------------------------------- > > So the ball is back in Vpython's court: the installer should look for sys.prefix ??? > > > > On Wed, Jul 14, 2010 at 11:43 AM, James Mueller <mu...@pi...> wrote: > No, this is exactly what they want. 6.2 is the version of the Enthought distribution. It doesn't agree with the python version, so perhaps this is a bad choice on their part, but I don't think they would consider it a bug. > > -Jim > >> >> > > <ATT00001..txt><ATT00002..txt> |
|
From: Gary P. <gar...@gm...> - 2010-07-14 17:43:27
|
Yow. I guess that's what happens when two people try to make life easy for the end user by producing one-click installers. There are packaging/installation systems that are supposed to take care of version dependency, but as far as I can tell they come with there own set of problems. This conflict should arise on Windows, too, shouldn't it? Evidently it's rare that someone wants both Vpython and Enthought... one has to wonder if it's worth the effort to fix (if it's fixable at all). Of course, I have my own opinion on that matter. As of today Enthought Python Distribution ships with numpy 1.3, but it doesn't really make sense for Vpython's tail to be wagged by Enthought. On the other hand, if Vpython's installer is overwriting Enthought's installation (or vice versa), that's no good either. James, after you built Vpython, what ended up broken? It may turn out that your solution is the practical one for people in this situation. -g On Wed, Jul 14, 2010 at 1:02 PM, James Mueller <mu...@pi...> wrote: > Bruce, > It is actually a little worse. When I dealt with this two years ago, an > additional problem was that the numpy that came with enthought was different > from the one in the visual package. So, after installing visual, the extra > packages in the Enthought distribution like scipy would crash; if I went > back to enthought's numpy, then visual would crash. I finally found it > easier to install the enthought distribution and then build visual using the > enthought numpy. > -Jim > > On Jul 14, 2010, at 12:47 PM, Bruce Sherwood wrote: > > This suggests that I should make available an optional VPython installer > that checks for a Python being available but not check for the version at > all, leaving it to the person doing the installing the responsibility for > having an appropriate level of Python installed. Gary, as a test you might > install VPython on the standard Python 2.6 (maybe on a different Mac) and > save a copy of the files that go into site-packages, then on your Enthought > machine just copy those files into site-packages. If the Enthought Python is > in fact an instance of Python 2.6, this should work. > > If you do this experiment, please let me know, as I don't have an Enthought > installation to try this on myself. > > Bruce Sherwood > > On Wed, Jul 14, 2010 at 9:55 AM, Gary Pajer <gar...@gm...> wrote: > >> You're right. Here's a snippet of my conversation with them: >> >> ---------------------------------------------------------- >> > The Mac EPD installer has a directory named >> > >> > /Library/Frameworks/Python.framework/Versions/6.2 >> > >> > But the Vpython installer checks to see if exists: >> >> > >> > /Library/Frameworks/Python.framework/Versions/2.6 >> > >> > I rather suspect that the "6.2" is a typo. Simply renaming the >> directory >> > name doesn't work ... stuff doesn't get found. >> >> No, the "6.2" refers to the EPD version, not the python version. It >> sounds like Vpython is either hardcoded to look at that dir, rather >> than use sys.prefix, or you're using the system python to install it. >> -------------------------------------------------- >> >> So the ball is back in Vpython's court: the installer should look for >> sys.prefix ??? >> >> >> >> On Wed, Jul 14, 2010 at 11:43 AM, James Mueller <mu...@pi...> wrote: >> >>> No, this is exactly what they want. 6.2 is the version of the Enthought >>> distribution. It doesn't agree with the python version, so perhaps this is >>> a bad choice on their part, but I don't think they would consider it a bug. >>> >>> -Jim >>> >>> >>> >>> > <ATT00001..txt><ATT00002..txt> > > > > > ------------------------------------------------------------------------------ > 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 > > |
|
From: James M. <mu...@pi...> - 2010-07-14 19:27:06
|
On Jul 14, 2010, at 1:43 PM, Gary Pajer wrote: > Yow. I guess that's what happens when two people try to make life easy for the end user by producing one-click installers. There are packaging/installation systems that are supposed to take care of version dependency, but as far as I can tell they come with there own set of problems. > > This conflict should arise on Windows, too, shouldn't it? Evidently it's rare that someone wants both Vpython and Enthought... one has to wonder if it's worth the effort to fix (if it's fixable at all). Of course, I have my own opinion on that matter. The PythonXY distribution is much better than Enthought, but that is due to the fact that they only support windows and can concentrate on doing one platform well. They have dozens of python packages including visual, so it really is one-stop shopping. > > As of today Enthought Python Distribution ships with numpy 1.3, but it doesn't really make sense for Vpython's tail to be wagged by Enthought. On the other hand, if Vpython's installer is overwriting Enthought's installation (or vice versa), that's no good either. I just downoaded the 6.2 version and it came with numpy 1.4.0! This is the version of numpy that was pulled due to ABI breakages. I can't see mixing this with the 1.3 version that visual builds against. You might be able to install a visual built against numpy 1.4.1. I don't know why Enthought doesn't update to 1.4.1. This is like what I had two years ago when enthought had numpy 1.1 and VPython had 1.2 > > James, after you built Vpython, what ended up broken? It may turn out that your solution is the practical one for people in this situation. This was two years ago, so it might be different now, but then there were conflicts between the visual and matplotlib. Each one wanting to control the event loop. You could load both of them, but you had to make sure that you didn't have a matplotlib graph window and a visual display window open at the same time. The question is, "what packages in the enthought distribution do you want? Is it easier to add them to a VPython install, or add visual to an enthought install. -Jim > > -g > > On Wed, Jul 14, 2010 at 1:02 PM, James Mueller <mu...@pi...> wrote: > Bruce, > It is actually a little worse. When I dealt with this two years ago, an additional problem was that the numpy that came with enthought was different from the one in the visual package. So, after installing visual, the extra packages in the Enthought distribution like scipy would crash; if I went back to enthought's numpy, then visual would crash. I finally found it easier to install the enthought distribution and then build visual using the enthought numpy. > > -Jim > > On Jul 14, 2010, at 12:47 PM, Bruce Sherwood wrote: > >> This suggests that I should make available an optional VPython installer that checks for a Python being available but not check for the version at all, leaving it to the person doing the installing the responsibility for having an appropriate level of Python installed. Gary, as a test you might install VPython on the standard Python 2.6 (maybe on a different Mac) and save a copy of the files that go into site-packages, then on your Enthought machine just copy those files into site-packages. If the Enthought Python is in fact an instance of Python 2.6, this should work. >> >> If you do this experiment, please let me know, as I don't have an Enthought installation to try this on myself. >> >> Bruce Sherwood >> >> On Wed, Jul 14, 2010 at 9:55 AM, Gary Pajer <gar...@gm...> wrote: >> You're right. Here's a snippet of my conversation with them: >> >> ---------------------------------------------------------- >> > The Mac EPD installer has a directory named >> > >> > /Library/Frameworks/Python.framework/Versions/6.2 >> > >> > But the Vpython installer checks to see if exists: >> >> > >> > /Library/Frameworks/Python.framework/Versions/2.6 >> > >> > I rather suspect that the "6.2" is a typo. Simply renaming the directory >> > name doesn't work ... stuff doesn't get found. >> >> No, the "6.2" refers to the EPD version, not the python version. It >> sounds like Vpython is either hardcoded to look at that dir, rather >> than use sys.prefix, or you're using the system python to install it. >> -------------------------------------------------- >> >> So the ball is back in Vpython's court: the installer should look for sys.prefix ??? >> >> >> >> On Wed, Jul 14, 2010 at 11:43 AM, James Mueller <mu...@pi...> wrote: >> No, this is exactly what they want. 6.2 is the version of the Enthought distribution. It doesn't agree with the python version, so perhaps this is a bad choice on their part, but I don't think they would consider it a bug. >> >> -Jim >> >>> >>> >> >> <ATT00001..txt><ATT00002..txt> > > > ------------------------------------------------------------------------------ > 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 > > > <ATT00001..txt><ATT00002..txt> |
|
From: Gary P. <gar...@gm...> - 2010-07-14 20:16:22
|
On Wed, Jul 14, 2010 at 3:26 PM, James Mueller <mu...@pi...> wrote: > > On Jul 14, 2010, at 1:43 PM, Gary Pajer wrote: > > Yow. I guess that's what happens when two people try to make life easy for > the end user by producing one-click installers. There are > packaging/installation systems that are supposed to take care of version > dependency, but as far as I can tell they come with there own set of > problems. > > This conflict should arise on Windows, too, shouldn't it? Evidently it's > rare that someone wants both Vpython and Enthought... one has to wonder if > it's worth the effort to fix (if it's fixable at all). Of course, I have my > own opinion on that matter. > > The PythonXY distribution is much better than Enthought, but that is due to > the fact that they only support windows and can concentrate on doing one > platform well. They have dozens of python packages including visual, so it > really is one-stop shopping. > > > As of today Enthought Python Distribution ships with numpy 1.3, but it > doesn't really make sense for Vpython's tail to be wagged by Enthought. On > the other hand, if Vpython's installer is overwriting Enthought's > installation (or vice versa), that's no good either. > > I just downoaded the 6.2 version and it came with numpy 1.4.0! This is the > version of numpy that was pulled due to ABI breakages. I can't see mixing > this with the 1.3 version that visual builds against. You might be able to > install a visual built against numpy 1.4.1. I don't know why Enthought > doesn't update to 1.4.1. > (AHA!!)**2 Of course, I installed Vpython after I installed EPD, so numpy 1.4.0 was overwritten by 1.3.0 ... I failed to heed my own warning. Ugh. > > This is like what I had two years ago when enthought had numpy 1.1 and > VPython had 1.2 > > > James, after you built Vpython, what ended up broken? It may turn out that > your solution is the practical one for people in this situation. > > This was two years ago, so it might be different now, but then there were > conflicts between the visual and matplotlib. > Each one wanting to control the event loop. You could load both of them, > but you had to make sure that you didn't have a matplotlib graph window and > a visual display window open at the same time. > > The question is, "what packages in the enthought distribution do you want? > Is it easier to add them to a VPython install, or add visual to an > enthought install. > > -Jim > > > > -g > > On Wed, Jul 14, 2010 at 1:02 PM, James Mueller <mu...@pi...> wrote: > >> Bruce, >> It is actually a little worse. When I dealt with this two years ago, an >> additional problem was that the numpy that came with enthought was different >> from the one in the visual package. So, after installing visual, the extra >> packages in the Enthought distribution like scipy would crash; if I went >> back to enthought's numpy, then visual would crash. I finally found it >> easier to install the enthought distribution and then build visual using the >> enthought numpy. >> -Jim >> >> On Jul 14, 2010, at 12:47 PM, Bruce Sherwood wrote: >> >> This suggests that I should make available an optional VPython installer >> that checks for a Python being available but not check for the version at >> all, leaving it to the person doing the installing the responsibility for >> having an appropriate level of Python installed. Gary, as a test you might >> install VPython on the standard Python 2.6 (maybe on a different Mac) and >> save a copy of the files that go into site-packages, then on your Enthought >> machine just copy those files into site-packages. If the Enthought Python is >> in fact an instance of Python 2.6, this should work. >> >> If you do this experiment, please let me know, as I don't have an >> Enthought installation to try this on myself. >> >> Bruce Sherwood >> >> On Wed, Jul 14, 2010 at 9:55 AM, Gary Pajer <gar...@gm...> wrote: >> >>> You're right. Here's a snippet of my conversation with them: >>> >>> ---------------------------------------------------------- >>> > The Mac EPD installer has a directory named >>> > >>> > /Library/Frameworks/Python.framework/Versions/6.2 >>> > >>> > But the Vpython installer checks to see if exists: >>> >>> > >>> > /Library/Frameworks/Python.framework/Versions/2.6 >>> > >>> > I rather suspect that the "6.2" is a typo. Simply renaming the >>> directory >>> > name doesn't work ... stuff doesn't get found. >>> >>> No, the "6.2" refers to the EPD version, not the python version. It >>> sounds like Vpython is either hardcoded to look at that dir, rather >>> than use sys.prefix, or you're using the system python to install it. >>> -------------------------------------------------- >>> >>> So the ball is back in Vpython's court: the installer should look for >>> sys.prefix ??? >>> >>> >>> >>> On Wed, Jul 14, 2010 at 11:43 AM, James Mueller <mu...@pi...>wrote: >>> >>>> No, this is exactly what they want. 6.2 is the version of the Enthought >>>> distribution. It doesn't agree with the python version, so perhaps this is >>>> a bad choice on their part, but I don't think they would consider it a bug. >>>> >>>> -Jim >>>> >>>> >>>> >>>> >> <ATT00001..txt><ATT00002..txt> >> >> >> >> >> ------------------------------------------------------------------------------ >> 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 >> >> > <ATT00001..txt><ATT00002..txt> > > > |
|
From: Gary P. <gar...@gm...> - 2010-07-14 20:23:55
|
On Wed, Jul 14, 2010 at 3:26 PM, James Mueller <mu...@pi...> wrote: > > On Jul 14, 2010, at 1:43 PM, Gary Pajer wrote: > > Yow. I guess that's what happens when two people try to make life easy for > the end user by producing one-click installers. There are > packaging/installation systems that are supposed to take care of version > dependency, but as far as I can tell they come with there own set of > problems. > > This conflict should arise on Windows, too, shouldn't it? Evidently it's > rare that someone wants both Vpython and Enthought... one has to wonder if > it's worth the effort to fix (if it's fixable at all). Of course, I have my > own opinion on that matter. > > The PythonXY distribution is much better than Enthought, but that is due to > the fact that they only support windows and can concentrate on doing one > platform well. They have dozens of python packages including visual, so it > really is one-stop shopping. > > > As of today Enthought Python Distribution ships with numpy 1.3, but it > doesn't really make sense for Vpython's tail to be wagged by Enthought. On > the other hand, if Vpython's installer is overwriting Enthought's > installation (or vice versa), that's no good either. > > I just downoaded the 6.2 version and it came with numpy 1.4.0! This is the > version of numpy that was pulled due to ABI breakages. I can't see mixing > this with the 1.3 version that visual builds against. You might be able to > install a visual built against numpy 1.4.1. I don't know why Enthought > doesn't update to 1.4.1. > Oh ... Enthought consciously chose to stick with 1.4.0 because they wanted to retain the datetime feature. (This was the crux of a long discussion on the numpy list a while back.) They plan to stick with 1.4.0 until 2.0 comes out. |
|
From: James M. <mu...@pi...> - 2010-07-14 22:51:41
|
Ahh. So, unless you need something that depends on the datetime feature, it is best to avoid Enthought until numpy 2.0. If you need Enthought, you need to build visual yourself to match your version of numpy. As an experiment, I just started going the other way, start with a basic vpython install and then add other packages to it. A download of the most recent scipy 0.7.2 binary works. I didn't try the release candidate of 0.8. A download of the most recent matplotlib (1.0.0) does not, but version 0.99.1 from September does. I think this indicates that the most recent binaries require numpy 1.4.1. I assume Bruce will get around to updating the VPython build to use the most recent numpy at sometime, That is about 95% of what I have used, and it is easy enough that I might be able to require a physics major to do it on their machine. For engineers, it is about 99% of what they would use Matlab for. The best thing about PythonXY is that if you are using more than visual in a course, you can just tell students to get PythonXY, and they have everything you might ever want. With Enthought, you have to make sure you build them a visual that matches the enthought version of numpy. > > Oh ... Enthought consciously chose to stick with 1.4.0 because they wanted to retain the datetime feature. (This was the crux of a long discussion on the numpy list a while back.) They plan to stick with 1.4.0 until 2.0 comes out. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X