Re: [Pyobjc-dev] Re: [Pyobjc-checkins] CVS: pyobjc/Examples/TableModel2 main.m,1.4,1.5

[Just v. R. <ju...@le...>]

Jack Jansen wrote:

> On zaterdag, nov 23, 2002, at 14:47 Europe/Amsterdam, Just van Rossum 
> wrote:
> > Go right ahead, but I don't care one single bit for 10.1, so I
> > think it's a waste of time (although it would probably be faster to
> > do it with /usr/bin/sh.
> 
> Forgot to reply to this bit. What makes 10.1.5 interesting is that it's 
> the last release that runs on 603 and 604 hardware, 10.2 is G3/G4-only. 

The only person I know that runs 10.1.5 for that reason (on an old 8500) uses it
as a headless server. The only app on that machine that matters is Apache... I
don't think this an interesting platform for (standalone) Python/PyObjC GUI apps
at *all*.

> And I haven't seen any numbers yet on how many people are sticking with 
> 10.1 because of the price of the upgrade...

On the other hand: Python is free ;-)

I'm not suggesting we should always demand the latest version (not at all) but
I'm all for taking full advantage of the fact that 10.2 ships with Python. I'm
convinced it will save us a lot of time.

> > Speaking of bundlebuilder and plistlib: I saw that Ronald checked
> > them in into the pyobjc project, which made me wonder whether
> > repository symlinks are possible across sf projects. Shall I just
> > open a support request and ask?
> 
> I think it would be a major can of worms. I think I would designate
> one as the main copy, and use "cvs import" in the other tree.

And manually update everytime the main copy has been upgraded? I'm not looking
forward to do _two_ checkins for each change to each of these files. Why would
it be a can of worms? I maintain those modules, and it's my excplicit goal to
stay compatible with Python 2.2.

Just