You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At least the following vanilla Python distributions: 2.7.1rc1, 3.1.2, 3.1.3rc1
and 3.2a4 are using a new help file naming convention: pythonNNNxxx.chm, where:
NNN - 3 digits of the version, i.e. 271 for version 2.7.1
xxx - trailing string for release type, a.k.a. "rc1", "a4", empty for normal
releases.
The easiest fix is probably to use the "--pythonXX" switch string as the
beginning of the filename and look for the first filename to match
pythonXX*.chm. Should be compatible with old and new distributions.
A more elaborate approach would be to read the "file version" of the
pythonXX.dll and remove dots from it:
3.2a4 -> 32a4
3.1.3rc1 -> 313rc1
2.7.1rs1 -> 271rc1
But it may break compatibility with older versions as the dlls were already
using all 3 digits, while the chm only used 2 (major+minor).
Original issue reported on code.google.com by fre...@ibelgique.com on 18 Nov 2010 at 4:42
The text was updated successfully, but these errors were encountered:
Also, it seems that PyScripter scans for help files in the directory only at
startup.
May be it can be changed to make the lookup only when the corresponding help
menu item is accessed.
Note. Right now if PyScripter is started with a recognised chm file, and then
this file get renamed/deleted, there is a small, but noticeable, delay when the
"Help->Python Manuals" is accessed, probably due to exception recovery from not
being able to open the file that it "believe" to exist.
Original comment by fre...@ibelgique.com on 18 Nov 2010 at 5:00
ActivePython seem to use yet another slightly different convention for its
naming of the help file: ActivePythonXX.chm
i.e. prepends "Active" and uses only 2 digits (major+minor) for both 2.x and
3.x versions.
Original comment by fre...@ibelgique.com on 19 Nov 2010 at 5:32
Original issue reported on code.google.com by
fre...@ibelgique.com
on 18 Nov 2010 at 4:42The text was updated successfully, but these errors were encountered: