Use cygwin to have a nice bash environment that allows you to easily run python scripts using specific interpreters or use virtualenv to create environments based on specific interpolations:
> mkdir project > cd project > C:\Python27\Scripts\virtualenv.exe -p C:\Python32\python.exe . > Scripts\activate
At this point, your env was installed in this project, and python
input will start python3.2
You would have typed deactivate
to return to normal env. With this approach, you can either configure this on a per-project basis to manage version dependencies between python projects, or make it more global for each python version as a whole. To you.
On nix-based systems, we have the luxury of the โshebangโ line at the top of the script to tell which interpreter to use. Windows only has file extension associations via the GUI, and you must be explicit on the command line in the form python <script.py>
source share