Am 25.02.2014 17:31, schrieb Whit Morriss:
forking it, making it py3 compatible, and issuing a pull request
In this case the show stopper is not pyramid_ldap which could easily be made Py 3 compatible, but the underlying libraries, particularly python-ldap which seems to be nontrival to port to Py 3 (it has a C extension and then the whole discussion starts again whether LDAP strings should be automatically converted to unicode strings now in Py 3 or stay as byte strings).
So at least in this case the question is more whether Python 3 is ready to go for web development, not whether Pyramid is ready. It's a bit disappointing to see that even such a mundane task as requesting an LDAP server is not yet solved in the Python 3 world (should actually be part of the standard lib). python3-ldap may be an alternative, but it's not compatible with python-ldap (and thus, ldappool) and looks still a bit experimental.
Still not sure where to go from here. Revert to Py 2? Put effort in making pyramid_ldap work with Py 3? Or maybe the solution is to not have Pyramid contact LDAP and other services directly, but use some middleware like Zato (https://zato.io/docs/)?
-- Chris -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
