pywin32-bugs Mailing List for Python for Windows Extensions (Page 93)
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-11-30 01:35:02
|
Bugs item #1065008, was opened at 2004-11-12 08:25 Message generated for change (Comment added) made by jiangwen365 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 Category: None Group: None >Status: Closed Resolution: Invalid Priority: 5 Submitted By: 江文 (jiangwen365) Assigned to: Nobody/Anonymous (nobody) Summary: Contrary to the Doc,ODBC module not accept Connection String Initial Comment: It seems that the ODBC module only works with DNS names, but not Connection Strings, like: odbc.odbc(('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\aaa.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' ) will fail. But it IS said to be acceptable in odbc module documents. ---------------------------------------------------------------------- >Comment By: 江文 (jiangwen365) Date: 2004-11-30 01:34 Message: Logged In: YES user_id=1147025 I just find out it's not pywin32's problem. ODBC Connection string != OLE DB Connection string, so an ODBC interface would never accpet connection strings that are intended for ADO. ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-13 08:24 Message: Logged In: YES user_id=1147025 Hi Mhmmond, Yes, it seems that the ODBC module does accept connection strings, but has some restrictions on the format of the string. Per your information, I finally get the code worked after changing the connection string to r'Driver={Microsoft Excel Driver (*.xls)};DBQ=C:\FreightAuditTool\ChinaTruckInvoices.xls' . But it is strange thing that the module don't accept the former string which is the most common format and can be perfectly accepted by ADODB. Regards, Xiao Zhou ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-13 04:15 Message: Logged In: YES user_id=14198 I'm fairly certain that *some* datasource strings work fine with this module. Unfortunately, I don't know enough about this to know where to start. ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-13 03:59 Message: Logged In: YES user_id=1147025 Oh, yes, but I think this is not the cause. I changed the strProcessFolder to be 'c:\FreightAuditTool', but it still returned the traceback: Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN While the ADODB part still correctly printed the ADO recode set object just as before: <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> which shows that the connection string has no problem. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 22:12 Message: Logged In: YES user_id=14198 You have made the same mistake again: strProcessFolder='c:\FreightAuditTool' That is an invalid folder name. What you probably mean is: strProcessFolder='c:\FreightAuditTool' or strProcessFolder=r'c:\FreightAuditTool' ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-12 15:07 Message: Logged In: YES user_id=1147025 Below is my code, ODBC module simply failed while it works with ADODB by COM: import dbi,odbc import win32com.client strProcessFolder='c:\FreightAuditTool' FileName='ChinaTruckInvoices.xls' con_str='Provider=Microsoft.Jet.OLEDB.4.0;Data Source=% s;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' %(strProcessFolder+'\'+FileName) print con_str sour_conn = win32com.client.gencache.EnsureDispatch ('ADODB.Connection') sour_conn.Open(con_str) recordset=sour_conn.Execute('select * from [Invoices$]')[0] print recordset a=odbc.odbc(con_str) and the output was: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\FreightAuditTool\ChinaTruckInvoices.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1" <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN I hope some one could fix the ODBC modue to support connection string. It's so easier to use and I found it seems run much faster than ADODB with Win32com. Also, It can easily be packaged by py2exe, while I found it's really a hard nut to crack packaging win32com modules. Regards Xiao Zhou ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 11:18 Message: Logged In: YES user_id=14198 Are you sure this is not a backslash quoting problem? As quoted: >>> "c:\a" 'c:\x07' >>> "c:\a" 'c:\a' >>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-28 10:57:04
|
Bugs item #1073933, was opened at 2004-11-27 07:05 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1073933&group_id=78018 Category: pythonwin Group: None >Status: Closed >Resolution: Wont Fix Priority: 5 Submitted By: Wojtek Swiatek (wsw70) Assigned to: Nobody/Anonymous (nobody) Summary: folding bug in comments Initial Comment: The folding in a comment section is wrong. For instance the code: """ hello world how are you where: should not be folded neither this one """ gets folded after the 'where' in pythinwin. I think that the folding should be completely disabled in a comments section. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2004-11-28 21:25 Message: Logged In: YES user_id=14198 Pythonwin uses the folding built in to Scintilla - hopefully it will improve the builtin folding in the future. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1073933&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-26 20:05:56
|
Bugs item #1073933, was opened at 2004-11-26 21:05 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=1073933&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: Wojtek Swiatek (wsw70) Assigned to: Nobody/Anonymous (nobody) Summary: folding bug in comments Initial Comment: The folding in a comment section is wrong. For instance the code: """ hello world how are you where: should not be folded neither this one """ gets folded after the 'where' in pythinwin. I think that the folding should be completely disabled in a comments section. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1073933&group_id=78018 |
|
From: mahesh <ma...@pr...> - 2004-11-26 11:40:23
|
Dear all,
=20
I was trying to automate the process of GUI mode installation of a =
product.
=20
Here is a sample piece of code that i was using to click a button =
(It works on most applications ) :
-------------------------------------------------------------------------=
-------------------------------------------------------------------
=20
'''
Get the next button on the window handle and Click "Next"
'''
def clickNext(xWindow,pageno,button=3D"Next"):
print "\t\t Clicking button !! ",button
btnEnter=3D[]
try:
btnEnter=3D findControl(xWindow, wantedClass=3D"Button", =
wantedText=3Dbutton)
if btnEnter:
print "\t Able to get the button =
",win32gui.GetWindowText(btnEnter[0])
except:
if btnEnter:
print "Unable to get the button =
",win32gui.GetWindowText(btnEnter[0])
print " $$$ EXCEPTION CLICKING THE BUTTON :> ",button," id=3D =
",btnEnter
#return 0
return 0
clickButton(btnEnter[0])
print "Operation Button Press on =
",win32gui.GetWindowText(btnEnter[0])," button on page ",pageno," on =
window ",xWindow
return 1
'''
Simulates a single mouse click on a button
'''
def clickButton(hwnd):
#print "Clicking ",win32gui.GetWindowText(hwnd)
_sendNotifyMessage(hwnd, win32con.BN_CLICKED)
#print "Clicked ",win32gui.GetWindowText(hwnd)
def _sendNotifyMessage(hwnd, nofifyMessage):
'''Send a notify message to a control.'''
hbutton=3Dhwnd
#print "WindowLong =3D =
",win32api.GetWindowLong(hwnd,win32con.GWL_ID)
print "Clicking ",win32gui.GetWindowText(hwnd)
=
#win32gui.SendMessage(win32gui.GetParent(hwnd),win32con.WM_COMMAND,_build=
WinLong(nofifyMessage,win32api.GetWindowLong(hwnd,win32con.GWL_ID)),hwnd)=
win32api.PostMessage(hbutton, win32con.WM_LBUTTONDOWN, 0, 0)
win32api.PostMessage(hbutton, win32con.WM_LBUTTONUP, 0, 0)
print "Clicked ",win32gui.GetWindowText(hwnd)
'''
Return a list of of controls of the given text and class
'''
def =
findControl(topHwnd,wantedText=3DNone,wantedClass=3DNone,selectionFunctio=
n=3DNone):
controls =3D findControls(topHwnd,
wantedText=3DwantedText,
wantedClass=3DwantedClass,
selectionFunction=3DselectionFunction)
if controls:
return controls
else:
raise WinGuiAutoError("No control found for topHwnd=3D" +
repr(topHwnd) +
", wantedText=3D" +
repr(wantedText) +
", wantedClass=3D" +
repr(wantedClass) +
", selectionFunction=3D" +
repr(selectionFunction))
def =
findControls(topHwnd,wantedText=3DNone,wantedClass=3DNone,selectionFuncti=
on=3DNone):
def searchChildWindows(currentHwnd):
results =3D []
childWindows =3D []
try:
win32gui.EnumChildWindows(currentHwnd,
_windowEnumerationHandler,
childWindows)
except win32gui.error:
# This seems to mean that the control *cannot* have child =
windows,
# i.e. not a container.
return
for childHwnd, windowText, windowClass in childWindows:
descendentMatchingHwnds =3D searchChildWindows(childHwnd)
if len(windowText)>0: pass
#print "childwindows : >",windowText, ">",len(windowText)
if descendentMatchingHwnds:
results +=3D descendentMatchingHwnds
if wantedText and \
not _normaliseText(wantedText) in =
_normaliseText(windowText):
continue
if wantedClass and \
not windowClass =3D=3D wantedClass:
continue
if selectionFunction and \
not selectionFunction(childHwnd):
continue
results.append(childHwnd)
return results
return searchChildWindows(topHwnd)
'''
Simulates a single mouse click on a button
'''
def clickButton(hwnd):
#print "Clicking ",win32gui.GetWindowText(hwnd)
_sendNotifyMessage(hwnd, win32con.BN_CLICKED)
#print "Clicked ",win32gui.GetWindowText(hwnd)
def _sendNotifyMessage(hwnd, nofifyMessage):
'''Send a notify message to a control.'''
hbutton=3Dhwnd
#print "Clicking >: ",hwnd, " || Parent is > =
",win32gui.GetParent(hwnd)
#print "WindowLong =3D =
",win32api.GetWindowLong(hwnd,win32con.GWL_ID)
print "Clicking ",win32gui.GetWindowText(hwnd)
=
#win32gui.SendMessage(win32gui.GetParent(hwnd),win32con.WM_COMMAND,_build=
WinLong(nofifyMessage,win32api.GetWindowLong(hwnd,win32con.GWL_ID)),hwnd)=
win32api.PostMessage(hbutton, win32con.WM_LBUTTONDOWN, 0, 0)
win32api.PostMessage(hbutton, win32con.WM_LBUTTONUP, 0, 0)
print "Clicked ",win32gui.GetWindowText(hwnd)
def _buildWinLong(high, low):
# return ((high << 16) | low)
return int(struct.unpack('>L',struct.pack('>2H',high,low)) [0])
-------------------------------------------------------------------------=
-------------------------------------------------------------------------=
-------------------------
Interestingly ,the installshield is coded in Java. So the problem i =
am facing is as follows :
Problem : I am unable to click the "Next" button using the above =
code for automation .
Description of the problem :
When we start the installer GUI comes up . Keep Pressing next =
(manually) screen1 -> screen2 -> screen 3 -> ...screen n ->......screen =
z(Finish screen).
Once we reach the nth screen and run the script to view all =
childwindows of the current installer window .I am able to get the =
handles of all the components that were residing in all the screens from =
1 to n. I am also able to edit the text in the textfield component and =
click to select the radio buttons.
But most importantly i am unable to click the button "Next" through =
the above code. In other words , Manual clicks on 'Next" works (Takes me =
from screen n to screen [n+1] ) but not through the above code .
So, is this a problem with respect to Java only (Java's Internal =
Event handling Architecture) ?
or Do u think any code level changes can be made to make the "Click" =
work ?
Thanks in advance,
Mahesh
|
|
From: Mark H. <mha...@sk...> - 2004-11-25 02:41:54
|
It appears you need to put that "foo" on your sys.path - I thought we handled some cases when it is not, but obviously not this one. Mark > -----Original Message----- > From: pyw...@li... > [mailto:pyw...@li...]On Behalf Of Jim > Panetta > Sent: Friday, 19 November 2004 2:19 PM > To: pyw...@li... > Subject: [pywin32-bugs] Problem starting a service. > > > The example service file win32/demos/service/pipeTestService.py is > showing very different behavior depending on *where* the file > is located: > > 1) When located under site-packages/win32/..., the service > starts with > no problem. > > 2) When started under site-packages/foo/pipeTestService.py, > the service > does not start: > > C:\Python23\Lib\site-packages\foo>copy > ..\win32\demos\service\pipeTestService.py pipeTestService.py > > C:\Python23\Lib\site-packages\foo>python pipeTestService.py install > Installing service PyPipeTestService to Python class > C:\Python23\Lib\site-packages\foo\pipeTestService.TestPipeService > Service installed > > C:\Python23\Lib\site-packages\foo>python pipeTestService.py > --wait 5 start > Starting service PyPipeTestService > Error starting service: The service did not respond to the start or > control request in a timely fashion. > > A look at the event log gives: > > Event Type: Error > > Event Source: Python Service > > Event Category: None > > Event ID: 4 > > Date: 11/18/2004 > > Time: 7:14:22 PM > > User: N/A > > Computer: GITOW1 > > Description: > > Python could not import the service's module > > > > exceptions.ImportError: No module named pipeTestService > > Any ideas? > > I'm running Python 2.3.4, pywin32 build 202 or 203. (Tried both) > > --Jim Panetta > > -- > My opinions are mine...not DOE's...not SLAC's...mine. > (except by random, unforseeable coincidences) > pa...@sl... -- Save the whales! Free the mallocs! > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from > real users. > Discover which products truly live up to the hype. Start reading now. > http://productguide.itmanagersjournal.com/ > _______________________________________________ > pywin32-bugs mailing list > pyw...@li... > https://lists.sourceforge.net/lists/listinfo/pywin32-bugs |
|
From: SourceForge.net <no...@so...> - 2004-11-23 12:13:42
|
Bugs item #1071645, was opened at 2004-11-23 13:11 Message generated for change (Comment added) made by netchan You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1071645&group_id=78018 Category: com Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sándor Pálfy (netchan) Assigned to: Nobody/Anonymous (nobody) Summary: Indentation error when an ASP page contains only python code Initial Comment: The follwing asp file causes "Internal Server Error - ASP error": ----------------------------------------- <script language="python" runat="server"> def a(): b=1 </script> ----------------------------------------- Error details: Python ActiveX Scripting Engine (0x80020009) expected an indented block /indenttest.asp, line 3 b=1 Now, the same page surrounded with simple <html> tags works just fine: ----------------------------------------- <html> <script language="python" runat="server"> def a(): b=1 </script> </html> ----------------------------------------- The same error happens even if you use the src attribute of the script tag for including a regular something.py file. ---------------------------------------------------------------------- >Comment By: Sándor Pálfy (netchan) Date: 2004-11-23 13:13 Message: Logged In: YES user_id=380124 The environment: Windows XP SP2, all patches. Python 2.3.4 (#53, May 25 2004, 21:17:02) [MSC v.1200 32 bit (Intel)] on win32 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1071645&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-23 12:11:11
|
Bugs item #1071645, was opened at 2004-11-23 13:11 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=1071645&group_id=78018 Category: com Group: None Status: Open Resolution: None Priority: 5 Submitted By: Sándor Pálfy (netchan) Assigned to: Nobody/Anonymous (nobody) Summary: Indentation error when an ASP page contains only python code Initial Comment: The follwing asp file causes "Internal Server Error - ASP error": ----------------------------------------- <script language="python" runat="server"> def a(): b=1 </script> ----------------------------------------- Error details: Python ActiveX Scripting Engine (0x80020009) expected an indented block /indenttest.asp, line 3 b=1 Now, the same page surrounded with simple <html> tags works just fine: ----------------------------------------- <html> <script language="python" runat="server"> def a(): b=1 </script> </html> ----------------------------------------- The same error happens even if you use the src attribute of the script tag for including a regular something.py file. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1071645&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-22 08:12:20
|
Bugs item #1054585, was opened at 2004-10-26 21:35 Message generated for change (Comment added) made by kjd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1054585&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: Kim Davies (kjd) Assigned to: Nobody/Anonymous (nobody) Summary: MFC71.DLL missing from install? Initial Comment: Pythonwin Build 203 for Python 2.4 (using b1) doesn't start, it exits on launch with this dialog box: "This application has failed to start because MFC71.DLL was not found. Re-installing the application may fix this problem." Previous versions of Pythonwin have worked fine on the machine, but this is the first time a 20x build has been used. System in Windows XP SP2. ---------------------------------------------------------------------- >Comment By: Kim Davies (kjd) Date: 2004-11-22 16:12 Message: Logged In: YES user_id=168657 Thanks for the advice! My only concern is that I am running a standard installation with the latest version of Windows, and I need to go hunting for DLLs just to get it running. If the DLL is necessary for normal operation on a vanilla Windows install, it should probably be bundled into the installation package. ---------------------------------------------------------------------- Comment By: jtidman (jtidman) Date: 2004-11-22 11:22 Message: Logged In: YES user_id=1163738 I searched all over microsoft.com to find these files. The best way that I came up with is to download the "ATC Voicepack SDK" from: http://www.microsoft.com/games/flightsimulator/fs2004_downloads_sdk.asp And install it. Then copy the dlls from the installed directory into \winnt\system32 (for win2K, or where ever else your OS stores dlls) Then uninstall the "ATC Voicepack SDK". PythonWin should then work fine. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2004-11-11 10:27 Message: Logged In: YES user_id=552329 This is a dupe of: [ 1016558 ] 202 Windows Installer requires MSVCR71.dll http://sourceforge.net/tracker/index.php?func=detail&aid=1016558&group_id=78018&atid=551954 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1054585&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-22 04:13:26
|
Bugs item #1054585, was opened at 2004-10-26 08:35 Message generated for change (Comment added) made by jtidman You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1054585&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: Kim Davies (kjd) Assigned to: Nobody/Anonymous (nobody) Summary: MFC71.DLL missing from install? Initial Comment: Pythonwin Build 203 for Python 2.4 (using b1) doesn't start, it exits on launch with this dialog box: "This application has failed to start because MFC71.DLL was not found. Re-installing the application may fix this problem." Previous versions of Pythonwin have worked fine on the machine, but this is the first time a 20x build has been used. System in Windows XP SP2. ---------------------------------------------------------------------- Comment By: jtidman (jtidman) Date: 2004-11-21 21:22 Message: Logged In: YES user_id=1163738 I searched all over microsoft.com to find these files. The best way that I came up with is to download the "ATC Voicepack SDK" from: http://www.microsoft.com/games/flightsimulator/fs2004_downloads_sdk.asp And install it. Then copy the dlls from the installed directory into \winnt\system32 (for win2K, or where ever else your OS stores dlls) Then uninstall the "ATC Voicepack SDK". PythonWin should then work fine. ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2004-11-10 20:27 Message: Logged In: YES user_id=552329 This is a dupe of: [ 1016558 ] 202 Windows Installer requires MSVCR71.dll http://sourceforge.net/tracker/index.php?func=detail&aid=1016558&group_id=78018&atid=551954 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1054585&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-21 02:15:27
|
Bugs item #1070284, was opened at 2004-11-21 02:15 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=1070284&group_id=78018 Category: pythonwin Group: None Status: Open Resolution: None Priority: 5 Submitted By: Robert Brewer (aminusfu) Assigned to: Nobody/Anonymous (nobody) Summary: find dialog not applying Initial Comment: In certain cases, the find dialog won't find instances of the given text in a document. This occurs when: 1. The user types Alt-E, Alt-F to open the find dialog. If the two keys are struck too quickly, the find dialog doesn't remember the default search, and doesn't seem to apply itself to the active window. 2. A new document is opened, and the find dialog is opened without moving the insertion point from the beginning of the document. In this case, the find operation fails to find any matches in the new document. I'm using Python 2.3.2 and pywin build 200. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1070284&group_id=78018 |
|
From: Jim P. <pa...@sl...> - 2004-11-19 03:19:36
|
The example service file win32/demos/service/pipeTestService.py is showing very different behavior depending on *where* the file is located: 1) When located under site-packages/win32/..., the service starts with no problem. 2) When started under site-packages/foo/pipeTestService.py, the service does not start: C:\Python23\Lib\site-packages\foo>copy ..\win32\demos\service\pipeTestService.py pipeTestService.py C:\Python23\Lib\site-packages\foo>python pipeTestService.py install Installing service PyPipeTestService to Python class C:\Python23\Lib\site-packages\foo\pipeTestService.TestPipeService Service installed C:\Python23\Lib\site-packages\foo>python pipeTestService.py --wait 5 start Starting service PyPipeTestService Error starting service: The service did not respond to the start or control request in a timely fashion. A look at the event log gives: > Event Type: Error > Event Source: Python Service > Event Category: None > Event ID: 4 > Date: 11/18/2004 > Time: 7:14:22 PM > User: N/A > Computer: GITOW1 > Description: > Python could not import the service's module > > exceptions.ImportError: No module named pipeTestService Any ideas? I'm running Python 2.3.4, pywin32 build 202 or 203. (Tried both) --Jim Panetta -- My opinions are mine...not DOE's...not SLAC's...mine. (except by random, unforseeable coincidences) pa...@sl... -- Save the whales! Free the mallocs! |
|
From: SourceForge.net <no...@so...> - 2004-11-15 16:31:35
|
Feature Requests item #1066764, was opened at 2004-11-15 10:31 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=1066764&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Garrett Smith (garrett1020) Assigned to: Nobody/Anonymous (nobody) Summary: Specifying small icons Initial Comment: I have an ico file with multiple formats (e.g. 16x16, 32x32, etc.) and would like to specify the 16x16 as the 'small icon' for my dialog. If my understanding is correct, I'd do this by using WNDCLASSEX and specifying a icon handle for hIconSm. If this is the only way to do this, it'd be great if WNDCLASSEX and RegisterClassEx were added to win32gui. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551957&aid=1066764&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-15 14:39:57
|
Bugs item #1053745, was opened at 2004-10-25 16:03 Message generated for change (Comment added) made by ogiesen You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1053745&group_id=78018 Category: installation Group: None >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Oliver Giesen (ogiesen) Assigned to: Nobody/Anonymous (nobody) Summary: PythonPath no longer set by installer. Initial Comment: I have meant to report this ever since the first 20x release but somehow never got around to it: Before the 20x releases the installer used to add the extensions to the PythonPath as sub-entries win32 and win32com respectively. This no longer is the case and as a result my WinCvs macros that make use of the extensions no longer work unless I add the extensions to the PythonPath manually. Is there something I have missed? Is there some other way to make the extensions "publicly importable" nowadays? ---------------------------------------------------------------------- >Comment By: Oliver Giesen (ogiesen) Date: 2004-11-15 15:39 Message: Logged In: YES user_id=158827 Ok, thanks to your hints the WinCvs developers were able to fix this on their end. Issue closed. Thanks a lot! ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-05 04:50 Message: Logged In: YES user_id=14198 It was removed as it causes problems when multiple installations of Python exist on the same machine. If one application wants to include a 'private' Python in their application directory, the global registry screws things. Removing these registry settings have solved many problems for people. If wincvs is using its own Python, then the current behaviour is unfortunately correct. There should be a way to specify what dir you want to install pywin32 in, but there isn't. The solution is to simply copy those pywin32 directories, and the .pth file (which has relative paths) to the cygwin python's site-packages directory. If cygwin is using the "global" Python, then it probably means cygwin is preventing site.py from running - this is what locates and processes the .pth files. I'm happy to help you resolve this, but am very unlikely to move back to the registry. ---------------------------------------------------------------------- Comment By: Oliver Giesen (ogiesen) Date: 2004-11-01 09:47 Message: Logged In: YES user_id=158827 Yes, that file is there and it does obviously get taken into account when I run Python scripts via python.exe, however, that's not what I do most of the time. Most of the time my scripts are run via Python23.dll (as macros embedded in WinCvs) and AFAICT that does not take into account the pywin32.pth file. This only works if the path is actually set in the PythonPath registry key, i.e. HKLM\SOFTWARE\Python\PythonCore\2.3\PythonPath . I'm simply a bit confused because I'm really sure that I never had to manually edit the PythonPath with the pre-200 installers. Was there a specific reason why this functionality has been removed from the installers? Or could this be a problem of the way WinCvs embeds Python? ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-10-26 01:04 Message: Logged In: YES user_id=14198 There should be a pywin32.pth file installed into your site-packages directory. Python loads this as it starts up - unless you have told Python not to process site.py You should be able to confirm this by running python.exe and printing sys.path ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1053745&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-15 08:11:08
|
Bugs item #1066510, was opened at 2004-11-15 21:11 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=1066510&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Andy Elvey (mr_moose) Assigned to: Nobody/Anonymous (nobody) Summary: Error message - "Can't load Python for pre-install script" Initial Comment: Hi all - I've downloaded and installed the Python 2.4 .msi file for Windows (I'm running Win XP). That install went fine, and I can run Python code at the usual prompt (>>>). The .msi file that I downloaded was - python-2.4b2.msi . I then downloaded the Python for Windows extensions (the file was pywin32-203.win32-py2.4.exe ). Double-clicked on that, and I got as far as "ready to install". I then clicked the "next" button, and I got the message "can't load Python for pre-install script". This was weird, because at the start of things (when I first double-clicked the .exe file), the .exe file *did* find my Python install (in C:\Python24 ), so goodness knows why it can't find Python later on .... :-) I haven't changed anything from the defaults .... the install of the .msi file was a full install, and I changed nothing whatsoever. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1066510&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-14 03:39:31
|
Bugs item #1066014, was opened at 2004-11-13 20:39 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=1066014&group_id=78018 Category: win32 Group: v1.0 (example) Status: Open Resolution: None Priority: 5 Submitted By: Jason R. Coombs (jaraco) Assigned to: Nobody/Anonymous (nobody) Summary: ASP script with high-characters causes 500 Server Error Initial Comment: Example VB Script works okay: <% Response.Write( "é!" ) %> Equivalent Python script fails with a 500 Server error: <%@language=Python%> <% Response.Write( "é!" ) %> An altered, but equivalent, Python script works fine: <%@language=Python%> <% Response.Write( "\xe9!" ) %> This problem cropped up in the last year or so. I don't know if it's an IIS 6 issue or a Python 2.3 issue. I'm using Python 2.3.4 with pywin32 build 202. I'm suspect it has something to do with the encoding of the script code that is passed to Python and its ActiveX Scripting Engine and the way the engine decodes (or doesn't) the script for evaluation. Is this something that should be addressed in the ActiveX Scripting engine or something that just needs a specifier for the encoding (either in the ASP declaration or a coding declaration in the Python script)? Any suggestions? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1066014&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-13 08:24:41
|
Bugs item #1065008, was opened at 2004-11-12 08:25 Message generated for change (Comment added) made by jiangwen365 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 Category: None Group: None Status: Open >Resolution: Invalid Priority: 5 Submitted By: 江文 (jiangwen365) Assigned to: Nobody/Anonymous (nobody) Summary: Contrary to the Doc,ODBC module not accept Connection String Initial Comment: It seems that the ODBC module only works with DNS names, but not Connection Strings, like: odbc.odbc(('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\aaa.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' ) will fail. But it IS said to be acceptable in odbc module documents. ---------------------------------------------------------------------- >Comment By: 江文 (jiangwen365) Date: 2004-11-13 08:24 Message: Logged In: YES user_id=1147025 Hi Mhmmond, Yes, it seems that the ODBC module does accept connection strings, but has some restrictions on the format of the string. Per your information, I finally get the code worked after changing the connection string to r'Driver={Microsoft Excel Driver (*.xls)};DBQ=C:\FreightAuditTool\ChinaTruckInvoices.xls' . But it is strange thing that the module don't accept the former string which is the most common format and can be perfectly accepted by ADODB. Regards, Xiao Zhou ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-13 04:15 Message: Logged In: YES user_id=14198 I'm fairly certain that *some* datasource strings work fine with this module. Unfortunately, I don't know enough about this to know where to start. ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-13 03:59 Message: Logged In: YES user_id=1147025 Oh, yes, but I think this is not the cause. I changed the strProcessFolder to be 'c:\FreightAuditTool', but it still returned the traceback: Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN While the ADODB part still correctly printed the ADO recode set object just as before: <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> which shows that the connection string has no problem. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 22:12 Message: Logged In: YES user_id=14198 You have made the same mistake again: strProcessFolder='c:\FreightAuditTool' That is an invalid folder name. What you probably mean is: strProcessFolder='c:\FreightAuditTool' or strProcessFolder=r'c:\FreightAuditTool' ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-12 15:07 Message: Logged In: YES user_id=1147025 Below is my code, ODBC module simply failed while it works with ADODB by COM: import dbi,odbc import win32com.client strProcessFolder='c:\FreightAuditTool' FileName='ChinaTruckInvoices.xls' con_str='Provider=Microsoft.Jet.OLEDB.4.0;Data Source=% s;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' %(strProcessFolder+'\'+FileName) print con_str sour_conn = win32com.client.gencache.EnsureDispatch ('ADODB.Connection') sour_conn.Open(con_str) recordset=sour_conn.Execute('select * from [Invoices$]')[0] print recordset a=odbc.odbc(con_str) and the output was: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\FreightAuditTool\ChinaTruckInvoices.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1" <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN I hope some one could fix the ODBC modue to support connection string. It's so easier to use and I found it seems run much faster than ADODB with Win32com. Also, It can easily be packaged by py2exe, while I found it's really a hard nut to crack packaging win32com modules. Regards Xiao Zhou ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 11:18 Message: Logged In: YES user_id=14198 Are you sure this is not a backslash quoting problem? As quoted: >>> "c:\a" 'c:\x07' >>> "c:\a" 'c:\a' >>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-13 04:15:59
|
Bugs item #1065008, was opened at 2004-11-12 19:25 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 Category: None Group: None Status: Open >Resolution: None Priority: 5 Submitted By: 江文 (jiangwen365) Assigned to: Nobody/Anonymous (nobody) Summary: Contrary to the Doc,ODBC module not accept Connection String Initial Comment: It seems that the ODBC module only works with DNS names, but not Connection Strings, like: odbc.odbc(('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\aaa.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' ) will fail. But it IS said to be acceptable in odbc module documents. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2004-11-13 15:15 Message: Logged In: YES user_id=14198 I'm fairly certain that *some* datasource strings work fine with this module. Unfortunately, I don't know enough about this to know where to start. ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-13 14:59 Message: Logged In: YES user_id=1147025 Oh, yes, but I think this is not the cause. I changed the strProcessFolder to be 'c:\FreightAuditTool', but it still returned the traceback: Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN While the ADODB part still correctly printed the ADO recode set object just as before: <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> which shows that the connection string has no problem. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-13 09:12 Message: Logged In: YES user_id=14198 You have made the same mistake again: strProcessFolder='c:\FreightAuditTool' That is an invalid folder name. What you probably mean is: strProcessFolder='c:\FreightAuditTool' or strProcessFolder=r'c:\FreightAuditTool' ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-13 02:07 Message: Logged In: YES user_id=1147025 Below is my code, ODBC module simply failed while it works with ADODB by COM: import dbi,odbc import win32com.client strProcessFolder='c:\FreightAuditTool' FileName='ChinaTruckInvoices.xls' con_str='Provider=Microsoft.Jet.OLEDB.4.0;Data Source=% s;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' %(strProcessFolder+'\'+FileName) print con_str sour_conn = win32com.client.gencache.EnsureDispatch ('ADODB.Connection') sour_conn.Open(con_str) recordset=sour_conn.Execute('select * from [Invoices$]')[0] print recordset a=odbc.odbc(con_str) and the output was: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\FreightAuditTool\ChinaTruckInvoices.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1" <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN I hope some one could fix the ODBC modue to support connection string. It's so easier to use and I found it seems run much faster than ADODB with Win32com. Also, It can easily be packaged by py2exe, while I found it's really a hard nut to crack packaging win32com modules. Regards Xiao Zhou ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 22:18 Message: Logged In: YES user_id=14198 Are you sure this is not a backslash quoting problem? As quoted: >>> "c:\a" 'c:\x07' >>> "c:\a" 'c:\a' >>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-13 04:00:36
|
Bugs item #1065008, was opened at 2004-11-12 08:25 Message generated for change (Settings changed) made by jiangwen365 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 Category: None Group: None >Status: Open Resolution: Invalid Priority: 5 Submitted By: 江文 (jiangwen365) Assigned to: Nobody/Anonymous (nobody) Summary: Contrary to the Doc,ODBC module not accept Connection String Initial Comment: It seems that the ODBC module only works with DNS names, but not Connection Strings, like: odbc.odbc(('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\aaa.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' ) will fail. But it IS said to be acceptable in odbc module documents. ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-13 03:59 Message: Logged In: YES user_id=1147025 Oh, yes, but I think this is not the cause. I changed the strProcessFolder to be 'c:\FreightAuditTool', but it still returned the traceback: Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN While the ADODB part still correctly printed the ADO recode set object just as before: <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> which shows that the connection string has no problem. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 22:12 Message: Logged In: YES user_id=14198 You have made the same mistake again: strProcessFolder='c:\FreightAuditTool' That is an invalid folder name. What you probably mean is: strProcessFolder='c:\FreightAuditTool' or strProcessFolder=r'c:\FreightAuditTool' ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-12 15:07 Message: Logged In: YES user_id=1147025 Below is my code, ODBC module simply failed while it works with ADODB by COM: import dbi,odbc import win32com.client strProcessFolder='c:\FreightAuditTool' FileName='ChinaTruckInvoices.xls' con_str='Provider=Microsoft.Jet.OLEDB.4.0;Data Source=% s;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' %(strProcessFolder+'\'+FileName) print con_str sour_conn = win32com.client.gencache.EnsureDispatch ('ADODB.Connection') sour_conn.Open(con_str) recordset=sour_conn.Execute('select * from [Invoices$]')[0] print recordset a=odbc.odbc(con_str) and the output was: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\FreightAuditTool\ChinaTruckInvoices.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1" <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN I hope some one could fix the ODBC modue to support connection string. It's so easier to use and I found it seems run much faster than ADODB with Win32com. Also, It can easily be packaged by py2exe, while I found it's really a hard nut to crack packaging win32com modules. Regards Xiao Zhou ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 11:18 Message: Logged In: YES user_id=14198 Are you sure this is not a backslash quoting problem? As quoted: >>> "c:\a" 'c:\x07' >>> "c:\a" 'c:\a' >>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-13 03:59:26
|
Bugs item #1065008, was opened at 2004-11-12 08:25 Message generated for change (Comment added) made by jiangwen365 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 Category: None Group: None Status: Closed Resolution: Invalid Priority: 5 Submitted By: 江文 (jiangwen365) Assigned to: Nobody/Anonymous (nobody) Summary: Contrary to the Doc,ODBC module not accept Connection String Initial Comment: It seems that the ODBC module only works with DNS names, but not Connection Strings, like: odbc.odbc(('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\aaa.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' ) will fail. But it IS said to be acceptable in odbc module documents. ---------------------------------------------------------------------- >Comment By: 江文 (jiangwen365) Date: 2004-11-13 03:59 Message: Logged In: YES user_id=1147025 Oh, yes, but I think this is not the cause. I changed the strProcessFolder to be 'c:\FreightAuditTool', but it still returned the traceback: Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN While the ADODB part still correctly printed the ADO recode set object just as before: <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> which shows that the connection string has no problem. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 22:12 Message: Logged In: YES user_id=14198 You have made the same mistake again: strProcessFolder='c:\FreightAuditTool' That is an invalid folder name. What you probably mean is: strProcessFolder='c:\FreightAuditTool' or strProcessFolder=r'c:\FreightAuditTool' ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-12 15:07 Message: Logged In: YES user_id=1147025 Below is my code, ODBC module simply failed while it works with ADODB by COM: import dbi,odbc import win32com.client strProcessFolder='c:\FreightAuditTool' FileName='ChinaTruckInvoices.xls' con_str='Provider=Microsoft.Jet.OLEDB.4.0;Data Source=% s;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' %(strProcessFolder+'\'+FileName) print con_str sour_conn = win32com.client.gencache.EnsureDispatch ('ADODB.Connection') sour_conn.Open(con_str) recordset=sour_conn.Execute('select * from [Invoices$]')[0] print recordset a=odbc.odbc(con_str) and the output was: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\FreightAuditTool\ChinaTruckInvoices.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1" <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN I hope some one could fix the ODBC modue to support connection string. It's so easier to use and I found it seems run much faster than ADODB with Win32com. Also, It can easily be packaged by py2exe, while I found it's really a hard nut to crack packaging win32com modules. Regards Xiao Zhou ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 11:18 Message: Logged In: YES user_id=14198 Are you sure this is not a backslash quoting problem? As quoted: >>> "c:\a" 'c:\x07' >>> "c:\a" 'c:\a' >>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-12 22:12:45
|
Bugs item #1065008, was opened at 2004-11-12 19:25 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 Category: None Group: None >Status: Closed Resolution: Invalid Priority: 5 Submitted By: 江文 (jiangwen365) Assigned to: Nobody/Anonymous (nobody) Summary: Contrary to the Doc,ODBC module not accept Connection String Initial Comment: It seems that the ODBC module only works with DNS names, but not Connection Strings, like: odbc.odbc(('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\aaa.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' ) will fail. But it IS said to be acceptable in odbc module documents. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2004-11-13 09:12 Message: Logged In: YES user_id=14198 You have made the same mistake again: strProcessFolder='c:\FreightAuditTool' That is an invalid folder name. What you probably mean is: strProcessFolder='c:\FreightAuditTool' or strProcessFolder=r'c:\FreightAuditTool' ---------------------------------------------------------------------- Comment By: 江文 (jiangwen365) Date: 2004-11-13 02:07 Message: Logged In: YES user_id=1147025 Below is my code, ODBC module simply failed while it works with ADODB by COM: import dbi,odbc import win32com.client strProcessFolder='c:\FreightAuditTool' FileName='ChinaTruckInvoices.xls' con_str='Provider=Microsoft.Jet.OLEDB.4.0;Data Source=% s;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' %(strProcessFolder+'\'+FileName) print con_str sour_conn = win32com.client.gencache.EnsureDispatch ('ADODB.Connection') sour_conn.Open(con_str) recordset=sour_conn.Execute('select * from [Invoices$]')[0] print recordset a=odbc.odbc(con_str) and the output was: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\FreightAuditTool\ChinaTruckInvoices.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1" <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN I hope some one could fix the ODBC modue to support connection string. It's so easier to use and I found it seems run much faster than ADODB with Win32com. Also, It can easily be packaged by py2exe, while I found it's really a hard nut to crack packaging win32com modules. Regards Xiao Zhou ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 22:18 Message: Logged In: YES user_id=14198 Are you sure this is not a backslash quoting problem? As quoted: >>> "c:\a" 'c:\x07' >>> "c:\a" 'c:\a' >>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-12 15:07:28
|
Bugs item #1065008, was opened at 2004-11-12 08:25 Message generated for change (Comment added) made by jiangwen365 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 Category: None Group: None >Status: Open Resolution: Invalid Priority: 5 Submitted By: 江文 (jiangwen365) Assigned to: Nobody/Anonymous (nobody) Summary: Contrary to the Doc,ODBC module not accept Connection String Initial Comment: It seems that the ODBC module only works with DNS names, but not Connection Strings, like: odbc.odbc(('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\aaa.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' ) will fail. But it IS said to be acceptable in odbc module documents. ---------------------------------------------------------------------- >Comment By: 江文 (jiangwen365) Date: 2004-11-12 15:07 Message: Logged In: YES user_id=1147025 Below is my code, ODBC module simply failed while it works with ADODB by COM: import dbi,odbc import win32com.client strProcessFolder='c:\FreightAuditTool' FileName='ChinaTruckInvoices.xls' con_str='Provider=Microsoft.Jet.OLEDB.4.0;Data Source=% s;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' %(strProcessFolder+'\'+FileName) print con_str sour_conn = win32com.client.gencache.EnsureDispatch ('ADODB.Connection') sour_conn.Open(con_str) recordset=sour_conn.Execute('select * from [Invoices$]')[0] print recordset a=odbc.odbc(con_str) and the output was: Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\FreightAuditTool\ChinaTruckInvoices.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1" <win32com.gen_py.Microsoft ActiveX Data Objects 2.5 Library.Fields instance at 0x17884424> Traceback (most recent call last): File "D:/PythonProjects/test.py", line 16, in ? a=odbc.odbc(con_str) dbi.operation-error: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified in LOGIN I hope some one could fix the ODBC modue to support connection string. It's so easier to use and I found it seems run much faster than ADODB with Win32com. Also, It can easily be packaged by py2exe, while I found it's really a hard nut to crack packaging win32com modules. Regards Xiao Zhou ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2004-11-12 11:18 Message: Logged In: YES user_id=14198 Are you sure this is not a backslash quoting problem? As quoted: >>> "c:\a" 'c:\x07' >>> "c:\a" 'c:\a' >>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-12 11:18:29
|
Bugs item #1065008, was opened at 2004-11-12 19:25 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 Category: None Group: None >Status: Pending >Resolution: Invalid Priority: 5 Submitted By: 江文 (jiangwen365) Assigned to: Nobody/Anonymous (nobody) Summary: Contrary to the Doc,ODBC module not accept Connection String Initial Comment: It seems that the ODBC module only works with DNS names, but not Connection Strings, like: odbc.odbc(('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\aaa.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' ) will fail. But it IS said to be acceptable in odbc module documents. ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2004-11-12 22:18 Message: Logged In: YES user_id=14198 Are you sure this is not a backslash quoting problem? As quoted: >>> "c:\a" 'c:\x07' >>> "c:\a" 'c:\a' >>> ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-12 08:25:36
|
Bugs item #1065008, was opened at 2004-11-12 08:25 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=1065008&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: 江文 (jiangwen365) Assigned to: Nobody/Anonymous (nobody) Summary: Contrary to the Doc,ODBC module not accept Connection String Initial Comment: It seems that the ODBC module only works with DNS names, but not Connection Strings, like: odbc.odbc(('Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\aaa.xls;Extended Properties="Excel 8.0;HDR=Yes;IMEX=1"' ) will fail. But it IS said to be acceptable in odbc module documents. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1065008&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-11 15:51:22
|
Patches item #1064568, was opened at 2004-11-11 16:51 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=1064568&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Stefan Schukat (sschukat) Assigned to: Nobody/Anonymous (nobody) Summary: Added GlobalInterface Table and more Safearray Variant Types Initial Comment: Until now only IStream marshalling was supported by pythoncom. This is not sufficient for all marshalling tasks. Therefore I patched the pythoncom DLL which allows now to create a Global Interface Table Object and access the IGlobalInterfaceTable interface. Secondly some VARIANT types where missing in the SafeArray support. This list was now extended. The new and changed files and a GIT test are attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551956&aid=1064568&group_id=78018 |
|
From: SourceForge.net <no...@so...> - 2004-11-11 02:30:34
|
Bugs item #1064265, was opened at 2004-11-11 15:30 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=1064265&group_id=78018 Category: win32 Group: None Status: Open Resolution: None Priority: 5 Submitted By: Tony Meyer (anadelonbrin) Assigned to: Nobody/Anonymous (nobody) Summary: Having system32 in sys.path causes problems for services Initial Comment: If system32 is on sys.path and a script is run as a Windows service, then it may die when it finds a zlib.dll in system32 before it tries to find one in PythonXX\DLLs. In Mark's own words: "I think that for a service (or for any Python program for that matter), we don't want system32 on sys.path" ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1064265&group_id=78018 |
2 messages has been excluded from this view by a project administrator.
