Menu
▾
▴
Re: [Visualpython-users] Problem installing on Mac (non-default python location perhaps?)
|
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> |
