Closed jeremygray closed 9 years ago
I have just added a note in the readme file about attempting to support Python 2.7 (modulo some potential unicode issues) as I've had anothe request. With Python 2.7.9, the launcher works properly on Windows ... but I remember reading not so long ago about passing the arguments to subprocess as a list like you did instead of the way I did. I will try to make the change here and, if it works, use the list approach. I'll need to read about supporting Python 2 and 3 (the last project I did which supported both was done 6 years ago!) as much "wisdom" about doing so has been uncovered since from what I have been reading.
it should work now (fingers crossed). I had broken something when trying to fix the unicode issue. Furthermore, I think I had made some assumptions about where the files would be launched; the new way should be more robust.
fixed with #10
Maybe supporting python 2.7 is too much of a hassle...
The launcher demo is not working for me on 2.7.8, due to
subprocess.check_input
expecting a list rather than string. The launcher is shown, but when trying to launch anything I get same the OSError:For me, passing a string to subprocess fails:
But doing as a list works as intended:
and when I hardcode that, then the launcher > python version button works as expected.