"type specific" to "type-specific"

[Retro]

BPO	13695

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/rhettinger'
closed_at = <Date 2012-01-18.16:05:19.186>
created_at = <Date 2012-01-02.05:48:08.628>
labels = ['type-feature', 'docs']
title = '"type specific" to "type-specific"'
updated_at = <Date 2012-01-18.16:05:19.184>
user = 'https://bugs.python.org/Retro'

bugs.python.org fields:

activity = <Date 2012-01-18.16:05:19.184>
actor = 'Retro'
assignee = 'rhettinger'
closed = True
closed_date = <Date 2012-01-18.16:05:19.186>
closer = 'Retro'
components = ['Documentation']
creation = <Date 2012-01-02.05:48:08.628>
creator = 'Retro'
dependencies = []
files = []
hgrepos = []
issue_num = 13695
keywords = []
message_count = 13.0
messages = ['150451', '150490', '151326', '151327', '151332', '151344', '151349', '151397', '151404', '151456', '151480', '151522', '151546']
nosy_count = 1.0
nosy_names = ['Retro']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue13695'
versions = ['Python 2.7', 'Python 3.2', 'Python 3.3']

[Retro]

Please visit the following link and fix the below text:

http://docs.python.org/library/unittest.html#unittest.TestCase.assertEqual

Changed in version 2.7: Added the automatic calling of >>>type-specific<<< equality function.

Just add the hyphen. Thanks.

[Retro]

Also

http://guide.python-distribute.org/quickstart.html#lay-out-your-project

needs to have the first sentence fixed: "python" to "Python"

and

http://docs.python.org/library/functools.html#functools.cmp_to_key

needs to have the word "Py3.x" fixed to "Python 3" (note: not to "Python 3.x" because functools.reduce() function also has the word "Python 3", so be consistent)

[python-dev]

New changeset 2dd96cf324ee by Ezio Melotti in branch '2.7':
bpo-13695: fix a couple of typos in the doc.
http://hg.python.org/cpython/rev/2dd96cf324ee

New changeset bff9ab281385 by Ezio Melotti in branch '3.2':
bpo-13695: fix a couple of typos in the doc.
http://hg.python.org/cpython/rev/bff9ab281385

New changeset 3b097e0892cf by Ezio Melotti in branch 'default':
bpo-13695: merge with 3.2.
http://hg.python.org/cpython/rev/3b097e0892cf

[ezio-melotti]

I fixed both 'type-specific' and 'Python 3'. The python-distribute link is not part of our documentation so I can't fix it.

[Retro]

There's also one more typo in the doc for cmp_to_key() function. Fix the first sentence "Transform an old-style comparison function to a key-function." to "Transform an old-style comparison function to a key function." (note the removal of the hyphen between words "key" and "function")

http://docs.python.org/library/functools.html#functools.cmp_to_key

[Retro]

Found one little bug again in http://docs.python.org/library/stdtypes.html#sequence-types-str-unicode-list-tuple-bytearray-buffer-xrange

Look at the table with the fields Operation, Result, Notes, and fix the fifth record of the Result field from "i'th item of s, origin 0" to "i-th item of s, origin 0".

So change only that apostrophe into a hyphen, so "i'th" to "i-th".

[birkenfeld]

Would you care to explain why that change needs to be made?

[Retro]

I guess you're reffering to the "i'th" --> "i-th" thing.

I found numerous occasions on the Internet that say like "n-th element blah blah blah", not "n'th element..."

So I guess writting this thing as "i-th" would be correct here, too.

[birkenfeld]

"numerous occasions" is not good enough. Why not let a native speaker decide?

[Retro]

Well, actually, it's the only correct way to write it (i-th). This is a simple orthographical error that was made. Ezio, please fix those two additional typos. And Georg, stop being such a wise-ass.

[birkenfeld]

Once you start contributing anything useful, I will start treating it as such.

[Retro]

Shut up, Georg! Ezio, please fix this two additional typos to close this bug report for good.

[Retro]

I am closing this issue report and opening another issue report with the two new doc typos that were not reported here before the commit of Ezio Melotti.