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 loewis
Recipients benjamin.peterson, gpolo, kbk, loewis, rhettinger
Date 2009-04-21.02:48:12
SpamBayes Score 1.5992185e-07
Marked as misclassified No
Message-id <49ED33EA.90604@v.loewis.de>
In-reply-to <1240280312.46.0.980295652285.issue5783@psf.upfronthosting.co.za>
Content
> Fragile solution, but it works.  IMO, it's a better design to just have
> the file named Python26.chm like it always used to be done.

That was also fragile, as this bug report demonstrates. It broke when
sphinx decided to put more version information into the file names.

So when the file naming algorithm changes in one place and not the
others, it *will* break, no matter what the old algorithm was. The
lesson to be learned is that you just should be *very* careful to ever
change file names. Applying that lesson to the status quo means that
IDLE has to change, not the file name of the CHM file.
History
Date User Action Args
2009-04-21 02:48:14loewissetrecipients: + loewis, rhettinger, kbk, benjamin.peterson, gpolo
2009-04-21 02:48:13loewislinkissue5783 messages
2009-04-21 02:48:12loewiscreate