|
Yes, I think so. I outlined a plan somewhere.. The big compatibility problem is that where you once used Python2.x's strings ("str") to pass binary data, you would now have to use Python3's "bytes". And, other places where you would pass strings (like for attribute names) you might now have to pass unicode strings and python-ldap would convert these to UTF-8 under the covers. The other minor compatibility issue was that there is no 'int' in Python3, only longs now, but that turns out to be hardly noticeable. But going back to the bytes/string/unicode problem, I'd like to know if anyone has 2to3 migration/porting experience and if they might share some advice/wisdom. d Bruno Aguirre wrote: My hability to code a Python module is limited. But im glad to give a hand. |
------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf
_______________________________________________ Python-LDAP-dev mailing list Python-LDAP-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
