Skip to content

Warning in test_labeled_data_unpacking.test_positional_parameter_names_as_function #5366

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.

Sign up for GitHub

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

Jump to bottom
Closed
mdboom opened this issue Oct 30, 2015 · 3 comments
Closed

Warning in test_labeled_data_unpacking.test_positional_parameter_names_as_function #5366

mdboom opened this issue Oct 30, 2015 · 3 comments
Milestone
v3.1.0

Comments

@mdboom
Copy link
Member

mdboom commented Oct 30, 2015 

matplotlib.tests.test_labeled_data_unpacking.test_positional_parameter_names_as_function ... /matplotlib/tests/test_labeled_data_unpacking.py:406: RuntimeWarning: Second argument is ambiguous: could be a color spec but is in data. Using as data.
Either rename the entry in data or use three arguments to plot.
  assert_equal(funcy(None, "x", "y1", data=data),
ok

@tacaswell: I think this warning is legit, and the test is testing it. In that case the test should put it in a catch_warnings block so it doesn't bubble out.
@tacaswell
Copy link
Member

Roughly related to https://github.com/matplotlib/matplotlib/pull/5244/files

@tacaswell tacaswell added this to the next bug fix release (2.0.1) milestone Oct 30, 2015
@QuLogic QuLogic modified the milestones: 2.0.1 (next bug fix release), 2.0.2 (next bug fix release) May 3, 2017
@tacaswell tacaswell modified the milestones: 2.1.1 (next bug fix release), 2.2 (next feature release) Oct 9, 2017
@github-actions
Copy link

This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

@github-actions github-actions bot added the status: inactive Marked by the “Stale” Github Action label Mar 18, 2023
@QuLogic QuLogic modified the milestones: future releases, v3.1.0 Mar 18, 2023
@QuLogic
Copy link
Member

QuLogic commented Mar 18, 2023

That file no longer exists, and neither does the test function, as it was removed in #10928.

@QuLogic QuLogic closed this as completed Mar 18, 2023
@QuLogic QuLogic removed the status: inactive Marked by the “Stale” Github Action label Mar 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v3.1.0
Development

No branches or pull requests
3 participants
@mdboom @tacaswell @QuLogic