pywin32-bugs Mailing List for Python for Windows Extensions (Page 103)
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...> - 2004-05-31 13:14:21
|
Bugs item #959162, was opened at 2004-05-24 00:01 Message generated for change (Comment added) made by gtegos You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=959162&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: john wolter (johnswolter) Assigned to: Nobody/Anonymous (nobody) Summary: Win98 SE pythonwin run failure Initial Comment: I installed the 2.3.4rc1 then your 201 build and found an error when I started pywin. The target system is a Win98 SE /w 64 RAM 4 GigaHD, nothing special etc. I've run 2.3.3 and wiin32all previously and all was ok. Let me know if there is anything I can do to correct this. Thanks for your package it has made a real difference. Startup runtime ERROR for pythonwin: File "C:\PYTHON23\Lib\site-packages\pythonwin\pywin\framework\intpyapp.py", line 163, in InitInstance import interact File "C:\PYTHON23\Lib\site-packages\pythonwin\pywin\framework\interact.py", line 26, in ? import winout File "C:\PYTHON23\Lib\site-packages\pythonwin\pywin\framework\winout.py", line 26, in ? from pywintypes import UnicodeType File "C:\PYTHON23\Lib\site-packages\win32\lib\pywintypes.py", line 69, in ? __import_pywin32_system_module__("pywintypes", globals()) File "C:\PYTHON23\Lib\site-packages\win32\lib\pywintypes.py", line 62, in __import_pywin32_system_module__ raise ImportError, "Can not locate " + filename exceptions.ImportError: Can not locate pywintypes23.dll ---------------------------------------------------------------------- Comment By: George Tegos (gtegos) Date: 2004-05-31 13:14 Message: Logged In: YES user_id=464497 We had the same symptoms on WinME and we discovered that the pywintypes dll was on the system directory, only it had 8.3 file name. We renamed the file to pywintypes23.dll (also the pythoncom23.dll) and everything went OK. ---------------------------------------------------------------------- Comment By: HAVOK (havok) Date: 2004-05-26 17:48 Message: Logged In: YES user_id=12566 this is a dupe of bug 917702 Solution: 1. Add C:\WINDOWS\SYSTEM to your PATH (c:\autoexec.bat) OR 2. Move pywintypes23.dll and that other dll (py*.dll) to C:\windows OR 3. Move those files to C:\Python23 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=959162&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-30 05:24:18
|
Bugs item #917702, was opened at 2004-03-16 17:51 Message generated for change (Comment added) made by rechapman You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=917702&group_id=78018 Category: installation Group: v1.0 (example) Status: Open Resolution: None Priority: 7 Submitted By: dak (dakcalouro) Assigned to: Nobody/Anonymous (nobody) Summary: pywintypes can't find pywintypes23.dll Initial Comment: After installing Python v2.3 and pywin32 build 200 on Windows ME, at startup pythonwin opens a window titled "Python Traceback when executing InitInstance handler". The window contains File "C:\PROGRAMS\PYTHON\Lib\site- packages\Pythonwin\pywin\framework\intpyapp.py", line 163, in InitInstance import interact File "C:\PROGRAMS\PYTHON\Lib\site- packages\Pythonwin\pywin\framework\interact.py", line 26, in ? import winout File "C:\PROGRAMS\PYTHON\Lib\site- packages\Pythonwin\pywin\framework\winout.py", line 26, in ? from pywintypes import UnicodeType File "C:\PROGRAMS\PYTHON\Lib\site-packages\win32 \lib\pywintypes.py", line 55, in ? __import_pywin32_system_module__("pywintypes", globals()) File "C:\PROGRAMS\PYTHON\Lib\site-packages\win32 \lib\pywintypes.py", line 48, in __import_pywin32_system_module__ raise ImportError, "Can not locate " + filename exceptions.ImportError: Can not locate pywintypes23.dll ------------------ end of error window contents I found the file pywintypes23.dll my C:\Programs\Python installation folder (I can't remember which subfolder) and copied it to the folders that seemed likely: C:\Programs\Python\DLLs, C:\WINDOWS\SYSTEM, C:\WINDOWS\SYSTEM32. Restarting pythonwin.exe gave the same error msg. I scanned pywintypes.py for workaround ideas, and copied pywintypes23.dll to C:\WINDOWS. Now pythonwin starts up without error (shows the version & copyright msg and the >>> interpreter prompt). This is OK as a workaround. ---------------------------------------------------------------------- Comment By: Bob Chapman (rechapman) Date: 2004-05-30 00:24 Message: Logged In: YES user_id=245167 This problem also exists with Build 201 of win32all under Windows 98SE. Pythonwin displays the same error messages and will not start until pywintypes23.dll is copied from c:\windows\system (where it is installed) to c:\windows. This workaround is not required for Build 201 under Windows XP and was NOT required for Build 163 (and previous) under Windows 98SE. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-04-28 18:34 Message: Logged In: YES user_id=14198 There have been a couple of reports like this on Win9x, with the same fix. Apparently the system32 directory is not on the path. It sounds like we are trying to copy to "system32" when we should just be copying to "windows" on that platform. ---------------------------------------------------------------------- Comment By: Peter Finlayson (frnknstn) Date: 2004-03-30 07:37 Message: Logged In: YES user_id=1009500 I had a similar problem, also with Python v2.3 and pywin32 build 200, but under Win98SE. For me, the pywintypes23.dll was installed to the c:\windows\system directory. I received the same error window. I resolved the problem by adding C:\WINDOWS\SYSTEM to my path in AUTOEXEC.BAT. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=917702&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-28 09:09:43
|
Bugs item #962094, was opened at 2004-05-28 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=962094&group_id=78018 Category: com Group: None Status: Open Resolution: None Priority: 5 Submitted By: Malte Forkel (mforkel) Assigned to: Nobody/Anonymous (nobody) Summary: Word9 unit conversion functions fail Initial Comment: The unit conversions functions of Word9 fail with an exception. Here is an example using CentimetersToPoint: >>> app.CentimetersToPoints <bound method _Application.CentimetersToPoints of <win32com.gen_py.Microsoft Word 9.0 Object Library._Application instance at 0x20221704>> >>> app.CentimetersToPoints(1.0) Traceback (most recent call last): File "<interactive input>", line 1, in ? File "win32com\gen_py\00020905-0000-0000-C000- 000000000046x0x8x1.py", line 14423, in CentimetersToPoints return self._oleobj_.InvokeTypes(371, LCID, 1, (4, 0), ((4, 1),),Centimeters) com_error: (-2147467259, 'Unbekannter Fehler', None, None) A workaround for this problem was suggested some time ago (http://groups.google.de/groups?hl=de&lr=&ie=UTF- 8&threadm=35D6EBE5.511C5430% 40appliedbiometrics.com&rnum=2&prev=/groups) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=962094&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-26 18:08:32
|
Bugs item #907801, was opened at 2004-03-01 21:10 Message generated for change (Comment added) made by havok You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=907801&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David W. Nichols (dwnichols) Assigned to: Nobody/Anonymous (nobody) Summary: failed shortcuts when changed Start Menu Group Initial Comment: When I installed Python 2.3.3, I changed Start Menu Group setting from its default of "Python 2.3" to "Python233". Here's the results from the final install screen: Creating .PTH file C:\Python23\pywin32.pth Copy pythoncom23.dll to C:\WINDOWS\system32 Copy pywintypes23.dll to C:\WINDOWS\system32 Registered: Python.Interpreter Registered: Python.Dictionary -> Software\Python\PythonCore\2.3\Help[None]=None -> Software\Python\PythonCore\2.3\Help\Pythonwin Reference[None]='C: \Python23\Lib\site-packages\PyWin32.chm' Creating directory C: \Python23\Lib\site-packages\win32com\gen_py Failed to create shortcut 'C:\Documents and Settings\All Users\Start Menu\Programs\Python 2.3\PythonWin.lnk' - error 0x80070003 The pywin32 extensions were successfully installed. ---------------------------------------------------------------------- Comment By: HAVOK (havok) Date: 2004-05-26 20:08 Message: Logged In: YES user_id=12566 Python seems to store this changed group in: HKLM\SOFTWARE\Python\PythonCore\2.3\InstallPath\InstallGroup Maybe the installation can use above key if it exists, keeping the existing stuff (Python 2.3) as a fallback. ---------------------------------------------------------------------- Comment By: Phillip Ruggera (pruggera) Date: 2004-05-10 06:45 Message: Logged In: YES user_id=16022 This happened to me too. I manually created a shortcut to C:\Python23\Lib\site-packages\pythonwin\Pythonwin.exe and all was well. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=907801&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-26 17:48:37
|
Bugs item #959162, was opened at 2004-05-24 02:01 Message generated for change (Comment added) made by havok You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=959162&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: john wolter (johnswolter) Assigned to: Nobody/Anonymous (nobody) Summary: Win98 SE pythonwin run failure Initial Comment: I installed the 2.3.4rc1 then your 201 build and found an error when I started pywin. The target system is a Win98 SE /w 64 RAM 4 GigaHD, nothing special etc. I've run 2.3.3 and wiin32all previously and all was ok. Let me know if there is anything I can do to correct this. Thanks for your package it has made a real difference. Startup runtime ERROR for pythonwin: File "C:\PYTHON23\Lib\site-packages\pythonwin\pywin\framework\intpyapp.py", line 163, in InitInstance import interact File "C:\PYTHON23\Lib\site-packages\pythonwin\pywin\framework\interact.py", line 26, in ? import winout File "C:\PYTHON23\Lib\site-packages\pythonwin\pywin\framework\winout.py", line 26, in ? from pywintypes import UnicodeType File "C:\PYTHON23\Lib\site-packages\win32\lib\pywintypes.py", line 69, in ? __import_pywin32_system_module__("pywintypes", globals()) File "C:\PYTHON23\Lib\site-packages\win32\lib\pywintypes.py", line 62, in __import_pywin32_system_module__ raise ImportError, "Can not locate " + filename exceptions.ImportError: Can not locate pywintypes23.dll ---------------------------------------------------------------------- Comment By: HAVOK (havok) Date: 2004-05-26 19:48 Message: Logged In: YES user_id=12566 this is a dupe of bug 917702 Solution: 1. Add C:\WINDOWS\SYSTEM to your PATH (c:\autoexec.bat) OR 2. Move pywintypes23.dll and that other dll (py*.dll) to C:\windows OR 3. Move those files to C:\Python23 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=959162&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-24 13:54:06
|
Bugs item #959449, was opened at 2004-05-24 15:54 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=959449&group_id=78018 Category: com Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jan Erik Breimo (jebreimo) Assigned to: Nobody/Anonymous (nobody) Summary: Error when using IID in all builds after 159 Initial Comment: The following script: import win32com.client.gencache Excel = win32com.client.gencache.EnsureModule ('{00020813-0000-0000-C000-000000000046}', 0, 1, 4) excel = Excel.Application() and simliar scripts that use other servers always fail as follows in builds 161, 163 and 201: D:\ws\k2is_source.CC-V2\Tools\Python\diverse>python ExcelTest.py Traceback (most recent call last): File "ExcelTest.py", line 3, in ? excel = Excel.Application() File "C:\Python23\Lib\site- packages\win32com\client\__init__.py", line 489, in __init__ if oobj is None: oobj = pythoncom.new(self.CLSID) TypeError: Only strings and iids can be converted to a CLSID. In builds 153, 155 and 159 the scripts run without errors. I'm using Python 2.3.3 on Win2k Professional SP 4 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=959449&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-24 00:01:50
|
Bugs item #959162, was opened at 2004-05-23 19: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=959162&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: john wolter (johnswolter) Assigned to: Nobody/Anonymous (nobody) Summary: Win98 SE pythonwin run failure Initial Comment: I installed the 2.3.4rc1 then your 201 build and found an error when I started pywin. The target system is a Win98 SE /w 64 RAM 4 GigaHD, nothing special etc. I've run 2.3.3 and wiin32all previously and all was ok. Let me know if there is anything I can do to correct this. Thanks for your package it has made a real difference. Startup runtime ERROR for pythonwin: File "C:\PYTHON23\Lib\site-packages\pythonwin\pywin\framework\intpyapp.py", line 163, in InitInstance import interact File "C:\PYTHON23\Lib\site-packages\pythonwin\pywin\framework\interact.py", line 26, in ? import winout File "C:\PYTHON23\Lib\site-packages\pythonwin\pywin\framework\winout.py", line 26, in ? from pywintypes import UnicodeType File "C:\PYTHON23\Lib\site-packages\win32\lib\pywintypes.py", line 69, in ? __import_pywin32_system_module__("pywintypes", globals()) File "C:\PYTHON23\Lib\site-packages\win32\lib\pywintypes.py", line 62, in __import_pywin32_system_module__ raise ImportError, "Can not locate " + filename exceptions.ImportError: Can not locate pywintypes23.dll ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=959162&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-19 11:34:37
|
Bugs item #956654, was opened at 2004-05-19 03:34 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=956654&group_id=78018 Category: installation Group: None Status: Open Resolution: None Priority: 5 Submitted By: Greg Chapman (glchapman) Assigned to: Nobody/Anonymous (nobody) Summary: Incomplete installation of v. 201.1 on Windows XP Initial Comment: I just installed pywin32 201.1 on a new Windows XP machine (using Python 2.3.3); this was the first pywin32 build I've installed on this machine. The installation apparently succeeded, however, right- clicking a .py file does not present "Edit" as a command (only "Edit with IDLE"). During installation, there was no option presented on whether to make Pythonwn my default python editor, as I believe used to be done with previous builds. I've also installed 201.1 on another XP machine which has had several previous pywin32 builds installed and uninstalled. There the "Edit" command is present in the context menu. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=956654&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-19 10:33:50
|
Patches item #944453, was opened at 2004-04-29 23:07 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=944453&group_id=78018 Category: None Group: None >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: alch (alch) Assigned to: Mark Hammond (mhammond) Summary: win32gui patch to enable balloon tooltips Initial Comment: Hi, I am using this patch in clamwin (http://clamwin.sourceforge.net) to display balloon tool-tips in the tray icon. It requires Internet Explorer 5.0 or higher on pre-XP Windows, but nowadays this seems to be no problem. I created the patch against current cvs. Regards, Alech ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2004-05-19 20:33 Message: Logged In: YES user_id=14198 Looks good to me! Thanks! Checking in win32gui.i; new revision: 1.41; previous revision: 1.40 ---------------------------------------------------------------------- Comment By: alch (alch) Date: 2004-05-19 17:09 Message: Logged In: YES user_id=1004158 it works on Windows Me and later, windows 98/NT is not supported because Internet Expolrer doesn't update shell32.dll ---------------------------------------------------------------------- Comment By: alch (alch) Date: 2004-05-19 17:04 Message: Logged In: YES user_id=1004158 sorry, forgot to tick the checkbox ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-05-18 08:04 Message: Logged In: YES user_id=14198 There is no patch attached! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=944453&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-19 07:09:20
|
Patches item #944453, was opened at 2004-04-29 23:07 Message generated for change (Comment added) made by alch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=944453&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: alch (alch) Assigned to: Mark Hammond (mhammond) Summary: win32gui patch to enable balloon tooltips Initial Comment: Hi, I am using this patch in clamwin (http://clamwin.sourceforge.net) to display balloon tool-tips in the tray icon. It requires Internet Explorer 5.0 or higher on pre-XP Windows, but nowadays this seems to be no problem. I created the patch against current cvs. Regards, Alech ---------------------------------------------------------------------- >Comment By: alch (alch) Date: 2004-05-19 17:09 Message: Logged In: YES user_id=1004158 it works on Windows Me and later, windows 98/NT is not supported because Internet Expolrer doesn't update shell32.dll ---------------------------------------------------------------------- Comment By: alch (alch) Date: 2004-05-19 17:04 Message: Logged In: YES user_id=1004158 sorry, forgot to tick the checkbox ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-05-18 08:04 Message: Logged In: YES user_id=14198 There is no patch attached! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=944453&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-19 07:04:45
|
Patches item #944453, was opened at 2004-04-29 23:07 Message generated for change (Comment added) made by alch You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=944453&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: alch (alch) Assigned to: Mark Hammond (mhammond) Summary: win32gui patch to enable balloon tooltips Initial Comment: Hi, I am using this patch in clamwin (http://clamwin.sourceforge.net) to display balloon tool-tips in the tray icon. It requires Internet Explorer 5.0 or higher on pre-XP Windows, but nowadays this seems to be no problem. I created the patch against current cvs. Regards, Alech ---------------------------------------------------------------------- >Comment By: alch (alch) Date: 2004-05-19 17:04 Message: Logged In: YES user_id=1004158 sorry, forgot to tick the checkbox ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-05-18 08:04 Message: Logged In: YES user_id=14198 There is no patch attached! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=944453&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-19 01:12:21
|
Bugs item #955432, was opened at 2004-05-18 06:01 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=955432&group_id=78018 Category: win32 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: odbc module not portable Initial Comment: I'm interested in using the ODBC module with unixODBC and/or iODBC on Linux. I've gotten it to work, after a fashion, with Python 2.3.3 and unixODBC 2.2.8 on SuSE Linux 8.2. I'd like to know how receptive you would be to portability patches. One category of changes conditionally compiles the Windows-specific things: windows.h, __declspec, etc. Another category of changes removes the few C++ things in an otherwise C-compatible module: declarations, comments, map(), etc. This is mostly in odbc.cpp, but there are also a few changes to dbi.h and dbi.cpp. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2004-05-19 11:12 Message: Logged In: YES user_id=14198 I'll get to this in a couple of days. The patches are likely to apply OK as these modules aren't really being developed. Without looking at the patch, and assuming using datetime can be b/w compatible, could we just use a "Python" level API to import the module and call the functions? I'm happy to accept it may not be worth it though. ---------------------------------------------------------------------- Comment By: Jon Willeke (willeke) Date: 2004-05-19 07:16 Message: Logged In: YES user_id=185468 The datetime module's C API is not fully baked, so I guess we're stuck with DBI, for a while. I submitted patches #956244 and #956247 to remove Windows and C++ dependencies. BTW, I think I omitted the -u option on some of the patches I submitted. Let me know if you have any problems with them. ---------------------------------------------------------------------- Comment By: Jon Willeke (willeke) Date: 2004-05-19 03:53 Message: Logged In: YES user_id=185468 I've submitted patches #956091, #956093, and #956094. The first patch has an attachment that includes the latter two, because they don't apply cleanly together. The only essential change to dbi.h is CALLCONV. There's also a warning in the initialization of noMethods in dbi.c. I'm not submitting a patch at this time, because I'd like to experiment with a DBI-less ODBC module. I'm not sure how to test ODBC without a DBMS and a DSN, so I don't have any tests, right now. There has been some discussion on the unixODBC list about developing an ODBC test framework. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-05-18 08:00 Message: Logged In: YES user_id=14198 I would be happy to support that - particularly if the changes came with a few tests - we don't have any at the moment, and that alone would be a big improvement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=955432&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-18 21:16:51
|
Bugs item #955432, was opened at 2004-05-17 20:01 Message generated for change (Comment added) made by willeke You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=955432&group_id=78018 Category: win32 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: odbc module not portable Initial Comment: I'm interested in using the ODBC module with unixODBC and/or iODBC on Linux. I've gotten it to work, after a fashion, with Python 2.3.3 and unixODBC 2.2.8 on SuSE Linux 8.2. I'd like to know how receptive you would be to portability patches. One category of changes conditionally compiles the Windows-specific things: windows.h, __declspec, etc. Another category of changes removes the few C++ things in an otherwise C-compatible module: declarations, comments, map(), etc. This is mostly in odbc.cpp, but there are also a few changes to dbi.h and dbi.cpp. ---------------------------------------------------------------------- >Comment By: Jon Willeke (willeke) Date: 2004-05-18 21:16 Message: Logged In: YES user_id=185468 The datetime module's C API is not fully baked, so I guess we're stuck with DBI, for a while. I submitted patches #956244 and #956247 to remove Windows and C++ dependencies. BTW, I think I omitted the -u option on some of the patches I submitted. Let me know if you have any problems with them. ---------------------------------------------------------------------- Comment By: Jon Willeke (willeke) Date: 2004-05-18 17:53 Message: Logged In: YES user_id=185468 I've submitted patches #956091, #956093, and #956094. The first patch has an attachment that includes the latter two, because they don't apply cleanly together. The only essential change to dbi.h is CALLCONV. There's also a warning in the initialization of noMethods in dbi.c. I'm not submitting a patch at this time, because I'd like to experiment with a DBI-less ODBC module. I'm not sure how to test ODBC without a DBMS and a DSN, so I don't have any tests, right now. There has been some discussion on the unixODBC list about developing an ODBC test framework. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-05-17 22:00 Message: Logged In: YES user_id=14198 I would be happy to support that - particularly if the changes came with a few tests - we don't have any at the moment, and that alone would be a big improvement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=955432&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-18 21:13:16
|
Patches item #956247, was opened at 2004-05-18 21:13 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=956247&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: convert C++ comments to C in dbi.cpp Initial Comment: This is one more (probably the last, for a while) patch for bug #955432 that converts C++ comments in dbi.cpp to C, so that it is C compatible. I also fixed a warning in the initialization of noMethods. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=956247&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-18 21:06:05
|
Patches item #956244, was opened at 2004-05-18 21:06 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=956244&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: platform portability patch for dbi.h Initial Comment: This is another patch for bug #955432 that replaces the CALLCONV macro in dbi.h with PyAPI_FUNC. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=956244&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-18 17:53:01
|
Bugs item #955432, was opened at 2004-05-17 20:01 Message generated for change (Comment added) made by willeke You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=955432&group_id=78018 Category: win32 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: odbc module not portable Initial Comment: I'm interested in using the ODBC module with unixODBC and/or iODBC on Linux. I've gotten it to work, after a fashion, with Python 2.3.3 and unixODBC 2.2.8 on SuSE Linux 8.2. I'd like to know how receptive you would be to portability patches. One category of changes conditionally compiles the Windows-specific things: windows.h, __declspec, etc. Another category of changes removes the few C++ things in an otherwise C-compatible module: declarations, comments, map(), etc. This is mostly in odbc.cpp, but there are also a few changes to dbi.h and dbi.cpp. ---------------------------------------------------------------------- >Comment By: Jon Willeke (willeke) Date: 2004-05-18 17:53 Message: Logged In: YES user_id=185468 I've submitted patches #956091, #956093, and #956094. The first patch has an attachment that includes the latter two, because they don't apply cleanly together. The only essential change to dbi.h is CALLCONV. There's also a warning in the initialization of noMethods in dbi.c. I'm not submitting a patch at this time, because I'd like to experiment with a DBI-less ODBC module. I'm not sure how to test ODBC without a DBMS and a DSN, so I don't have any tests, right now. There has been some discussion on the unixODBC list about developing an ODBC test framework. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-05-17 22:00 Message: Logged In: YES user_id=14198 I would be happy to support that - particularly if the changes came with a few tests - we don't have any at the moment, and that alone would be a big improvement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=955432&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-18 17:40:58
|
Patches item #956091, was opened at 2004-05-18 17:37 Message generated for change (Comment added) made by willeke You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=956091&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: minimal platform portability patch for odbc.cpp Initial Comment: This is the first of three patches addressing bug #955432. It is a minimal patch to allow odbc.cpp to be compiled by GNU g++ on Linux. Since the three patches don't apply cleanly on top of each other, I'm also attaching a complete patch. The first change conditions the inclusion of windows.h on MS_WINDOWS, which is defined in pyconfig.h (included by Python.h). The second change defines NOMINMAX within the MS_WINDOWS condition, to inhibit the definition of the Visual C++-specific max() macro. The third change defines a max() function. I did this, rather than use the max template function, in anticipation of making the module C compatible. The fourth change replaces NULL with 0, where the function returns int. The fifth change fixes the use of Visual C++-specific for-loop scoping. The final change replaces extern "C" __declspec with PyMODINIT_FUNC. ---------------------------------------------------------------------- >Comment By: Jon Willeke (willeke) Date: 2004-05-18 17:40 Message: Logged In: YES user_id=185468 Here's the complete patch, including #956093 and #956094. By the way, these are all against pywin32 201.1. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=956091&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-18 17:38:21
|
Patches item #956094, was opened at 2004-05-18 17:38 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=956094&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: convert C++ comments to C in odbc.cpp Initial Comment: This is the third of three patches addressing bug #955432. It changes the C++ comments in odbc.cpp to C comments, for compatibility with C90 compilers, like gcc in -ansi or std=c89 mode. I'm not familiar with autoduck; if someone uses it, he'll need to confirm that these changes don't break it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=956094&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-18 17:37:55
|
Patches item #956093, was opened at 2004-05-18 17:37 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=956093&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: minimal C portability patch for odbc.cpp Initial Comment: This is the second of three patches addressing bug #955432. It is a minimal patch to allow odbc.cpp to be compiled by GNU gcc on Linux (in which case it should be renamed to odbc.c). The code remains C++ compatible. The first change defines bool, true, and false in a block conditioned on _cplusplus. The second change moves a variable definition out of a for-loop initializer. If you apply this patch after the previous patch, this change won't apply cleanly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=956093&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-18 17:37:23
|
Patches item #956091, was opened at 2004-05-18 17:37 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=956091&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: minimal platform portability patch for odbc.cpp Initial Comment: This is the first of three patches addressing bug #955432. It is a minimal patch to allow odbc.cpp to be compiled by GNU g++ on Linux. Since the three patches don't apply cleanly on top of each other, I'm also attaching a complete patch. The first change conditions the inclusion of windows.h on MS_WINDOWS, which is defined in pyconfig.h (included by Python.h). The second change defines NOMINMAX within the MS_WINDOWS condition, to inhibit the definition of the Visual C++-specific max() macro. The third change defines a max() function. I did this, rather than use the max template function, in anticipation of making the module C compatible. The fourth change replaces NULL with 0, where the function returns int. The fifth change fixes the use of Visual C++-specific for-loop scoping. The final change replaces extern "C" __declspec with PyMODINIT_FUNC. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=956091&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-17 22:04:30
|
Patches item #944453, was opened at 2004-04-29 23:07 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=944453&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: alch (alch) Assigned to: Mark Hammond (mhammond) Summary: win32gui patch to enable balloon tooltips Initial Comment: Hi, I am using this patch in clamwin (http://clamwin.sourceforge.net) to display balloon tool-tips in the tray icon. It requires Internet Explorer 5.0 or higher on pre-XP Windows, but nowadays this seems to be no problem. I created the patch against current cvs. Regards, Alech ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2004-05-18 08:04 Message: Logged In: YES user_id=14198 There is no patch attached! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=944453&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-17 22:03:28
|
Feature Requests item #955095, was opened at 2004-05-17 15:17 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=955095&group_id=78018 Category: win32 Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Tom Flanagan (knio) Assigned to: Nobody/Anonymous (nobody) Summary: win32api: missing functions Initial Comment: SystemParametersInfo EnumWindows ShowWindow GetWindowRect SetWindowPlacement GetWindowPlacement GetWindowText IsWindowVisible MoveWindow SetWindowsHookEx UnhookWindowsHookEx To name a few. Any reason these haven't been implemented yet? I feel like i'm missing something here. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2004-05-18 08:03 Message: Logged In: YES user_id=14198 Many of these functions are implemented in the win32gui module. A few aren't, and I'd be happy to receive patches which add them. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=955095&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-17 22:00:40
|
Bugs item #955432, was opened at 2004-05-18 06:01 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=955432&group_id=78018 Category: win32 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: odbc module not portable Initial Comment: I'm interested in using the ODBC module with unixODBC and/or iODBC on Linux. I've gotten it to work, after a fashion, with Python 2.3.3 and unixODBC 2.2.8 on SuSE Linux 8.2. I'd like to know how receptive you would be to portability patches. One category of changes conditionally compiles the Windows-specific things: windows.h, __declspec, etc. Another category of changes removes the few C++ things in an otherwise C-compatible module: declarations, comments, map(), etc. This is mostly in odbc.cpp, but there are also a few changes to dbi.h and dbi.cpp. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2004-05-18 08:00 Message: Logged In: YES user_id=14198 I would be happy to support that - particularly if the changes came with a few tests - we don't have any at the moment, and that alone would be a big improvement. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=955432&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-17 20:01:25
|
Bugs item #955432, was opened at 2004-05-17 20: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=955432&group_id=78018 Category: win32 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jon Willeke (willeke) Assigned to: Nobody/Anonymous (nobody) Summary: odbc module not portable Initial Comment: I'm interested in using the ODBC module with unixODBC and/or iODBC on Linux. I've gotten it to work, after a fashion, with Python 2.3.3 and unixODBC 2.2.8 on SuSE Linux 8.2. I'd like to know how receptive you would be to portability patches. One category of changes conditionally compiles the Windows-specific things: windows.h, __declspec, etc. Another category of changes removes the few C++ things in an otherwise C-compatible module: declarations, comments, map(), etc. This is mostly in odbc.cpp, but there are also a few changes to dbi.h and dbi.cpp. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=955432&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-05-17 05:17:14
|
Feature Requests item #955095, was opened at 2004-05-16 23:17 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=955095&group_id=78018 Category: win32 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tom Flanagan (knio) Assigned to: Nobody/Anonymous (nobody) Summary: win32api: missing functions Initial Comment: SystemParametersInfo EnumWindows ShowWindow GetWindowRect SetWindowPlacement GetWindowPlacement GetWindowText IsWindowVisible MoveWindow SetWindowsHookEx UnhookWindowsHookEx To name a few. Any reason these haven't been implemented yet? I feel like i'm missing something here. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=955095&group_id=78018 |
2 messages has been excluded from this view by a project administrator.
