From timothywayne.cook at gmail.com Sun Jan 3 12:44:35 2010 From: timothywayne.cook at gmail.com (Tim Cook) Date: Sun Jan 3 15:44:49 2010 Subject: [egenix-users] egenix-mx-base 3.1.3 on Ubuntu 9.10 Message-ID: <1262529875.25239.60.camel@localhost> Hi All, I have an open source project ( https://launchpad.net/oship ) where I am using egenix-mx-base. I happened to install (using buildout) 3.1.2 to begin experimenting with it, especially the DateTime functionality. During this time 3.1.3 was published and the other developers are now unable to install egenix-mx-base In fact, after some experimentation; I cannot install 3.1.3 either. While the team uses a mixture of platforms and OSs. We do know that both 32 bit and AMD64 bit machines using Ubuntu 9.10 all receive (essentially) the same traceback (see below). Could you please "unhide" version 3.1.2 on Pypi until the issue is resolved? http://wiki.python.org/moin/CheeseShopTutorial This way I can pin the version to 3.1.2 "Exposing Multiple Releases When a new release of a package is submitted to the Package Index, all previous releases of that package are hidden from the display. This means that listings and searches will no longer find those releases. You may use the package admin interface to un-hide releases. This may be useful if you have both a stable and a development release active at the same time. These will be hidden again on the next submission of meta-data." ************************************************************************ Installing app. Getting distribution for 'egenix-mx-base'. In file included from mx/TextTools/mxTextTools/mxte.c:42: mx/TextTools/mxTextTools/mxte_impl.h: In function ?mxTextTools_TaggingEngine?: mx/TextTools/mxTextTools/mxte_impl.h:345: warning: pointer targets in initialization differ in signedness mx/TextTools/mxTextTools/mxte_impl.h:364: warning: pointer targets in initialization differ in signedness mx/BeeBase/mxBeeBase/btr.c:269: warning: ?dumpNode? defined but not used mx/URL/mxURL/mxURL.c: In function ?mxURL_SetFromString?: mx/URL/mxURL/mxURL.c:676: warning: pointer targets in initialization differ in signedness mx/UID/mxUID/mxUID.c: In function ?mxUID_Verify?: mx/UID/mxUID/mxUID.c:333: warning: pointer targets in passing argument 1 of ?sscanf? differ in signedness /usr/include/stdio.h:415: note: expected ?const char * __restrict__? but argument is of type ?unsigned char *? mx/UID/mxUID/mxUID.c: In function ?mxUID_New?: mx/UID/mxUID/mxUID.c:462: warning: pointer targets in passing argument 1 of ?mxUID_CRC16? differ in signedness mx/UID/mxUID/mxUID.c:199: note: expected ?unsigned char *? but argument is of type ?char *? In file included from /usr/include/string.h:640, from /usr/include/python2.6/Python.h:38, from mx/UID/mxUID/mx.h:66, from mx/UID/mxUID/mxUID.c:27: In function ?memset?, inlined from ?mxUID_Fold? at mx/UID/mxUID/mxUID.c:239, inlined from ?mxUID_fold? at mx/UID/mxUID/mxUID.c:630: /usr/include/bits/string3.h:82: warning: call to ?__warn_memset_zero_len? declared with attribute warning: memset used with constant zero length parameter; this could be due to transposed parameters error: Setup script exited with error: build/bdist.linux-x86_64-py2.6_ucs4/dumb/egenix_mx_base-3.1.3-py2.6.egg-info: Is a directory An error occured when trying to install egenix-mx-base 3.1.3. Look above this message for any errors that were output by easy_install. While: Installing app. Getting distribution for 'egenix-mx-base'. Error: Couldn't install: egenix-mx-base 3.1.3 ************************************************************************ Thanks, Tim -- *************************************************************** Timothy Cook, MSc LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == (upon request) Academic.Edu Profile: http://uff.academia.edu/TimothyCook You may get my Public GPG key from popular keyservers or from this link http://timothywayne.cook.googlepages.com/home -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : /mailman-archives/egenix-users/attachments/20100103/de4dc021/attachment.bin From mal at egenix.com Mon Jan 4 20:10:40 2010 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 4 20:10:44 2010 Subject: [egenix-users] egenix-mx-base 3.1.3 on Ubuntu 9.10 In-Reply-To: <1262529875.25239.60.camel@localhost> References: <1262529875.25239.60.camel@localhost> Message-ID: <4B423D30.20402@egenix.com> Tim Cook wrote: > Hi All, > > I have an open source project ( https://launchpad.net/oship ) where I am > using egenix-mx-base. > > I happened to install (using buildout) 3.1.2 to begin experimenting with > it, especially the DateTime functionality. > > During this time 3.1.3 was published and the other developers are now > unable to install egenix-mx-base > > In fact, after some experimentation; I cannot install 3.1.3 either. > While the team uses a mixture of platforms and OSs. We do know that > both 32 bit and AMD64 bit machines using Ubuntu 9.10 all receive > (essentially) the same traceback (see below). Which version of Python and setuptools are you using ? > Could you please "unhide" version 3.1.2 on Pypi until the issue is > resolved? http://wiki.python.org/moin/CheeseShopTutorial This way I can > pin the version to 3.1.2 This we'd rather not do, since 3.1.2 and previous versions have a serious bug in mxBeeBase on Mac OS X and BSD platforms. > "Exposing Multiple Releases > When a new release of a package is submitted to the Package Index, all > previous releases of that package are hidden from the display. This > means that listings and searches will no longer find those releases. > > You may use the package admin interface to un-hide releases. This may be > useful if you have both a stable and a development release active at the > same time. These will be hidden again on the next submission of > meta-data." > > ************************************************************************ > Installing app. > Getting distribution for 'egenix-mx-base'. > In file included from mx/TextTools/mxTextTools/mxte.c:42: > mx/TextTools/mxTextTools/mxte_impl.h: In function > ?mxTextTools_TaggingEngine?: > mx/TextTools/mxTextTools/mxte_impl.h:345: warning: pointer targets in > initialization differ in signedness > mx/TextTools/mxTextTools/mxte_impl.h:364: warning: pointer targets in > initialization differ in signedness > mx/BeeBase/mxBeeBase/btr.c:269: warning: ?dumpNode? defined but not used > mx/URL/mxURL/mxURL.c: In function ?mxURL_SetFromString?: > mx/URL/mxURL/mxURL.c:676: warning: pointer targets in initialization > differ in signedness > mx/UID/mxUID/mxUID.c: In function ?mxUID_Verify?: > mx/UID/mxUID/mxUID.c:333: warning: pointer targets in passing argument 1 > of ?sscanf? differ in signedness > /usr/include/stdio.h:415: note: expected ?const char * __restrict__? but > argument is of type ?unsigned char *? > mx/UID/mxUID/mxUID.c: In function ?mxUID_New?: > mx/UID/mxUID/mxUID.c:462: warning: pointer targets in passing argument 1 > of ?mxUID_CRC16? differ in signedness > mx/UID/mxUID/mxUID.c:199: note: expected ?unsigned char *? but argument > is of type ?char *? > In file included from /usr/include/string.h:640, > from /usr/include/python2.6/Python.h:38, > from mx/UID/mxUID/mx.h:66, > from mx/UID/mxUID/mxUID.c:27: > In function ?memset?, > inlined from ?mxUID_Fold? at mx/UID/mxUID/mxUID.c:239, > inlined from ?mxUID_fold? at mx/UID/mxUID/mxUID.c:630: > /usr/include/bits/string3.h:82: warning: call to > ?__warn_memset_zero_len? declared with attribute warning: memset used > with constant zero length parameter; this could be due to transposed > parameters All of the above are compiler warnings, so I guess the problem has something to do with setuptools... > error: Setup script exited with error: > build/bdist.linux-x86_64-py2.6_ucs4/dumb/egenix_mx_base-3.1.3-py2.6.egg-info: Is a directory > An error occured when trying to install egenix-mx-base 3.1.3. Look above > this message for any errors that were output by easy_install. > While: > Installing app. > Getting distribution for 'egenix-mx-base'. > Error: Couldn't install: egenix-mx-base 3.1.3 -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jan 04 2010) >>> 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 timothywayne.cook at gmail.com Mon Jan 4 18:24:51 2010 From: timothywayne.cook at gmail.com (Tim Cook) Date: Mon Jan 4 21:25:04 2010 Subject: [egenix-users] egenix-mx-base 3.1.3 on Ubuntu 9.10 In-Reply-To: <4B423D30.20402@egenix.com> References: <1262529875.25239.60.camel@localhost> <4B423D30.20402@egenix.com> Message-ID: <1262636691.5181.104.camel@localhost> Hi Marc-Andre, Thanks for the prompt reply. On Mon, 2010-01-04 at 20:10 +0100, M.-A. Lemburg wrote: > Which version of Python and setuptools are you using ? Python 2.6.4 and Python 2.6.2 depending on the developer. Everyone gets the same pinned version of setuptools: setuptools = 0.6c11 > > > Could you please "unhide" version 3.1.2 on Pypi until the issue is > > resolved? http://wiki.python.org/moin/CheeseShopTutorial This way I can > > pin the version to 3.1.2 > > This we'd rather not do, since 3.1.2 and previous versions have > a serious bug in mxBeeBase on Mac OS X and BSD platforms. Hmmm, okay. > All of the above are compiler warnings, so I guess the problem > has something to do with setuptools... Okay. Any ideas? We do have a temporary work around right now by unzipping the downloaded file (from the egenix website) into the virtual environment and then using setup.py install to put it inside the project. however this is kind of ugly compared to getting an egg automatically. :-) Thanks, --Tim -- *************************************************************** Timothy Cook, MSc LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == (upon request) Academic.Edu Profile: http://uff.academia.edu/TimothyCook You may get my Public GPG key from popular keyservers or from this link http://timothywayne.cook.googlepages.com/home -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : /mailman-archives/egenix-users/attachments/20100104/0ad63496/attachment.bin From mal at egenix.com Mon Jan 4 22:34:14 2010 From: mal at egenix.com (M.-A. Lemburg) Date: Mon Jan 4 22:34:19 2010 Subject: [egenix-users] egenix-mx-base 3.1.3 on Ubuntu 9.10 In-Reply-To: <1262636691.5181.104.camel@localhost> References: <1262529875.25239.60.camel@localhost> <4B423D30.20402@egenix.com> <1262636691.5181.104.camel@localhost> Message-ID: <4B425ED6.5010109@egenix.com> Tim Cook wrote: > Hi Marc-Andre, > Thanks for the prompt reply. > > On Mon, 2010-01-04 at 20:10 +0100, M.-A. Lemburg wrote: > >> Which version of Python and setuptools are you using ? > > Python 2.6.4 and Python 2.6.2 depending on the developer. > Everyone gets the same pinned version of setuptools: > setuptools = 0.6c11 > >> >>> Could you please "unhide" version 3.1.2 on Pypi until the issue is >>> resolved? http://wiki.python.org/moin/CheeseShopTutorial This way I can >>> pin the version to 3.1.2 >> >> This we'd rather not do, since 3.1.2 and previous versions have >> a serious bug in mxBeeBase on Mac OS X and BSD platforms. > > Hmmm, okay. > >> All of the above are compiler warnings, so I guess the problem >> has something to do with setuptools... > > Okay. Any ideas? > We do have a temporary work around right now by unzipping the downloaded > file (from the egenix website) into the virtual environment and then > using setup.py install to put it inside the project. however this is > kind of ugly compared to getting an egg automatically. :-) I've now tracked this down: The "problem" is that egenix-mx-base now provides it's own implementation of bdist_egg which easy_install use to build an egg from the source tarball. Due to the monkey patching applied by setuptools, a lot of distutils internals get modified in non-standard ways and while our bdist_egg works without problems to build the egg (e.g. if run manually), easy_install appears to expect some side effects caused by its various patched distutils commands which our version does not provide. We could provide egg files via PyPI as well, but the problem with that is ... again easy_install: it doesn't know about the difference between UCS2 and UCS4 builds of Python and so the eggs cannot use names which include this important build detail. While the system default Python installations typically use UCS4 on Linux, custom builds (as in e.g. Zope and Plone) often use the Python default UCS2. Since we're already experimenting with our own PyPI index to address the UCS2/UCS4 problem, you might want to use that for the time being... For UCS2 builds: python easy_install -i http://downloads.egenix.com/python/index/ucs2/ egenix-mx-base For UCS4 builds: python easy_install -i http://downloads.egenix.com/python/index/ucs4/ egenix-mx-base If you're using buildout, just add the correct index URL for the index to your "find-links = ..." section in buildout.cfg. See e.g. http://plone.org/documentation/manual/developer-manual/managing-projects-with-buildout/understanding-buildout.cfg for some details on how this works. In the next release of egenix-mx-base, we'll also add some support code to mxSetup.py which disables our own bdist_egg command if we find that setuptools has hooked up on distutils ;-) -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jan 04 2010) >>> 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 timothywayne.cook at gmail.com Mon Jan 4 21:08:05 2010 From: timothywayne.cook at gmail.com (Tim Cook) Date: Tue Jan 5 00:08:20 2010 Subject: [egenix-users] egenix-mx-base 3.1.3 on Ubuntu 9.10 In-Reply-To: <4B425ED6.5010109@egenix.com> References: <1262529875.25239.60.camel@localhost> <4B423D30.20402@egenix.com> <1262636691.5181.104.camel@localhost> <4B425ED6.5010109@egenix.com> Message-ID: <1262646485.5181.137.camel@localhost> Hi, Thanks for the great support. On Mon, 2010-01-04 at 22:34 +0100, M.-A. Lemburg wrote: > I've now tracked this down: ... > Due to the monkey patching applied by setuptools, a lot of > distutils internals get modified in non-standard ways and while > our bdist_egg works without problems to build the egg (e.g. > if run manually), easy_install appears to expect some side > effects caused by its various patched distutils commands > which our version does not provide. > Arrrgh! > We could provide egg files via PyPI as well, but the problem > with that is ... again easy_install: it doesn't know about the > difference between UCS2 and UCS4 builds of Python and so the > eggs cannot use names which include this important build detail. > > While the system default Python installations typically use > UCS4 on Linux, custom builds (as in e.g. Zope and Plone) > often use the Python default UCS2. An ongoing issue that I'm not sure why the labeling of eggs hasn't been adopted so easy_install could detect the correct one. http://bugs.python.org/setuptools/issue78 maybe I'm missing a bigger issue but this solution seems pretty straight forward to me. > Since we're already experimenting with our own PyPI index > to address the UCS2/UCS4 problem, you might want to use that > for the time being... > > For UCS2 builds: > python easy_install -i http://downloads.egenix.com/python/index/ucs2/ egenix-mx-base > > For UCS4 builds: > python easy_install -i http://downloads.egenix.com/python/index/ucs4/ egenix-mx-base > > If you're using buildout, just add the correct index URL for > the index to your "find-links = ..." section in buildout.cfg. This is a solution. We could put both find-links = lines in buildout.cfg and comment out the UCS2 one. Put a note in the installation instructions that if mx-base fails then have the user execute: python -c "import sys;print(sys.maxunicode<66000)and'UCS2'or'UCS4'" If they get back UCS2; change which line is commented in buildout.cfg ????? I just want to make installation as simple as possible. > In the next release of egenix-mx-base, we'll also add some > support code to mxSetup.py which disables our own bdist_egg > command if we find that setuptools has hooked up on > distutils ;-) > Thanks. Looking forward to the next version. Cheers, Tim -- *************************************************************** Timothy Cook, MSc LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook Skype ID == (upon request) Academic.Edu Profile: http://uff.academia.edu/TimothyCook You may get my Public GPG key from popular keyservers or from this link http://timothywayne.cook.googlepages.com/home -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : /mailman-archives/egenix-users/attachments/20100104/bb0a8502/attachment.bin From bdivey at gmail.com Thu Jan 14 10:40:52 2010 From: bdivey at gmail.com (Bryn Divey) Date: Thu Jan 14 09:41:15 2010 Subject: [egenix-users] mxODBC and Access 2007 Message-ID: <2a4e8c141001140040w7c84d49du50374bc715238fe0@mail.gmail.com> Hi all, A client who's using mxODBC over Microsoft Access has reported that with Access 2007 they're getting crashing happening - specifically, APPCRASH in mso.dll. The problem disappears when switching to an older version of Access (2003). The problem is reproducible across various machines. Does anyone know if this is a mxODBC error or an error lower down in Office? I'm a Unix dev, and not too familiar with the windows realm (; Thanks, Bryn Divey -------------- next part -------------- An HTML attachment was scrubbed... URL: /mailman-archives/egenix-users/attachments/20100114/97067995/attachment.htm From mal at egenix.com Thu Jan 14 10:21:24 2010 From: mal at egenix.com (M.-A. Lemburg) Date: Thu Jan 14 10:21:28 2010 Subject: [egenix-users] mxODBC and Access 2007 In-Reply-To: <2a4e8c141001140040w7c84d49du50374bc715238fe0@mail.gmail.com> References: <2a4e8c141001140040w7c84d49du50374bc715238fe0@mail.gmail.com> Message-ID: <4B4EE214.3030100@egenix.com> Bryn Divey wrote: > Hi all, > > A client who's using mxODBC over Microsoft Access has reported that with > Access 2007 they're getting crashing happening - specifically, APPCRASH in > mso.dll. The problem disappears when switching to an older version of Access > (2003). The problem is reproducible across various machines. Does anyone > know if this is a mxODBC error or an error lower down in Office? I'm a Unix > dev, and not too familiar with the windows realm (; This is the first time we hear of such a problem. Are there any entries in the Windows error log related to this ? Could you provide a test database and Python script which shows the problem ? Thanks, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Jan 14 2010) >>> 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/