pywin32-bugs Mailing List for Python for Windows Extensions (Page 27)
OLD project page for the Python extensions for Windows
Brought to you by:
mhammond
Menu
▾
▴
pywin32-bugs — Automated tracker notifications (not for bug reports!)
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
(24) |
May
(19) |
Jun
(15) |
Jul
(43) |
Aug
(39) |
Sep
(25) |
Oct
(43) |
Nov
(19) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(21) |
Feb
(18) |
Mar
(14) |
Apr
(80) |
May
(56) |
Jun
(24) |
Jul
(30) |
Aug
(17) |
Sep
(36) |
Oct
(106) |
Nov
(38) |
Dec
(30) |
| 2005 |
Jan
(14) |
Feb
(14) |
Mar
(48) |
Apr
(28) |
May
(49) |
Jun
(23) |
Jul
(9) |
Aug
(13) |
Sep
(28) |
Oct
(21) |
Nov
(8) |
Dec
(26) |
| 2006 |
Jan
(56) |
Feb
(33) |
Mar
(33) |
Apr
(18) |
May
(16) |
Jun
(9) |
Jul
(24) |
Aug
(16) |
Sep
(14) |
Oct
(37) |
Nov
(38) |
Dec
(22) |
| 2007 |
Jan
(7) |
Feb
(16) |
Mar
(11) |
Apr
(15) |
May
(15) |
Jun
(8) |
Jul
(24) |
Aug
(26) |
Sep
(18) |
Oct
(11) |
Nov
(20) |
Dec
(1) |
| 2008 |
Jan
(19) |
Feb
(55) |
Mar
(7) |
Apr
(35) |
May
(66) |
Jun
(38) |
Jul
(26) |
Aug
(5) |
Sep
(25) |
Oct
(25) |
Nov
(18) |
Dec
(18) |
| 2009 |
Jan
(25) |
Feb
(38) |
Mar
(29) |
Apr
(25) |
May
(5) |
Jun
(11) |
Jul
(16) |
Aug
(16) |
Sep
(16) |
Oct
(1) |
Nov
(15) |
Dec
(33) |
| 2010 |
Jan
(13) |
Feb
(11) |
Mar
(1) |
Apr
(24) |
May
(26) |
Jun
(19) |
Jul
(22) |
Aug
(51) |
Sep
(38) |
Oct
(39) |
Nov
(25) |
Dec
(27) |
| 2011 |
Jan
(40) |
Feb
(31) |
Mar
(21) |
Apr
(42) |
May
(11) |
Jun
(16) |
Jul
(20) |
Aug
(14) |
Sep
(6) |
Oct
(8) |
Nov
(34) |
Dec
(7) |
| 2012 |
Jan
(60) |
Feb
(24) |
Mar
(6) |
Apr
(28) |
May
(41) |
Jun
(15) |
Jul
(14) |
Aug
(25) |
Sep
(30) |
Oct
(18) |
Nov
(30) |
Dec
(9) |
| 2013 |
Jan
(3) |
Feb
(8) |
Mar
(17) |
Apr
(23) |
May
(34) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2010-12-15 23:48:48
|
Bugs item #3137807, was opened at 2010-12-15 22:13 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&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: pythonwin Group: None Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Greg Hazel (ghazel) Assigned to: Nobody/Anonymous (nobody) Summary: Pythonwin can't open a file with # -*- encoding: binary -*- Initial Comment: If a file starts with "# -*- encoding: binary -*-", Pythonwin cannot seem to open it. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-12-16 10:48 Message: Yeah - I guess it is reasonable that in the case of an unknown encoding pythonwin should print a warning and treat it as latin-1 (the default) instead of dumping an exception.. ---------------------------------------------------------------------- Comment By: Greg Hazel (ghazel) Date: 2010-12-16 10:40 Message: Well, I'm not the original author of any files I've encountered with this preamble, so I can't say why it was chosen, nor can I use something different to start with. However, I believe the author's intention, and certainly a reasonable approach, would be to treat binary encoding like 8bit ascii, which I assume is the same as you would treat it if there was no encoding specified at all. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-12-16 10:24 Message: Hrm - pep 263 which defines this behaviour says the encoding must be "known" and my tests demonstrate python itself refuses to work with such files. It is hard to justify a special case for the string "binary" - can't you just use latin-1 or similar to achieve the same result? The issue is pythonwin uses that encoding to determine how to translate the bytes into characters... ---------------------------------------------------------------------- Comment By: Greg Hazel (ghazel) Date: 2010-12-16 08:49 Message: I have run in to this with several source files, which were some reason marked with that preamble but otherwise perfectly editable. Also, I can open notepad.exe in pythonwin just fine. I'm not expecting pythonwin to work miracles and let me edit binary data correctly, I just think it should let me open files no matter what they say at the beginning (like notepad.exe opens just fine). Otherwise, I have to open the file with Wordpad, strip the preamble, then open with Pythonwin (and remember to put it back later). Very troublesome. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-12-16 06:43 Message: pythonwin only supports editing text and without a text based encoding it can't do much. If the problem is that the error message is unclear I can look at fixing that, but will not enable actual editing of the file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-15 23:40:50
|
Bugs item #3137807, was opened at 2010-12-15 11:13 Message generated for change (Comment added) made by ghazel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&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: pythonwin Group: None Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: Greg Hazel (ghazel) Assigned to: Nobody/Anonymous (nobody) Summary: Pythonwin can't open a file with # -*- encoding: binary -*- Initial Comment: If a file starts with "# -*- encoding: binary -*-", Pythonwin cannot seem to open it. ---------------------------------------------------------------------- >Comment By: Greg Hazel (ghazel) Date: 2010-12-15 23:40 Message: Well, I'm not the original author of any files I've encountered with this preamble, so I can't say why it was chosen, nor can I use something different to start with. However, I believe the author's intention, and certainly a reasonable approach, would be to treat binary encoding like 8bit ascii, which I assume is the same as you would treat it if there was no encoding specified at all. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-12-15 23:24 Message: Hrm - pep 263 which defines this behaviour says the encoding must be "known" and my tests demonstrate python itself refuses to work with such files. It is hard to justify a special case for the string "binary" - can't you just use latin-1 or similar to achieve the same result? The issue is pythonwin uses that encoding to determine how to translate the bytes into characters... ---------------------------------------------------------------------- Comment By: Greg Hazel (ghazel) Date: 2010-12-15 21:49 Message: I have run in to this with several source files, which were some reason marked with that preamble but otherwise perfectly editable. Also, I can open notepad.exe in pythonwin just fine. I'm not expecting pythonwin to work miracles and let me edit binary data correctly, I just think it should let me open files no matter what they say at the beginning (like notepad.exe opens just fine). Otherwise, I have to open the file with Wordpad, strip the preamble, then open with Pythonwin (and remember to put it back later). Very troublesome. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-12-15 19:43 Message: pythonwin only supports editing text and without a text based encoding it can't do much. If the problem is that the error message is unclear I can look at fixing that, but will not enable actual editing of the file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-15 23:24:17
|
Bugs item #3137807, was opened at 2010-12-15 22:13 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&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: pythonwin Group: None Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: Greg Hazel (ghazel) Assigned to: Nobody/Anonymous (nobody) Summary: Pythonwin can't open a file with # -*- encoding: binary -*- Initial Comment: If a file starts with "# -*- encoding: binary -*-", Pythonwin cannot seem to open it. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-12-16 10:24 Message: Hrm - pep 263 which defines this behaviour says the encoding must be "known" and my tests demonstrate python itself refuses to work with such files. It is hard to justify a special case for the string "binary" - can't you just use latin-1 or similar to achieve the same result? The issue is pythonwin uses that encoding to determine how to translate the bytes into characters... ---------------------------------------------------------------------- Comment By: Greg Hazel (ghazel) Date: 2010-12-16 08:49 Message: I have run in to this with several source files, which were some reason marked with that preamble but otherwise perfectly editable. Also, I can open notepad.exe in pythonwin just fine. I'm not expecting pythonwin to work miracles and let me edit binary data correctly, I just think it should let me open files no matter what they say at the beginning (like notepad.exe opens just fine). Otherwise, I have to open the file with Wordpad, strip the preamble, then open with Pythonwin (and remember to put it back later). Very troublesome. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-12-16 06:43 Message: pythonwin only supports editing text and without a text based encoding it can't do much. If the problem is that the error message is unclear I can look at fixing that, but will not enable actual editing of the file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-15 21:49:19
|
Bugs item #3137807, was opened at 2010-12-15 11:13 Message generated for change (Comment added) made by ghazel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&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: pythonwin Group: None >Status: Open Resolution: Wont Fix Priority: 5 Private: No Submitted By: Greg Hazel (ghazel) Assigned to: Nobody/Anonymous (nobody) Summary: Pythonwin can't open a file with # -*- encoding: binary -*- Initial Comment: If a file starts with "# -*- encoding: binary -*-", Pythonwin cannot seem to open it. ---------------------------------------------------------------------- >Comment By: Greg Hazel (ghazel) Date: 2010-12-15 21:49 Message: I have run in to this with several source files, which were some reason marked with that preamble but otherwise perfectly editable. Also, I can open notepad.exe in pythonwin just fine. I'm not expecting pythonwin to work miracles and let me edit binary data correctly, I just think it should let me open files no matter what they say at the beginning (like notepad.exe opens just fine). Otherwise, I have to open the file with Wordpad, strip the preamble, then open with Pythonwin (and remember to put it back later). Very troublesome. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-12-15 19:43 Message: pythonwin only supports editing text and without a text based encoding it can't do much. If the problem is that the error message is unclear I can look at fixing that, but will not enable actual editing of the file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-15 19:43:09
|
Bugs item #3137807, was opened at 2010-12-15 22:13 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&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: pythonwin Group: None >Status: Pending >Resolution: Wont Fix Priority: 5 Private: No Submitted By: Greg Hazel (ghazel) Assigned to: Nobody/Anonymous (nobody) Summary: Pythonwin can't open a file with # -*- encoding: binary -*- Initial Comment: If a file starts with "# -*- encoding: binary -*-", Pythonwin cannot seem to open it. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-12-16 06:43 Message: pythonwin only supports editing text and without a text based encoding it can't do much. If the problem is that the error message is unclear I can look at fixing that, but will not enable actual editing of the file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-15 11:13:36
|
Bugs item #3137807, was opened at 2010-12-15 11:13 Message generated for change (Tracker Item Submitted) made by ghazel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&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: pythonwin Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Greg Hazel (ghazel) Assigned to: Nobody/Anonymous (nobody) Summary: Pythonwin can't open a file with # -*- encoding: binary -*- Initial Comment: If a file starts with "# -*- encoding: binary -*-", Pythonwin cannot seem to open it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3137807&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-13 20:09:27
|
Patches item #3136751, was opened at 2010-12-13 21:09 Message generated for change (Tracker Item Submitted) made by zseil You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3136751&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: Ziga Seilnacht (zseil) Assigned to: Nobody/Anonymous (nobody) Summary: All BOOLAPI_NL functions in win32event swallow errors Initial Comment: SetEvent, ResetEvent, ReleaseMutex and SetWaitableTimer can still fail even after their handle argument has been validated (e.g. if the handle is closed or if it is a handle to a different object than the one expected by the function). The attached patch simply removes the BOOLAPI_NL and replaces it with error checking BOOLAPI. Tests are also included. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=3136751&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-11 00:43:10
|
Bugs item #3134684, was opened at 2010-12-11 11:24 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3134684&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: Tom Anderson (twocsies) Assigned to: Nobody/Anonymous (nobody) Summary: Can't install Python for Windows extensions Initial Comment: I'm on Windows 7. I just installed Python3.1 and now I'm trying to install pywin32-214 because it's a dependency for OpenNI. I navigated to the directory pywin32-214\pywin32-214 and ran this command: python setup.py -q install and then I got the error: File "setup.py", line 106 print msg % args SyntaxError: invalid syntax ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2010-12-11 11:43 Message: If you really want to install from sources, try setup3.py instead of setup.py - but you probably just want the binary builds - try "View all Files" button and grab the 3.1 installer executable. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3134684&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-11 00:24:41
|
Bugs item #3134684, was opened at 2010-12-11 10:54 Message generated for change (Tracker Item Submitted) made by twocsies You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3134684&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: Tom Anderson (twocsies) Assigned to: Nobody/Anonymous (nobody) Summary: Can't install Python for Windows extensions Initial Comment: I'm on Windows 7. I just installed Python3.1 and now I'm trying to install pywin32-214 because it's a dependency for OpenNI. I navigated to the directory pywin32-214\pywin32-214 and ran this command: python setup.py -q install and then I got the error: File "setup.py", line 106 print msg % args SyntaxError: invalid syntax ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3134684&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-07 08:33:29
|
Bugs item #3092278, was opened at 2010-10-21 22:02 Message generated for change (Comment added) made by mikhailedoshin 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: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-07 11:33 Message: As a matter of a fact, yes, I had not used the most recent version from the CVS repository (I didn't realize that the comments are sorted in reversed chronological order, so I thought that "I spoke too soon" came after "I've checked in a fix" :) . Once I exported the most recent version, the problem went away, so please disregard my comment. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-12-07 00:44 Message: To the people still reporting problems here: have you updated to the current CVS trunk, and have you read and followed the updated instructions in setup.py? ---------------------------------------------------------------------- Comment By: Ricardo Nuno Almeida (nitro-12) Date: 2010-12-06 11:30 Message: Reproduced the issue as well. Python 2.7, Win 7 x64, VS2010. Tried installing windows sdk7 afterwards or building using MingW. no success. ---------------------------------------------------------------------- Comment By: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-04 04:33 Message: I encountered the same problem; Win XP, VS 2008, MS SDK 7.0, Python 2.7. I'm trying to compile build 214, except for the win32job.i file, which I upgraded to v1.7 according to #3084013. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-17 08:25 Message: I've checked in a fix for this. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 09: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 08: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-10 16: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 16:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-01 16: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 |
|
From: SourceForge.net <no...@so...> - 2010-12-06 21:44:58
|
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-12-07 08:44 Message: To the people still reporting problems here: have you updated to the current CVS trunk, and have you read and followed the updated instructions in setup.py? ---------------------------------------------------------------------- Comment By: Ricardo Nuno Almeida (nitro-12) Date: 2010-12-06 19:30 Message: Reproduced the issue as well. Python 2.7, Win 7 x64, VS2010. Tried installing windows sdk7 afterwards or building using MingW. no success. ---------------------------------------------------------------------- Comment By: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-04 12:33 Message: I encountered the same problem; Win XP, VS 2008, MS SDK 7.0, Python 2.7. I'm trying to compile build 214, except for the win32job.i file, which I upgraded to v1.7 according to #3084013. ---------------------------------------------------------------------- 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 |
|
From: SourceForge.net <no...@so...> - 2010-12-06 19:13:19
|
Bugs item #3130627, was opened at 2010-12-06 11:13 Message generated for change (Tracker Item Submitted) made by cjgohlke You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3130627&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: Christoph Gohlke (cjgohlke) Assigned to: Nobody/Anonymous (nobody) Summary: build fails with Python3.2b1 Initial Comment: Using current pywin32 sources from CVS and Python 3.2b1 binaries from python.org, the build fails with the following error: win32\src\PyUnicode.cpp(258) : error C2664: 'PyUnicodeUCS2_AsWideChar' : cannot convert parameter 1 from 'PyUnicodeObject *' to 'PyObject *' Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast Same for win32\src\win32consolemodule.cpp, line 112. This is related to Python changeset r85298 <http://svn.python.org/view?view=rev&revision=85298>: PyUnicode_AsWideCharString() takes a PyObject*, not a PyUnicodeObject* All unicode functions uses PyObject* except PyUnicode_AsWideChar(). Fix the prototype for the new function PyUnicode_AsWideCharString(). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3130627&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-06 11:43:51
|
Bugs item #2905909, was opened at 2009-11-30 11:10 Message generated for change (Comment added) made by chaoskcw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2905909&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: pythonwin Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) Summary: assert sys.modules[modname] is old_mod error in pywintypes Initial Comment: When running Apache+Mod Python (Python 2.4), I was getting this error - [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] Traceback (most recent call last): [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "C:\\Python24\\Lib\\site-packages\\mod_python\\importer.py", line 1537, in HandlerDispatch\n default=default_handler, arg=req, silent=hlist.silent) [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "C:\\Python24\\Lib\\site-packages\\mod_python\\importer.py", line 1229, in _process_target\n result = _execute_target(config, req, object, arg) [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "C:\\Python24\\Lib\\site-packages\\mod_python\\importer.py", line 1128, in _execute_target\n result = object(arg) [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\core\\handlers\\modpython.py", line 228, in handler\n return ModPythonHandler()(req) [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\core\\handlers\\modpython.py", line 201, in __call__\n response = self.get_response(request) [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\core\\handlers\\base.py", line 73, in get_response\n response = middleware_method(request) [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\contrib\\sessions\\middleware.py", line 10, in process_request\n engine = import_module(settings.SESSION_ENGINE) [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\utils\\importlib.py", line 35, in import_module\n __import__(name) [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\contrib\\sessions\\backends\\db.py", line 2, in ?\n from django.contrib.sessions.models import Session [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\contrib\\sessions\\models.py", line 4, in ?\n from django.db import models [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\db\\models\\__init__.py", line 12, in ?\n from django.db.models.fields.files import FileField, ImageField [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\db\\models\\fields\\files.py", line 8, in ?\n from django.core.files.storage import default_storage [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\core\\files\\storage.py", line 7, in ?\n from django.core.files import locks, File [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "c:\\python24\\Lib\\site-packages\\django\\core\\files\\locks.py", line 25, in ?\n import pywintypes [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "C:\\Python24\\Lib\\site-packages\\win32\\lib\\pywintypes.py", line 124, in ?\n __import_pywin32_system_module__("pywintypes", globals()) [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] File "C:\\Python24\\Lib\\site-packages\\win32\\lib\\pywintypes.py", line 114, in __import_pywin32_system_module__\n assert sys.modules[modname] is old_mod [Mon Nov 30 15:13:50 2009] [error] [client 127.0.0.1] AssertionError With PythonDebug = On, assert took effect. I removed it and it worked without any issues. I found that another user - <a href="http://markmail.org/message/hqnf6obaillzspxj#query:assert%20sys.modules[modname]%20is%20old_mod+page:1+mid:nahkqunchycwqtd4+state:results">here</a> also has the same issue. He solved it by going back a version. ---------------------------------------------------------------------- Comment By: ChaosKCW (chaoskcw) Date: 2010-12-06 11:43 Message: Hi, I am experiencing this issue as well, are there any solutions? ---------------------------------------------------------------------- Comment By: Ian Rolfe (slothie2) Date: 2010-04-27 15:11 Message: I "got this working" by just commenting out the 2 asserts and replacing them with a 'pass' I put some debugs in, it seems that the same module is being used, but different instances: [Tue Apr 27 15:49:31 2010] [error] C:\\Python26\\lib\\site-packages\\MySQLdb\\__init__.py:34: DeprecationWarning: the sets module is deprecated [Tue Apr 27 15:49:31 2010] [error] from sets import ImmutableSet [Tue Apr 27 15:49:31 2010] [error] Version is < 3 [Tue Apr 27 15:49:31 2010] [error] sys.modules = <module 'pywintypes' from 'C:\\Windows\\system32\\pywintypes26.dll'> id=50175152 file=C:\\Windows\\system32\\pywintypes26.dll [Tue Apr 27 15:49:31 2010] [error] mod = <module 'pywintypes' from 'C:\\Windows\\system32\\pywintypes26.dll'> id=50175152 file=C:\\Windows\\system32\\pywintypes26.dll [Tue Apr 27 15:49:31 2010] [error] old_mod = <module 'pywintypes' from 'C:\\Windows\\system32\\pywintypes26.dll'> id=50175152 file=C:\\Windows\\system32\\pywintypes26.dll [Tue Apr 27 15:49:34 2010] [error] [client 127.0.0.1] File does not exist: C:/Program Files/Apache Software Foundation/Apache2.2/htdocs/san/media/css/san.css, referer: http://localhost/san/letters/ [Tue Apr 27 15:53:57 2010] [error] C:\\Python26\\lib\\site-packages\\MySQLdb\\__init__.py:34: DeprecationWarning: the sets module is deprecated [Tue Apr 27 15:53:57 2010] [error] from sets import ImmutableSet [Tue Apr 27 15:53:57 2010] [error] Version is < 3 [Tue Apr 27 15:53:57 2010] [error] sys.modules = <module 'pywintypes' from 'C:\\Windows\\system32\\pywintypes26.dll'> id=50175152 file=C:\\Windows\\system32\\pywintypes26.dll [Tue Apr 27 15:53:57 2010] [error] mod = <module 'pywintypes' from 'C:\\Windows\\system32\\pywintypes26.dll'> id=61248048 file=C:\\Windows\\system32\\pywintypes26.dll [Tue Apr 27 15:53:57 2010] [error] old_mod = <module 'pywintypes' from 'C:\\Windows\\system32\\pywintypes26.dll'> id=61248048 file=C:\\Windows\\system32\\pywintypes26.dll Note that the 1st request was OK but the second had a different instance of the same dll. Is this likely to cause problems? ---------------------------------------------------------------------- Comment By: Steve McCusker (stevemccusker) Date: 2009-12-11 03:10 Message: I have just come across this problem. I am using Apache 2.2, Django 1.1, Python 2.6.2 and mod_wsgi (mod_wsgi-win32-ap22py26-2.5.so) on Win XP Pro (SP3). It allworked fine until PayPal POSTed a notification. This was , of course, from a different IP address from the previous GETs and POSTs. It caused the above error. After I read this bug report I simple commented out the two Assert statements and it then seemed to work OK. I did do a debug dump from pywintypes just before the assert statements just using the python unicode() function on the two modules (old_mod and mod) and they looked the same from that. Changing back to the older version as reported above did not help. Cheers Steve McCusker ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2009-11-30 23:25 Message: My concern is that assertion may be indicating pywintypesxx.dll has been loaded twice by the process, causing subtle problems with the types. It would be interesting to know what the __file__ attribute is on the 2 objects. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2905909&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-12-06 08:30:56
|
Bugs item #3092278, was opened at 2010-10-21 18:02 Message generated for change (Comment added) made by nitro-12 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: Ricardo Nuno Almeida (nitro-12) Date: 2010-12-06 08:30 Message: Reproduced the issue as well. Python 2.7, Win 7 x64, VS2010. Tried installing windows sdk7 afterwards or building using MingW. no success. ---------------------------------------------------------------------- Comment By: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-04 01:33 Message: I encountered the same problem; Win XP, VS 2008, MS SDK 7.0, Python 2.7. I'm trying to compile build 214, except for the win32job.i file, which I upgraded to v1.7 according to #3084013. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-17 05:25 Message: I've checked in a fix for this. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 06: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 05: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-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 |
|
From: SourceForge.net <no...@so...> - 2010-12-04 01:33:06
|
Bugs item #3092278, was opened at 2010-10-21 22:02 Message generated for change (Comment added) made by mikhailedoshin 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: Mikhail Edoshin (mikhailedoshin) Date: 2010-12-04 04:33 Message: I encountered the same problem; Win XP, VS 2008, MS SDK 7.0, Python 2.7. I'm trying to compile build 214, except for the win32job.i file, which I upgraded to v1.7 according to #3084013. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-17 08:25 Message: I've checked in a fix for this. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2010-11-16 09: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 08: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-10 16: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 16:12 Message: Same issue here, python 2.7, VS2008, windows sdk 7.1 ---------------------------------------------------------------------- Comment By: stephane (stephane42) Date: 2010-11-01 16: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 |
|
From: SourceForge.net <no...@so...> - 2010-11-30 05:20:05
|
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 |
|
From: SourceForge.net <no...@so...> - 2010-11-30 05:20:04
|
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 |
|
From: SourceForge.net <no...@so...> - 2010-11-27 00:20:05
|
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 |
|
From: SourceForge.net <no...@so...> - 2010-11-21 22:16:50
|
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 |
|
From: SourceForge.net <no...@so...> - 2010-11-21 19:06:46
|
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 |
|
From: SourceForge.net <no...@so...> - 2010-11-21 18:51:52
|
Bugs item #3114713, was opened at 2010-11-21 18:51 Message generated for change (Tracker Item Submitted) 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? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=3114713&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2010-11-17 05:25:48
|
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 |
|
From: SourceForge.net <no...@so...> - 2010-11-16 21:07:44
|
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 |
|
From: SourceForge.net <no...@so...> - 2010-11-16 06:38:58
|
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 |
|
From: SourceForge.net <no...@so...> - 2010-11-16 05:03:58
|
Bugs item #3075086, was opened at 2010-09-25 05:55 Message generated for change (Comment added) made by mhammond 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: Pending >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: Mark Hammond (mhammond) Date: 2010-11-16 16: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 16: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 |
2 messages has been excluded from this view by a project administrator.
