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

Django 3.0 is not compatible with extension #78

Closed
MuslimBeibytuly opened this issue Dec 4, 2019 · 12 comments
Closed

Django 3.0 is not compatible with extension #78

MuslimBeibytuly opened this issue Dec 4, 2019 · 12 comments
Assignees

Comments

@MuslimBeibytuly
Copy link

celery | File "/usr/local/lib/python3.8/site-packages/django_rest_passwordreset/models.py", line 3, in
celery | from django.utils.encoding import python_2_unicode_compatible
celery | ImportError: cannot import name 'python_2_unicode_compatible' from 'django.utils.encoding' (/usr/local/lib/python3.8/site-packages/django/utils/encoding.py)

@pakond
Copy link

pakond commented Dec 5, 2019

same problem here

@Close0
Copy link

Close0 commented Dec 11, 2019

+1

@ghost
Copy link

ghost commented Dec 13, 2019

#76 solves this issue

@frankyjquintero
Copy link

@anx-hnezbeda new realease please for support Django 3.0

@emilyemorehouse
Copy link

#80 is also required for Django 3.0 support (you'll see a psycopg2.errors.InvalidTableDefinition: multiple primary keys for table "django_rest_passwordreset_resetpasswordtoken" are not allowed error otherwise).

@neoCheck
Copy link

Hi @anx-hnezbeda thank you for maintaining the porject so far. Could you please make a new release which will allow us to use ithank you 😸

@yhoiseth
Copy link
Contributor

@chekroA In case it's helpful: I think you can install the version you need even before a new release is ready by specifying a branch.

@ghost
Copy link

ghost commented Jan 30, 2020

We made the 1.1.0 release today. This release includes #76 and #80

@yhoiseth
Copy link
Contributor

yhoiseth commented Feb 3, 2020

Thanks a lot 😃

@neoCheck neoCheck removed their assignment Feb 11, 2020
@tiago-peres
Copy link

For any particular reason this issue is still "Open"?

@neoCheck
Copy link

No, I think it should be closed. The issue was resolved in the 1.1.0 release. Thank you

@ghost
Copy link

ghost commented Apr 20, 2020

Yes it can be closed 🙂

This issue was closed.
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

8 participants