From: Bill Bumgarner <bbum@co...> - 2001-04-06 06:17:20
That makes sense to me. It is definitely more useful than the last
python setup.py sdist will do the right thing. :-)
I believe that the next step should be to look at replacing all the
legacy stuff and cleaning up the method dispatch issues....
On Friday, April 6, 2001, at 01:43 AM, Steven D. Majewski wrote:
> Bill -- I submitted that patch to add ".m" files to python, and
> I got a note it was accepted.
> With your changes to use distutils, it ought to build and install
> out of the box on OSX with Python2.1 once it is released.
> ( Which will probably be soon. )
> I think it's probably time for us to put out a release.
> I changed the #ifdefs, which, because I originally didn't know
> how to test for OSX, were a hack that probably broke the build
> for other platforms.
> In ObjC.h, MACOSX is defined if defined(__APPLE__) &&
> #ifdef MACOSX is used elsewhere.
> I did it that way because I think the __APPLE__ & __MACH__ trick is
> a little too tricky -- I would rather eventually change it so that
> setup adds a -D line with system name.
> I tried to make it #define DARWIN at first, but the compiler
> complained about it. Somewhere there is a precompiled header
> that uses DARWIN, but I didn't want to rely on it being defined
> elsewhere until I can find it.
> I'll probably try to see if I can shake out any more bugs, and
> then make a tar file and put it on sourceforge as a release.
> -- Steve Majewski
> Pyobjc-dev mailing list
From: Andrew Zeldis <azeldis@ma...> - 2001-04-06 14:18:17
Just to back this up - I haven't been able to work with it much recently but
I did get the pyobjc module built with python 2.1b2 using distutils (after a
"patch" of my own to add .m). It worked like a charm.
It would be great if pyObjC could be included in standard python as an
optional platform-specific module - they do stuff like that for sunAudioDev
etc right? Like, part of the standard dist, only built on appropriate
Anyway, cheers to you to for the great work!
From: Steven D. Majewski <sdm7g@mi...> - 2001-04-06 16:24:24
I bumped the version in ObjC.h up to .56, then I saw that
you set it to 0.9 in setup.py.
Considering that we're going to tackle some major upgrading
and weeding of obsolete methods, I think we need to leave
a bit more "space" before a 1.0 release.
How about 0.6 ?
From: Bill Bumgarner <bbum@co...> - 2001-04-06 16:25:29
Of course, there is always .9[0-9][0-9]... numbers are neat that way,
there is always in infinite # of 'em available between two points.
(Seriously, though, 0.6 is more appropriate)
On Friday, April 6, 2001, at 12:24 PM, Steven D. Majewski wrote:
> I bumped the version in ObjC.h up to .56, then I saw that
> you set it to 0.9 in setup.py.
> Considering that we're going to tackle some major upgrading
> and weeding of obsolete methods, I think we need to leave
> a bit more "space" before a 1.0 release.
> How about 0.6 ?
> -- Steve