Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

FUTURE BUG: reconsider how we deep-copy path objects #29157#29161

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed
saikarna913 wants to merge2 commits intomatplotlib:mainfromsaikarna913:Feature2
Closed

FUTURE BUG: reconsider how we deep-copy path objects #29157#29161

saikarna913 wants to merge2 commits intomatplotlib:mainfromsaikarna913:Feature2

Conversation

saikarna913
Copy link
Contributor

PR summary

  • it is necessary to solve the infinite recursion in__deep_copy__ function in path.py
  • it is creating the deep copy without infinite recursion
  • adding the memo dictionary with id as the self and value as the new instance created , makes the deep copy to stop the infinite recursion when same class is called since in MRO, the object will be the path class since there are no super classes for the path class which searches for__deep_copy__

PR checklist

Copy link

@github-actionsgithub-actionsbot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Thank you for opening your first PR into Matplotlib!

If you have not heard from us in a week or so, please leave a new comment below and that should bring it to our attention. Most of our reviewers are volunteers and sometimes things fall through the cracks.

You can also join uson gitter for real-time discussion.

For details on testing, writing docs, and our review process, please seethe developer guide

We strive to be a welcoming and open project. Please follow ourCode of Conduct.

@tacaswell
Copy link
Member

See#21280 for the context of why we are usingsuper(). We want to say "do the normal deepcopy thing and then make an extra change before it goes back to the user" and the original motivation for this was to fix deepcopy forPath sub-classes wheresuper() may have a non-trivial MRO to walk.

@rcomer
Copy link
Member

This PR requires a high level of python knowledge/experience, certainly beyond my level.@saikarna913 since you have opened a new PR against an easier issue, did you decide this one is also beyond your level? If so we should close this to signal to other contributors that the issue is available to work on.

@saikarna913saikarna913 closed this by deleting the head repositoryDec 8, 2024
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@github-actionsgithub-actions[bot]github-actions[bot] left review comments

Assignees
No one assigned
Projects
Status: Waiting for author
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

FUTURE BUG: reconsider how we deep-copy path objects
3 participants
@saikarna913@tacaswell@rcomer

[8]ページ先頭

©2009-2025 Movatter.jp