Speaking about the CHM, why does it include the version number in it's filename? Why isn't it named python.chm instead of python266.chm, just like we have python.exe and not python266.exe? I have shortcut links in the QuickLaunch area to the documentation for quick access and in a different launcher program. Each time I upgrade Python I must update them because of the embedded version number. Regards, Adal
Am 25.08.2010 17:03, schrieb Adal Chiriliuc:
Wrt. software, any "why" question is tricky. It's in the file name because the generator that generates it puts it there. Now, why does it put it there? Because it does so for any other distribution format of the documentation. It used to be python26.chm (i.e. without the micro version), and was deliberately changed - primarily for consistency, AFAIK. Now, why do the other formats have a version number in them? So that you can have them all in the same directory, and they won't overwrite each other. And so that if you downloaded one of them, you'd still know what it is that you downloaded afterwards. Regards, Martin
On Thu, Aug 26, 2010 at 1:08 AM, "Martin v. Löwis" <martin@v.loewis.de> wrote:
The one deployed with the binaries installer could still be renamed to python.chm. When you start the CHM file, the first thing hitting you is a huge "Python v2.6.5 documentation" header, so I don't think anybody would be confused. And there doesn't seem to be a link to download the CHM files (the last I could find on python.org is for Python 2.6.2). Anyway, this is not a big issue. Regards, Adal
Am 25.08.2010 17:03, schrieb Adal Chiriliuc:
Wrt. software, any "why" question is tricky. It's in the file name because the generator that generates it puts it there. Now, why does it put it there? Because it does so for any other distribution format of the documentation. It used to be python26.chm (i.e. without the micro version), and was deliberately changed - primarily for consistency, AFAIK. Now, why do the other formats have a version number in them? So that you can have them all in the same directory, and they won't overwrite each other. And so that if you downloaded one of them, you'd still know what it is that you downloaded afterwards. Regards, Martin
On Thu, Aug 26, 2010 at 1:08 AM, "Martin v. Löwis" <martin@v.loewis.de> wrote:
The one deployed with the binaries installer could still be renamed to python.chm. When you start the CHM file, the first thing hitting you is a huge "Python v2.6.5 documentation" header, so I don't think anybody would be confused. And there doesn't seem to be a link to download the CHM files (the last I could find on python.org is for Python 2.6.2). Anyway, this is not a big issue. Regards, Adal
participants (2)
-
"Martin v. Löwis" -
Adal Chiriliuc