I approved it, but I don't think I spent more than a minute thinking about it. Since 3.0 is fundamentally incompatible with 2.x, I don't think it's important to keep a record in the docs about when something was added during the 2.x era -- future historians can dig that out of the 2.6 docs if they care.
There just isn't a use case (that I can think of) for trying to write code that works in 3.0 *and* in some other version earlier than 2.6. And even for 2.6 vs. 3.0 the best you can do is run 2to3 over the 2.6 sources. So I don't see how someone using 3.0 would be interested in which 2.x version something was added. --Guido On 9/1/07, Fred Drake <[EMAIL PROTECTED]> wrote: > On Sep 1, 2007, at 8:33 AM, georg.brandl wrote: > > Remove versionadded and versionchanged directives, fold information > > into text where necessary. > > Was this discussed somewhere and I just missed the discussion? > Removing information from the documentation source is somewhat > disturbing. > > The descriptions should be complete for the current version without > the added/changed notes, but those are important for anyone dealing > with multiple versions. I suspect that won't really change when > people move to Python 3.0, so I doubt removing these is actually a > good thing. (Displaying them could be made optional, though.) > > > -Fred > > -- > Fred Drake <fdrake at acm.org> > > > > _______________________________________________ > Python-3000-checkins mailing list > [email protected] > http://mail.python.org/mailman/listinfo/python-3000-checkins > -- --Guido van Rossum (home page: http://www.python.org/~guido/) _______________________________________________ Python-3000-checkins mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000-checkins
