pywin32-bugs Mailing List for Python for Windows Extensions (Page 115)
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...> - 2003-08-13 11:22:55
|
Bugs item #787974, was opened at 2003-08-13 11:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=787974&group_id=78018 Category: win32 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ian Parker (ianparker) Assigned to: Nobody/Anonymous (nobody) Summary: PyGetCounterInfo() fails on XP Initial Comment: PyGetCounterInfo() in win32pdh needs the same fix as previously made to PyEnumObjectItems(). The return from the call to pPdhGetCounterInfo to obtain the buffer size is PDH_MORE_DATA on XP instead of zero. Are ther any more call with this problem? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=787974&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-12 20:33:18
|
Bugs item #787563, was opened at 2003-08-12 19:59 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=787563&group_id=78018 Category: win32 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Dietmar Schwertberger (dschwertberger) Assigned to: Nobody/Anonymous (nobody) Summary: fatal error with taskbar Initial Comment: e.g. with demos\win32gui_taskbar.py: Fatal Python error: This thread state must be current when releasing Python 2.3; win32all versions 1.55 and 1.57; Windows 2000 OK with 2.2; 1.48; Windows 98 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=787563&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-11 07:24:46
|
Bugs item #784962, was opened at 2003-08-07 12:13 Message generated for change (Comment added) made by geary You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 Category: None Group: None Status: Open Resolution: Works For Me Priority: 5 Submitted By: John J Smith (johnjsmith) Assigned to: Nobody/Anonymous (nobody) Summary: Installation crash in recent win32all's. Initial Comment: The win32all installer has been crashing on me for the last few win32all releases. This has happened for Python 2.2.3 with win32all-156 and Python 2.3 with win32all-157. It has also happened for some previous win32all releases (such as 153 and 155 with Python 2.3). The error occurs during the `Completing Installation' stage, when the message box says `Registering COM Server AXScript Engine'. The error message is the usual `This program has performed an illegal operation and will be shut down' message. Pressing the `Details' button gives: WIN32ALL-156 caused an invalid page fault in module MSVCRT.DLL at 016f:7800b936. Registers: EAX=006b61a0 CS=016f EIP=7800b936 EFLGS=00010202 EBX=00000000 SS=0177 ESP=0063cad4 EBP=0063caf0 ECX=00000120 DS=0177 ESI=01ddab0c FS=3fb7 EDX=00000000 ES=0177 EDI=00000013 GS=0000 Bytes at CS:EIP: 89 5a 04 8b 55 0c 89 4d fc 8b 5a 04 8b 52 08 89 Stack dump: 00760840 01ddab10 00000001 006b8930 00000000 000004d0 00000120 0063cb34 7800b30c 0075005c 01ddac2c 00760840 00000000 00000001 bff813f8 81d52568 (This is with Python 2.2.3 and win32all-156.) This has happened on both WinXP and Win98SE. Once this happens, the win32all uninstaller doesn't work (says `can't find install.log'). If Python is installed with the `Non-Admin' option, then win32all installs fine (presumably because it never reaches the `Registering COM Server AXScript Engine' stage). I haven't seen anyone else report this, so looks like I'm the only one. Any help is greatly appreciated. ---------------------------------------------------------------------- Comment By: Michael Geary (geary) Date: 2003-08-11 00:24 Message: Logged In: YES user_id=114596 I see a very similar crash when installing win32all-154 on a Python 2.2.2 installation. This is on a clean Windows XP virtual machine with nothing but VS.NET 2003 installed. If I install Python 2.2.2 on this VM and then install win32all-154, it crashes. If I then run the pyscript.py, that succeeds. After reverting the VM, if I install Python 2.2.2 and then install win32all-152, it succeeds. If I then install win32all-154 (letting it uninstall 152), this also succeeds. So the crash happens only when installing 154 without having previously installed 152. The crash is an access violation writing to location 0. Here is the stack trace (with apologies for its length): ntdll.dll!77f57e4f() ntdll.dll!77f93a50() ntdll.dll!77f93a50() ntdll.dll!77f57cf7() ntdll.dll!77f588f5() ntdll.dll!77f93a73() ntdll.dll!77f5be44() kernel32.dll!77e78bf1() kernel32.dll!77e78c14() kernel32.dll!77e78c14() msvcrt.dll!77c2ac14() msvcrt.dll!77c2ac2a() msvcrt.dll!77c2ac55() python22.dll!1e04f836() python22.dll!1e052b2d() python22.dll!1e052963() python22.dll!1e05306b() python22.dll!1e052ef3() python22.dll!1e05e84b() python22.dll!1e05e886() python22.dll!1e040f66() python22.dll!1e040d92() ntdll.dll!77f58ec1() msvcrt.dll!77c2ab2e() msvcrt.dll!77c2ab33() msvcrt.dll!77c2ab33() python22.dll!1e040ab3() python22.dll!1e04025b() ntdll.dll!77f588f5() python22.dll!1e03afdb() ntdll.dll!77f58ec1() msvcrt.dll!77c2ab2e() msvcrt.dll!77c2ab33() python22.dll!1e02f9ab() msvcrt.dll!77c2ab33() python22.dll!1e04f9eb() python22.dll!1e03fe16() python22.dll!1e03fe4c() python22.dll!1e03fac6() ntdll.dll!77f93a73() ntdll.dll!77f58a7e() ntdll.dll!77f58ec1() python22.dll!1e016137() python22.dll!1e015e89() python22.dll!1e03a90f() python22.dll!1e03f98f() python22.dll!1e00d2f8() python22.dll!1e04d469() python22.dll!1e006ccc() python22.dll!1e014977() python22.dll!1e012879() python22.dll!1e01376f() python22.dll!1e013e2f() python22.dll!1e0109f2() python22.dll!1e03f701() python22.dll!1e040ddc() python22.dll!1e02fc88() python22.dll!1e02fc88() python22.dll!1e051151() python22.dll!1e050dcb() python22.dll!1e040ab3() python22.dll!1e04025b() python22.dll!1e03afdb() python22.dll!1e03ac39() ntdll.dll!77f8d98c() msvcrt.dll!77c2af77() ntdll.dll!77f83367() python22.dll!1e03fe16() python22.dll!1e03fb04() user32.dll!77d48fb4() ntdll.dll!77f93a73() ntdll.dll!77f58a7e() ntdll.dll!77f58ec1() python22.dll!1e04d469() python22.dll!1e072ae1() python22.dll!1e072b09() python22.dll!1e072d2b() python22.dll!1e01349d() python22.dll!1e072ac9() python22.dll!1e072b09() python22.dll!1e072d2b() python22.dll!1e03f98f() python22.dll!1e00d2f8() python22.dll!1e04d469() python22.dll!1e012c54() python22.dll!1e01376f() python22.dll!1e013e2f() python22.dll!1e039390() python22.dll!1e006ccc() python22.dll!1e014977() python22.dll!1e00d427() python22.dll!1e04d469() python22.dll!1e012c54() python22.dll!1e01376f() python22.dll!1e013e2f() python22.dll!1e039390() python22.dll!1e006ccc() python22.dll!1e014977() python22.dll!1e00d427() python22.dll!1e04d469() python22.dll!1e012c54() python22.dll!1e01376f() python22.dll!1e013e2f() python22.dll!1e014c14() python22.dll!1e012d1a() python22.dll!1e01376f() python22.dll!1e013e2f() python22.dll!1e039390() python22.dll!1e006ccc() python22.dll!1e014977() python22.dll!1e006ca1() PyWise22.dll!00a91bd8() -Mike ---------------------------------------------------------------------- Comment By: John J Smith (johnjsmith) Date: 2003-08-08 03:12 Message: Logged In: YES user_id=830565 Okay, here is some more info. This sequence on a newly installed Win98SE works: Install Python 2.2.3 Install win32all-152 This sequence on a newly installed Win98SE crashes: Install Python 2.2.3 Install win32all-154 This sequence on a newly installed Win98SE *works*: Install Python 2.2.3 Install win32all-152 Uninstall win32all-152 Install win32all-154 And, finally, this also works on a fresh Win98SE: Install Python 2.2.3 Install win32all-152 Uninstall win32all-152 Install win32all-154 Uninstall win32all-154 Uninstall Python 2.2.3 Install Python 2.3 Install win32all-157 The installer crash has happened for me on at least 5 PCs with very different configurations (spanning Win98SE, Win2K, WinXP, Athlon, P3, P4, and different peripherals and drivers). In each case, Python and win32all were being installed for the first time on the PC. My guess is that most people are upgrading from cleanly installed versions of win32all, and are therefore not seeing the problem. ---------------------------------------------------------------------- Comment By: John J Smith (johnjsmith) Date: 2003-08-08 01:47 Message: Logged In: YES user_id=830565 I assume you mean run it after the failed installation. I tried it on Python 2.3, win32all-157, Win98SE, and it worked: Registered: Python Registration of Python ActiveX Scripting Engine complete. And yes, an admin install even after crashing does work, and I've been using it. However it would be nice to have a clean install (especially for eventual un-installation and upgradation). ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2003-08-07 21:07 Message: Logged In: YES user_id=14198 Can you please see if running "win32comext\axscript\client\pyscript.py" also crashes for you? An admin install should still actually work fine - just can't be uninstalled, and a couple of demo COM objects won't be installed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-09 13:09:05
|
Bugs item #785258, was opened at 2003-08-08 09:01 Message generated for change (Comment added) made by comcol You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=785258&group_id=78018 Category: None Group: None Status: Open >Resolution: Invalid Priority: 5 Submitted By: Mark Carter (comcol) Assigned to: Nobody/Anonymous (nobody) Summary: Recent breakage in VBComponents Initial Comment: I use Office 2000, Windows 98, and I have recently upgraded to python 2.3 and win32all-155.exe The following code worked in python 2.2 under an old pywin32: xlApp = Dispatch("Excel.Application") xlApp.Visible = 1 xlApp.Workbooks.Add() xlApp.ActiveWorkbook.SaveAs(sys.path[0] + '\temp.xls') wb = xlApp.Workbooks("temp.xls") wbc = wb.VBProject.VBComponents # <---- CAUSES CRASH IN 2.3 xlApp.Quit() del xlApp but I get a GPE in 2.3, when the code finishes execution: EXCEL caused an invalid page fault in module OLE32.DLL at 0167:65f18ae3. If you comment out the line wbc = ... then I get no GPE. ---------------------------------------------------------------------- >Comment By: Mark Carter (comcol) Date: 2003-08-09 13:09 Message: Logged In: YES user_id=478116 Response by mhammond: I think this is a bug in Excel, but it is not clear why Python 2.3 shows it, but 2.2 does not. If you set wbc to None before closing, it doesn't crash. I think the problem is that Excel doesn't like being shut down when references to it still exist. You should try and make sure that pythoncom._GetInterfaceCount() returns zero before quitting ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=785258&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-08 13:13:44
|
Bugs item #785374, was opened at 2003-08-08 13:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=785374&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Ruben Marquez (rrm1) Assigned to: Nobody/Anonymous (nobody) Summary: Pythonwin startup error. Initial Comment: On an XP Profesional Machine, I upgraded from Python23rc1 to Python23 final. I uninstalled the old packages and installed the new ones (Python23, and win32all-155) in a different location, "D:\Programs\Python23". It all seemed to install correctly, but when trying to start the Pythonwin application the following error appeared in window: <Error getting traceback - cant import traceback>exceptions.ImportError: No module named pywin.framework.startup I then decided to start from scratch. I removed again all my python related packages. I deleted any remnants of the installation folder. I went to the registry and deleted the Python23 key. I rebooted the machine. I installed Python into D:\Programs\Python23, and it installed correctly. I then installed win32all-155.exe. It all seemed to go well, the Start Menu shortcuts were created, no errors. But when I tried to start the Pythonwin application it failed again with the same error message: <Error getting traceback - cant import traceback>exceptions.ImportError: No module named pywin.framework.startup Interestingly, when I launch the following, the app starts fine: D:\Programs\Python23\Lib\site- packages\Pythonwin\start_pythonwin.pyw But, if I launch the following, I get the error: D:\Programs\Python23\pythonwin.exe -Ruben ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=785374&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-08 10:12:08
|
Bugs item #784962, was opened at 2003-08-07 19:13 Message generated for change (Comment added) made by johnjsmith You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 Category: None Group: None Status: Open Resolution: Works For Me Priority: 5 Submitted By: John J Smith (johnjsmith) Assigned to: Nobody/Anonymous (nobody) Summary: Installation crash in recent win32all's. Initial Comment: The win32all installer has been crashing on me for the last few win32all releases. This has happened for Python 2.2.3 with win32all-156 and Python 2.3 with win32all-157. It has also happened for some previous win32all releases (such as 153 and 155 with Python 2.3). The error occurs during the `Completing Installation' stage, when the message box says `Registering COM Server AXScript Engine'. The error message is the usual `This program has performed an illegal operation and will be shut down' message. Pressing the `Details' button gives: WIN32ALL-156 caused an invalid page fault in module MSVCRT.DLL at 016f:7800b936. Registers: EAX=006b61a0 CS=016f EIP=7800b936 EFLGS=00010202 EBX=00000000 SS=0177 ESP=0063cad4 EBP=0063caf0 ECX=00000120 DS=0177 ESI=01ddab0c FS=3fb7 EDX=00000000 ES=0177 EDI=00000013 GS=0000 Bytes at CS:EIP: 89 5a 04 8b 55 0c 89 4d fc 8b 5a 04 8b 52 08 89 Stack dump: 00760840 01ddab10 00000001 006b8930 00000000 000004d0 00000120 0063cb34 7800b30c 0075005c 01ddac2c 00760840 00000000 00000001 bff813f8 81d52568 (This is with Python 2.2.3 and win32all-156.) This has happened on both WinXP and Win98SE. Once this happens, the win32all uninstaller doesn't work (says `can't find install.log'). If Python is installed with the `Non-Admin' option, then win32all installs fine (presumably because it never reaches the `Registering COM Server AXScript Engine' stage). I haven't seen anyone else report this, so looks like I'm the only one. Any help is greatly appreciated. ---------------------------------------------------------------------- >Comment By: John J Smith (johnjsmith) Date: 2003-08-08 10:12 Message: Logged In: YES user_id=830565 Okay, here is some more info. This sequence on a newly installed Win98SE works: Install Python 2.2.3 Install win32all-152 This sequence on a newly installed Win98SE crashes: Install Python 2.2.3 Install win32all-154 This sequence on a newly installed Win98SE *works*: Install Python 2.2.3 Install win32all-152 Uninstall win32all-152 Install win32all-154 And, finally, this also works on a fresh Win98SE: Install Python 2.2.3 Install win32all-152 Uninstall win32all-152 Install win32all-154 Uninstall win32all-154 Uninstall Python 2.2.3 Install Python 2.3 Install win32all-157 The installer crash has happened for me on at least 5 PCs with very different configurations (spanning Win98SE, Win2K, WinXP, Athlon, P3, P4, and different peripherals and drivers). In each case, Python and win32all were being installed for the first time on the PC. My guess is that most people are upgrading from cleanly installed versions of win32all, and are therefore not seeing the problem. ---------------------------------------------------------------------- Comment By: John J Smith (johnjsmith) Date: 2003-08-08 08:47 Message: Logged In: YES user_id=830565 I assume you mean run it after the failed installation. I tried it on Python 2.3, win32all-157, Win98SE, and it worked: Registered: Python Registration of Python ActiveX Scripting Engine complete. And yes, an admin install even after crashing does work, and I've been using it. However it would be nice to have a clean install (especially for eventual un-installation and upgradation). ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2003-08-08 04:07 Message: Logged In: YES user_id=14198 Can you please see if running "win32comext\axscript\client\pyscript.py" also crashes for you? An admin install should still actually work fine - just can't be uninstalled, and a couple of demo COM objects won't be installed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-08 09:01:17
|
Bugs item #785258, was opened at 2003-08-08 09:01 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=785258&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Mark Carter (comcol) Assigned to: Nobody/Anonymous (nobody) Summary: Recent breakage in VBComponents Initial Comment: I use Office 2000, Windows 98, and I have recently upgraded to python 2.3 and win32all-155.exe The following code worked in python 2.2 under an old pywin32: xlApp = Dispatch("Excel.Application") xlApp.Visible = 1 xlApp.Workbooks.Add() xlApp.ActiveWorkbook.SaveAs(sys.path[0] + '\temp.xls') wb = xlApp.Workbooks("temp.xls") wbc = wb.VBProject.VBComponents # <---- CAUSES CRASH IN 2.3 xlApp.Quit() del xlApp but I get a GPE in 2.3, when the code finishes execution: EXCEL caused an invalid page fault in module OLE32.DLL at 0167:65f18ae3. If you comment out the line wbc = ... then I get no GPE. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=785258&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-08 08:47:17
|
Bugs item #784962, was opened at 2003-08-07 19:13 Message generated for change (Comment added) made by johnjsmith You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 Category: None Group: None Status: Open >Resolution: Works For Me Priority: 5 Submitted By: John J Smith (johnjsmith) Assigned to: Nobody/Anonymous (nobody) Summary: Installation crash in recent win32all's. Initial Comment: The win32all installer has been crashing on me for the last few win32all releases. This has happened for Python 2.2.3 with win32all-156 and Python 2.3 with win32all-157. It has also happened for some previous win32all releases (such as 153 and 155 with Python 2.3). The error occurs during the `Completing Installation' stage, when the message box says `Registering COM Server AXScript Engine'. The error message is the usual `This program has performed an illegal operation and will be shut down' message. Pressing the `Details' button gives: WIN32ALL-156 caused an invalid page fault in module MSVCRT.DLL at 016f:7800b936. Registers: EAX=006b61a0 CS=016f EIP=7800b936 EFLGS=00010202 EBX=00000000 SS=0177 ESP=0063cad4 EBP=0063caf0 ECX=00000120 DS=0177 ESI=01ddab0c FS=3fb7 EDX=00000000 ES=0177 EDI=00000013 GS=0000 Bytes at CS:EIP: 89 5a 04 8b 55 0c 89 4d fc 8b 5a 04 8b 52 08 89 Stack dump: 00760840 01ddab10 00000001 006b8930 00000000 000004d0 00000120 0063cb34 7800b30c 0075005c 01ddac2c 00760840 00000000 00000001 bff813f8 81d52568 (This is with Python 2.2.3 and win32all-156.) This has happened on both WinXP and Win98SE. Once this happens, the win32all uninstaller doesn't work (says `can't find install.log'). If Python is installed with the `Non-Admin' option, then win32all installs fine (presumably because it never reaches the `Registering COM Server AXScript Engine' stage). I haven't seen anyone else report this, so looks like I'm the only one. Any help is greatly appreciated. ---------------------------------------------------------------------- >Comment By: John J Smith (johnjsmith) Date: 2003-08-08 08:47 Message: Logged In: YES user_id=830565 I assume you mean run it after the failed installation. I tried it on Python 2.3, win32all-157, Win98SE, and it worked: Registered: Python Registration of Python ActiveX Scripting Engine complete. And yes, an admin install even after crashing does work, and I've been using it. However it would be nice to have a clean install (especially for eventual un-installation and upgradation). ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2003-08-08 04:07 Message: Logged In: YES user_id=14198 Can you please see if running "win32comext\axscript\client\pyscript.py" also crashes for you? An admin install should still actually work fine - just can't be uninstalled, and a couple of demo COM objects won't be installed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-08 04:07:27
|
Bugs item #784962, was opened at 2003-08-08 05:13 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John J Smith (johnjsmith) Assigned to: Nobody/Anonymous (nobody) Summary: Installation crash in recent win32all's. Initial Comment: The win32all installer has been crashing on me for the last few win32all releases. This has happened for Python 2.2.3 with win32all-156 and Python 2.3 with win32all-157. It has also happened for some previous win32all releases (such as 153 and 155 with Python 2.3). The error occurs during the `Completing Installation' stage, when the message box says `Registering COM Server AXScript Engine'. The error message is the usual `This program has performed an illegal operation and will be shut down' message. Pressing the `Details' button gives: WIN32ALL-156 caused an invalid page fault in module MSVCRT.DLL at 016f:7800b936. Registers: EAX=006b61a0 CS=016f EIP=7800b936 EFLGS=00010202 EBX=00000000 SS=0177 ESP=0063cad4 EBP=0063caf0 ECX=00000120 DS=0177 ESI=01ddab0c FS=3fb7 EDX=00000000 ES=0177 EDI=00000013 GS=0000 Bytes at CS:EIP: 89 5a 04 8b 55 0c 89 4d fc 8b 5a 04 8b 52 08 89 Stack dump: 00760840 01ddab10 00000001 006b8930 00000000 000004d0 00000120 0063cb34 7800b30c 0075005c 01ddac2c 00760840 00000000 00000001 bff813f8 81d52568 (This is with Python 2.2.3 and win32all-156.) This has happened on both WinXP and Win98SE. Once this happens, the win32all uninstaller doesn't work (says `can't find install.log'). If Python is installed with the `Non-Admin' option, then win32all installs fine (presumably because it never reaches the `Registering COM Server AXScript Engine' stage). I haven't seen anyone else report this, so looks like I'm the only one. Any help is greatly appreciated. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2003-08-08 14:07 Message: Logged In: YES user_id=14198 Can you please see if running "win32comext\axscript\client\pyscript.py" also crashes for you? An admin install should still actually work fine - just can't be uninstalled, and a couple of demo COM objects won't be installed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-08 04:03:49
|
Patches item #781823, was opened at 2003-08-02 11:20 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=781823&group_id=78018 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Roger Upole (rupole) Assigned to: Nobody/Anonymous (nobody) Summary: SID/SecurityDescriptor string conversions Initial Comment: API functions to convert SIDs and Security descriptors to strings and vice-versa. Two of these mirror a couple of hand-rolled functions already in win32security (GetTextualSid and GetBinarySid). Very handy for storing default permissions in a database. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2003-08-08 14:03 Message: Logged In: YES user_id=14198 Thanks, Checked in, but I did an #ifdef for those 2 tokens that failed. If these are very common, we can just add the literals (ie, an "#else" block to the #ifdefs I added) Checking in win32security.i; new revision: 1.10; previous revision: 1.9 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=781823&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-08 03:58:20
|
Patches item #784643, was opened at 2003-08-07 19:24 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=784643&group_id=78018 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Lijun Qin (qinlj) Assigned to: Nobody/Anonymous (nobody) Summary: A patch to fix a serious bug in univgw.cpp Initial Comment: in win32com/src/univgw.cpp, line 393, The sequence of IDispatch member functions is incorrect, this is the right one: if (isDispatch) { vtbl->methods[3] = (pfnGWMethod) univgw_GetTypeInfoCount; vtbl->methods[4] = (pfnGWMethod) univgw_GetTypeInfo; vtbl->methods[5] = (pfnGWMethod) univgw_GetIDsOfNames; vtbl->methods[6] = (pfnGWMethod) univgw_Invoke; } ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2003-08-08 13:58 Message: Logged In: YES user_id=14198 Fixed - thanks. Checking in univgw.cpp; new revision: 1.7; previous revision: 1.6 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=784643&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-07 19:13:21
|
Bugs item #784962, was opened at 2003-08-07 19:13 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John J Smith (johnjsmith) Assigned to: Nobody/Anonymous (nobody) Summary: Installation crash in recent win32all's. Initial Comment: The win32all installer has been crashing on me for the last few win32all releases. This has happened for Python 2.2.3 with win32all-156 and Python 2.3 with win32all-157. It has also happened for some previous win32all releases (such as 153 and 155 with Python 2.3). The error occurs during the `Completing Installation' stage, when the message box says `Registering COM Server AXScript Engine'. The error message is the usual `This program has performed an illegal operation and will be shut down' message. Pressing the `Details' button gives: WIN32ALL-156 caused an invalid page fault in module MSVCRT.DLL at 016f:7800b936. Registers: EAX=006b61a0 CS=016f EIP=7800b936 EFLGS=00010202 EBX=00000000 SS=0177 ESP=0063cad4 EBP=0063caf0 ECX=00000120 DS=0177 ESI=01ddab0c FS=3fb7 EDX=00000000 ES=0177 EDI=00000013 GS=0000 Bytes at CS:EIP: 89 5a 04 8b 55 0c 89 4d fc 8b 5a 04 8b 52 08 89 Stack dump: 00760840 01ddab10 00000001 006b8930 00000000 000004d0 00000120 0063cb34 7800b30c 0075005c 01ddac2c 00760840 00000000 00000001 bff813f8 81d52568 (This is with Python 2.2.3 and win32all-156.) This has happened on both WinXP and Win98SE. Once this happens, the win32all uninstaller doesn't work (says `can't find install.log'). If Python is installed with the `Non-Admin' option, then win32all installs fine (presumably because it never reaches the `Registering COM Server AXScript Engine' stage). I haven't seen anyone else report this, so looks like I'm the only one. Any help is greatly appreciated. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=784962&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-07 09:24:19
|
Patches item #784643, was opened at 2003-08-07 09:24 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=784643&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Lijun Qin (qinlj) Assigned to: Nobody/Anonymous (nobody) Summary: A patch to fix a serious bug in univgw.cpp Initial Comment: in win32com/src/univgw.cpp, line 393, The sequence of IDispatch member functions is incorrect, this is the right one: if (isDispatch) { vtbl->methods[3] = (pfnGWMethod) univgw_GetTypeInfoCount; vtbl->methods[4] = (pfnGWMethod) univgw_GetTypeInfo; vtbl->methods[5] = (pfnGWMethod) univgw_GetIDsOfNames; vtbl->methods[6] = (pfnGWMethod) univgw_Invoke; } ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=784643&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-04 14:41:59
|
Bugs item #782844, was opened at 2003-08-04 09:41 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=782844&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Raymond A. St. Marie (rastm2) Assigned to: Nobody/Anonymous (nobody) Summary: Pythonwin/Options/Format Apply-button won't work Initial Comment: After changeing some font sizes and colors successfully, I wished to change the "unterminated string" background color. While the color changes show up in the example window_ I can't Apply them because the Apply button will not ungrey itself after making a selection. Fortunately, the background color is white and I can read the text. More of a feature restriction then a bug. :) Win 98 (not SE) win32all - 155 downloaded on the July29th2003 # 46 The Apply button seems to work in other Option windows. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=782844&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-03 16:45:14
|
Feature Requests item #782374, was opened at 2003-08-03 16:45 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=782374&group_id=78018 Category: None Group: None Status: Open Priority: 5 Submitted By: simon place (psi-man) Assigned to: Nobody/Anonymous (nobody) Summary: simple gui shortcut Initial Comment: i'm know this is very lazy, but if the various debug modes in the execute script dialog could each have their own button, one click instead of three, and you're also less likely to accidentally run in the previous mode when you didn't want it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=782374&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-03 16:37:27
|
Bugs item #782372, was opened at 2003-08-03 16:37 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=782372&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: simon place (psi-man) Assigned to: Nobody/Anonymous (nobody) Summary: simple gui inconsistency Initial Comment: when typing in a watch expression the first character is missed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=782372&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-02 01:27:29
|
Bugs item #772804, was opened at 2003-07-17 00:21 Message generated for change (Comment added) made by rupole You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=772804&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: John Lim (johnlim) Assigned to: Nobody/Anonymous (nobody) Summary: Failed Installation: Entry Point Not Found Initial Comment: Towards the end of the installer, I get this error message: ------- Python Win32 extensions Installation: win32all-154.exe - Entry Point Not Found The procedure entry point ? PyWinObject_FromSECURITY_DESCRIPTOR@@YAPAU_obj ect@@PAU_SECURITY_DESCRIPTOR@@I@Z could not be located in the dynamic link library PyWinTypes22.dll. Error in installer script. Traceback (most recent call last): File "e:\TEMP\FinishInstall.py", line 101, in ApplyEntryPoint apply(ep, args) File "e:\TEMP\FinishInstall.py", line 82, in DoCompileAllAndRegisterCOM FindDuplicates(mod, dir) File "e:\TEMP\FinishInstall.py", line 143, in FindDuplicates import win32api ImportError: DLL load failed: The specified procedure could not be found. ------- If it helps, FYI I tried using the ActivePython 2.2.2 build 224 (unsuccessfully) before attempting to install PyWin32 manually. http://bugs.activestate.com/ActivePython/show_bug. cgi?id=26267 ---------------------------------------------------------------------- Comment By: Roger Upole (rupole) Date: 2003-08-01 20:27 Message: Logged In: YES user_id=771074 The argument types for PyWinObject_FromSECURITY_DESCRIPTOR have changed. Most likely you have an old version of PyWinTypes or win32api hanging around. Try doing a complete uninstall of the win32 extensions first, making sure both of these files are gone. Roger ---------------------------------------------------------------------- Comment By: Paul Moore (pmoore) Date: 2003-07-28 14:32 Message: Logged In: YES user_id=113328 Seems to be fixed in win32all-157 ---------------------------------------------------------------------- Comment By: Paul Moore (pmoore) Date: 2003-07-21 16:33 Message: Logged In: YES user_id=113328 I get this too, with Python 2.3c1 and win32all-155. I'm using Windows 2000 Pro, SP4. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=772804&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-08-02 01:20:53
|
Patches item #781823, was opened at 2003-08-01 20:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=781823&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Roger Upole (rupole) Assigned to: Nobody/Anonymous (nobody) Summary: SID/SecurityDescriptor string conversions Initial Comment: API functions to convert SIDs and Security descriptors to strings and vice-versa. Two of these mirror a couple of hand-rolled functions already in win32security (GetTextualSid and GetBinarySid). Very handy for storing default permissions in a database. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=781823&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-07-29 23:31:05
|
Bugs item #774215, was opened at 2003-07-19 10:40 Message generated for change (Comment added) made by durea You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=774215&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: Art Du Rea (durea) Assigned to: Nobody/Anonymous (nobody) Summary: Can't install on non-std Python installation Initial Comment: ( I also submitted this in the Support section) Esteemed Python People and Lurkers: I would really like to install the Win extensions to Python ... I just started using Python and I LOVE it! I've never seen Python before in my life, and with the PeachPit Press Python Visual Quick Start book, I got a simple HTML Automatic Table generator up and running in a total of about 4 hours! The problem is I can NOT install the Win extensions! My Python is installed in: "F:\Applications\Python" and the Win extension installer (win32all-153.exe) just can't find it. I click the "Continue anyway" button on the popup, but it just jumps back to the same popup and will NOT continue no matter what I do. How can I get the extensions installed on my Non-Standard Python installation? Thank you for your gracious and patient assistance with this issue. Art Du Rea Carlisle, PA USA NoSpam e-mail: imadeptNOGI@NOGOpa-net Remove the caps letters (NO Garbage In : NO Garbage Out) ---------------------------------------------------------------------- >Comment By: Art Du Rea (durea) Date: 2003-07-29 19:31 Message: Logged In: YES user_id=826097 I hope box is where I'm supposed to comment ... it sure would be nice just to have a "REPLY" button ... Anyway, I found another site with a message from a Python user with my exact problem ... There ought to be a big flaming warning to NOT upload the latest version of wxPython ... it is for the BETA Python 2.3! There is virtually no distinction between the boxes to download the win32 for Python 2.2.3 and 2.3, and it is totally trivial to get confused and download the wrong one, which I did! (And I'm obviously not the only one!) I tried to get back to this message thread, but SourceForge is not very friendly IM-notso-HO. I did get wxPython "working" so to speak. I've tried to run all 8 of the sample programs ... at least a couple of them don't run at all or else crash the system. At least a couple of others run, but if I play "musical windows" (make different resident windows active) with WinExplorer or whatever, the system hangs. All I wanted was a couple of quick and easy interface popups, but that is not what wx is. If you want, I'll give you more quantitative data on this ... send a direct e-mail to my_...@NO... ... remove the cap letters. I do LOVE Python and am using it for text file filtering and HTML table generation (120 or so linked entries). I just wish that I had a couple of simple, reliable add-on popups for user interface to go with vanilla Python. Before I would use it heavily, though, I would need to be able to generate execuatbles. This has been a terribly negative letter, but I want to thank you most sincerely for your efforts and your tremendous achievements. I hope you have enjoyed yourself and I look forward to hearing from you! Blessings in abundance, all the best, and ENJOY! Art Du Rea NO Garbage In - NO Garbage Out PC P-II 350 w/192 Meg Win98 SE ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2003-07-29 03:04 Message: Logged In: YES user_id=14198 Please try the latest win32all versions (156/7) - they should work in that case. Please let us know either way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=774215&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-07-29 08:38:40
|
Bugs item #774215, was opened at 2003-07-20 00:40 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=774215&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: Art Du Rea (durea) Assigned to: Nobody/Anonymous (nobody) Summary: Can't install on non-std Python installation Initial Comment: ( I also submitted this in the Support section) Esteemed Python People and Lurkers: I would really like to install the Win extensions to Python ... I just started using Python and I LOVE it! I've never seen Python before in my life, and with the PeachPit Press Python Visual Quick Start book, I got a simple HTML Automatic Table generator up and running in a total of about 4 hours! The problem is I can NOT install the Win extensions! My Python is installed in: "F:\Applications\Python" and the Win extension installer (win32all-153.exe) just can't find it. I click the "Continue anyway" button on the popup, but it just jumps back to the same popup and will NOT continue no matter what I do. How can I get the extensions installed on my Non-Standard Python installation? Thank you for your gracious and patient assistance with this issue. Art Du Rea Carlisle, PA USA NoSpam e-mail: imadeptNOGI@NOGOpa-net Remove the caps letters (NO Garbage In : NO Garbage Out) ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2003-07-29 17:04 Message: Logged In: YES user_id=14198 Please try the latest win32all versions (156/7) - they should work in that case. Please let us know either way. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=774215&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-07-29 07:17:49
|
Bugs item #736517, was opened at 2003-05-13 01:49 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=736517&group_id=78018 Category: com Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Shack Toms (shacktoms) Assigned to: Mark Hammond (mhammond) Summary: Memory Leak Initial Comment: There is a memory leak associated with events delivered through the IConnectionPoint interface. The leak occurs when a ByRef VARIANT parameter is passed through the interface as an inout parameter. The culprit appears to be oleargs.cpp, specifically the routine PythonOleArgHelper::MakeObjToVariant, which is called to replace the original VARIANT with the returned one. In the case VT_VARIANT | VT_BYREF, with bCreateBuffers as false, the routine calls VariantClear(var), which only clears the referencing VARIANT and not the referenced one. This call should be VariantClear(V_VARIANTREF(var)), which will clear memory held by the referenced VARIANT before the subsequent call to PyCom_VariantFromPyObject simply overwrites that VARIANT. The code as written depends on V_VARIANTREF(var) to remain valid after calling VariantClear(var), which seems a dangerous assumption. Note that this repair follows the same logic as is used in the existing code for the VT_BSTR | VT_BYREF case, in which SysFreeString(*V_BSTRREF(var)) is called, for the reason that VariantClear(var) wouldn't free the indirectly referenced BSTR. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2003-07-29 17:00 Message: Logged In: YES user_id=14198 Fixed in revision 1.21, so already in the latest win32all Thanks ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2003-05-14 00:28 Message: Logged In: YES user_id=14198 Thanks! Looks right to me. I will check it in as soon as I re-run all the tests. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=736517&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-07-29 07:17:00
|
Bugs item #737373, was opened at 2003-05-14 09:33 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=737373&group_id=78018 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Mark Hammond (mhammond) Assigned to: Mark Hammond (mhammond) Summary: Installer has wrong version info in pyd files Initial Comment: Just wanted to alert you to a small problem with the win32all 152 binary build for Python 2.2. The Windows version information appears to be incorrect or at least inconsistent with win32all 150 for Python 2.2. The 150 binaries are versioned 2.2.0.150, but the 152 binaries are versioned 2.1.0.152. This caused my installation of 152 over 150 to NOT replace the binaries, since they appear to be older from a versioning perspective. All of the win32 binaries appear to be affected. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2003-07-29 17:01 Message: Logged In: YES user_id=14198 Changed my build process to stop this happening. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=737373&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-07-29 06:59:33
|
Bugs item #728896, was opened at 2003-04-28 22:49 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=728896&group_id=78018 Category: win32 Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Mark Hammond (mhammond) Assigned to: Mark Hammond (mhammond) Summary: Strange exception handling in win32api registry fns Initial Comment: Hi, The registry handling methods in win32api seem to have problems with the Python exception handling. It took me some time, but I have managed to isolate the problem to a simple program. But the problem is more severe in more complicated situations, and there it seems to happen with most (or all) registry methods (win32api.Reg...()). The methods of _winreg module do not exhibit this problem. For now, I am using _winreg. However, it would be nice if the problem could be tracked down inside the win32api's source code and be fixed. regards, Hung Jung Lu #---------------------------------------------------------------------- # OS used: Windows XP # # Python 2.1 # program works correctly: correct exception message displayed # # Python 2.2.2 (win32all build 152) # (a) In Pythonwin intractive window, you get # SystemError: error return without exception set # (b) When running with python.exe, it crashes # # Python 2.3b1 (win32all build 153) # (a) In Pythonwin intractive window, you get # SystemError: error return without exception set # (b) When running with python.exe, program exits silently, # which is not the correct behavior # # Comments: # (a) equivalent _winreg module methods do not have problem. # (b) problem seems to happen with most, or all, win32api.Reg...() # methods, not in this particular example, but in more # complicated programs (involving classes) # import win32con import win32api def reg_operation(): hkey = win32api.RegCreateKey(win32con.HKEY_CURRENT_USER, r'Software\Spam') x = 3/0 # or a statement like: raise 'error' try: reg_operation() except: x = 5/0 # or a statement like: raise 'error' ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2003-07-29 16:59 Message: Logged In: YES user_id=14198 This has been fixed - my test_win32api module no longer shows a stale exception. Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=728896&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-07-29 06:56:09
|
Bugs item #722082, was opened at 2003-04-16 06:22 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=722082&group_id=78018 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Greg Chapman (glchapman) Assigned to: Nobody/Anonymous (nobody) Summary: Potential crash in win32clipboard.SetClipboardData Initial Comment: Consider the following: Python 2.2.2 (#37, Oct 14 2002, 17:02:34) [MSC 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> class crasher(object): pass ... >>> obj = crasher() >>> import win32clipboard >>> win32clipboard.OpenClipboard() >>> win32clipboard.EmptyClipboard() >>> win32clipboard.SetClipboardData(0, obj) (Python Crashes -- same thing happens under 2.3a2). The problem appears to be the assumption (in py_set_clipboard_data) that a non-NULL tp_as_buffer implies a valid bf_getreadbuffer. This is not true; in particular, tp_as_buffer is always non-NULL for new-style classes. I'd suggest using PyObject_AsReadBuffer instead of directly manipulating tp_as_buffer. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2003-07-29 16:56 Message: Logged In: YES user_id=14198 Fixed by Roger Upole in rev 1.11 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=722082&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2003-07-29 06:48:25
|
Patches item #732056, was opened at 2003-05-04 14:06 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=732056&group_id=78018 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Roger Upole (rupole) Assigned to: Nobody/Anonymous (nobody) Summary: Fix memory leak in security descriptor functions Initial Comment: In function that converts security descriptor to absolute format, minium amount of memory for ACL's and Sid's was allocated, but if SACL, DACL, owner sid or group sid was not present it was never freed. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2003-07-29 16:48 Message: Logged In: YES user_id=14198 Thanks! Checking in PySECURITY_DESCRIPTOR.cpp; new revision: 1.9; previous revision: 1.8 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=732056&group_id=78018 |
2 messages has been excluded from this view by a project administrator.
