Ronald Oussoren <ron...@ma...> writes:
> Is anyone still interested in PyObjC on OSX 10.4? I haven't done any
> development on 10.4 in a long time and while having 10.4 support would
> be nice to have I don't think I'll ever get around to finishing 10.4
> support in PyObjC 2.x.
Yes, for my part. It would finally allow me to move a significant
application I'm maintaining off of PyObjC 1.4 and yet still support
existing older client machines.
Currently, I'm using 1.4 and generating 10.4 compatible installations
because of client need, and in fact have had to not only keep a
separate 10.4 development system, but hold back on the 10.4.11 system
update since it contains the webkit interface change that didn't work
properly with the PyObjC 1.4 wrapper.
I'm sure there are ways[*] to manually maintain two builds, but the
current discontinuity between PyObjC 1.4 on a 10.4 system for 10.4
clients, versus PyObjC 2.x on 10.5+ systems for 10.5+ clients is
unfortunate from a maintenance perspective, and something I had hoped
would eventually disappear.
I suppose an alternative to supporting 2.x under 10.4 would be to
officially declare it never to be supported, since that would at least
force the issue for me to figure out a different approach rather than
waiting for such support.
-- David
[*] I've only seen fairly complex approaches to try to have a single
development system (whether 10.4 generating 10.5+ compatible binaries,
or 10.5+ generating 10.4 compatible binaries), so in this main case
I've just frozen things in the 10.4 environment to help manage
maintenance, but I had hoped that was a near term thing until a
migration path was available.
|
