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

Replace deepcopy of the Q object #543

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rrauenza
Copy link

@rrauenza rrauenza commented May 9, 2023

No description provided.

@rrauenza rrauenza marked this pull request as ready for review May 9, 2023 19:41
@rrauenza
Copy link
Author

rrauenza commented May 9, 2023

Still trying to run unit tests locally, hoping marking this PR as ready would trigger some on project side.

@rrauenza
Copy link
Author

rrauenza commented May 9, 2023

See #542

@rrauenza rrauenza changed the title Replace a deepcopy of the Q object with Q.all() Replace a deepcopy of the Q object May 9, 2023
@rrauenza rrauenza changed the title Replace a deepcopy of the Q object Replace deepcopy of the Q object May 9, 2023
@rrauenza rrauenza force-pushed the patch0 branch 6 times, most recently from 6616348 to ebf9c4d Compare May 10, 2023 23:56
@TomHaii
Copy link

TomHaii commented Jun 7, 2023

Can also confirm that is indeed fixing the issue in deepcopying Q objects. (reproduced on Python 3.7)

@alphatownsman
Copy link

Is there some unittest can cover the case it fixes?

@rrauenza
Copy link
Author

rrauenza commented Jul 7, 2023

I think if the existing unit tests work, that is sufficient, since it shows the change doesn't break from the current method of copying.

We could assign a non picklable object attr to one of the children to prevent future regression?

j-antunes pushed a commit to j-antunes/django-polymorphic that referenced this pull request Nov 14, 2023
@AdamDonna
Copy link
Contributor

+1 to adding a non picklable object attr to prevent future regressions or even an explicit scenario that should break in 3.7 without this fix

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

Successfully merging this pull request may close these issues.

4 participants