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

Fixed deprecated APIs in lines.py#26902

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

Merged
ksunden merged 1 commit intomatplotlib:mainfromrsp2210:main
Sep 27, 2023
Merged

Conversation

rsp2210
Copy link
Contributor

@rsp2210rsp2210 commentedSep 23, 2023
edited
Loading

PR summary

Fixed deprecated parts in set_xdata and set_ydata APIs in lines.py

PR checklist

@rsp2210
Copy link
ContributorAuthor

While working on your suggestions, I tried to update my codebase and squash my commits to 1 but it resulted in a merge conflict which I could not resolve. Therefore, I created a new PR. I hope that's ok.

@ksunden
Copy link
Member

@rsp2210 I would highly recommend not working onmain, which can help avoid some of those conflicts.

Can you rename the file to reflect the PR number (looks like an issue came in that snagged the number you put)?

Also add a blank line to the end of the release note file to make pre-commit CI happy.

@@ -0,0 +1,4 @@
``set_xdata`` and ``set_ydata`` requires an iterable.
Copy link
Member

Choose a reason for hiding this comment

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

This should mentionLine2D. Feel free to copy from the original deprecation release note:

``Line2D``
~~~~~~~~~~
When creating a Line2D or using `.Line2D.set_xdata` and `.Line2D.set_ydata`,
passing x/y data as non sequence is deprecated.

@rsp2210
Copy link
ContributorAuthor

@rsp2210 I would highly recommend not working onmain, which can help avoid some of those conflicts.

Can you rename the file to reflect the PR number (looks like an issue came in that snagged the number you put)?

Also add a blank line to the end of the release note file to make pre-commit CI happy.

I'll keep this in mind. Thanks for the guidance.

~~~~~~~~~~

When creating a Line2D or using `.Line2D.set_xdata` and `.Line2D.set_ydata`,
passing x/y data as non sequence is deprecated.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
passing x/y data as non sequence isdeprecated.
passing x/y data as non sequence isnow an error.

@ksunden
Copy link
Member

Do you feel comfortable squashing your commits down to avoid adding and deleting the same file?

Comment on lines 1 to 4
``Line2D``
~~~~~~~~~~

When creating a Line2D or using `.Line2D.set_xdata` and `.Line2D.set_ydata`,
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
``Line2D``
~~~~~~~~~~
When creating a Line2D or using `.Line2D.set_xdata` and `.Line2D.set_ydata`,
``Line2D``
~~~~~~~~~~
When creating a Line2D or using `.Line2D.set_xdata` and `.Line2D.set_ydata`,

Trailing whitespace

Copy link
Member

@QuLogicQuLogic left a comment

Choose a reason for hiding this comment

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

LGTM other than the trailing whitespace and squashing.

@ksundenksunden mentioned this pull requestSep 25, 2023
14 tasks
@rsp2210
Copy link
ContributorAuthor

LGTM other than the trailing whitespace and squashing.

I addressed the white space issue and followed the standard approach of squashing but it somehow increased the commits

@QuLogic
Copy link
Member

It appears you rebased commits fromupstream/main onto yourmain, not your ownmain on toupstream/main. This is usually why it's best to start from a separate branch.

@ksunden
Copy link
Member

Looks like the changes got lost in the rebase/sync with main, which made it so there are no commits here and this got closed...

@rsp2210rsp2210 reopened thisSep 26, 2023
@rsp2210
Copy link
ContributorAuthor

Looks like the changes got lost in the rebase/sync with main, which made it so there are no commits here and this got closed...

Yes, I'm trying to resolve the conflicts and I've never faced such issues before, learned much more about GitHub functionalities and good practices. I'll definitely keep in mind to not work on the main branch again, as this PR was made from the main branch I had no options but to reset and work on it to squash my commits. Therefore, I reopened it after applying changes. I really appreciate your patience with me.

~~~~~~~~~~

When creating a Line2D or using `.Line2D.set_xdata` and `.Line2D.set_ydata`,
passing x/y data as non sequence is now an error.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
passing x/y data as non sequence is now an error.
passing x/y data as non sequence is now an error.

This should fix pre-commit ci, which is complaining about the end of the file here

@ksundenksunden added this to thev3.9.0 milestoneSep 27, 2023
@ksundenksunden merged commit870293a intomatplotlib:mainSep 27, 2023
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@rcomerrcomerrcomer left review comments

@QuLogicQuLogicQuLogic approved these changes

@ksundenksundenksunden approved these changes

Assignees
No one assigned
Projects
None yet
Milestone
v3.9.0
Development

Successfully merging this pull request may close these issues.

4 participants
@rsp2210@ksunden@QuLogic@rcomer

[8]ページ先頭

©2009-2025 Movatter.jp