forked from xarg/django-stdimage
-
-
Notifications
You must be signed in to change notification settings - Fork 63
Django 3.2 setUpTestData uses copy.deepcopy() #246
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
Labels
Comments
Hi @vchrisb, Thanks for reaching out and good find. Would you be interested in providing a patch? I be delighted to review it. Best, |
I'll see what I can do. 👍 |
I am facing similar issue with django32 tests cases. Is there any plan for patch ? |
codingjoe
pushed a commit
to vchrisb/django-stdimage
that referenced
this issue
Mar 19, 2022
codingjoe
pushed a commit
to vchrisb/django-stdimage
that referenced
this issue
Mar 19, 2022
codingjoe
pushed a commit
that referenced
this issue
Mar 19, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using
setUpTestData()
withdjango-stdimage
in Django 3.2 does not work anymore, as it look likecopy.deepcopy()
is not supported withdjango-stdimage
.The text was updated successfully, but these errors were encountered: