References to Python 1.5

[d0bd5d4f-9468-428f-bdd3-18136fa41d93]

BPO	214318
Nosy	@freddrake

^{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: ```python assignee = 'https://github.com/freddrake' closed_at = created_at = labels = ['docs'] title = 'References to Python 1.5' updated_at = user = 'https://bugs.python.org/jpettit' ``` bugs.python.org fields: ```python activity = actor = 'fdrake' assignee = 'fdrake' closed = True closed_date = None closer = None components = ['Documentation'] creation = creator = 'jpettit' dependencies = [] files = [] hgrepos = [] issue_num = 214318 keywords = [] message_count = 2.0 messages = ['1357', '1358'] nosy_count = 2.0 nosy_names = ['fdrake', 'jpettit'] pr_nums = [] priority = 'normal' resolution = 'fixed' stage = None status = 'closed' superseder = None type = None url = 'https://bugs.python.org/issue214318' versions = [] ```

[d0bd5d4f-9468-428f-bdd3-18136fa41d93]

In the documentation, there are references to Python's library path that often use "/usr/local/lib/python1.5" instead of "/usr/local/lib/python2.0". A quick "find" and "grep" shows the following pages:

./api/embedding.html
./api/includes.html
./dist/node13.html
./lib/module-pdb.html
./lib/module-pprint.html
./lib/module-site.html
./lib/profile-instant.html
./lib/typesmodules.html

The only one that might be a problem is "./lib/module-site.html", since it mentions Python 2.0b1.1 explicitly and states that its library is installed in "python1.5".

[freddrake]

The markup has been extended so that we have a mark for the "short" flavor of the version number. I've modified the documents to use it where needed and possible.

Note that material in {verbatim} environments still don't use this, as macros are not expanded in that context. To avoid changing those with each release, I'm going to leave those as they are; I don't think that will hurt, though it does seem less than ideal.