Message260468
> My weak opinion is that a new parameter is a new API item, not just a change in behaviour, so should probably have “versionadded”.
This was my reasoning as well.
Also, when I noticed so many instances of ``.. versionchanged`` that all say “Added the *x* parameter” (or whatever), it strikes me that these are a *large class of changes*, which all have some kind of addition in common. If you think about it, deprecations and removals are also changes, but they are a large-enough class of changes to merit a distinct markup directive.
So, just as this is true for “deprecated” or “deprecated-removed”, I believe it is just as true for “added”. Once all additions, deprecations, and removals have been marked up as such, I think find that there’s still PLENTY of annotations that remain under ``.. versionchanged``.
Put another way:
Since these are all different types of changes, it is most useful to the reader if the most specific *type* of change is reflected in the markup. |
|
Date |
User |
Action |
Args |
2016-02-18 16:27:57 | Tony R. | set | recipients:
+ Tony R., georg.brandl, ezio.melotti, docs@python, berker.peksag, martin.panter |
2016-02-18 16:27:57 | Tony R. | set | messageid: <1455812877.69.0.541684407424.issue26366@psf.upfronthosting.co.za> |
2016-02-18 16:27:57 | Tony R. | link | issue26366 messages |
2016-02-18 16:27:57 | Tony R. | create | |
|