ldap compatibility is by no means a measure of utility to web-applications. i've seen very few webapps need ldap, though many GUI and email systems often need it.
i'm wasn't a fan of python3 for web development about a year ago, because most of the core web utilities I needed weren't ported to python3 yet (oauth processors, document analyzers, etc). that has started to change quite a bit, and is well past the 50% mark... but not at 100% yet. i think you'd be best served by making a list of all the 3rd party tools you need, and dividing them into python-2 and python-3 columns. a lot of projects on pypi and github are marked "beta" but are definitely production ready and used in large scale environments. I've found "beta" be a better measure of the number-of-developers and maturity of automatic tests than a representative of stability. if you can make your project happen on python-3, i'd opt for that route. -- 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 pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
