'async' is a reserved keyword in Python 3.7 about duo_client_python

[AaronAtDuo]

#59 is up to resolve this. Hope to merge it soon!

[AaronAtDuo]

Sure thing. Sorry it got overlooked. We'll try to get that updated shortly.

[mschwager]

Side note: it may be worthwhile to allow failures on Python 3.7 on TravisCI for now (https://docs.travis-ci.com/user/customizing-the-build/#Rows-that-are-Allowed-to-Fail). Since that version hasn't been officially released yet it seems sane to not prioritize working on it, and not block green builds on that work.

[sontek]

Just ran into this while upgrading our releases to 3.7. Can we get a new release?

[gettes]

Yes, another vote for getting this fixed for 3.7 and the need to support alias1-4 for users objects, please!!

[jholt13]

Adding another voice to this, an updated library for Python3.7 would be appreciated.

[gettes]

Yes, not only the alias1..4 support on update but 3.7 as well. I believe the issue is ‘async’ is reserved. We run python apps in Docker containers and use the latest version of python so this too is needed. Thanks! /mrg

…

On Sep 11, 2018, at 4:47 PM, Justin Holt ***@***.***> wrote: Adding another voice to this, an updated library for Python3.7 would be appreciated. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#41 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAWpd2bHQfJieLIwUWy1gsd2HehiWNcCks5uaCFPgaJpZM4SCcT8>.

[AaronAtDuo]

Hi all,
We hope to address this soon. Duo uses this client internally, so we have to be careful about a backwards-incompatible change, in order to avoid breaking any of our own products...

So please bear with us as we work through that process, and we'll keep you posted when we are ready to address the 'async' parameter.

Aaron

[gettes]

Aaron - and everyone else at Duo - THANK YOU for the update and the commitment to move forward on this client. We very much appreciate the work you guys do! /mrg

…

On Sep 17, 2018, at 4:22 PM, AaronAtDuo ***@***.***> wrote: Hi all, We hope to address this soon. Duo uses this client internally, so we have to be careful about a backwards-incompatible change, in order to avoid breaking any of our own products... So please bear with us as we work through that process, and we'll keep you posted when we are ready to address the 'async' parameter. Aaron — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#41 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAWpdwoFLSN_gDy_3FHoOElXYEYCbWBCks5ucAR2gaJpZM4SCcT8>.

[AaronAtDuo]

My team has merged the PR, this issue should be resolved. Please let us know if there's any problems.

[taras-rudnyk-exa]

@AaronAtDuo, thanks for fixing this issue. Could you please upload new version (4.0.0) to PyPI?

[onkarnewgen]

Rename 'async' to anything else on each place in auth.py It will work fine