On Sat, Jul 21, 2018 at 01:13:14AM BST, Johan Huldtgren wrote: > On 2018/07/20 18:25, Stuart Henderson wrote: > > On 2018/07/20 10:24, Johan Huldtgren wrote: > >> On 2018/07/12 12:38, Raf Czlonka wrote: > >>> On Thu, Dec 07, 2017 at 04:34:13PM GMT, Johan Huldtgren wrote: > >>>>> there was a request recently to add a python3 flavor to py-oauth2, > > > > Did they say what they wanted it for? It seems that this has largely been > > replaced with oauthlib (certainly has in the ports tree anyway, and the > > module > > was only really added to support py-discogs-client). It would be easier to > > decide what to do with net/py-oauth2 if there was a reason to keep it. > > It was to get allow productivity/calcurse to sync with google calendar via > a python3 script[1] which apparently required an OAuth2 python library. I > don't know if this can be solved with oauthlib. If there is no use for > py-oauth2, as the original submitter I am more than happy to let it die, as > I have no use for it anymore.
I made a mistake - the dependency is on oauth2*client*[0], not any of the other oauth2 Python libraries mentioned below. [0] https://github.com/google/oauth2client [1] https://git.calcurse.org/calcurse.git/commit/contrib/caldav/calcurse-caldav.py?id=479e39fbb7393dcca7d3a475a09128b8c7ea7a43 > .jh > > [1] > http://git.calcurse.org/calcurse.git/tree/contrib/caldav/calcurse-caldav.py > > > (Annoyingly there are pypi projects "oauth2", "py-oauth2" and > > "python-oauth2" > > which makes it a bit confusing to decide if any projects are really using it > > ...) This only adds to the confusion. Regards and sorry for the noise. Raf
