Yves de Champlain wrote:
Le 07-02-17 à 11:32, Yves de Champlain a écrit :
Le 07-02-17 à 11:18, [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]> a écrit :
Revision
22092 <http://trac.macosforge.org/projects/macports/changeset/22092>
Author
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
Date
2007-02-17 08:18:26 -0800 (Sat, 17 Feb 2007)
Log Message
new port py25-bz2 - python 2.5 bindings to bzip2
I am a bit confused. Python 2.5 is presented as current production
version on python.org, but these commits make it look like a special
case. Is there some sort of problem with python 2.5 on Mac ? Or is
this a problem with how python is managed in MacPorts ?
Just let me be a little more precise : could there be py24-* and py25-*
ports for python ports that use a specific PortGroup and py-* ports for
python packages that don't use a PortGroup ?
But wouldn't that require the Python builds to have a common shared
place to look for non-binary modules, so we only have to depend upon one
port. Also, non-binary modules that depends upon binary modules would
still need to be versioned for each version of Python, I think :)
Regards,
Blair
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-dev
