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. |