Re: [Pyobjc-dev] PyObjc and Python 2.5

[Bob I. <bo...@re...>]

On 9/25/06, Bob Ippolito <bo...@re...> wrote:
> On 9/25/06, Ronald Oussoren <ron...@ma...> wrote:
> >
> > On Sep 25, 2006, at 4:37 PM, Bob Ippolito wrote:
> >
> > > On 9/25/06, Ronald Oussoren <ron...@ma...> wrote:
> > >>
> > >> On Monday, September 25, 2006, at 03:21PM, Michael Tsai
> > >> <li...@mj...> wrote:
> > >>
> > >> >On Sep 24, 2006, at 5:27 PM, Bob Ippolito wrote:
> > >> >
> > >> >> Either way, you need to install bdist_mpkg to use it. easy_install
> > >> >> bdist_mpkg.
> > >> >
> > >> >Installing it from svn worked, but why didn't this happen
> > >> >automatically when building PyObjC? It "just worked" before the
> > >> >switch to setuptools.
> > >>
> > >> That needs to be investigated. I noticed the same thing when the
> > >> switch to setuptools was done and installed bdist_mpkg by hand to
> > >> get going again. I then promptly forgot about this issue :-(
> > >
> > > The problem is what I said it was.. the bdist_mpkg tarball was built
> > > with a too old version of setuptools. It just needs to be rebuilt and
> > > uploaded again, or a 2.5 egg needs to go up.
> >
> > Sorry about the confusion, I hadn't read your e-mail yet. Is there
> > any chance that you'll do that in the near future?
>
> I'll do it when PyPI is fixed:
>
> Submitting dist/bdist_mpkg-0.4.2.tar.gz to http://www.python.org/pypi
> Upload failed (400): Bad Request

Turns out that just means PyPI refuses to replace files that exist.
Removed and rebuilt the most recent version of everything in the
py2app suite (though no 2.5 eggs yet, the source packages should be
tagged properly with the latest setuptools).

-bob