More info: If you do a
From future.utils import native And use native(dn) it will get you further (it will get a connection) But the tests fail a bit further down then where I am assuming we see more py3/py2 conversion problems. The issue is that we get a “newstr” in bytes for the dn and probably other variables suffer of the same issue. Cheers Bolke > On 6 Mar 2017, at 22:43, Bolke de Bruin <[email protected]> wrote: > > > Hint: It might be required to do a 'decode(“utf-8”)’ to make it pass. > > See the discussion on: https://github.com/cannatag/ldap3/issues/305 > > Bolke > > >> On 6 Mar 2017, at 08:00, Bolke de Bruin <[email protected]> wrote: >> >> Thanks! Much appreciated. >> >>> On 5 Mar 2017, at 22:23, Jayesh Senjaliya <[email protected]> wrote: >>> >>> Hi Bolke, >>> >>> I can help with ldap issue. >>> >>> I have faced same issue while trying to integrate with ldap earlier, and I >>> tracked down to the same get_connection function you mention in the ticket. >>> I think its really due to there difference between implementation of python >>> 2 vs python3 lib. >>> >>> anyway, I will look into it ( from this Tuesday) to see what kind of fix we >>> can put on Airflow side. >>> >>> Thanks >>> Jayesh >>> >>> >>> On Sun, Mar 5, 2017 at 11:24 AM, Bolke de Bruin <[email protected]> wrote: >>> >>>> Hi Folks, >>>> >>>> Our Travis builds have been failing for quite some time. This is due to 2 >>>> issues: >>>> >>>> 1. Pyscopg2 2.7.0 has a small regression that treats “None” as a string. I >>>> have a PR out that works around the issue: https://github.com/apache/ >>>> incubator-airflow/pull/2126 . This needs a review. >>>> >>>> 2. The python 2 builds are failing with ldap errors, while the same config >>>> passes on python 3. Honestly I am a bit at a loss here and I raised the >>>> issue with Ldap3 itself (https://github.com/cannatag/ldap3/issues/305), >>>> but it might not even be their issue. Trouble is I cannot reproduce it >>>> locally in a Jupyter notebook. >>>> >>>> I really need some help with #2, because debugging has been a challenge >>>> and for every change we try to make to get us to release I have to verify >>>> the output of the builds to see if the ‘right’ tests failed. >>>> >>>> Can someone please take a look? >>>> >>>> Cheers >>>> Bolke >>>> >>>> >>>> >> >
