Home Original page

Compiling 2.1.1 on Mac OS X 10.1

Compiling 2.1.1 on Mac OS X 10.1 - test failures

Steve Holden sholden at holdenweb.com
Fri Oct 5 07:33:58 EDT 2001 
"Just van Rossum" <just at letterror.com> wrote in message
news:3BBD5C43.D3813A2E at letterror.com...
> Richard Jones wrote:
> >
> > On Friday 05 October 2001 13:21, Steve Holden wrote:
> > > Richard:
> > >
> > > You should go to http://python.sf.net and report these bugs. Follow
the
> > > link to the project page, then select bugs. There's a "Submit New"
link
> > > close to the top of the page.
> >
> > Yep, was going to do that - just wanted to share with the community a
bit a
> > see if I would be able to submit useful information with the bugs :)
>
> Yet a lot of things have changed or have been fixed since 2.1.1, so it
would
> be best to test with 2.2a4, or even better, CVS Python.
>
While I agree that bug reports about the latest and greatest Python are what
helps drive the language forward, I don't think we should neglect the bugfix
releases, particularly since they could be significant in helping
organizations maintain a "constant-level Python" when they can't necessarily
upgrade at eaxh release for compatibility reasons.

not-that-python-is-ever-backwards-incompatible-ly y'rs  - steve
--
http://www.holdenweb.com/
More information about the Python-list mailing list