Python for Windows extensions

Bugs item #3075086, was opened at 2010-09-24 19:55
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3075086&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
>Status: Closed
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Tim ()
Assigned to: Nobody/Anonymous (nobody)
Summary: AssertionError building extensions

Initial Comment:
I'm getting an AssertionError when I attempt to install the Python for Windows extensions. My environment is Windows XP with all the latest security updates applied, and Microsoft Visual Studio 2005 and 2008 both installed. Here's the traceback I'm getting:

building exe 'Pythonwin'
Traceback (most recent call last):
  File "C:\Documents and Settings\TimothyB.GSD\My Documents\Downloads\pywin32-21
4\setup.py", line 2152, in <module>
    ('', ('pywin32.pth',)),
  File "C:\Python26\lib\distutils\core.py", line 152, in setup
    dist.run_commands()
  File "C:\Python26\lib\distutils\dist.py", line 975, in run_commands
    self.run_command(cmd)
  File "C:\Python26\lib\distutils\dist.py", line 995, in run_command
    cmd_obj.run()
  File "C:\Documents and Settings\TimothyB.GSD\My Documents\Downloads\pywin32-21
4\setup.py", line 1251, in run
    install.run(self)
  File "C:\Python26\lib\distutils\command\install.py", line 577, in run
    self.run_command('build')
  File "C:\Python26\lib\distutils\cmd.py", line 333, in run_command
    self.distribution.run_command(command)
  File "C:\Python26\lib\distutils\dist.py", line 995, in run_command
    cmd_obj.run()
  File "C:\Documents and Settings\TimothyB.GSD\My Documents\Downloads\pywin32-21
4\setup.py", line 596, in run
    build.run(self)
  File "C:\Python26\lib\distutils\command\build.py", line 134, in run
    self.run_command(cmd_name)
  File "C:\Python26\lib\distutils\cmd.py", line 333, in run_command
    self.distribution.run_command(command)
  File "C:\Python26\lib\distutils\dist.py", line 995, in run_command
    cmd_obj.run()
  File "C:\Python26\lib\distutils\command\build_ext.py", line 340, in run
    self.build_extensions()
  File "C:\Documents and Settings\TimothyB.GSD\My Documents\Downloads\pywin32-21
4\setup.py", line 891, in build_extensions
    self._build_scintilla()
  File "C:\Documents and Settings\TimothyB.GSD\My Documents\Downloads\pywin32-21
4\setup.py", line 825, in _build_scintilla
    assert os.path.isdir(build_temp), build_temp
AssertionError

Any ideas?

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2010-11-30 05:20

Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 05:03

Message:
Or maybe the space in the name is wrong - either way, I can't repro this.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-10-27 05:00

Message:
No real clue I'm afraid - it would seem build_temp is an empty string -
some 'print' debugging in setup.py might be the best way to try and see why
this is happening.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3075086&group_id=78018

Bugs item #3094288, was opened at 2010-10-25 04:57
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3094288&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: PyIProfAdmin.h(6) : error C2143: syntax error : missing ';'

Initial Comment:
I'm trying to build python for win using VS2008, python 2.7 on XP.

After going through some mapi issues, the compilation now fails with this
message.

Please find the complete trace attached

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 15:58

Message:
oops - I meant "2.6 or later"

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 15:53

Message:
Sorry for the delay - to build Python 2.6, try the Windows 7 SDK at
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b
- I just updated (in CVS) the comments in setup.py to reflect my current
build environment (which I just rebuilt in a VM)

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2010-10-30 20:40

Message:
I'm using the windows SDK version 6.1

is this incorrect ?  I was using this SDK together with VS2008 to
get the python build itself working.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-10-27 12:02

Message:
The problem seems to be that IProfAdmin isn't defined.  I  guess this will
have something to do with the windows sdk version being used - I can see
that interface defined in mapix.h, which should be included via
PyMAPIUtil.h.  You might need to grep your SDK dir to find where this is
defined, or try and diagnose why it isn't being included for you (eg, some
#define needed before including mapi, etc)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3094288&group_id=78018

Bugs item #3094288, was opened at 2010-10-25 04:57
Message generated for change (Settings changed) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3094288&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Pending
>Resolution: Works For Me
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: PyIProfAdmin.h(6) : error C2143: syntax error : missing ';'

Initial Comment:
I'm trying to build python for win using VS2008, python 2.7 on XP.

After going through some mapi issues, the compilation now fails with this
message.

Please find the complete trace attached

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 15:58

Message:
oops - I meant "2.6 or later"

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 15:53

Message:
Sorry for the delay - to build Python 2.6, try the Windows 7 SDK at
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b
- I just updated (in CVS) the comments in setup.py to reflect my current
build environment (which I just rebuilt in a VM)

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2010-10-30 20:40

Message:
I'm using the windows SDK version 6.1

is this incorrect ?  I was using this SDK together with VS2008 to
get the python build itself working.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-10-27 12:02

Message:
The problem seems to be that IProfAdmin isn't defined.  I  guess this will
have something to do with the windows sdk version being used - I can see
that interface defined in mapix.h, which should be included via
PyMAPIUtil.h.  You might need to grep your SDK dir to find where this is
defined, or try and diagnose why it isn't being included for you (eg, some
#define needed before including mapi, etc)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3094288&group_id=78018

Bugs item #3094288, was opened at 2010-10-24 17:57
Message generated for change (Comment added) made by tw55413
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3094288&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Pending
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: PyIProfAdmin.h(6) : error C2143: syntax error : missing ';'

Initial Comment:
I'm trying to build python for win using VS2008, python 2.7 on XP.

After going through some mapi issues, the compilation now fails with this
message.

Please find the complete trace attached

----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-16 21:07

Message:
works indeed with the Windows 7.1 sdk

Thx !

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 04:58

Message:
oops - I meant "2.6 or later"

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 04:53

Message:
Sorry for the delay - to build Python 2.6, try the Windows 7 SDK at
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b
- I just updated (in CVS) the comments in setup.py to reflect my current
build environment (which I just rebuilt in a VM)

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2010-10-30 09:40

Message:
I'm using the windows SDK version 6.1

is this incorrect ?  I was using this SDK together with VS2008 to
get the python build itself working.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-10-27 01:02

Message:
The problem seems to be that IProfAdmin isn't defined.  I  guess this will
have something to do with the windows sdk version being used - I can see
that interface defined in mapix.h, which should be included via
PyMAPIUtil.h.  You might need to grep your SDK dir to find where this is
defined, or try and diagnose why it isn't being included for you (eg, some
#define needed before including mapi, etc)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3094288&group_id=78018

Bugs item #3094288, was opened at 2010-10-24 17:57
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3094288&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: https://www.google.com/accounts ()
Assigned to: Nobody/Anonymous (nobody)
Summary: PyIProfAdmin.h(6) : error C2143: syntax error : missing ';'

Initial Comment:
I'm trying to build python for win using VS2008, python 2.7 on XP.

After going through some mapi issues, the compilation now fails with this
message.

Please find the complete trace attached

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2010-11-30 05:20

Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-16 21:07

Message:
works indeed with the Windows 7.1 sdk

Thx !

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 04:58

Message:
oops - I meant "2.6 or later"

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 04:53

Message:
Sorry for the delay - to build Python 2.6, try the Windows 7 SDK at
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b
- I just updated (in CVS) the comments in setup.py to reflect my current
build environment (which I just rebuilt in a VM)

----------------------------------------------------------------------

Comment By: https://www.google.com/accounts ()
Date: 2010-10-30 09:40

Message:
I'm using the windows SDK version 6.1

is this incorrect ?  I was using this SDK together with VS2008 to
get the python build itself working.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-10-27 01:02

Message:
The problem seems to be that IProfAdmin isn't defined.  I  guess this will
have something to do with the windows sdk version being used - I can see
that interface defined in mapix.h, which should be included via
PyMAPIUtil.h.  You might need to grep your SDK dir to find where this is
defined, or try and diagnose why it isn't being included for you (eg, some
#define needed before including mapi, etc)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3094288&group_id=78018

Bugs item #3107919, was opened at 2010-11-13 00:15
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3107919&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: gauthier fleutot (fleutotg)
Assigned to: Nobody/Anonymous (nobody)
Summary: install with mingw issue

Initial Comment:
I try installing pywin32-214 on a winXP-SP3 machine.
No visual studio 2003 installed.
setup.py install stops  with the following error:

error: Python was built with Visual Studio 2003;
extensions must be built with a compiler than can generate compatible binaries.
Visual Studio 2003 was not found on this system. If you have Cygwin installed,
you can try compiling with MingW32, by passing "-c mingw32" to setup.py.

Since I have mingw installed I tried:

setup.py build -c mingw32

The result is:
Building pywin32 2.5.214.0
running build
running build_py
running build_ext
Traceback (most recent call last):
  File "setup.py", line 2152, in <module>
    ('', ('pywin32.pth',)),
  File "C:\Program\python25\lib\distutils\core.py", line 151, in setup
    dist.run_commands()
  File "C:\Program\python25\lib\distutils\dist.py", line 974, in run_commands
    self.run_command(cmd)
  File "C:\Program\python25\lib\distutils\dist.py", line 994, in run_command
    cmd_obj.run()
  File "setup.py", line 596, in run
    build.run(self)
  File "C:\Program\python25\lib\distutils\command\build.py", line 112, in run
    self.run_command(cmd_name)
  File "C:\Program\python25\lib\distutils\cmd.py", line 333, in run_command
    self.distribution.run_command(command)
  File "C:\Program\python25\lib\distutils\dist.py", line 994, in run_command
    cmd_obj.run()
  File "C:\Program\python25\lib\distutils\command\build_ext.py", line 290, in ru
n
    self.build_extensions()
  File "setup.py", line 872, in build_extensions
    self.build_extension(ext)
  File "setup.py", line 1065, in build_extension
    why = self._why_cant_build_extension(ext)
  File "setup.py", line 760, in _why_cant_build_extension
    raise RuntimeError("Can't find a version in Windows.h")
RuntimeError: Can't find a version in Windows.h

I tried to define WINVER and _WIN32_WINNT in c:\MinGw\include\Windows.h, to 0x0502, but it did not help.
I read somewhere that there were a binary that can be used, but couldn't find it.

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2010-11-13 11:10

Message:
MingGW isn't supported and I've never even tried to use it for this - so
you can expect some problems - but I will accept any patches you can make
to fix it.

This particular problem can probably be moved on from by setting the env
var MSSDK=c:\mingw - but as mentioned, I expect other problems will follow
and you will probably need to determine those problems yourself.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3107919&group_id=78018

Bugs item #3107919, was opened at 2010-11-13 00:15
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3107919&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: gauthier fleutot (fleutotg)
Assigned to: Nobody/Anonymous (nobody)
Summary: install with mingw issue

Initial Comment:
I try installing pywin32-214 on a winXP-SP3 machine.
No visual studio 2003 installed.
setup.py install stops  with the following error:

error: Python was built with Visual Studio 2003;
extensions must be built with a compiler than can generate compatible binaries.
Visual Studio 2003 was not found on this system. If you have Cygwin installed,
you can try compiling with MingW32, by passing "-c mingw32" to setup.py.

Since I have mingw installed I tried:

setup.py build -c mingw32

The result is:
Building pywin32 2.5.214.0
running build
running build_py
running build_ext
Traceback (most recent call last):
  File "setup.py", line 2152, in <module>
    ('', ('pywin32.pth',)),
  File "C:\Program\python25\lib\distutils\core.py", line 151, in setup
    dist.run_commands()
  File "C:\Program\python25\lib\distutils\dist.py", line 974, in run_commands
    self.run_command(cmd)
  File "C:\Program\python25\lib\distutils\dist.py", line 994, in run_command
    cmd_obj.run()
  File "setup.py", line 596, in run
    build.run(self)
  File "C:\Program\python25\lib\distutils\command\build.py", line 112, in run
    self.run_command(cmd_name)
  File "C:\Program\python25\lib\distutils\cmd.py", line 333, in run_command
    self.distribution.run_command(command)
  File "C:\Program\python25\lib\distutils\dist.py", line 994, in run_command
    cmd_obj.run()
  File "C:\Program\python25\lib\distutils\command\build_ext.py", line 290, in ru
n
    self.build_extensions()
  File "setup.py", line 872, in build_extensions
    self.build_extension(ext)
  File "setup.py", line 1065, in build_extension
    why = self._why_cant_build_extension(ext)
  File "setup.py", line 760, in _why_cant_build_extension
    raise RuntimeError("Can't find a version in Windows.h")
RuntimeError: Can't find a version in Windows.h

I tried to define WINVER and _WIN32_WINNT in c:\MinGw\include\Windows.h, to 0x0502, but it did not help.
I read somewhere that there were a binary that can be used, but couldn't find it.

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2010-11-13 11:12

Message:
Oops - rereading I was wrong - the env var will not fix this issue.  You
will need to dig into setup.py to see how to make the version declarations
match.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-13 11:10

Message:
MingGW isn't supported and I've never even tried to use it for this - so
you can expect some problems - but I will accept any patches you can make
to fix it.

This particular problem can probably be moved on from by setting the env
var MSSDK=c:\mingw - but as mentioned, I expect other problems will follow
and you will probably need to determine those problems yourself.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3107919&group_id=78018

Bugs item #3107919, was opened at 2010-11-12 13:15
Message generated for change (Settings changed) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3107919&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: gauthier fleutot (fleutotg)
Assigned to: Nobody/Anonymous (nobody)
Summary: install with mingw issue

Initial Comment:
I try installing pywin32-214 on a winXP-SP3 machine.
No visual studio 2003 installed.
setup.py install stops  with the following error:

error: Python was built with Visual Studio 2003;
extensions must be built with a compiler than can generate compatible binaries.
Visual Studio 2003 was not found on this system. If you have Cygwin installed,
you can try compiling with MingW32, by passing "-c mingw32" to setup.py.

Since I have mingw installed I tried:

setup.py build -c mingw32

The result is:
Building pywin32 2.5.214.0
running build
running build_py
running build_ext
Traceback (most recent call last):
  File "setup.py", line 2152, in <module>
    ('', ('pywin32.pth',)),
  File "C:\Program\python25\lib\distutils\core.py", line 151, in setup
    dist.run_commands()
  File "C:\Program\python25\lib\distutils\dist.py", line 974, in run_commands
    self.run_command(cmd)
  File "C:\Program\python25\lib\distutils\dist.py", line 994, in run_command
    cmd_obj.run()
  File "setup.py", line 596, in run
    build.run(self)
  File "C:\Program\python25\lib\distutils\command\build.py", line 112, in run
    self.run_command(cmd_name)
  File "C:\Program\python25\lib\distutils\cmd.py", line 333, in run_command
    self.distribution.run_command(command)
  File "C:\Program\python25\lib\distutils\dist.py", line 994, in run_command
    cmd_obj.run()
  File "C:\Program\python25\lib\distutils\command\build_ext.py", line 290, in ru
n
    self.build_extensions()
  File "setup.py", line 872, in build_extensions
    self.build_extension(ext)
  File "setup.py", line 1065, in build_extension
    why = self._why_cant_build_extension(ext)
  File "setup.py", line 760, in _why_cant_build_extension
    raise RuntimeError("Can't find a version in Windows.h")
RuntimeError: Can't find a version in Windows.h

I tried to define WINVER and _WIN32_WINNT in c:\MinGw\include\Windows.h, to 0x0502, but it did not help.
I read somewhere that there were a binary that can be used, but couldn't find it.

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2010-11-27 00:20

Message:
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-13 00:12

Message:
Oops - rereading I was wrong - the env var will not fix this issue.  You
will need to dig into setup.py to see how to make the version declarations
match.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-13 00:10

Message:
MingGW isn't supported and I've never even tried to use it for this - so
you can expect some problems - but I will accept any patches you can make
to fix it.

This particular problem can probably be moved on from by setting the env
var MSSDK=c:\mingw - but as mentioned, I expect other problems will follow
and you will probably need to determine those problems yourself.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3107919&group_id=78018

Bugs item #3114713, was opened at 2010-11-21 18:51
Message generated for change (Comment added) made by muesliflyer
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3114713&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Andreas Lemke (muesliflyer)
Assigned to: Nobody/Anonymous (nobody)
Summary: error: command 'mc.exe' failed: No such file or directory

Initial Comment:
I am trying to install pywin32-214 on Win7-64bit. I installed Visual C++ 2008 (Microsoft Visual Studio 2008, Version 9.0.30729.1 SP, Microsoft .NET Framework Version 3.5 SP1)

Installation fails with this message:
---
python.exe setup.py install
...
building 'perfmondata' extension
creating build\temp.win32-2.7\Release\win32\src\perfmon
mc.exe -h win32\src\perfmon -r build\temp.win32-2.7\Relea
n32\src\perfmon\PyPerfMsgs.mc
error: command 'mc.exe' failed: No such file or directory
---

Now I read that VC++ 2008 does not contain mc.exe.
I am also puzzled that installing pywin32 causes it to be "built". Doesn't it come pre-built? Am I missing something?
What did I do wrong?

----------------------------------------------------------------------

>Comment By: Andreas Lemke (muesliflyer)
Date: 2010-11-21 19:06

Message:
Meanwhile, I discovered the windows installers and was able to install
pywin32 this way successfully.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3114713&group_id=78018

Bugs item #3114713, was opened at 2010-11-22 05:51
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3114713&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Private: No
Submitted By: Andreas Lemke (muesliflyer)
Assigned to: Nobody/Anonymous (nobody)
Summary: error: command 'mc.exe' failed: No such file or directory

Initial Comment:
I am trying to install pywin32-214 on Win7-64bit. I installed Visual C++ 2008 (Microsoft Visual Studio 2008, Version 9.0.30729.1 SP, Microsoft .NET Framework Version 3.5 SP1)

Installation fails with this message:
---
python.exe setup.py install
...
building 'perfmondata' extension
creating build\temp.win32-2.7\Release\win32\src\perfmon
mc.exe -h win32\src\perfmon -r build\temp.win32-2.7\Relea
n32\src\perfmon\PyPerfMsgs.mc
error: command 'mc.exe' failed: No such file or directory
---

Now I read that VC++ 2008 does not contain mc.exe.
I am also puzzled that installing pywin32 causes it to be "built". Doesn't it come pre-built? Am I missing something?
What did I do wrong?

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2010-11-22 09:16

Message:
Are you using the free edition of VS2008?  If so, you are correct that it
doesn't include mc.exe, but we do need it, meaning the free version isn't
suitable for building pywin32.  Please re-open if I've misunderstood.

----------------------------------------------------------------------

Comment By: Andreas Lemke (muesliflyer)
Date: 2010-11-22 06:06

Message:
Meanwhile, I discovered the windows installers and was able to install
pywin32 this way successfully.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3114713&group_id=78018

Bugs item #3092278, was opened at 2010-10-21 18:02
Message generated for change (Comment added) made by tw55413
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Paul Carroll (cameraguy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unresolved external symbol _CLSID_MachineDebugManager

Initial Comment:
Hi,

I've some (rather old) python scripts that I'm trying to get running on my 'new' computer.  In particular, the scripts make use of the Mr. Hammond's Win32 extensions, and my new machine is a Windows 7x64 box, using VS 2008.  I installed Python 2.7, and win32 build 214.  On my first attempt to install (setup.py -p install), I got a compilation error -- the one described in bug #3084013.  So, to resolve this error, I re-synced with the latest Win32 from CVS, and now when I attempt to install, it gets further but I then get the linker error "Unresolved external _CLISD_MachineDebugManager" when attempting to build axdebug.pyd

I tried both ehte x86 and x64 variants of the base python tool (v2.7) -- same result.

Any suggestions?  

Thanks

/Paul


----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-10 13:12

Message:
Same issue here, python 2.7, VS2008, windows sdk 7.1

----------------------------------------------------------------------

Comment By: stephane  (stephane42)
Date: 2010-11-01 13:32

Message:
I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Bugs item #3092278, was opened at 2010-10-21 18:02
Message generated for change (Comment added) made by tw55413
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Paul Carroll (cameraguy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unresolved external symbol _CLSID_MachineDebugManager

Initial Comment:
Hi,

I've some (rather old) python scripts that I'm trying to get running on my 'new' computer.  In particular, the scripts make use of the Mr. Hammond's Win32 extensions, and my new machine is a Windows 7x64 box, using VS 2008.  I installed Python 2.7, and win32 build 214.  On my first attempt to install (setup.py -p install), I got a compilation error -- the one described in bug #3084013.  So, to resolve this error, I re-synced with the latest Win32 from CVS, and now when I attempt to install, it gets further but I then get the linker error "Unresolved external _CLISD_MachineDebugManager" when attempting to build axdebug.pyd

I tried both ehte x86 and x64 variants of the base python tool (v2.7) -- same result.

Any suggestions?  

Thanks

/Paul


----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-10 13:39

Message:
this symbol seems to be located in pdm.dll, a dll includen with Internet
Explorer

no idea on how to link against it ??

----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-10 13:12

Message:
Same issue here, python 2.7, VS2008, windows sdk 7.1

----------------------------------------------------------------------

Comment By: stephane  (stephane42)
Date: 2010-11-01 13:32

Message:
I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Bugs item #3092278, was opened at 2010-10-22 05:02
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
>Status: Pending
>Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Paul Carroll (cameraguy)
Assigned to: Nobody/Anonymous (nobody)
Summary: Unresolved external symbol _CLSID_MachineDebugManager

Initial Comment:
Hi,

I've some (rather old) python scripts that I'm trying to get running on my 'new' computer.  In particular, the scripts make use of the Mr. Hammond's Win32 extensions, and my new machine is a Windows 7x64 box, using VS 2008.  I installed Python 2.7, and win32 build 214.  On my first attempt to install (setup.py -p install), I got a compilation error -- the one described in bug #3084013.  So, to resolve this error, I re-synced with the latest Win32 from CVS, and now when I attempt to install, it gets further but I then get the linker error "Unresolved external _CLISD_MachineDebugManager" when attempting to build axdebug.pyd

I tried both ehte x86 and x64 variants of the base python tool (v2.7) -- same result.

Any suggestions?  

Thanks

/Paul


----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 16:01

Message:
I can't reproduce this when using a later platform SDK - I've updated
setup.py to reflect a new build environment I just setup - for VS2008 I had
to use the Windows SDK for Windows 7 from
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b

----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-11 00:39

Message:
this symbol seems to be located in pdm.dll, a dll includen with Internet
Explorer

no idea on how to link against it ??

----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-11 00:12

Message:
Same issue here, python 2.7, VS2008, windows sdk 7.1

----------------------------------------------------------------------

Comment By: stephane  (stephane42)
Date: 2010-11-02 00:32

Message:
I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Bugs item #3092278, was opened at 2010-10-22 05:02
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
>Status: Open
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Paul Carroll (cameraguy)
>Assigned to: Mark Hammond (mhammond)
Summary: Unresolved external symbol _CLSID_MachineDebugManager

Initial Comment:
Hi,

I've some (rather old) python scripts that I'm trying to get running on my 'new' computer.  In particular, the scripts make use of the Mr. Hammond's Win32 extensions, and my new machine is a Windows 7x64 box, using VS 2008.  I installed Python 2.7, and win32 build 214.  On my first attempt to install (setup.py -p install), I got a compilation error -- the one described in bug #3084013.  So, to resolve this error, I re-synced with the latest Win32 from CVS, and now when I attempt to install, it gets further but I then get the linker error "Unresolved external _CLISD_MachineDebugManager" when attempting to build axdebug.pyd

I tried both ehte x86 and x64 variants of the base python tool (v2.7) -- same result.

Any suggestions?  

Thanks

/Paul


----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 17:38

Message:
Actually,, I spoke too soon - I don't get the problem using the sdk
included with vs2008 but do with the installed platform sdk I mentioned.  I
was confused by a combination of setup.py using an arbitrary installed SDK
and some cmd-prompts having the mssdk env var set and some not.  I'm trying
to work out a fix.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 16:01

Message:
I can't reproduce this when using a later platform SDK - I've updated
setup.py to reflect a new build environment I just setup - for VS2008 I had
to use the Windows SDK for Windows 7 from
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b

----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-11 00:39

Message:
this symbol seems to be located in pdm.dll, a dll includen with Internet
Explorer

no idea on how to link against it ??

----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-11 00:12

Message:
Same issue here, python 2.7, VS2008, windows sdk 7.1

----------------------------------------------------------------------

Comment By: stephane  (stephane42)
Date: 2010-11-02 00:32

Message:
I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Bugs item #3092278, was opened at 2010-10-22 05:02
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: installation
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Paul Carroll (cameraguy)
Assigned to: Mark Hammond (mhammond)
Summary: Unresolved external symbol _CLSID_MachineDebugManager

Initial Comment:
Hi,

I've some (rather old) python scripts that I'm trying to get running on my 'new' computer.  In particular, the scripts make use of the Mr. Hammond's Win32 extensions, and my new machine is a Windows 7x64 box, using VS 2008.  I installed Python 2.7, and win32 build 214.  On my first attempt to install (setup.py -p install), I got a compilation error -- the one described in bug #3084013.  So, to resolve this error, I re-synced with the latest Win32 from CVS, and now when I attempt to install, it gets further but I then get the linker error "Unresolved external _CLISD_MachineDebugManager" when attempting to build axdebug.pyd

I tried both ehte x86 and x64 variants of the base python tool (v2.7) -- same result.

Any suggestions?  

Thanks

/Paul


----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2010-11-17 16:25

Message:
I've checked in a fix for this.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 17:38

Message:
Actually,, I spoke too soon - I don't get the problem using the sdk
included with vs2008 but do with the installed platform sdk I mentioned.  I
was confused by a combination of setup.py using an arbitrary installed SDK
and some cmd-prompts having the mssdk env var set and some not.  I'm trying
to work out a fix.

----------------------------------------------------------------------

Comment By: Mark Hammond (mhammond)
Date: 2010-11-16 16:01

Message:
I can't reproduce this when using a later platform SDK - I've updated
setup.py to reflect a new build environment I just setup - for VS2008 I had
to use the Windows SDK for Windows 7 from
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6b6c21d2-2006-4afa-9702-529fa782d63b

----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-11 00:39

Message:
this symbol seems to be located in pdm.dll, a dll includen with Internet
Explorer

no idea on how to link against it ??

----------------------------------------------------------------------

Comment By: Erik Janssens (tw55413)
Date: 2010-11-11 00:12

Message:
Same issue here, python 2.7, VS2008, windows sdk 7.1

----------------------------------------------------------------------

Comment By: stephane  (stephane42)
Date: 2010-11-02 00:32

Message:
I have the same pb. I am using python 2.6.4 and VS2008 on Win7 x64.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3092278&group_id=78018

Bugs item #3102779, was opened at 2010-11-04 20:32
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3102779&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: com
Group: None
>Status: Closed
>Resolution: Out of Date
Priority: 5
Private: No
Submitted By: Docent ()
Assigned to: Nobody/Anonymous (nobody)
Summary: makepy created files fail on Python 3.1

Initial Comment:
Python 3.1, PyWin32-214, Windows XP Pro Sp3 32-bit, Excel 2007

The makepy generated files are not compatible with Python 3.
How to reproduce (For Excel 2007)

import win32com.client
import os, sys


try:
    win32com.client.gencache.EnsureModule('{00020813-0000-0000-C000-000000000046}', 0, 1, 6)

    xl = win32com.client.Dispatch("Excel.Application")
    xl.Visible = 1
    xl.DisplayAlerts = False
    wb = xl.Workbooks.Add()
    sh = wb.Sheets(1)
    print(str(sh.Cells(1,1)))

finally:
    xl.Quit()

-----------------
Result:

Traceback (most recent call last):
  File "test.py", line 13, in <module>
    print(str(sh.Cells(1,1)))
  File "C:\prog\Python31\lib\site-packages\win32com\gen_py\00020813-0000-0000-C0
00-000000000046x0x1x6.py", line 27028, in __str__
    return str(self.__unicode__(*args))
  File "C:\prog\Python31\lib\site-packages\win32com\gen_py\00020813-0000-0000-C0
00-000000000046x0x1x6.py", line 27024, in __unicode__
    return unicode(self.__call__(*args))
NameError: global name 'unicode' is not defined



----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2010-11-12 14:58

Message:
Thanks for the report, but this was fixed in r1.67 of genpy.py - it will
appear in the next pywin32 release.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3102779&group_id=78018

Bugs item #3102414, was opened at 2010-11-04 06:12
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3102414&group_id=78018

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: com
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Private: No
Submitted By: Gregory Petrosyan (gregory_p)
Assigned to: Nobody/Anonymous (nobody)
Summary: Script that works from PythonWin does not work from python

Initial Comment:
I've encountered a strange issue: script like this:

import win32com.client
w = win32com.client.Dispatch('WMPlayer.OCX.7')
t = w.newMedia('C:/test.wma')
w.currentMedia = t

when launched from python.exe, does nothing (without any exceptions etc.); when launched from PythonWin, sound is produced. Also, if I try to use WMPlayer.OCX.7 to play audio CD, then it *does* spin up when launched from python.exe, but no sound is produced again. From PythonWin, everything works as expected.

(I should clarify, this is not the sound output issue: w.playState property does end up being different in these 2 scenarios!)

What can be the difference between PythonWin and python.exe that causes this strange bug?

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2010-11-12 13:56

Message:
Pythonwin is built on MFC and therefore gets support for COM "controls" (or
OCX) for free.  python.exe hosted would need this support explicitly added
using a fair bit of COM magic - a tutorial on hosting controls from any
language might get you going.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3102414&group_id=78018