Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python 3.x compliant #31

Closed
foxmask opened this issue Apr 5, 2014 · 10 comments
Closed

Python 3.x compliant #31

foxmask opened this issue Apr 5, 2014 · 10 comments

Comments

@foxmask
Copy link

foxmask commented Apr 5, 2014

Hi, since the release of Python 3.4.x a lot can now be done, more than with python 2.7.x - I tried to install your api but oauth2 is not compliant at all for Python 3. It looks like oauthlib is the right lib to handle third party auth. Do you plan to switch to oauthlib or may you already did a dedicated branch for python 3.x ?
Regards

@cshoe
Copy link
Contributor

cshoe commented Apr 17, 2014

Hi @foxmask. This is definitely on my todo list. Thanks for the lead on oauthlib. I'll get to it as soon as I can.

@foxmask
Copy link
Author

foxmask commented Apr 20, 2014

thanks - I'll wait for it to finish to port my actual python module https://github.com/foxmask/django-th-readability for python 3.4x too

@cshoe
Copy link
Contributor

cshoe commented Apr 21, 2014

Oh man. Putting the pressure on! :)

I'm really hoping to have something done in the next couple days.

@cshoe cshoe mentioned this issue Apr 22, 2014
@greasematic
Copy link

Any updates on this? Really waiting for python3.4 support for readability

@cshoe
Copy link
Contributor

cshoe commented Sep 3, 2014

Hey @greasematic,

There is a PR open for this. It could probably use a little bit of testing and looks like it needs to be caught back up with master.

Unfortunately, I don't have write access to this repo anymore so I can't merge.

@greasematic
Copy link

Yep, saw the PR. Have left a comment there too. Hoping the folks with write access take note

@foxmask
Copy link
Author

foxmask commented Jun 26, 2015

could we fork and apply your PR on our own fork ? or everything is dead since 2 years without any activity....

@cshoe
Copy link
Contributor

cshoe commented Jun 26, 2015

I think forking is probably the best option. I don't know if this project is going to get much attention anymore.

@philipforget
Copy link
Contributor

@foxmask really sorry for how long it took me to address this. @cshoe thanks for doing 99% of that fix, just finished up the docs changes and added tox and travis ci integration.

I think @tylergaw is going to kill me for this though

chair-python

@tylergaw
Copy link

I'm into it 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants