Re: Preparing release 2.3.1
Hi Michael, > I'd like to release 2.3.1 soon. still one question: Do you plan to upload some .eggs to PyPI then? I meanwhile successfully build eggs for i686-linux as well as Mac OS X 10.4 PPC (Intel platforms should work the same way) using Py 2.3 + 2.4. Nice to have would be an egg for the Windows platform, which I can't build due to the lack of a proper Windows devel environment. Anyway, after 2.3.1 is released, I'd be happy to contribute the mentioned .egg files - could you then upload them to PyPI? I could do that, too, but it's for you to decide... Best regards, Torsten -- Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de Ich schreibe dir einen langen Brief, weil ich keine Zeit habe, einen kurzen zu schreiben.-- Johann Wolfgang von Goethe -- - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: Preparing release 2.3.1
Torsten Kurbad wrote: > Hi Michael, >> I'd like to release 2.3.1 soon. > still one question: Do you plan to upload some .eggs to PyPI then? > I meanwhile successfully build eggs for i686-linux as well as Mac OS X 10.4 > PPC (Intel platforms should work the same way) using Py 2.3 + 2.4. > > Nice to have would be an egg for the Windows platform, which I can't build > due to the lack of a proper Windows devel environment. > > Anyway, after 2.3.1 is released, I'd be happy to contribute the mentioned > .egg files - could you then upload them to PyPI? > I could do that, too, but it's for you to decide... > Hi guys, Don't forget that the easy_install command works perfectly with project download pages on sf.net. So, I don't think it is necessary to upload .eggs to PyPI. In my opinion it would be better to keep files on sf.net and publish just the URL to the download page on PyPI. Best Regards, -- Timur Izhbulatov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7245 + ext.205 F:+7 495 105 7246 E:[EMAIL PROTECTED] Building Successful Supply Chains - One Solution At A Time. www.oilspace.com - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: Preparing release 2.3.1
Timur Izhbulatov wrote: > Don't forget that the easy_install command works perfectly with > project download pages on sf.net. So, I don't think it is necessary to > upload .eggs to PyPI. The question for me is: Does zc.buildout support this method. To clearify: We are developing projects that are widely based on Zope3 (http://www.zope.org). The zope corporation developed a concept named buildout to install .eggs locally in a project directory, which is interesting for users who don't have permission to write into the system's site-packages. This way, also different versions of python packages may coexist peacefully, since buildouts don't know the environment of their neighbors. I will check, if the buildout.cfg supports checking out and building eggs from sf.net, but nevertheless, building on e.g. OS X is a bit tricky, since it lacks the appropriate openldap-2.3 and sasl headers, not even to speak of Win32... And uploading to PyPI is as easy as: # python setup.py register bdist_egg upload Regards, Torsten -- Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de Ich schreibe dir einen langen Brief, weil ich keine Zeit habe, einen kurzen zu schreiben.-- Johann Wolfgang von Goethe -- - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: Preparing release 2.3.1
Torsten Kurbad wrote: > Timur Izhbulatov wrote: >> Don't forget that the easy_install command works perfectly with >> project download pages on sf.net. So, I don't think it is necessary to >> upload .eggs to PyPI. > The question for me is: Does zc.buildout support this method. To clearify: We > are developing projects that are widely based on Zope3 (http://www.zope.org). > The zope corporation developed a concept named buildout to install .eggs > locally in a project directory, which is interesting for users who don't have > permission to write into the system's site-packages. This way, also different > versions of python packages may coexist peacefully, since buildouts don't > know the environment of their neighbors. > > I will check, if the buildout.cfg supports checking out and building eggs > from sf.net, but nevertheless, building on e.g. OS X is a bit tricky, since > it lacks the appropriate openldap-2.3 and sasl headers, not even to speak of > Win32... According to [1] buildout supports the 'find-links' option which should solve your problem. Also, I don't think it has something to do with the location of your python libraries. For example, I keep most of the stuff I need in $HOME/lib/python. > And uploading to PyPI is as easy as: > > # python setup.py register bdist_egg upload Of course. But I think it's better to keep all eggs in one basket =) [1] http://www.zope.org/DevHome/Buildout/egg.html Cheers, -- Timur Izhbulatov OILspace, 26 Leninskaya sloboda, bld. 2, 2nd floor, 115280 Moscow, Russia P:+7 495 105 7245 + ext.205 F:+7 495 105 7246 E:[EMAIL PROTECTED] Building Successful Supply Chains - One Solution At A Time. www.oilspace.com - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: Preparing release 2.3.1
Timur Izhbulatov wrote: > > According to [1] buildout supports the 'find-links' option which > should solve your problem. Yes, I actively use that option to support our local eggs... ;o) So, not to get into some misunderstandings here: You'd like to keep the _precompiled_ .eggs in sf.net , not just the source? That would be perfectly fine with me. Regards, Torsten -- Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de Ich schreibe dir einen langen Brief, weil ich keine Zeit habe, einen kurzen zu schreiben.-- Johann Wolfgang von Goethe -- - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: Preparing release 2.3.1
Hi I tried the CVS head and got problem First I got this error when building the egg cc: unrecognized option '-R/usr/local/openldap-2.3/lib' The full command is /kolab/bin/cc -pthread -shared build/temp.linux-i686-2.4/Modules/LDAPObject.o build/temp.linux-i686-2.4/Modules/ldapcontrol.o build/temp.linux-i686-2.4/Modules/common.o build/temp.linux-i686-2.4/Modules/constants.o build/temp.linux-i686-2.4/Modules/errors.o build/temp.linux-i686-2.4/Modules/functions.o build/temp.linux-i686-2.4/Modules/schema.o build/temp.linux-i686-2.4/Modules/ldapmodule.o build/temp.linux-i686-2.4/Modules/message.o build/temp.linux-i686-2.4/Modules/version.o build/temp.linux-i686-2.4/Modules/options.o -L/usr/local/openldap-2.3/lib -R/usr/local/openldap-2.3/lib -lldap_r -llber -lsasl2 -lssl -lcrypto -o build/lib.linux-i686-2.4/_ldap.so I removed the references to /usr/local/openldap-2.3/ in setup.cfg and got and egg, I installed the egg and removed any old file from site packages rm -rf dsml.py dsml.pyoldapurl.pyc ldif.py ldif.pyo dsml.pyc ldapurl.py ldapurl.pyo ldif.pyc ldap/ I got the fologing error when starting my project: Traceback (most recent call last): File "./start-emailgency.py", line 53, in ? from emailgency.controllers import Root File "/s0/asx/src/emailgency/trunk/emailgency/controllers.py", line 8, in ? import main_ctrl, pas_sub_ctrl, addr_ctrl, common_ctrl File "/s0/asx/src/emailgency/trunk/emailgency/main_ctrl.py", line 12, in ? from emailgency import json, eg_dns, eg_mail, rrdtoolx, egsyslib, eg_config File "/s0/asx/src/emailgency/trunk/emailgency/egsyslib.py", line 8, in ? from eg_kolab_lib import KolabConnection File "/s0/asx/src/emailgency/trunk/emailgency/eg_kolab_lib.py", line 4, in ? import ldap, ldap.modlist, ldapurl File "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/__init__.py", line 48, in ? from functions import open,initialize,init,get_option,set_option File "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/functions.py", line 36, in ? from ldap.ldapobject import LDAPObject File "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/ldapobject.py", line 40, in ? from ldap.controls import LDAPControl,DecodeControlTuples,EncodeControlTuples File "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/controls.py", line 85, in ? class MatchedValuesControl(LDAPControl): File "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/controls.py", line 93, in MatchedValuesControl controlType = ldap.LDAP_CONTROL_VALUESRETURNFILTER AttributeError: 'module' object has no attribute 'LDAP_CONTROL_VALUESRETURNFILTER' any idea ? On 7/16/07, Michael Ströder <[EMAIL PROTECTED]> wrote: > HI! > > I'd like to release 2.3.1 soon. There are some interesting improvements > in HEAD but not yet released. Therefore testing of HEAD is needed. > Thanks to the contributors! > > Please provide feedback ideally on the mailing list. Thanks. > > Ciao, Michael. > > Current CHANGES: > > Released 2.3.1 2007-07-xx > > Changes since 2.3.0: > > * Support for setuptools (building .egg, thanks to Torsten) > * Support for matched values control (RFC 3876, thanks to Andreas) > > Lib/ > * Fixed ldif (see SF#1709111, thanks to Dmitry) > > Modules/ > * Added constant MOD_INCREMENT to support > modify+increment extension (see RFC 4525, thanks to Andreas) > > - > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > ___ > Python-LDAP-dev mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > -- -- Alain Spineux aspineux gmail com May the sources be with you - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: Preparing release 2.3.1
I did this, and it looks to be working. Also with my unicode extension :-) diff -r -c python-ldap-2.3.1/Modules/constants.c python-ldap/Modules/constants.c *** python-ldap-2.3.1/Modules/constants.c Tue Jun 5 11:56:15 2007 --- python-ldap/Modules/constants.c Tue Jul 17 15:26:14 2007 *** *** 263,266 --- 263,270 PyDict_SetItemString( d, "LDAP_CONTROL_PAGE_OID", obj ); Py_DECREF(obj); + obj = PyString_FromString(LDAP_CONTROL_VALUESRETURNFILTER); + PyDict_SetItemString( d, "LDAP_CONTROL_VALUESRETURNFILTER", obj ); + Py_DECREF(obj); + } On 7/17/07, Alain Spineux <[EMAIL PROTECTED]> wrote: > Hi > I tried the CVS head and got problem > > First I got this error when building the egg > > cc: unrecognized option '-R/usr/local/openldap-2.3/lib' > > The full command is > > /kolab/bin/cc -pthread -shared > build/temp.linux-i686-2.4/Modules/LDAPObject.o > build/temp.linux-i686-2.4/Modules/ldapcontrol.o > build/temp.linux-i686-2.4/Modules/common.o > build/temp.linux-i686-2.4/Modules/constants.o > build/temp.linux-i686-2.4/Modules/errors.o > build/temp.linux-i686-2.4/Modules/functions.o > build/temp.linux-i686-2.4/Modules/schema.o > build/temp.linux-i686-2.4/Modules/ldapmodule.o > build/temp.linux-i686-2.4/Modules/message.o > build/temp.linux-i686-2.4/Modules/version.o > build/temp.linux-i686-2.4/Modules/options.o > -L/usr/local/openldap-2.3/lib -R/usr/local/openldap-2.3/lib -lldap_r > -llber -lsasl2 -lssl -lcrypto -o build/lib.linux-i686-2.4/_ldap.so > > I removed the references to /usr/local/openldap-2.3/ in setup.cfg and > got and egg, I installed > the egg and removed any old file from site packages > > rm -rf dsml.py dsml.pyoldapurl.pyc ldif.py ldif.pyo dsml.pyc > ldapurl.py ldapurl.pyo ldif.pyc ldap/ > > I got the fologing error when starting my project: > > Traceback (most recent call last): > File "./start-emailgency.py", line 53, in ? > from emailgency.controllers import Root > File "/s0/asx/src/emailgency/trunk/emailgency/controllers.py", line 8, in ? > import main_ctrl, pas_sub_ctrl, addr_ctrl, common_ctrl > File "/s0/asx/src/emailgency/trunk/emailgency/main_ctrl.py", line 12, in ? > from emailgency import json, eg_dns, eg_mail, rrdtoolx, egsyslib, > eg_config > File "/s0/asx/src/emailgency/trunk/emailgency/egsyslib.py", line 8, in ? > from eg_kolab_lib import KolabConnection > File "/s0/asx/src/emailgency/trunk/emailgency/eg_kolab_lib.py", line 4, in ? > import ldap, ldap.modlist, ldapurl > File > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/__init__.py", > line 48, in ? > from functions import open,initialize,init,get_option,set_option > File > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/functions.py", > line 36, in ? > from ldap.ldapobject import LDAPObject > File > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/ldapobject.py", > line 40, in ? > from ldap.controls import > LDAPControl,DecodeControlTuples,EncodeControlTuples > File > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/controls.py", > line 85, in ? > class MatchedValuesControl(LDAPControl): > File > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/controls.py", > line 93, in MatchedValuesControl > controlType = ldap.LDAP_CONTROL_VALUESRETURNFILTER > AttributeError: 'module' object has no attribute > 'LDAP_CONTROL_VALUESRETURNFILTER' > > any idea ? > > On 7/16/07, Michael Ströder <[EMAIL PROTECTED]> wrote: > > HI! > > > > I'd like to release 2.3.1 soon. There are some interesting improvements > > in HEAD but not yet released. Therefore testing of HEAD is needed. > > Thanks to the contributors! > > > > Please provide feedback ideally on the mailing list. Thanks. > > > > Ciao, Michael. > > > > Current CHANGES: > > > > Released 2.3.1 2007-07-xx > > > > Changes since 2.3.0: > > > > * Support for setuptools (building .egg, thanks to Torsten) > > * Support for matched values control (RFC 3876, thanks to Andreas) > > > > Lib/ > > * Fixed ldif (see SF#1709111, thanks to Dmitry) > > > > Modules/ > > * Added constant MOD_INCREMENT to support > > modify+increment extension (see RFC 4525, thanks to Andreas) > > > > - > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > ___ > > Python-LDAP-dev mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > > > > > -- > -- > Alain Spineux > aspineux gmail com > May the sources be with you > -- -- Alain Spineux aspineux gmail com May the sources be with you -
Re: Preparing release 2.3.1
Hi again Could you add a note about how to build an egg at the end of INSALL file ? To avoid to spend 10min looking for the correct syntax in the setuptools documentation :-) python setup.py bdist_egg thanks On 7/17/07, Alain Spineux <[EMAIL PROTECTED]> wrote: > I did this, and it looks to be working. > Also with my unicode extension :-) > > > diff -r -c python-ldap-2.3.1/Modules/constants.c > python-ldap/Modules/constants.c > *** python-ldap-2.3.1/Modules/constants.c Tue Jun 5 11:56:15 2007 > --- python-ldap/Modules/constants.c Tue Jul 17 15:26:14 2007 > *** > *** 263,266 > --- 263,270 > PyDict_SetItemString( d, "LDAP_CONTROL_PAGE_OID", obj ); > Py_DECREF(obj); > > + obj = PyString_FromString(LDAP_CONTROL_VALUESRETURNFILTER); > + PyDict_SetItemString( d, "LDAP_CONTROL_VALUESRETURNFILTER", obj ); > + Py_DECREF(obj); > + > } > > > > On 7/17/07, Alain Spineux <[EMAIL PROTECTED]> wrote: > > Hi > > I tried the CVS head and got problem > > > > First I got this error when building the egg > > > > cc: unrecognized option '-R/usr/local/openldap-2.3/lib' > > > > The full command is > > > > /kolab/bin/cc -pthread -shared > > build/temp.linux-i686-2.4/Modules/LDAPObject.o > > build/temp.linux-i686-2.4/Modules/ldapcontrol.o > > build/temp.linux-i686-2.4/Modules/common.o > > build/temp.linux-i686-2.4/Modules/constants.o > > build/temp.linux-i686-2.4/Modules/errors.o > > build/temp.linux-i686-2.4/Modules/functions.o > > build/temp.linux-i686-2.4/Modules/schema.o > > build/temp.linux-i686-2.4/Modules/ldapmodule.o > > build/temp.linux-i686-2.4/Modules/message.o > > build/temp.linux-i686-2.4/Modules/version.o > > build/temp.linux-i686-2.4/Modules/options.o > > -L/usr/local/openldap-2.3/lib -R/usr/local/openldap-2.3/lib -lldap_r > > -llber -lsasl2 -lssl -lcrypto -o build/lib.linux-i686-2.4/_ldap.so > > > > I removed the references to /usr/local/openldap-2.3/ in setup.cfg and > > got and egg, I installed > > the egg and removed any old file from site packages > > > > rm -rf dsml.py dsml.pyoldapurl.pyc ldif.py ldif.pyo dsml.pyc > > ldapurl.py ldapurl.pyo ldif.pyc ldap/ > > > > I got the fologing error when starting my project: > > > > Traceback (most recent call last): > > File "./start-emailgency.py", line 53, in ? > > from emailgency.controllers import Root > > File "/s0/asx/src/emailgency/trunk/emailgency/controllers.py", line 8, in > > ? > > import main_ctrl, pas_sub_ctrl, addr_ctrl, common_ctrl > > File "/s0/asx/src/emailgency/trunk/emailgency/main_ctrl.py", line 12, in ? > > from emailgency import json, eg_dns, eg_mail, rrdtoolx, egsyslib, > > eg_config > > File "/s0/asx/src/emailgency/trunk/emailgency/egsyslib.py", line 8, in ? > > from eg_kolab_lib import KolabConnection > > File "/s0/asx/src/emailgency/trunk/emailgency/eg_kolab_lib.py", line 4, > > in ? > > import ldap, ldap.modlist, ldapurl > > File > > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/__init__.py", > > line 48, in ? > > from functions import open,initialize,init,get_option,set_option > > File > > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/functions.py", > > line 36, in ? > > from ldap.ldapobject import LDAPObject > > File > > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/ldapobject.py", > > line 40, in ? > > from ldap.controls import > > LDAPControl,DecodeControlTuples,EncodeControlTuples > > File > > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/controls.py", > > line 85, in ? > > class MatchedValuesControl(LDAPControl): > > File > > "/kolab/lib/python/site-packages/python_ldap-2.3.1-py2.4-linux-i686.egg/ldap/controls.py", > > line 93, in MatchedValuesControl > > controlType = ldap.LDAP_CONTROL_VALUESRETURNFILTER > > AttributeError: 'module' object has no attribute > > 'LDAP_CONTROL_VALUESRETURNFILTER' > > > > any idea ? > > > > On 7/16/07, Michael Ströder <[EMAIL PROTECTED]> wrote: > > > HI! > > > > > > I'd like to release 2.3.1 soon. There are some interesting improvements > > > in HEAD but not yet released. Therefore testing of HEAD is needed. > > > Thanks to the contributors! > > > > > > Please provide feedback ideally on the mailing list. Thanks. > > > > > > Ciao, Michael. > > > > > > Current CHANGES: > > > > > > Released 2.3.1 2007-07-xx > > > > > > Changes since 2.3.0: > > > > > > * Support for setuptools (building .egg, thanks to Torsten) > > > * Support for matched values control (RFC 3876, thanks to Andreas) > > > > > > Lib/ > > > * Fixed ldif (see SF#1709111, thanks to Dmitry) > > > > > > Modules/ > > > * Added constant MOD_INCREMENT to support > > > modify+increment extension (see RFC 4525, thanks to Andreas) > > > > > > - > > > This SF.net email is sponsored by DB2 Express > > > Download DB
Re: Preparing release 2.3.1
Alain Spineux wrote: > Hi again > > Could you add a note about how to build an egg at the end of INSALL file ? > To avoid to spend 10min looking for the correct syntax in the > setuptools documentation :-) > The setup.py comes with a very neat option that could have saved you lots of trouble and works with both distutils and setuptools. ;o) Try: python setup.py --help-commands Regards, Torsten -- Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de Ich schreibe dir einen langen Brief, weil ich keine Zeit habe, einen kurzen zu schreiben.-- Johann Wolfgang von Goethe -- - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: Preparing release 2.3.1
Alain Spineux wrote: > I did this, and it looks to be working. Ouch! Modules/constants.c was not comitted to CVS. Thanks. > Also with my unicode extension :-) I knew you would ask for it. I will follow-up on this later... Ciao, Michael. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re: Preparing release 2.3.1
Torsten Kurbad wrote: >> I'd like to release 2.3.1 soon. > still one question: Do you plan to upload some .eggs to PyPI then? > I meanwhile successfully build eggs for i686-linux as well as Mac OS > X 10.4 PPC (Intel platforms should work the same way) using Py 2.3 + > 2.4. > > Nice to have would be an egg for the Windows platform, which I can't > build due to the lack of a proper Windows devel environment. > > Anyway, after 2.3.1 is released, I'd be happy to contribute the > mentioned .egg files - could you then upload them to PyPI? I could do > that, too, but it's for you to decide... Being in the role of the maintainer I'm always concerned about continuous support for a certain mechanism. Since .egg files are platform-specific the question arises: Who is going to provide which builds for every new release? On which platforms/distros? With which OpenLDAP/SASL/OpenSSL libs? Today especially the situation regarding Win32 builds is poor. A *strong* commitment of volunteers is needed... Ciao, Michael. - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
Re[2]: Preparing release 2.3.1
On Wednesday, July 18, 2007 at 08:01 Michael Ströder wrote: > Being in the role of the maintainer I'm always concerned about > continuous support for a certain mechanism. Understandable. > Since .egg files are > platform-specific the question arises: > Who is going to provide which builds for every new release? Good question. > On which platforms/distros? > With which OpenLDAP/SASL/OpenSSL libs? There are some systems that make the decision easy: Mac OS X, e.g. comes with a set of SASL and OpenLDAP libs by default. After getting the necessary headers from a Linux-Installation I was able to build .eggs there with the standard system-Python (2.3.5). On Linux, of course, the situation is much more difficult. I use Gentoo, which is in many ways very standards compatible, but I use bleeding edge libraries, like glibc 2.6, OpenLDAP 2.3.36 etc. The past showed that an old distribution, like RedHat 8, combined with some newer libraries, but with an "old" glibc provides almost 100% compatibility of binary builds to other distros. I think, it's a question of defining prerequisites, like: If you want to run this from an .egg, you need at least OpenLDAP 2.3, etc. But still, it's a complex task that should be shared among several people. > Today especially the situation regarding Win32 builds is poor. A > *strong* commitment of volunteers is needed... Yes, I understand that. For the moment let's perhaps agree to the following: After 2.3.1 is out, I will build .eggs on every platform and every OS at my disposal and put them in our "private" distribution at http://svn.kmrc.de/distribution If you want to, you may announce that on the Homepage and/or in the docs then, but with a remark saying that these .eggs may be out of date. Whenever I can spare the time, I'll build .eggs for upcoming releases. Greetings, Torsten -- Fon: +49-7071-700240 | Fax: +49-7071-700241 | http://www.tk-webart.de Never make anything simple and efficient when a way can be found to make it complex and wonderful. - Murphy's Law No. 13 - - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ Python-LDAP-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
