[Python-3000] versionadded/versionchanged in doc

Terry Reedy tjreedy at udel.edu
Tue Dec 19 22:47:04 CET 2006

"Neal Norwitz" <nnorwitz at gmail.com> wrote in message 
news:ee2a432c0612191303n100aba92v8a07535daa3da0d at mail.gmail.com...
> What do we want to do with the current versionadded/versionchanged
> markups in the doc for 3k?  Should we remove all references to 1.x
> changes?  all 2.x changes?  Keep them?  all of them?
> Given we are trying to clean things up, I think I'd prefer to remove
> all the old references to 1.x/2.x changes.  I'm not sure how to handle
> any of the 3.x changes.  I expect those will be in a separate porting
> doc or some such.  So my first thought is that it would be nice to
> have all the doc be clean.

I am pretty sure that a large majority of people learning Python for the 
first time with Python 3 would prefer this.  If Python3 is as successful as 
we might hope, new Pythoneers will become the majority.

>  My only concern is that it might be confusing for people.

Perhaps for some, but I would expect that docs cluttered with 'New/changed 
in 3.0' to be just as confusing for others.  Perhaps we need two versions 
of the docs: a Python x.y set and a Python forever set.

Terry Jan Reedy

More information about the Python-3000 mailing list