[Pyobjc-dev] pyobjc.sourceforge.net

[Steven D. M. <sd...@mi...>]

[Trying this again from the right machine.]

Although nothing has changed in the cvs repository or the pyobjc
web pages at sourceforge, there *HAS* been some work going on.

If you look at some of the discussion forums, you will see that
an awful lot of folks are having trouble with ssh & cvs since
the recent move and upgrades at SourceForge.

On comp.lang.python on Wed, 24 Jan 2001, Tim Peters wrote:

> > Does anyone know what going on at SourceForge ?
>
> According to http://sourceforge.net/ today,
>
>     Hosted Projects:   14,366
>     Registered Users: 110,619
>
> I guess that if we dug deep enough, that would pretty much explain
> everything <0.3 wink>.
>
> growing-pains-ly y'rs  - tim
>

The problem seems to be with a backlog of new projects which all
require some manual setup or intervention.

I figure we can give it another week or so, to see if they get it
together, before we take up discussion of looking for another site
to host development.

BTW: The Python 2.1a1 distribution seems to have all of the patches
to build on Mac OSX with objc support. However, they changed some
of the setup and module building to use disutils, and a couple of
new things broke. Most of these are being patched for the next
release. pyobjc *ALMOST* builds "out of the box" for the new python2.1a1:
The lib/python2.1/config/makesetup script has changed from using $(CCC)
to $(CXX), and the default for that is "g++" , so if it's not set to
"c++" it won't work on OSX. ( I'm not sure that I'ld call that a bug,
and we're probably going to have to update the setup to disutils
anyway, so we might as well fix it there. )


BTW2: Actually, the old build of ObjC.so still worked with 2.1a1,
but I wanted to test that it would build with the new distribution.

-- Steve Majewski