Do I really need to install python25 when Leopard already has Python 2.5?

[Bryan Blackburn]

On Tue, Nov 04, 2008 at 12:57:42PM -0800, Dave Llopis said:
> Ah, good point, thanks.
> What I was *really* after was iPython for Python 2.6, which turns out not to
> have even been completed yet!
> Instead, py25-ipython is what I'm trying to install. I see that it requires
> py25-scientific, which isn't supplied by Leopard.
> I also have python26 installed, so it seemed a bit ridiculous to install a
> third copy of Python.

The python26 port isn't useful right now, as there are no py26- ports, and
no way to create them for most people (those running MacPorts 1.6); fixing
the underlying issue with this is one of the final bits before we get a 1.7
beta released...

For now I'd say, if at all possible, go with the 2.5 version of stuff.

Bryan


> 
> It's not like it's any great burden to install python25: I was mostly
> interested in using this as an opportunity to learn more about port
> dependency management in general.
> 
> 
> On Tue, Nov 4, 2008 at 12:14, Bryan Blackburn <blb at macports.org> wrote:
> 
> > On Tue, Nov 04, 2008 at 11:53:48AM -0800, Dave Llopis said:
> > > I want to install a port that has a dependency on python25.
> > > Shouldn't the Leopard-supplied Python 2.5 effectively fulfill this
> > > requirement?
> >
> > No, see:
> >
> > <http://trac.macports.org/wiki/FAQ#WhyisMacPortsusingitsownlibraries>
> >
> > In most cases there's a good reason why a given port ends up wanting
> > python25, usually because it needs some py25- port; which port were you
> > attempting to install?
> >
> > Bryan
> >
> >
> > > If so, is there a proper way for me to either:
> > >   a) Convince the dependent port that the dependency is met
> > > or
> > >   b) Convince the dependent port that it doesn't depend on python25
> > >
> > > Thanks!
> >
> >