Message 191275 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	belopolsky
Recipients	belopolsky, docs@python, eric.araujo, ezio.melotti, georg.brandl
Date	2013-06-16.17:38:42
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1371404322.72.0.560114246685.issue18176@psf.upfronthosting.co.za>
In-reply-to

Content
Here is what grep revealed: $ find Doc -name \*.rst \| xargs grep -n '6\.2\.0' Doc/library/stdtypes.rst:357: See http://www.unicode.org/Public/6.2.0/ucd/extracted/DerivedNumericType.txt Doc/library/unicodedata.rst:18:this database is compiled from the `UCD version 6.2.0 Doc/library/unicodedata.rst:19:<http://www.unicode.org/Public/6.2.0/ucd>`_. Doc/library/unicodedata.rst:169:.. [#] http://www.unicode.org/Public/6.2.0/ucd/NameAliases.txt Doc/library/unicodedata.rst:171:.. [#] http://www.unicode.org/Public/6.2.0/ucd/NamedSequences.txt I added a note next to UNIDATA_VERSION = "6.2.0" in makeunicodedata.py script. The makeunicodedata.py would be a place to put code that would update the docs automatically, but with only two affected files I don't think this is worth the effort. Chances are at least unicodedata.rst will benefit from a manual review to reflect any substantive changes in the UCD.

Here is what grep revealed:

$ find Doc -name \*.rst | xargs grep -n '6\.2\.0'
Doc/library/stdtypes.rst:357:   See http://www.unicode.org/Public/6.2.0/ucd/extracted/DerivedNumericType.txt
Doc/library/unicodedata.rst:18:this database is compiled from the `UCD version 6.2.0
Doc/library/unicodedata.rst:19:<http://www.unicode.org/Public/6.2.0/ucd>`_.
Doc/library/unicodedata.rst:169:.. [#] http://www.unicode.org/Public/6.2.0/ucd/NameAliases.txt
Doc/library/unicodedata.rst:171:.. [#] http://www.unicode.org/Public/6.2.0/ucd/NamedSequences.txt

I added a note next to UNIDATA_VERSION = "6.2.0" in makeunicodedata.py script. The makeunicodedata.py would be a place to put code that would update the docs automatically, but with only two affected files I don't think this is worth the effort.  Chances are at least unicodedata.rst will benefit from a manual review to reflect any substantive changes in the UCD.

History
Date	User	Action	Args
2013-06-16 17:38:42	belopolsky	set	recipients: + belopolsky, georg.brandl, ezio.melotti, eric.araujo, docs@python
2013-06-16 17:38:42	belopolsky	set	messageid: <1371404322.72.0.560114246685.issue18176@psf.upfronthosting.co.za>
2013-06-16 17:38:42	belopolsky	link	issue18176 messages
2013-06-16 17:38:42	belopolsky	create