You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Python 2 end-of-life is approaching, we need to port user-sync to Python 3 for customers who are transitioning. As with umapi-client, we should support both Python 2 and 3.
The text was updated successfully, but these errors were encountered:
@ianmak I'd like you to take a shot at this. First look at the sources for the umapi-client, where I did this conversion a while ago. The key is to use the six module, which is a shim layer that maps both the 2.7 and 3.x modules to the same namespace. Then you find all the places where 2.7-isms are used, and you convert them to be the six-compatible version which also run in 3.x. Do some research and then tell me what you think; I think this could be right up your alley.
* move to pyldap rather than python-ldap to get py3 compatibility.
* carefully fix all the py2 and py3 CSV stuff to work with all character encodings, on both input and output.
* carefully fix all the ldap connections to use unicode for all input parameters, and only to apply decoding to output bytes.
As Python 2 end-of-life is approaching, we need to port user-sync to Python 3 for customers who are transitioning. As with umapi-client, we should support both Python 2 and 3.
The text was updated successfully, but these errors were encountered: