[Pythonmac-SIG] Re: How easy to just replace Panther's Python?

Paul Berkowitz berkowit at silcom.com
Wed Dec 17 23:01:25 EST 2003


But that would apply to absolutely everything, including all built-in Apple
applications, files, frameworks, etc. So the solution is simple for you:
don't upgrade the OS until you're ready.

-- 
Paul Berkowitz


> From: "W.T. Bridgman" <wtbridgman at radix.net>
> Date: Wed, 17 Dec 2003 22:34:16 -0500
> To: PythonMac <pythonmac-sig at python.org>
> Subject: Re: [Pythonmac-SIG] Re: How easy to just replace Panther's Python?
> 
> Kind of late  joining this thread but since no one voiced this issue.
> 
> I dislike this idea.
> 
> I predominantly develop for my own use (scientific research, in-house
> tool development) and having platform changes can set me back months.
> 
> I last had VTK running with python wrappers under 10.1.  When I
> upgraded to 10.2, many components wouldn't build and I've only recently
> got the entire system working again.  I'm delaying upgrading to 10.3
> due to this experience.
> 
> If I encounter some type of code bug and I develop a work-around, I at
> least want to get some use out of the code on *my* time table - not
> that determined by a vendor update.  When I've completed the project at
> hand and ready to update, then I can update knowing that I'll have to
> revise some of my code components.  I don't want to be in a situation
> where I need to upgrade due to a OS security issue but must also take
> some update that may break my existing tools.
> 
> As a result, I have traditionally ripped out Apple's installation and
> installed Python as a framework from scratch.
> 
> My $0.02,
> Tom
> 
> On Wednesday, December 10, 2003, at 07:27  PM, Paul Berkowitz wrote:
> 
>> On 12/10/03 3:33 PM, "Russell E. Owen" <rowen at cesmail.net> wrote:
>> 
>>> I'd much rather upgrade Python than work around bugs that have been
>>> fixed, especially since Python 2.3 has other known bugs.
>> 
>> I find this a bit disturbing. New versions are always going to have
>> some
>> bugs that need fixing or working around. I think Python on the Mac
>> will only
>> be taken up in a big way when pretty well everyone agrees to work with
>> what
>> Apple supplies. You need to be be able to depend on users having the
>> same
>> Python as you, the developer. I think that's what Jack and others have
>> been
>> working towards, and have come much of the way. I keep waiting for the
>> "all
>> clear" to get more involved myself, but it never seems to come.
>> 
>> Apple were pretty good about including Python 2.3 in OS 10.3 - even
>> delaying
>> the odd deadline or two, from what I've been told, or in any case
>> coordinating them. Wouldn't the next step be to request Apple to
>> include
>> Python version  updates in OS updates? So if Python 2.3.1 is ready for
>> OS
>> 10.3.2 beta testing, to please include it? Then you can just ask your
>> users
>> to update to OS 10.3.2 when it comes out.
>> 
>> -- 
>> Paul Berkowitz
>> 
>> 
>> 
>> _______________________________________________
>> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
>> http://mail.python.org/mailman/listinfo/pythonmac-sig
>> 
> 
> 
> _______________________________________________
> Pythonmac-SIG maillist  -  Pythonmac-SIG at python.org
> http://mail.python.org/mailman/listinfo/pythonmac-sig
> 





More information about the Pythonmac-SIG mailing list