-
Notifications
You must be signed in to change notification settings - Fork 88
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.5 compatibility problem #66
Comments
Sorry for not responding sooner, github mails go into a bit of a black hole for me :( I've reproduced this locally and will push a fix over the next day or two. Thanks! |
No problema, glad it helped :) |
Reopening because I haven’t fixed it yet :) |
This issue still haven't been fixed |
The issue and a solution was raised by silvioBi on 2020-04-12 danfairs#66
Any progress on this? There are some forks that claim to work with Django 3.x, but I would rather use upstream |
Would be nice if you can merge the related PR #67 Django 2.2 LTS support will end soon |
I hope this one will be fixed. BTW Thank You :) |
It's merged but the in Pypi is not update, unfortunately, the PR was missing the version bump.
|
@MattFanto I tried to install it based on your command and it was a no go. Is that command able to be used in requirements.txt? |
@Jazzthedog depends on what you are using (poetry pipenv, ...) the pip command should be something like
|
Thanks Matt, I fixed the problem manually before you replied.. :) The fact that i fixed it manually, when i update my requirements.txt, it will still be wrong? And, I can assume later when i publish this project to Heroku for example, i will have to go back manually correct it again :( How do you 'pin' to a particular package commit# in requirements.txt? |
Hi everyone! Unfortunately I haven't been able to reach Dan about this but a couple weeks ago I decided to create a spin-off package built from the ground up with modern Django and Python versions in mind. If you're still waiting for Django 3.0+ support, I invite you to check out |
Awesome, thanks @julianwachholz, I'll switch to that. |
I reached out to Dan on twitter, his company's twitter, and his linkedin. Hopefully something happens =) |
Hello I'm using Django 3.0.5 and
django.utils.decorators.available_attrs
is not supported anymore but it is used inlazysignup/decorators.py
. I have substituted it withWRAPPER_ASSIGNMENTS
as suggested in the docs and this it works fine:Sorry if I might have missed something or not used the right format but be patient this is the first issue that I open.
Hope it helped :)
The text was updated successfully, but these errors were encountered: