pywin32-bugs Mailing List for Python for Windows Extensions (Page 40)
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...> - 2009-11-12 21:36:07
|
Patches item #2896861, was opened at 2009-11-13 03:06 Message generated for change (Tracker Item Submitted) made by nearfar You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=2896861&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sridhar Ratnakumar (nearfar) Assigned to: Nobody/Anonymous (nobody) Summary: AutoDuck Py3k port Initial Comment: Hey Mark, This is Sridhar from ActiveState. Since Trent is involved with Komodo, I am working on ActivePython these days. While working on supporting pywin32 for ActivePython-3.x, I had to port AutoDuck to Python 3.1. I'm attaching the patch here. Please review. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=2896861&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-11-11 17:25:34
|
Patches item #2896067, was opened at 2009-11-11 22:55 Message generated for change (Tracker Item Submitted) made by nearfar You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=2896067&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sridhar Ratnakumar (nearfar) Assigned to: Nobody/Anonymous (nobody) Summary: Patch for a successful "setup.py --prefix" Initial Comment: Since APy build scripts run "setup.py install --prefix=<path to image dir>", we should use distutils' self.prefix (instead of sys.prefix - that points to the Python build directory) when finding previously installed file. Index: pywin32/setup.py =================================================================== --- pywin32/setup.py.orig 2009-11-10 17:00:30.000000000 -0800 +++ pywin32/setup.py 2009-11-10 17:00:49.000000000 -0800 @@ -1283,7 +1283,7 @@ if not self.dry_run and not self.root: # We must run the script we just installed into Scripts, as it # may have had 2to3 run over it. - filename = os.path.join(sys.prefix, "Scripts", "pywin32_postinstall.py") + filename = os.path.join(self.prefix, "Scripts", "pywin32_postinstall.py") if not os.path.isfile(filename): raise RuntimeError("Can't find '%s'" % (filename,)) print "Executing post install script..." ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=2896067&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-11-11 01:15:17
|
Bugs item #2895488, was opened at 2009-11-11 08:37 Message generated for change (Settings changed) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2895488&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Sridhar Ratnakumar (nearfar) >Assigned to: Mark Hammond (mhammond) Summary: win32/help/ is missing Initial Comment: the 214 source tarball is missing the win32/help/ directory. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2009-11-11 12:15 Message: Thanks - I've made the fix locally and will commit it after I next test the build. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2895488&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-11-10 21:37:13
|
Bugs item #2895488, was opened at 2009-11-11 03:07 Message generated for change (Tracker Item Submitted) made by nearfar You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2895488&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sridhar Ratnakumar (nearfar) Assigned to: Nobody/Anonymous (nobody) Summary: win32/help/ is missing Initial Comment: the 214 source tarball is missing the win32/help/ directory. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2895488&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-11-01 21:27:27
|
Bugs item #2890181, was opened at 2009-11-01 16:43 Message generated for change (Settings changed) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2890181&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: win32 Group: None >Status: Closed Resolution: Invalid Priority: 5 Private: No Submitted By: Andrew Ziem (andrewziem) Assigned to: Nobody/Anonymous (nobody) Summary: GetOpenFileNameW doesn't support unicode Initial Comment: Calling win32gui.GetOpenFileNameW with a unicode (German umlaut) title causes poor display of characters. Tested with Python 2.5.4 and pywin32-213.win32-py2.5.exe. I'll attach example code. Interesting that shell.SHBrowseForFolder works OK with umlaut. ---------------------------------------------------------------------- Comment By: Andrew Ziem (andrewziem) Date: 2009-11-02 02:53 Message: Sorry, I didn't pass the data correctly ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2890181&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-11-01 15:53:08
|
Bugs item #2890181, was opened at 2009-10-31 22:43 Message generated for change (Settings changed) made by andrewziem You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2890181&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: win32 Group: None Status: Open >Resolution: Invalid Priority: 5 Private: No Submitted By: Andrew Ziem (andrewziem) Assigned to: Nobody/Anonymous (nobody) Summary: GetOpenFileNameW doesn't support unicode Initial Comment: Calling win32gui.GetOpenFileNameW with a unicode (German umlaut) title causes poor display of characters. Tested with Python 2.5.4 and pywin32-213.win32-py2.5.exe. I'll attach example code. Interesting that shell.SHBrowseForFolder works OK with umlaut. ---------------------------------------------------------------------- >Comment By: Andrew Ziem (andrewziem) Date: 2009-11-01 08:53 Message: Sorry, I didn't pass the data correctly ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2890181&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-11-01 05:43:57
|
Bugs item #2890181, was opened at 2009-10-31 22:43 Message generated for change (Tracker Item Submitted) made by andrewziem You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2890181&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: win32 Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Andrew Ziem (andrewziem) Assigned to: Nobody/Anonymous (nobody) Summary: GetOpenFileNameW doesn't support unicode Initial Comment: Calling win32gui.GetOpenFileNameW with a unicode (German umlaut) title causes poor display of characters. Tested with Python 2.5.4 and pywin32-213.win32-py2.5.exe. I'll attach example code. Interesting that shell.SHBrowseForFolder works OK with umlaut. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2890181&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-10-14 02:21:08
|
Bugs item #2869632, was opened at 2009-09-29 09:38 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2869632&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: com Group: None >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: David Moore (igalboc) Assigned to: Nobody/Anonymous (nobody) Summary: win32com makepy has a print statement in it Initial Comment: It is very difficult to redirect print statements when using win32com inside an application, and extra verbosity on the command line can confuse users. Please change to using the standard logging module for errors and warnings, as these can be managed more effectively. The print statement should at the least be changed to a sys.stderr write to match the other errors. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2009-10-14 02:21 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2009-09-29 10:00 Message: sounds reasonable - please consider sending a patch... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2869632&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-29 10:00:13
|
Bugs item #2869632, was opened at 2009-09-29 19:38 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2869632&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: com Group: None >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: David Moore (igalboc) Assigned to: Nobody/Anonymous (nobody) Summary: win32com makepy has a print statement in it Initial Comment: It is very difficult to redirect print statements when using win32com inside an application, and extra verbosity on the command line can confuse users. Please change to using the standard logging module for errors and warnings, as these can be managed more effectively. The print statement should at the least be changed to a sys.stderr write to match the other errors. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2009-09-29 20:00 Message: sounds reasonable - please consider sending a patch... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2869632&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-29 09:38:31
|
Bugs item #2869632, was opened at 2009-09-29 11:38 Message generated for change (Tracker Item Submitted) made by igalboc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2869632&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: com Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: David Moore (igalboc) Assigned to: Nobody/Anonymous (nobody) Summary: win32com makepy has a print statement in it Initial Comment: It is very difficult to redirect print statements when using win32com inside an application, and extra verbosity on the command line can confuse users. Please change to using the standard logging module for errors and warnings, as these can be managed more effectively. The print statement should at the least be changed to a sys.stderr write to match the other errors. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2869632&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-28 17:24:51
|
Bugs item #1799934, was opened at 2007-09-21 20:29 Message generated for change (Comment added) made by zooko You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1799934&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: installation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Zooko O'Whielacronx (zooko) Assigned to: Nobody/Anonymous (nobody) Summary: easy_install silently fails Initial Comment: If I install pywin32 by executing pywin32-210.win32-py2.5.exe , it works. If I run "easy_install pywin32" then it claims that it is downloading and installing pywin32-210.win32-py2.5.exe , and after a while it claims that it has successfully installed it, but an attempt to use pywin32 yields errors like this: $ python -c 'import win32process' Traceback (most recent call last): File "<string>", line 1, in <module> ImportError: DLL load failed: The specified module could not be found. I'm not sure whether this should be considered a bug in pywin32 or in easy_install, or both. Regards, Zooko ---------------------------------------------------------------------- >Comment By: Zooko O'Whielacronx (zooko) Date: 2009-09-28 17:24 Message: Hey good news! I used distribute v0.6.3 from http://pypi.python.org/pypi/distribute and gave it this URL: http://downloads.sourceforge.net/project/pywin32/pywin32/Build%20214/pywin32-214.win32-py2.6.exe?use_mirror=softlayer and it worked! Here is the command line that I executed: easy_install -v "http://downloads.sourceforge.net/project/pywin32/pywin32/Build%20214/pywin32-214.win32-py2.6.exe?use_mirror=softlayer" so, if only pywin32 were hosted on pypi or if a direct link to the .exe's were registered in the metadata which is hosted on pypi then a simple 'easy_install pywin32' would work, and so would automatic installation of pywin32 when installing projects which specify that they depend on pywin32 in their setup.py. So please upload the pywin32 binaries to pypi, or else configure the metadata to point to some URL (I'm afraid I'm not sure which one) which will let easy_install find the binaries on sf.net. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2009-02-13 22:28 Message: Well, I think I was wrong when I said that pywin32 212 can be easy_install'ed. Probably I accidentally already had pywin32 installed when I tested it. I just tested it again and it doesn't work -- ImportError win32api. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2009-01-02 18:10 Message: Having pywin32 hosted somewhere that easy_install will discover is needed for the imminent release of tahoe-lafs v1.3.0. However, if the current release of pywin32 is not hosted on pypi, we can instead upload a copy of the pywin32 package to a tahoe grid. :-) http://allmydata.org/trac/tahoe/ticket/566 # host tahoe dependencies on a tahoe grid ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-12-29 17:19 Message: Please upload pywin32 212 to http://pypi.python.org and then we can close this ticket. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-12-03 12:07 Message: Okay I just tested pywin32 212 with the latest trunk of setuptools (0.6c10dev), and it worked! However, the pywin32 package is not linked from http://pypi.python.org/simple/pywin32 , so easy_install doesn't know how to download it. Please put a link on http://pypi.python.org/simple/pywin32 pointing to the 212 binaries and this ticket is done. ---------------------------------------------------------------------- Comment By: Hartmut Goebel (htgoebel) Date: 2008-09-04 10:29 Message: Logged In: YES user_id=376953 Originator: NO There are actually two problems: 1) pywin32_postinstall.py can not be run manually when using eggs since it does not use pkg_resources. This is fixed by patch 2092722 <http://sourceforge.net/tracker/index.php?func=detail&aid=2092722&group_id=78018&atid=551956>. 2) easy_install does not run pywin32_postinstall.py. It looks like there is no mechanism to do this. This problem has been filed at <http://bugs.python.org/setuptools/issue18> ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-06-02 20:31 Message: Logged In: YES user_id=52562 Originator: YES This is the ticket on the setuptools issue tracker to track the progress of fixing this in setuptools: http://bugs.python.org/setuptools/issue18 ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2008-05-03 01:30 Message: Logged In: YES user_id=14198 Originator: NO That installer is quite recent - you may need to get the latest setuptools rather than the latest pywin32. Either way, just grab the CVS sources, install the Vista SDK, and execute "setup.py" - to get some basic instructions printed. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-05-03 00:56 Message: Logged In: YES user_id=52562 Originator: YES Well, I'm afraid that starship.python.net/crew/mhammond/pywin32-210.9.win32-py2.5.exe doesn't work with the current setuptools -- setuptools v0.6 final. Could you tell me how to build pywin32 packages from CVS so I can experiment? Thanks. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2008-05-03 00:39 Message: Logged In: YES user_id=14198 Originator: NO Try starship.python.net/crew/mhammond/pywin32-210.9.win32-py2.5.exe. Note I'm not sure of the status of the bug I referred to - ie, I'm not sure if a released version of setuptools has the bug fixed (but I assume you are ontop of that :) ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-05-02 17:48 Message: Logged In: YES user_id=52562 Originator: YES Hi, I went to test this so I could definitely close this bug, but it turns out that pywin32 build 211 isn't downloadable yet. ---------------------------------------------------------------------- Comment By: SourceForge Robot (sf-robot) Date: 2008-04-23 02:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2008-04-08 21:20 Message: Logged In: YES user_id=14198 Originator: NO I believe PJE recently fixed a bug in setuptools that was causing problems with pywin32 as an egg. Please try again after build 211 is released. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2008-01-25 14:17 Message: Logged In: YES user_id=52562 Originator: YES See also: http://mail.python.org/pipermail/distutils-sig/2007-July/007823.html ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2007-09-30 23:33 Message: Logged In: YES user_id=14198 Originator: NO I've no idea - that too is an easy_install question. I've never used easy_install to install pywin32, and I've never recommended anyone else do it either. ---------------------------------------------------------------------- Comment By: Zooko O'Whielacronx (zooko) Date: 2007-09-30 22:57 Message: Logged In: YES user_id=52562 Originator: YES I will see if I can make the pywin32_postinstall.py stuff get done automatically upon easy_install. In the meantime, is there some way to make this failure loud instead of silent? How do you tell easy_install: yes, there is a package in the expected format (.zip) in the expected place (pypi), but it isn't actually going to work? ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2007-09-21 23:57 Message: Logged In: YES user_id=14198 Originator: NO After install, pywin32_postinstall.py needs to be run, but ezsetup apparently does not provide a facility to do that. You may like to ask them for such a facility. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1799934&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-17 22:51:42
|
Bugs item #2860921, was opened at 2009-09-18 06:14 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2860921&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Wont Fix Priority: 5 Private: No Submitted By: dmitryam (dmitryam) Assigned to: Nobody/Anonymous (nobody) Summary: PyTime broken in python 3.1 Initial Comment: Python 2.x and 3.x have different handling of pytime when you need to create a datetime object for COM from a python datetime object Here is the example which can show you the difference in 2.x and 3.1 import pywintypes import datetime x = datetime.datetime(2009,1,1) y = pywintypes.Time(x) print(type(x),type(y)) ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2009-09-18 08:51 Message: pywin32 has moved to datetime objects in Python 3.x, so differences are expected, particularly when printing dates and times. This was a design decision and can't be fixed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2860921&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-17 20:14:10
|
Bugs item #2860921, was opened at 2009-09-18 00:14 Message generated for change (Tracker Item Submitted) made by dmitryam You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2860921&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: dmitryam (dmitryam) Assigned to: Nobody/Anonymous (nobody) Summary: PyTime broken in python 3.1 Initial Comment: Python 2.x and 3.x have different handling of pytime when you need to create a datetime object for COM from a python datetime object Here is the example which can show you the difference in 2.x and 3.1 import pywintypes import datetime x = datetime.datetime(2009,1,1) y = pywintypes.Time(x) print(type(x),type(y)) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2860921&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-14 22:24:16
|
Bugs item #2858719, was opened at 2009-09-15 03:40 Message generated for change (Settings changed) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2858719&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: com Group: None >Status: Closed >Resolution: Wont Fix Priority: 5 Private: No Submitted By: Cyrille Rey (cyr34) Assigned to: Nobody/Anonymous (nobody) Summary: win32com can be used only one time in embedded python Initial Comment: Hello all I embed python interpreters in a C++ program. For each script to execute I create a new interpreter. In this environment I can use the win32 extensions only one time. Here is a little piece of code to illustrate the problem: int main(int argc, char **argv) { Py_Initialize(); Py_SetProgramName(argv[0]); PyThreadState *save_tstate=PyThreadState_Swap(NULL); PyThreadState *state=Py_NewInterpreter(); int rc=PyRun_SimpleString("import sys\nimport win32com.client\nw=win32com.client.Dispatch("Word.Application")\nw.Visible = 1\n"); //this works well printf("%d\n",rc); Py_EndInterpreter(state); PyThreadState_Swap(save_tstate); state=Py_NewInterpreter(); rc=PyRun_SimpleString("import sys\nimport win32com.client\nw=win32com.client.Dispatch("Word.Application")\nw.Visible = 1\n"); //this and all further atemps will fail printf("%d\n",rc); Py_EndInterpreter(state); PyThreadState_Swap(save_tstate); ; } Here is the output of this little program: Traceback (most recent call last): File "<string>", line 8 (13), in <module> File "C:\cre\2009.2\techlog\PythonScripts\External261_x86\win32com\__init__.py", line 6, in <module> import pythoncom File "C:\cre\2009.2\techlog\PythonScripts\External261_x86\Lib\pythoncom.py", line 3, in <module> File "C:\cre\2009.2\techlog\PythonScripts\External261_x86\Lib\pywintypes.py", line 20, in __import_pywin32_system_module__ TypeError: 'NoneType' object is not callable I use Python 2.6 compiled with MSC v.8 32 bit (Intel)] on win32 with Pywin32- 214 Is there any way to overcome this problem? ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2009-09-15 08:23 Message: Sorry, this is a limitation of the PyGILState API used by pywin32; pywin32 will never be able to play with the multiple interpreter API, nor work correctly with multiple interpreter initializations and cleanups ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2858719&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-14 17:40:06
|
Bugs item #2858719, was opened at 2009-09-14 19:40 Message generated for change (Tracker Item Submitted) made by cyr34 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2858719&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: com Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Cyrille Rey (cyr34) Assigned to: Nobody/Anonymous (nobody) Summary: win32com can be used only one time in embedded python Initial Comment: Hello all I embed python interpreters in a C++ program. For each script to execute I create a new interpreter. In this environment I can use the win32 extensions only one time. Here is a little piece of code to illustrate the problem: int main(int argc, char **argv) { Py_Initialize(); Py_SetProgramName(argv[0]); PyThreadState *save_tstate=PyThreadState_Swap(NULL); PyThreadState *state=Py_NewInterpreter(); int rc=PyRun_SimpleString("import sys\nimport win32com.client\nw=win32com.client.Dispatch("Word.Application")\nw.Visible = 1\n"); //this works well printf("%d\n",rc); Py_EndInterpreter(state); PyThreadState_Swap(save_tstate); state=Py_NewInterpreter(); rc=PyRun_SimpleString("import sys\nimport win32com.client\nw=win32com.client.Dispatch("Word.Application")\nw.Visible = 1\n"); //this and all further atemps will fail printf("%d\n",rc); Py_EndInterpreter(state); PyThreadState_Swap(save_tstate); ; } Here is the output of this little program: Traceback (most recent call last): File "<string>", line 8 (13), in <module> File "C:\cre\2009.2\techlog\PythonScripts\External261_x86\win32com\__init__.py", line 6, in <module> import pythoncom File "C:\cre\2009.2\techlog\PythonScripts\External261_x86\Lib\pythoncom.py", line 3, in <module> File "C:\cre\2009.2\techlog\PythonScripts\External261_x86\Lib\pywintypes.py", line 20, in __import_pywin32_system_module__ TypeError: 'NoneType' object is not callable I use Python 2.6 compiled with MSC v.8 32 bit (Intel)] on win32 with Pywin32- 214 Is there any way to overcome this problem? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2858719&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-12 18:18:23
|
Patches item #2857646, was opened at 2009-09-12 13:18 Message generated for change (Tracker Item Submitted) made by smichr You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=2857646&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christopher Smith (smichr) Assigned to: Nobody/Anonymous (nobody) Summary: all trailing space stripped on enter Initial Comment: AutoIndent.py strips trailing space UNLESS the line happens to contain only space. This patch makes it strip that space, too. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=2857646&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-12 01:50:53
|
Bugs item #2857273, was opened at 2009-09-12 10:02 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Wont Fix Priority: 5 Private: No Submitted By: no_hope (no_hope) Assigned to: Nobody/Anonymous (nobody) Summary: Handling type complex Initial Comment: I think win32com may not handle Python's complex type correctly. I use win32com client to manipulate variable inside LabVIEW. When I read LabVIEW's complex variable it is returned as a tuple. However, when I try to write to a LabVIEW's complex variable using tuple, I get pywintypes.com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147352571), 2) in ._oleobj_.InvokeTypes as if there is type mismatch. If I supply an object of type complex, win32com is happy but LabVIEW complains (presumably because it wants a tuple). Is it possible that this is a bug since win32com client sometimes uses tuple and sometimes complex for the same object? ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2009-09-12 11:50 Message: Yeah, that exception is a COM error thrown by labview. To be quite honest, I'm not sure what type win32com will attempt to pass in that case, but there is no simple COM type which can represent a complex number ---------------------------------------------------------------------- Comment By: no_hope (no_hope) Date: 2009-09-12 10:17 Message: Then how come win32com gives me an error unless I give it a an object of type complex? Or is pywintypes.com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147352571), 2) LabVIEW's exception, not win32com's? ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2009-09-12 10:08 Message: COM doesn't define a complex type, so win32com doesn't either. I've no idea what LabVIEW would be expecting to be passed here - but I'm guessing it uses a simple array of 2 integers or floats, which is what makes you think win32com sometimes uses a tuple. You probably need to ask the labview guys what they use to represent a complex number. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-12 00:17:01
|
Bugs item #2857273, was opened at 2009-09-12 00:02 Message generated for change (Comment added) made by no_hope You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Wont Fix Priority: 5 Private: No Submitted By: no_hope (no_hope) Assigned to: Nobody/Anonymous (nobody) Summary: Handling type complex Initial Comment: I think win32com may not handle Python's complex type correctly. I use win32com client to manipulate variable inside LabVIEW. When I read LabVIEW's complex variable it is returned as a tuple. However, when I try to write to a LabVIEW's complex variable using tuple, I get pywintypes.com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147352571), 2) in ._oleobj_.InvokeTypes as if there is type mismatch. If I supply an object of type complex, win32com is happy but LabVIEW complains (presumably because it wants a tuple). Is it possible that this is a bug since win32com client sometimes uses tuple and sometimes complex for the same object? ---------------------------------------------------------------------- Comment By: no_hope (no_hope) Date: 2009-09-12 00:17 Message: Then how come win32com gives me an error unless I give it a an object of type complex? Or is pywintypes.com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147352571), 2) LabVIEW's exception, not win32com's? ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2009-09-12 00:08 Message: COM doesn't define a complex type, so win32com doesn't either. I've no idea what LabVIEW would be expecting to be passed here - but I'm guessing it uses a simple array of 2 integers or floats, which is what makes you think win32com sometimes uses a tuple. You probably need to ask the labview guys what they use to represent a complex number. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-12 00:09:21
|
Bugs item #2857273, was opened at 2009-09-12 10:02 Message generated for change (Settings changed) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: Wont Fix Priority: 5 Private: No Submitted By: no_hope (no_hope) Assigned to: Nobody/Anonymous (nobody) Summary: Handling type complex Initial Comment: I think win32com may not handle Python's complex type correctly. I use win32com client to manipulate variable inside LabVIEW. When I read LabVIEW's complex variable it is returned as a tuple. However, when I try to write to a LabVIEW's complex variable using tuple, I get pywintypes.com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147352571), 2) in ._oleobj_.InvokeTypes as if there is type mismatch. If I supply an object of type complex, win32com is happy but LabVIEW complains (presumably because it wants a tuple). Is it possible that this is a bug since win32com client sometimes uses tuple and sometimes complex for the same object? ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2009-09-12 10:08 Message: COM doesn't define a complex type, so win32com doesn't either. I've no idea what LabVIEW would be expecting to be passed here - but I'm guessing it uses a simple array of 2 integers or floats, which is what makes you think win32com sometimes uses a tuple. You probably need to ask the labview guys what they use to represent a complex number. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-12 00:08:59
|
Bugs item #2857273, was opened at 2009-09-12 10:02 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open >Resolution: Wont Fix Priority: 5 Private: No Submitted By: no_hope (no_hope) Assigned to: Nobody/Anonymous (nobody) Summary: Handling type complex Initial Comment: I think win32com may not handle Python's complex type correctly. I use win32com client to manipulate variable inside LabVIEW. When I read LabVIEW's complex variable it is returned as a tuple. However, when I try to write to a LabVIEW's complex variable using tuple, I get pywintypes.com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147352571), 2) in ._oleobj_.InvokeTypes as if there is type mismatch. If I supply an object of type complex, win32com is happy but LabVIEW complains (presumably because it wants a tuple). Is it possible that this is a bug since win32com client sometimes uses tuple and sometimes complex for the same object? ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2009-09-12 10:08 Message: COM doesn't define a complex type, so win32com doesn't either. I've no idea what LabVIEW would be expecting to be passed here - but I'm guessing it uses a simple array of 2 integers or floats, which is what makes you think win32com sometimes uses a tuple. You probably need to ask the labview guys what they use to represent a complex number. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-12 00:02:17
|
Bugs item #2857273, was opened at 2009-09-12 00:02 Message generated for change (Tracker Item Submitted) made by no_hope You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: no_hope (no_hope) Assigned to: Nobody/Anonymous (nobody) Summary: Handling type complex Initial Comment: I think win32com may not handle Python's complex type correctly. I use win32com client to manipulate variable inside LabVIEW. When I read LabVIEW's complex variable it is returned as a tuple. However, when I try to write to a LabVIEW's complex variable using tuple, I get pywintypes.com_error: (-2147352567, 'Exception occurred.', (0, None, None, None, 0, -2147352571), 2) in ._oleobj_.InvokeTypes as if there is type mismatch. If I supply an object of type complex, win32com is happy but LabVIEW complains (presumably because it wants a tuple). Is it possible that this is a bug since win32com client sometimes uses tuple and sometimes complex for the same object? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2857273&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-02 23:33:43
|
Bugs item #2820666, was opened at 2009-07-13 19:23 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2820666&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ignacio Perez (trancos7) Assigned to: Nobody/Anonymous (nobody) Summary: Install problem XP Initial Comment: When I try to install pywin32-214.win32-py3.1.exe on a system with Windows XP SP3 the installation finish with this message: Copied pythoncom31.dll to C:\WINDOWS\system32\pythoncom31.dll Copied pywintypes31.dll to C:\WINDOWS\system32\pywintypes31.dll Registered: Python.Interpreter Registered: Python.Dictionary Registered: Python -> Software\Python\PythonCore\3.1\Help[None]=None -> Software\Python\PythonCore\3.1\Help\Pythonwin Reference[None]='C:\\Python31\\Lib\\site-packages\\PyWin32.chm' Failed to register pythonwin as editor 'utf8' codec can't decode bytes in position 39-43: unsupported Unicode code range The pywin32 extensions were successfully installed. Traceback (most recent call last): File "<string>", line 398, in install File "<string>", line 208, in RegisterPythonwin WindowsError: [Error 5] Acceso denegado The user has admin rights. Thanks in advance. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2009-09-03 09:33 Message: and the next question is why utf8 is even being attempted here... ---------------------------------------------------------------------- Comment By: Ignacio Perez (trancos7) Date: 2009-09-02 22:03 Message: My OS language and locale are spanish. ---------------------------------------------------------------------- Comment By: Vernon Cole (kf7xm) Date: 2009-09-02 05:04 Message: This appears to be a non-English installation of Windows -- with a filename which cannot be decoded using utf8. What language / locale are you using? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2820666&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-02 12:03:20
|
Bugs item #2820666, was opened at 2009-07-13 11:23 Message generated for change (Comment added) made by trancos7 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2820666&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ignacio Perez (trancos7) Assigned to: Nobody/Anonymous (nobody) Summary: Install problem XP Initial Comment: When I try to install pywin32-214.win32-py3.1.exe on a system with Windows XP SP3 the installation finish with this message: Copied pythoncom31.dll to C:\WINDOWS\system32\pythoncom31.dll Copied pywintypes31.dll to C:\WINDOWS\system32\pywintypes31.dll Registered: Python.Interpreter Registered: Python.Dictionary Registered: Python -> Software\Python\PythonCore\3.1\Help[None]=None -> Software\Python\PythonCore\3.1\Help\Pythonwin Reference[None]='C:\\Python31\\Lib\\site-packages\\PyWin32.chm' Failed to register pythonwin as editor 'utf8' codec can't decode bytes in position 39-43: unsupported Unicode code range The pywin32 extensions were successfully installed. Traceback (most recent call last): File "<string>", line 398, in install File "<string>", line 208, in RegisterPythonwin WindowsError: [Error 5] Acceso denegado The user has admin rights. Thanks in advance. ---------------------------------------------------------------------- Comment By: Ignacio Perez (trancos7) Date: 2009-09-02 14:03 Message: My OS language and locale are spanish. ---------------------------------------------------------------------- Comment By: Vernon Cole (kf7xm) Date: 2009-09-01 21:04 Message: This appears to be a non-English installation of Windows -- with a filename which cannot be decoded using utf8. What language / locale are you using? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2820666&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-09-01 19:04:08
|
Bugs item #2820666, was opened at 2009-07-13 03:23 Message generated for change (Comment added) made by kf7xm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2820666&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ignacio Perez (trancos7) Assigned to: Nobody/Anonymous (nobody) Summary: Install problem XP Initial Comment: When I try to install pywin32-214.win32-py3.1.exe on a system with Windows XP SP3 the installation finish with this message: Copied pythoncom31.dll to C:\WINDOWS\system32\pythoncom31.dll Copied pywintypes31.dll to C:\WINDOWS\system32\pywintypes31.dll Registered: Python.Interpreter Registered: Python.Dictionary Registered: Python -> Software\Python\PythonCore\3.1\Help[None]=None -> Software\Python\PythonCore\3.1\Help\Pythonwin Reference[None]='C:\\Python31\\Lib\\site-packages\\PyWin32.chm' Failed to register pythonwin as editor 'utf8' codec can't decode bytes in position 39-43: unsupported Unicode code range The pywin32 extensions were successfully installed. Traceback (most recent call last): File "<string>", line 398, in install File "<string>", line 208, in RegisterPythonwin WindowsError: [Error 5] Acceso denegado The user has admin rights. Thanks in advance. ---------------------------------------------------------------------- >Comment By: Vernon Cole (kf7xm) Date: 2009-09-01 13:04 Message: This appears to be a non-English installation of Windows -- with a filename which cannot be decoded using utf8. What language / locale are you using? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2820666&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2009-08-29 06:02:53
|
Bugs item #2846720, was opened at 2009-08-29 05:56 Message generated for change (Comment added) made by farshizzo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2846720&group_id=78018 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: win32 Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Farshid Lashkari (farshizzo) Assigned to: Nobody/Anonymous (nobody) Summary: win32ui crash in embedded app (212 -> 213 & 214 regression) Initial Comment: I have an application that embeds python and uses the win32ui module. Everything worked fine until I upgraded from 212 to 214. After the upgrade my application crashes on exit. The Visual Studio debugger is showing that the crash is occurring after my application calls CoUninitialize. Here is a rough outline of what my app does: CoInitialize(NULL) InitPython() RunPythonCode() //This code will import win32ui ClosePython() CoUninitialize() Simply importing the win32ui module causes the crash. I don't even need to call any of the modules functions. If I don't import win32ui then my application exits cleanly. I tried downgrading to version 213 but the crash still occurs. Version 212 seems to be the last version that was stable with my application. ---------------------------------------------------------------------- Comment By: Farshid Lashkari (farshizzo) Date: 2009-08-29 06:02 Message: Forgot to mention that I'm using Python 2.4 & 2.6, and both exhibit the same behavior. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=2846720&group_id=78018 |
2 messages has been excluded from this view by a project administrator.
