I develop on both Windows and Linux. In fact, I often work on the same projects in both environments.

In general, I find both environments to be mostly the same, as far as Python development is concerned. Mostly the same that is, except that virtualenvwrapper isn’t available on windows.

If you’re not familiar with virtualenvwrapper, it is a brilliant shell script that makes virtualenv super easy to work with. I highly recommend it (except of course if you’re on Windows)

One of the best things about virtualenvwrapper is it lets you quickly and easily activate any available virtualenv with the `workon` command.

$ workon virtualenv_name

(virtualenv_name)/path/to/project/dir/$

Not only does it activate the environment, but it will also automatically ‘cd’ you to the project’s working directory. You have to set the up manually but it is super simple, just add the ‘cd’ command to the ‘postactivate’ hook that virtualenvwrapper sets up in the virtualenv’s directory.

So, no virtualenvwrapper for Windows, but there are other ways to get a command shell which is already good to go for a given project.

In fact, it only takes a simple shortcut to cmd.exe with a few arguments. Create a new shortcut using the right-click context menu, then set

  • Target: %windir%\system32\cmd.exe /k More >