On Dec 23, 2004, at 7:01 PM, Charles Hartman wrote:
Fixing this for 2.4.1 and 2.3.5 themselves is rather easy (and sketched in the mail mentioned above). Fixing this in the Apple-installed 2.3 is a bit more difficult, though. We can either modify it in-place (with admin permission) or do a complicated patch that Ronald came up with last year. While in general you should not muck with Apple-installed things I think that for this once I have a preference for the simple in-place modification over the slightly convoluted patch. Opinions, anyone?
As a more or less perpetual newbie at this, much as I welcome the chance to upgrade, I cast my vote for a *reversible* change in the Apple-installed version. If I screw everything up, I'd like to be able to go back. Or, alternatively, make it impossible even for me to screw up. (Ha ha.)
It's pretty much impossible to screw up. Basically it should be an installer .pkg that simply tosses a single file to a specific place, replacing what was there. There is no need to revert to the original version of this file because that one is half-broken to begin with.
-bob
_______________________________________________ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
