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 ned.deily
Recipients ddvento@ucar.edu, doko, eric.araujo, ned.deily
Date 2013-02-08.21:15:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1360358146.49.0.760842091453.issue17161@psf.upfronthosting.co.za>
In-reply-to
Content
It would be helpful in the future if you would open separate issues for each problem you report.  To address your points:

1) For unix-y builds, the static library along with other files needed for embedding Python are installed in the standard Python library directory in the config subdirectory (e.g. /usr/lib/python2.7/config).

2a) I don't see any indication of point version number in the currently generated man page: it simply refers to "2.7".  The file name ".1" in the file name refers to what man section the man page belongs in, e.g. "man 1 python2.7".

2b) The Python makefile was changed (c208f5c1e4fe) between the 2.6 and 2.7 releases to install the versioned man page.  I am guessing that it was an oversight that the unversioned man page install was dropped.  Perhaps Matthias can shed some light on this.  The man page installs should likely follow the "alt" scheme, meaning there should be both "altmaninstall" and "maninstall" targets called respectively from "altinstall" and "install", with the latter installing the unversioned link.
History
Date User Action Args
2013-02-08 21:15:46ned.deilysetrecipients: + ned.deily, doko, eric.araujo, ddvento@ucar.edu
2013-02-08 21:15:46ned.deilysetmessageid: <1360358146.49.0.760842091453.issue17161@psf.upfronthosting.co.za>
2013-02-08 21:15:46ned.deilylinkissue17161 messages
2013-02-08 21:15:46ned.deilycreate