(32-bit) PyScripter 2.6 works with (32-bit) Python 2.7.10, but doesn't seem to with (32-bit) Python 2.7.11

[Russell J]

With Python 2.10 installed (in the default location), I can successfully bring up 32-bit PyScripter 2.6 with any of the following commands:

    "C:\Program Files (x86)\PyScripter\pyscripter.exe"
    "C:\Program Files (x86)\PyScripter\pyscripter.exe" --python27
    "C:\Program Files (x86)\PyScripter\pyscripter.exe" --pythondllpath C:\Windows\System32
    "C:\Program Files (x86)\PyScripter\pyscripter.exe" --pythondllpath C:\Windows\SysWow64
    "C:\Program Files (x86)\PyScripter\pyscripter.exe" --python27 --pythondllpath C:\Windows\System32
    "C:\Program Files (x86)\PyScripter\pyscripter.exe" --python27 --pythondllpath C:\Windows\SysWow64

    NOTE:
       
        Python.exe and PythonW.exe are both located in C:\Python27
       
        Python27.dll is located in both C:\Windows\System32 and C:\Windows\SysWow64
       
Yet, when I uninstall Python 2.7.10 and then install Python 2.7.11 to the same location,
not one of those commands successfully brings up  PyScripter 2.6
(even though Python.exe, PythonW.exe, and Python27.dll are all installed in the same places that they were with Python 2.10).

If I then uninstall Python 2.7.11 and install Python 2.7.10 to the same location, I'm able to bring up PyScripter successfully again.

Does anyone have any idea what might be causing this?

Since:

     Python 2.7.10 itself didn't come out until May 2015, 2 months after PyScripter 2.6.

     The main files are named the same and located in the same places.

I wouldn't think PyScripter 2.6 would differentiate between Python 2.7.10 and 2.7.11.

Apparently, though, it somehow does.

Thank you.

- Russell J

P.S. - I don't think this is unique to 32-bit, but didn't thoroughly test it.

[Russell J]

Oops!

That should read:

With Python 2.7.10 installed (in the default location), I can successfully bring up 32-bit PyScripter 2.6 with any of the following commands:
...

Yet, when I uninstall Python 2.7.10 and then install Python 2.7.11 to the same location,
not one of those commands successfully brings up  PyScripter 2.6

(even though Python.exe, PythonW.exe, and Python27.dll are all installed in the same places that they were with Python 2.7.10).
...

Sorry about that.

- Russell J.

- Russell J.

[BBands]

I haven't tried 2.7.11, but I guess that PyScripter can't recognize a Python version > 2.7.10 yet.

     John

[Russell J]

John (BBands),

That's what it looks like to me.

As far as I know, though, 2.7.11 is primarily just a bug-fix release,

And since (by default) both 2.7.10 and 2.7.11 are installed to the same location (C:\Python27), have the same .dll name (python27.dll), etc., I'm puzzled as to why this works for 2.7.10 but not 2.7.11.

I guess I should submit an issue on GitHub.

Thanks.

- Russell J