[Python-Dev] Python and the Unicode Character Database (original) (raw)
Georg Brandl g.brandl at gmx.net
Thu Dec 2 13:57:41 CET 2010
- Previous message: [Python-Dev] Python and the Unicode Character Database
- Next message: [Python-Dev] Python and the Unicode Character Database
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Am 01.12.2010 23:39, schrieb "Martin v. Löwis":
As of today, "What’s New In Python 3.2" [1] does not even mention the unicodedata upgrade to 6.0.0. One reason was that I was instructed not to change "What's New" a few years ago.
Maybe all past, present and future whatsnew maintainers can agree on these rules, which I copied directly from whatsnew/3.2.rst?
Rules for maintenance:
Anyone can add text to this document. Do not spend very much time on the wording of your changes, because your text will probably get rewritten to some degree.
The maintainer will go through Misc/NEWS periodically and add changes; it's therefore more important to add your changes to Misc/NEWS than to this file.
This is not a complete list of every single change; completeness is the purpose of Misc/NEWS. Some changes I consider too small or esoteric to include. If such a change is added to the text, I'll just remove it. (This is another reason you shouldn't spend too much time on writing your addition.)
If you want to draw your new text to the attention of the maintainer, add 'XXX' to the beginning of the paragraph or section.
It's OK to just add a fragmentary note about a change. For example: "XXX Describe the transmogrify() function added to the socket module." The maintainer will research the change and write the necessary text.
You can comment out your additions if you like, but it's not necessary (especially when a final release is some months away).
Credit the author of a patch or bugfix. Just the name is sufficient; the e-mail address isn't necessary. It's helpful to add the issue number:
XXX Describe the transmogrify() function added to the socket module.
(Contributed by P.Y. Developer; :issue:
12345.)
This saves the maintainer the effort of going through the SVN log when researching a change.
Georg
- Previous message: [Python-Dev] Python and the Unicode Character Database
- Next message: [Python-Dev] Python and the Unicode Character Database
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]