Changes in this release docs

[Jeff Blaine]

Something that has always bothered me about the 'Changes in this
release' docs for new features (generators for instance): There's
usually no explanation for why the feature was added. Sure, it's
nice to leave the feature open-ended to not pigeon hole its usage,
but I think (and maybe this is just me) people are likely to make
better use of the language's new features if they "get it" more
directly through an explanation of the hole that was filled in
the language. That is, someone requested it and had a reason to
want it. What was that reason, in real-world terms?

I don't think it's reasonable to expect language _users_ to keep
up with PEPs, etc.

Just a humble request for consideration.

 

[=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=]

Something that has always bothered me about the 'Changes in this
release' docs for new features (generators for instance): There's
usually no explanation for why the feature was added.

Which document are you specifically referring to? AFAICT, there is
no document titled "Changes in this release", atleast not for Python.

I don't think it's reasonable to expect language _users_ to keep
up with PEPs, etc.

But is it asked to much for users to read the PEP when they want
to find out the rationale for a change?

Regards,
Martin

 

[Jeff Blaine]

Which document are you specifically referring to? AFAICT, there is
no document titled "Changes in this release", atleast not for Python.

I guess I should have used the exact wording.

http://docs.python.org/whatsnew/whatsnew23.html

But is it asked to much for users to read the PEP when they want
to find out the rationale for a change?

I'm not really interested in rationalization of a change. That's
what the PEPs are for.

I don't really know how to respond to you.

I know my point and how I feel about it and why I had a "reaction"
to what I was reading. Personally, I think it's something that
would better Python release notes with minimal effort and get people
up to speed better, faster, etc.

That said, I wholeheartedly thank Andrew K. for his many years of
work on the language, and don't mean to slight his document.

Merely a suggestion. Bye.

 

[=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=]

I guess I should have used the exact wording.

http://docs.python.org/whatsnew/whatsnew23.html

Thanks. I really did not know what you were referring to, because
there also is

http://www.python.org/2.3/highlights.html
http://www.python.org/2.3/NEWS.txt

I'm not really interested in rationalization of a change. That's
what the PEPs are for.

I thought you were asking for information why a change is made.
To me, this is the same as asking "what was the rationale for the
change"; that question is (or should be) answered in the PEP.

That said, I wholeheartedly thank Andrew K. for his many years of
work on the language, and don't mean to slight his document.

And indeed, it might be better to direct remarks about this document
directly to him. He is the only one making changes to it, so only he
can offer more than sympathy.

Regards,
Martin