On 19 Dec, 2007, at 23:21, Christopher Barker wrote:
> Nehemiah Dacres wrote:
>> so we're still not supporting Apple's shipped python?
That depends on what you mean by "support" ;-)
>>
>
> Well, Apple does what Apples does. Every single version of python that
> they have shipped as had at least
I support your decision not to fully support Apple's python, and Mac Ports
uses internal distros of all supported software. (in other words. if pyhton
2.5 is a dependency, you will wind up with MacPorts' version of python at
/opt/local/bin/ and it's up to you to decide which one to use.
On Dec 20,
On Dec 20, 2007, at 5:35 AM, Ronald Oussoren wrote:
>> never provided an update within an OS-X version. (For example, if
>> nothing else, the Apple python with Leopard doesn't build Universal
>> Binaries when you use setup.py)
>
> That's easily fixable. I'm thinking about reviving Jack's MacPython
William Kyngesburye wrote:
> On Dec 20, 2007, at 5:35 AM, Ronald Oussoren wrote:
>
>>> never provided an update within an OS-X version. (For example, if
>>> nothing else, the Apple python with Leopard doesn't build Universal
>>> Binaries when you use setup.py)
>>
>> That's easily fixable.
Yes, it
William Kyngesburye wrote:
> On Dec 20, 2007, at 5:35 AM, Ronald Oussoren wrote:
>
>>> never provided an update within an OS-X version. (For example, if
>>> nothing else, the Apple python with Leopard doesn't build Universal
>>> Binaries when you use setup.py)
>>
>> That's easily fixable.
Yes, it
