From craig.a.hall at gmail.com Wed Mar 4 13:11:20 2009 From: craig.a.hall at gmail.com (Craig Hall) Date: Wed Mar 4 20:11:24 2009 Subject: [egenix-users] getting around install with py2.4 not found in registry Message-ID: I'm running on WinXP (32 bit), and in the process of moving from python 2.2 to 2.4 and trying to install the mxDateTime library Have downloaded egenix-mx-base-3.1.2.win32-py2.4.exe When trying to install, receive error that "Python version 2.4 required, which was not found in the registry." Based on another post in the mailing list, I tried to open the exe in winZip, but it failed to open saying "start of central directory not found: Zip file corrupt". What's the correct method to install? Can I fake the appropriate registry entry with regedit? thanks Craig -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20090304/800d8280/attachment.htm From mal at egenix.com Wed Mar 4 21:20:44 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Mar 4 21:20:47 2009 Subject: [egenix-users] getting around install with py2.4 not found in registry In-Reply-To: References: Message-ID: <49AEE29C.30306@egenix.com> On 2009-03-04 20:11, Craig Hall wrote: > I'm running on WinXP (32 bit), and in the process of moving from python 2.2 > to 2.4 and trying to install the mxDateTime library > > Have downloaded egenix-mx-base-3.1.2.win32-py2.4.exe > > When trying to install, receive error that "Python version 2.4 required, > which was not found in the registry." How did you install Python on the system ? The standard python.org installer will create all necessary registry entries for you... unless you are seeing this bug: http://bugs.python.org/issue4567 > Based on another post in the mailing list, I tried to open the exe in > winZip, but it failed to open saying "start of central directory not found: > Zip file corrupt". Try using 7-zip: http://www.7-zip.org/ > What's the correct method to install? The wininst installer assumes that you have the standard python.org version of Python installed. > Can I fake the appropriate registry entry with regedit? Probably, but I'm not sure what these are, only their path: HKEY_LOCAL_MACHINE\SOFTWARE\Python\PythonCore\ -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 04 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From mal at egenix.com Wed Mar 4 22:45:34 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Wed Mar 4 22:45:38 2009 Subject: [egenix-users] getting around install with py2.4 not found in registry In-Reply-To: <0016e649c9268b394b0464516c36@google.com> References: <0016e649c9268b394b0464516c36@google.com> Message-ID: <49AEF67E.4050207@egenix.com> On 2009-03-04 22:06, craig.a.hall@gmail.com wrote: > this install was copied from a different product's install CD already > unzipped into it's directory structure as opposed to installed from the > distribution > > the 7-zip did the trick! > > I just tested from the command line and the mxDateTime calls are looking > good > > thanks! You're welcome ! -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 04 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From wenping0 at yahoo.com Fri Mar 6 10:21:32 2009 From: wenping0 at yahoo.com (Wenping Wang) Date: Fri Mar 6 19:21:37 2009 Subject: [egenix-users] A quiestion from a mx.TextTools newbie Message-ID: <332678.29401.qm@web52912.mail.re2.yahoo.com> Hello Friends, I'm new to mx.TextTools & am learning this powerful tool by reading David Mertz's excellent book "Text Processing in Python". Naturally I tried the examples in the book. One particular example concerning mx.TextTools is the one under "mx.TextTools.AppendTagobj" on Page 307. Unfortunately, that example from David's book doesn't work. I was able to tweak the code to make it work. But I was puzzled why it doesn't work. I attach the segment of codes here. #--- example code starts from mx.TextTools import * #--- 1st approach: failure words = (('word', AllIn+AppendTagobj, alpha), (None, AllIn, whitespace, MatchFail, -1)) tag('this and that', words) #--- 2nd approach: success words = (('word', AllIn, alpha), (None, AllIn, whitespace, +1), (None,EOF,Here,-2)) tag('this and that', words) #--- 3rd approach: success word = [] def emiter(tl,txt,l,r,s): word.append(txt[l:r]) words = ((emiter, AllIn+CallTag, alpha), (None, AllIn, whitespace, MatchFail, -1)) tag('this and that', words) #--- example code ends Can someone provide me some insight why the 1st approach doesn't work while the 2nd & 3rd work? BTW, I'm using mx.TextTools 3.1.2 on Windows. Thanks much. Best, Wenping Wang -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20090306/bd4301a2/attachment.htm From mal at egenix.com Fri Mar 6 23:14:16 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 6 23:14:20 2009 Subject: [egenix-users] A quiestion from a mx.TextTools newbie In-Reply-To: <332678.29401.qm@web52912.mail.re2.yahoo.com> References: <332678.29401.qm@web52912.mail.re2.yahoo.com> Message-ID: <49B1A038.6080101@egenix.com> On 2009-03-06 19:21, Wenping Wang wrote: > Hello Friends, > > I'm new to mx.TextTools & am learning this powerful tool by reading David Mertz's excellent book "Text Processing in Python". Naturally I tried the examples in the book. One particular example concerning mx.TextTools is the one under "mx.TextTools.AppendTagobj" on Page 307. > > Unfortunately, that example from David's book doesn't work. I was able to tweak the code to make it work. But I was puzzled why it doesn't work. I attach the segment of codes here. > > #--- example code starts > from mx.TextTools import * > > #--- 1st approach: failure > words = (('word', AllIn+AppendTagobj, alpha), > (None, AllIn, whitespace, MatchFail, -1)) > tag('this and that', words) > > #--- 2nd approach: success > words = (('word', AllIn, alpha), > (None, AllIn, whitespace, +1), > (None,EOF,Here,-2)) > tag('this and that', words) > > #--- 3rd approach: success > word = [] > def emiter(tl,txt,l,r,s): > word.append(txt[l:r]) > > words = ((emiter, AllIn+CallTag, alpha), > (None, AllIn, whitespace, MatchFail, -1)) > tag('this and that', words) > #--- example code ends > > Can someone provide me some insight why the 1st approach doesn't work while the 2nd & 3rd work? BTW, I'm using mx.TextTools 3.1.2 on Windows. It fails because the tagging engine pointers moves beyond the last 't' in the string and there is no EOF check in the tag table. AllIn will never succeed on EOF. BTW: mxTextTools has support for jump labels, so it's usually better to use those (the compiler will then convert these to offsets), e.g. from mx.TextTools import * words = ( 'parse_word', ('word', AllIn, alpha, 'parse_whitespace'), 'parse_whitespace', (None, AllIn, whitespace, 'test_for_eof', 'parse_word'), 'test_for_eof', (None, EOF, Here, 'parse_word'), ) print tag('this and that', words) -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 06 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From mal at egenix.com Fri Mar 6 23:38:40 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 6 23:38:44 2009 Subject: [egenix-users] A question from a mx.TextTools newbie In-Reply-To: <363832.42166.qm@web52906.mail.re2.yahoo.com> References: <332678.29401.qm@web52912.mail.re2.yahoo.com> <49B1A038.6080101@egenix.com> <363832.42166.qm@web52906.mail.re2.yahoo.com> Message-ID: <49B1A5F0.7040502@egenix.com> On 2009-03-06 23:34, Wenping Wang wrote: > Thanks Marc-Andre for your reply. > > Your explanation for why the 1st approach fails makes sense to me. However, following the same logic, should one expect that the 3rd approach would fail too since there is NO EOF testing there? That the 1st fails & the 3rd succeeds is puzzling. The 3rd example fails as well (ie. doesn't match): >>> #--- 3rd approach: success ... word = [] >>> def emiter(tl,txt,l,r,s): ... word.append(txt[l:r]) ... >>> words = ((emiter, AllIn+CallTag, alpha), ... (None, AllIn, whitespace, MatchFail, -1)) >>> tag('this and that', words) (0, [], 13) However, the tagging engine has no control over what you do in a tag function, so it cannot undo the appends you did in there. >>> word ['this', 'and', 'that'] That's why you still see a result. > Best, > Wenping Wang > > > > > ________________________________ > From: M.-A. Lemburg > To: Wenping Wang > Cc: egenix-users@egenix.com > Sent: Friday, March 6, 2009 5:14:16 PM > Subject: Re: [egenix-users] A quiestion from a mx.TextTools newbie > > On 2009-03-06 19:21, Wenping Wang wrote: >> Hello Friends, >> >> I'm new to mx.TextTools & am learning this powerful tool by reading David Mertz's excellent book "Text Processing in Python". Naturally I tried the examples in the book. One particular example concerning mx.TextTools is the one under "mx.TextTools.AppendTagobj" on Page 307. >> >> Unfortunately, that example from David's book doesn't work. I was able to tweak the code to make it work. But I was puzzled why it doesn't work. I attach the segment of codes here. >> >> #--- example code starts >> from mx.TextTools import * >> >> #--- 1st approach: failure >> words = (('word', AllIn+AppendTagobj, alpha), >> (None, AllIn, whitespace, MatchFail, -1)) >> tag('this and that', words) >> >> #--- 2nd approach: success >> words = (('word', AllIn, alpha), >> (None, AllIn, whitespace, +1), >> (None,EOF,Here,-2)) >> tag('this and that', words) >> >> #--- 3rd approach: success >> word = [] >> def emiter(tl,txt,l,r,s): >> word.append(txt[l:r]) >> >> words = ((emiter, AllIn+CallTag, alpha), >> (None, AllIn, whitespace, MatchFail, -1)) >> tag('this and that', words) >> #--- example code ends >> >> Can someone provide me some insight why the 1st approach doesn't work while the 2nd & 3rd work? BTW, I'm using mx.TextTools 3.1.2 on Windows. It fails because the tagging engine pointers moves beyond the > last 't' in the string and there is no EOF check in the tag > table. AllIn will never succeed on EOF. BTW: mxTextTools has support for jump labels, so it's usually > better to use those (the compiler will then convert these to offsets), > e.g. from mx.TextTools import * words = ( 'parse_word', ('word', AllIn, alpha, 'parse_whitespace'), 'parse_whitespace', (None, AllIn, whitespace, 'test_for_eof', 'parse_word'), 'test_for_eof', (None, EOF, Here, 'parse_word'), ) print tag('this and that', words) -- > Marc-Andre Lemburg > eGenix.com Professional Python Services directly from the Source (#1, Mar 06 2009) >>>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ > > > -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 06 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From info at egenix.com Mon Mar 16 23:36:41 2009 From: info at egenix.com (eGenix Team: M.-A. Lemburg) Date: Mon Mar 16 23:41:46 2009 Subject: [egenix-users] ANN: eGenix pyOpenSSL Distribution 0.8.1-0.9.8j-1 Message-ID: <49BED479.4000704@egenix.com> ________________________________________________________________________ ANNOUNCING eGenix.com pyOpenSSL Distribution Version 0.8.1-0.9.8j-1 An easy to install and use repackaged distribution of the pyOpenSSL Python interface for OpenSSL - available on Windows and Unix platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-pyOpenSSL-Distribution-0.8.1-0.9.8j-1-GA.html ________________________________________________________________________ INTRODUCTION The eGenix.com pyOpenSSL Distribution includes everything you need to get started with SSL in Python. It comes with an easy to use installer that includes the most recent OpenSSL library versions in pre-compiled form. pyOpenSSL is an open-source Python add-on (http://pyopenssl.sf.net/) that allows writing SSL aware networking applications as well as certificate management tools. OpenSSL is an open-source implementation of the SSL protocol (http://www.openssl.org/). For more information, please see the product page: http://www.egenix.com/products/python/pyOpenSSL/ ________________________________________________________________________ NEWS This new release of the eGenix.com pyOpenSSL Distribution fixes a serious problem in pyOpenSSL 0.8 related to threaded applications. The problem causes invalid thread states in the Python interpreter which then result in random core dumps and seg faults. The patch was provided by Maxim Sobolev on SourceForge: http://sourceforge.net/tracker/index.php?func=detail&aid=2543118&group_id=31249&atid=401760 Note that this patch has not yet been integrated into upstream pyOpenSSL. We have also fixed several compiler warnings found in the code. The version of pyOpenSSL you find in the source release has those patches applied. Binaries are available for Linux x86 and x64 as well as Windows x86 and include pyOpenSSL as well as the OpenSSL libraries. For Plone users and friends of buildout scripts, we have added pre-built binaries for Windows. They install just like the Linux versions and allow easy integration of the archives into buildout scripts. ________________________________________________________________________ DOWNLOADS The download archives and instructions for installing the package can be found at: http://www.egenix.com/products/python/pyOpenSSL/ ________________________________________________________________________ UPGRADING Before installing this version of pyOpenSSL, please make sure that you uninstall any previously installed pyOpenSSL version. Otherwise, you could end up not using the included OpenSSL libs. _______________________________________________________________________ SUPPORT Commercial support for these packages is available from eGenix.com. Please see http://www.egenix.com/services/support/ for details about our support offerings. Enjoy, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 16 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From tentin.quarantino at gmail.com Tue Mar 17 12:08:58 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Tue Mar 17 20:09:03 2009 Subject: [egenix-users] mxODBC, windows, mdb, local and network access Message-ID: Hello egenix community, I want to believe that mxODBC will help me accomplish my task. :) Of course, my success will depend on how I approach my task. That is why I seek guidance from the egenix community. I look forward to purchasing the mxODBC product if it will be a part of my solution. I have a mdb file which is version JET4 indicating Access 2000 or Access XP. I created an ODBC Data source so that I could access this file's data with egenix's mxODBC product via Python. I like how the mxODBC library returns the data as built-in Python data types. That's very convenient. This was done on the "localhost", as it were, on a Windows host. Now, I want to access the same ODBC data source (on the Windows host) from a Linux host across the network. I am hoping that Windows can accommodate this by putting the Data Source on the network. I am confident that mxODBC will accommodate this by simply using the appropriate DSN. What would the DSN would look like for this? If it is not possible, what needs to change in my approach? I would prefer to continue to use the mxODBC product in my solution due to the way it conveniently returns data. Note, while reading the egenix archives, I saw references to mdbtools on Linux. I have started to investigate this solution. However, (prior to RTFMing) I fear that mdbtools will not return data as nice Python built-in types such as tuples and instead just text. So far that appears to be my experience. It does not appear to have the programming convenience and integration with Python as does mxODBC. Cheers, TQ From mal at egenix.com Tue Mar 17 21:14:15 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Tue Mar 17 21:14:20 2009 Subject: [egenix-users] mxODBC, windows, mdb, local and network access In-Reply-To: References: Message-ID: <49C00497.5070302@egenix.com> On 2009-03-17 20:08, Tentin Quarantino wrote: > Hello egenix community, > > I want to believe that mxODBC will help me accomplish my task. :) > > Of course, my success will depend on how I approach my task. > That is why I seek guidance from the egenix community. > I look forward to purchasing the mxODBC product if it will be a part > of my solution. > > I have a mdb file which is version JET4 indicating Access 2000 or Access XP. > I created an ODBC Data source so that I could access this file's data > with egenix's mxODBC product via Python. I like how the mxODBC library returns > the data as built-in Python data types. That's very convenient. > This was done on the "localhost", as it were, on a Windows host. > > Now, I want to access the same ODBC data source (on the Windows host) from > a Linux host across the network. I am hoping that Windows can accommodate > this by putting the Data Source on the network. I am confident that mxODBC > will accommodate this by simply using the appropriate DSN. > What would the DSN would look like for this? This will not work with mxODBC since it requires an ODBC driver on the same machine where you use it, ie. a Linux ODBC driver for the Access database file. I am not even sure whether this is possible given that Access uses a very file-based approach to storage. However, this is exactly the kind of situation we developed mxODBC Connect for: http://www.egenix.com/products/python/mxODBCConnect/ You install the easy to port client part of mxODBC Connect on the client machine where you run you Python script, ie. the Linux box. You don't need an ODBC driver for the client machine. On the server side, the Windows box, you install the mxODBC Connect Server which can then use all ODBC data sources you have configured on the Windows box (including the one for the JET4 MDB file). mxODBC Connect then does all the networking needed for the two parts to communicate with each other - and you can benefit from compression and SSL-level security as well. The interface on the client side is the mostly same as offered by the standalone mxODBC when used directly on the Windows box. > If it is not possible, what needs to change in my approach? > I would prefer to continue to use the mxODBC product in my solution due > to the way it conveniently returns data. > > Note, while reading the egenix archives, I saw references to mdbtools on Linux. > I have started to investigate this solution. However, (prior to > RTFMing) I fear that > mdbtools will not return data as nice Python built-in types such as tuples and > instead just text. So far that appears to be my experience. It does > not appear to > have the programming convenience and integration with Python as does mxODBC. Even if you use mdbtools, you would still have to put the MDB file on a network share with all the problems associated with this. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 17 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From info at egenix.com Wed Mar 18 15:35:04 2009 From: info at egenix.com (eGenix Team: M.-A. Lemburg) Date: Wed Mar 18 15:36:49 2009 Subject: [egenix-users] ANN: eGenix pyOpenSSL Distribution 0.8.1-0.9.8j now also for Mac OS X Message-ID: <49C10698.6080509@egenix.com> ________________________________________________________________________ ANNOUNCING eGenix.com pyOpenSSL Distribution Version 0.8.1-0.9.8j An easy to install and use repackaged distribution of the pyOpenSSL Python interface for OpenSSL - available on Windows, Mac OS X and Unix platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-pyOpenSSL-Distribution-0.8.1-0.9.8j-1-GA.html ________________________________________________________________________ INTRODUCTION The eGenix.com pyOpenSSL Distribution includes everything you need to get started with SSL in Python. It comes with an easy to use installer that includes the most recent OpenSSL library versions in pre-compiled form. pyOpenSSL is an open-source Python add-on (http://pyopenssl.sf.net/) that allows writing SSL aware networking applications as well as certificate management tools. OpenSSL is an open-source implementation of the SSL protocol (http://www.openssl.org/). For more information, please see the product page: http://www.egenix.com/products/python/pyOpenSSL/ ________________________________________________________________________ NEWS This new release of the eGenix.com pyOpenSSL Distribution fixes a serious problem in pyOpenSSL 0.8 related to threaded applications. The problem causes invalid thread states in the Python interpreter which then result in random core dumps and seg faults. The patch was provided by Maxim Sobolev on SourceForge: http://sourceforge.net/tracker/index.php?func=detail&aid=2543118&group_id=31249&atid=401760 Note that this patch has not yet been integrated into upstream pyOpenSSL. We have also fixed several compiler warnings found in the code. The version of pyOpenSSL you find in the source release has those patches applied. Binaries are available for Linux x86 and x64 as well as Windows x86 and Mac OS X PPC/Intel. They include pyOpenSSL and the necessary OpenSSL libraries. For Plone users and friends of buildout scripts, we have added pre-built binaries for Windows. They install just like the Linux versions and allow easy integration of the archives into buildout scripts. ________________________________________________________________________ DOWNLOADS The download archives and instructions for installing the package can be found at: http://www.egenix.com/products/python/pyOpenSSL/ ________________________________________________________________________ UPGRADING Before installing this version of pyOpenSSL, please make sure that you uninstall any previously installed pyOpenSSL version. Otherwise, you could end up not using the included OpenSSL libs. _______________________________________________________________________ SUPPORT Commercial support for these packages is available from eGenix.com. Please see http://www.egenix.com/services/support/ for details about our support offerings. Enjoy, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 18 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From info at egenix.com Thu Mar 19 11:04:34 2009 From: info at egenix.com (eGenix Team: M.-A. Lemburg) Date: Thu Mar 19 11:06:44 2009 Subject: [egenix-users] ANN: eGenix mxODBC Connect 1.0.1 - Python Database Interface Message-ID: <49C218B2.2040409@egenix.com> ________________________________________________________________________ ANNOUNCING eGenix.com mxODBC Connect Python Database Interface Version 1.0.1 Our new client-server product for connecting Python applications to relational databases - from all major platforms This announcement is also available on our web-site for online reading: http://www.egenix.com/company/news/eGenix-mxODBC-Connect-1.0.1-GA.html ________________________________________________________________________ INTRODUCTION The mxODBC Connect Database Interface for Python allows users to easily connect Python applications to all major databases on the market today in a highly portable and convenient way. Unlike our mxODBC Python extension, mxODBC Connect is designed as client-server application, so you no longer need to find production quality ODBC drivers for all the platforms you target with your Python application. Instead you use an easy to install Python client library which connects directly to the mxODBC Connect database server over the network. This makes mxODBC Connect the ideal basis for writing cross-platform database programs and utilities in Python, especially if you run applications that need to communicate with databases such as MS SQL Server and MS Access, Oracle Database, IBM DB2 and Informix, Sybase ASE and Sybase Anywhere, MySQL, PostgreSQL, SAP MaxDB and many more, that run on Windows or Linux machines. By removing the need to install and configure ODBC drivers on the client side, mxODBC Connect greatly simplifies setup and configuration of database driven client applications, while at the same time making the network communication between client and database server more efficient and more secure. For more information, please see the product page: http://www.egenix.com/products/python/mxODBCConnect/ ________________________________________________________________________ NEWS mxODBC Connect 1.0.1 is a patch-level release of our new mxODBC Connect product. * More Robust We have made the client and server more robust in case of communication failures. Even if the client applications fail to shutdown the server connection before exiting, the server will free up resources used by the client on the server side and rollback transactions as necessary. * More Platform Support With the 1.0.1 release we are also providing much better platform support for the mxODBC Connect Client: we have fixed a problem in 1.0.0 that prevented the installation of the pre-built clients on non-Linux systems. The mxODBC Connect Client can now be installed on most platforms supported by Python, since it is written in a platform independent, portable way. The pre-built archives also make it possible to integrate the clients into build system such as buildout (used in Zope and Plone) or other distutils-based deployment systems. * Ideal for Building Bridges As a result, connecting from e.g. Mac OS X to an SQL Server database has never been easier. You can even keep the data sources you already have configured on your Windows machine and connect to them as if your application were running on the database server itself. ________________________________________________________________________ UPGRADING You are encouraged to upgrade to this latest mxODBC Connect release. When upgrading, please always upgrade both the server and the client installations to the same version - even for patch level releases. Customers who have purchased mxODBC Connect 1.0 licenses can download and upgrade their existing installations without having to purchase new licenses or upgrades. The licenses will continue to work with version 1.0.1. Users of our stand-alone mxODBC product will have to purchase new licenses from our online shop in order to use mxODBC Connect. You can request 30-day evaluation licenses by visiting our web-site or writing to sales@egenix.com, stating your name (or the name of the company) and the number of eval licenses that you need. http://www.egenix.com/products/python/mxODBCConnect/#Evaluation ________________________________________________________________________ DOWNLOADS The download archives as well as instructions for installation and configuration of the product can be found on the product page: http://www.egenix.com/products/python/mxODBCConnect/ Evaluation licenses for the server part are available free of charge: http://www.egenix.com/products/python/mxODBCConnect/#Evaluation The client part of mxODBC Connect is always free of charge. _______________________________________________________________________ SUPPORT Commercial support for this product is available from eGenix.com. Please see http://www.egenix.com/services/support/ for details about our support offerings. Enjoy, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 19 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From tentin.quarantino at gmail.com Thu Mar 19 16:45:04 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Fri Mar 20 00:45:08 2009 Subject: [egenix-users] how to connect with mxODBC Connect? Message-ID: Hello, After reading archives, in particular a thread from April 2006 with subject line "Difficulty connecting", I am feeling particularly stuck. When using egenix mx.odbc library locally, I am able to use my data source with no problem. However when attempting to connect remotely via mxODBC Connect, the client prints the following: mx.ODBCConnect.Error.OperationalError: None of the configured mxODBC Connect Servers allow connections. What should I be examining? I am open to any suggestions. Please.... any at all. :) As I mention, mx.ODBC works fine locally... records are spewing from the only data source on the entire Windows machine. Cheers! From mal at egenix.com Fri Mar 20 10:48:07 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 20 10:48:13 2009 Subject: [egenix-users] how to connect with mxODBC Connect? In-Reply-To: References: Message-ID: <49C36657.4010206@egenix.com> On 2009-03-20 00:45, Tentin Quarantino wrote: > Hello, > > After reading archives, in particular a thread from April 2006 with > subject line "Difficulty connecting", I am feeling particularly stuck. > > When using egenix mx.odbc library locally, I am able to use my data > source with no problem. > > However when attempting to connect remotely via mxODBC Connect, the > client prints the following: > > mx.ODBCConnect.Error.OperationalError: None of the configured mxODBC > Connect Servers allow connections. > > What should I be examining? > I am open to any suggestions. Please.... any at all. :) As I suggested in off-list email: please send in your configuration files. In order for the client and server to make contact, the configurations have to match. The above error suggests that the client is trying to connect using one or more methods (depending on what you have configured in the client-config.ini) and then gives up either after hitting a timeout or finding that it cannot open connections to the configured mxODBC Connect Server(s). > As I mention, mx.ODBC works fine locally... records are spewing > from the only data source on the entire Windows machine. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 20 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From tentin.quarantino at gmail.com Sat Mar 21 15:16:07 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Sat Mar 21 23:16:12 2009 Subject: [egenix-users] mx.ODBCConnect vs mx.ODBC, why am I seeing differences Message-ID: Hi, Perhaps I need perspective from other users. I am experiencing different behavior with the same "driverString" when running the two packages "mx.ODBCConnect" and "mx.ODBC"? Here is a brief summary: # # mx.ODBC test code # import mx.ODBC.Windows as odbc # initialize "driverString" with exact same value as test code below db = odbc.DriverConnect(driverString) # Open a cursor cursor = db.cursor() # ------------------------------- # # mx.ODBCConnect test code # from mx.ODBCConnect.Client import ServerSession session = ServerSession(config_file=myConfig) server = session.open() # assume successful connection to the mxODBC Connect Server # initialize "driverString" with exact same value as test code above db = server.DriverConnect(driverString) # Open a cursor cursor = db.cursor() # ------------------------------- In both tests above, the "driverString" is same exact code. The "driverString" is a common form. DRIVER={Microsoft Access Driver (*.mdb)};DBQ=C:\MyAccessDB.mdb;UID=;PWD=secrt It works with mx.ODBC. The second one generates an authentication error: mx.ODBCConnect.Error.ProgrammingError: ('42000', -1905, '[Microsoft][ODBC Microsoft Access Driver] Not a valid password.', 10102) What should I investigate to solve this problem? Could the null UID cause a problem for mx.ODBCConnect? Any recommendations welcome! :) Cheers! From mark at bronsteinlaw.com Sun Mar 22 22:06:03 2009 From: mark at bronsteinlaw.com (Mark Bronstein) Date: Mon Mar 23 03:06:08 2009 Subject: [egenix-users] plone 3.1 buildout Message-ID: <49C6EE8B.3090709@bronsteinlaw.com> Is there a working sample buildout recipe to install the Zope MXODBC DA into Plone 3.1? The last list discussion about this was back in 10/08 and I wondered if there was a working buildout recipe I could look it. Thanks Mark From mal at egenix.com Mon Mar 23 11:10:06 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Mar 23 11:10:11 2009 Subject: [egenix-users] mx.ODBCConnect vs mx.ODBC, why am I seeing differences In-Reply-To: References: Message-ID: <49C75FFE.1030606@egenix.com> On 2009-03-21 23:16, Tentin Quarantino wrote: > Hi, > > Perhaps I need perspective from other users. > > I am experiencing different behavior with the same "driverString" when > running the two packages "mx.ODBCConnect" and "mx.ODBC"? > > Here is a brief summary: > > # > # mx.ODBC test code > # > import mx.ODBC.Windows as odbc > # initialize "driverString" with exact same value as test code below > db = odbc.DriverConnect(driverString) > # Open a cursor > cursor = db.cursor() > > # ------------------------------- > > # > # mx.ODBCConnect test code > # > > from mx.ODBCConnect.Client import ServerSession > session = ServerSession(config_file=myConfig) > server = session.open() > # assume successful connection to the mxODBC Connect Server > # initialize "driverString" with exact same value as test code above > db = server.DriverConnect(driverString) > # Open a cursor > cursor = db.cursor() > > # ------------------------------- > > In both tests above, the "driverString" is same exact code. > The "driverString" is a common form. > DRIVER={Microsoft Access Driver (*.mdb)};DBQ=C:\MyAccessDB.mdb;UID=;PWD=secrt > > It works with mx.ODBC. > > The second one generates an authentication error: > mx.ODBCConnect.Error.ProgrammingError: ('42000', -1905, > '[Microsoft][ODBC Microsoft Access Driver] Not a valid password.', > 10102) > > > What should I investigate to solve this problem? > > Could the null UID cause a problem for mx.ODBCConnect? Yes. It is possible that the Access driver defaults to the login name of the user accessing the database on the server. Since the mxODBC Connect Server runs as service, the user account name is different than the one you use to log in to the machine. To prevent such problems, always provide a full UID in the connection string. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 23 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2009-03-19: Released mxODBC.Connect 1.0.1 http://python.egenix.com/ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From mal at egenix.com Mon Mar 23 11:19:45 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Mar 23 11:19:48 2009 Subject: [egenix-users] plone 3.1 buildout In-Reply-To: <49C6EE8B.3090709@bronsteinlaw.com> References: <49C6EE8B.3090709@bronsteinlaw.com> Message-ID: <49C76241.1000604@egenix.com> On 2009-03-23 03:06, Mark Bronstein wrote: > > Is there a working sample buildout recipe to install the Zope MXODBC DA > into Plone 3.1? > > The last list discussion about this was back in 10/08 and I wondered if > there was a working buildout recipe I could look it. AFAIK, there is a recipe for mxODBC (our Python extension) available on PyPI, but not for the mxODBC Zope DA. However, it should be easy to write one based on the mxODBC recipe, since the download and installation process is similar. Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 23 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2009-03-19: Released mxODBC.Connect 1.0.1 http://python.egenix.com/ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ From tentin.quarantino at gmail.com Mon Mar 23 14:39:17 2009 From: tentin.quarantino at gmail.com (Tentin Quarantino) Date: Mon Mar 23 22:39:24 2009 Subject: [egenix-users] mx.ODBCConnect vs mx.ODBC, why am I seeing differences In-Reply-To: <49C75FFE.1030606@egenix.com> References: <49C75FFE.1030606@egenix.com> Message-ID: Hi! >> Could the null UID cause a problem for mx.ODBCConnect? > > Yes. > > It is possible that the Access driver defaults to the login name > of the user accessing the database on the server. Since the mxODBC > Connect Server runs as service, the user account name is different > than the one you use to log in to the machine. > > To prevent such problems, always provide a full UID in the connection > string. > As I am accessing the database of a 3rd party, then I would need to persuade the 3rd party to use a username. Thanks for the advice. It was not until I tried using a different Windows box, that I was able to get things to work. It would appear your speculation regarding the cause is likely correct. Cheers! From rb2.net at gmail.com Thu Mar 26 20:28:53 2009 From: rb2.net at gmail.com (Rene Bourgoin) Date: Fri Mar 27 01:28:57 2009 Subject: [egenix-users] Zope 2.11 install help Message-ID: <1e6b7e620903261728ve342032v16e5c101fa609455@mail.gmail.com> Downloaded mxodbc for zope 2.11 phython 2.4 Get the message below when i start zope console. Your Zope installation is using: Python 2.4.4 UCS2 *** Problem importing the eGenix mx Extensions: Please make sure that you have downloaded and installed the right eGenix mxODBC Zope DA version for your version of Zope. Zope uses the Python interpreter to run products and binaries for different versions of the interpreter are mutually incompatible. -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20090326/372a2caa/attachment.htm From mal at egenix.com Fri Mar 27 12:53:39 2009 From: mal at egenix.com (M.-A. Lemburg) Date: Fri Mar 27 12:53:44 2009 Subject: [egenix-users] Zope 2.11 install help In-Reply-To: <1e6b7e620903261728ve342032v16e5c101fa609455@mail.gmail.com> References: <1e6b7e620903261728ve342032v16e5c101fa609455@mail.gmail.com> Message-ID: <49CCBE43.5070804@egenix.com> On 2009-03-27 01:28, Rene Bourgoin wrote: > Downloaded mxodbc for zope 2.11 phython 2.4 > > Get the message below when i start zope console. > > Your Zope installation is using: Python 2.4.4 UCS2 > > *** Problem importing the eGenix mx Extensions: > > Please make sure that you have downloaded and installed > the right eGenix mxODBC Zope DA version for your version > of Zope. Zope uses the Python interpreter to run products > and binaries for different versions of the interpreter are > mutually incompatible. Have you installed the UCS2 package of the mxODBC Zope DA ? -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Mar 27 2009) >>> Python/Zope Consulting and Support ... http://www.egenix.com/ >>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ >>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/ ________________________________________________________________________ 2009-03-19: Released mxODBC.Connect 1.0.1 http://python.egenix.com/ ::: Try our new mxODBC.Connect Python Database Interface for free ! :::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/