Re: [Ironpython-users] IronPython 2.7.5 Schedule

(Answering myself -- sorry) I have re-read the PEP and skimmed the .c code for the launcher. There is provision in the PLW for setting a default version of Python, but it appears that the only choices allowed are versions of CPython selected (by number) from pythons found in the registry. One cou

Re: [Ironpython-users] IronPython 2.7.5 Schedule

Under no circumstances should the .py extension ever be taken away from *Python Launcher for Windows* . I have not looked at what happens when PLW is run on a computer which does not have a version of CPython installed. If it does the right thing (launc

Re: [Ironpython-users] IronPython 2.7.5 Schedule

I have cp34837, cp34892, cp34910 fixed. I will make a PR. I also have some workarounds where I am not clear if they should get into release: 1. cp32331 - better unicode success rate in real application, but decreased number of unit test passed 2. update to installer to modify PATH and register .p

[Ironpython-users] IronPython 2.7.5 Schedule

I know everyone wants to hear about ItonPython 3, but it's time to talk about IronPython 2.7 for a bit. Enough changes have accumulated (thanks Pawel!) that it's probably time for another release. I'm thinking Beta 1 around March 17, Beta 2 around April 1, and an RC/final around April 15. Does anyb