The installers will find the correct installation from the Windows registry, and will install in the correct place, side by side, system wide. I have installations varying from Python 2,3 to Python 3.3-64 on my laptop.
Since installing Python 3.3, with its new Python loader, I have almost stopped using virtualenv, since I can easily pick my Python version from the command line: C:> py -3.2-32 myprog.py (But, of course, that is not the only reason for using virtualenv.) -- On Thu, Apr 18, 2013 at 11:51 AM, Dinesh B Vadhia <dineshbvad...@hotmail.com > wrote: > ** > Hi! This is my first question on the list and not sure if this question > has been asked as I can't find searchable archives. > > When developing 32-bit and 64-bit applications in respective virtualenv's, > do pywin32-32 and pywin32-64 have to be installed in the respective > virtualenv's? Or, are the two pywin32's installed system-wide? > > > > > > _______________________________________________ > python-win32 mailing list > python-win32@python.org > http://mail.python.org/mailman/listinfo/python-win32 > >
_______________________________________________ python-win32 mailing list python-win32@python.org http://mail.python.org/mailman/listinfo/python-win32
