[python-win32] pywin32 and virtualenv

[Dinesh B Vadhia]

Ignoring virtualenv initially.

On a Windows 8 machine, installed Python 2.7.4 64-bit system-wide.  Installed Python 2.7.4 32-bit into a separate folder.

Ran pywin32-218.win32-amd64--py2.7.exe successfully.

Ran pywin32-218.win32-py2.7.exe in the Python 32-bit folder which generated the errors (shown in the pywin32 installer window):

    close failed in file object destructor:
    sys.excepthook is missing
    lost sys.stderr

No mention of successful installation in installer window.




From: Vernon D. Cole 
Sent: Thursday, April 18, 2013 7:12 PM
To: Dinesh B Vadhia 
Cc: python-win32 at python.org 
Subject: Re: [python-win32] pywin32 and virtualenv


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 <dineshbvadhia at 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 at python.org
  http://mail.python.org/mailman/listinfo/python-win32



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-win32/attachments/20130419/176434d1/attachment-0001.html>