-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Deprecate support for dash-offset = None. #15828
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
Conversation
87e9acf
to
9300485
Compare
Could we normalize The failures look real, but did not dig into them.... |
The failures are real, need to look into it. |
9300485
to
5345d49
Compare
5345d49
to
5b1be65
Compare
838c6fc
to
93f43a3
Compare
figured out the failure, now fixed, should be good to go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rebase and maybe small tweak to a sentence.
e.g. `plot([1, 2], ls=(None, (4, 4)))` which was previously a synonym for `plot([1, 2], ls=(0, (4, 4)))` which means "dash-pattern of 4pt-long dashes separated by 4pt spaces, with an offset of 0pt at start". Passing None instead of 0 was already not (likely, never) supported for pdf, ps, or svg (an exception is raised at savefig() time for ps/svg, an invalid pdf is generated). There isn't much of a point in supporting None (this also makes e.g. mplcairo more complex because of static typing in C++ extensions), so just deprecate it.
93f43a3
to
eb76378
Compare
edited accordingly, and rebased. |
PR Summary
e.g.
plot([1, 2], ls=(None, (4, 4)))
which was previously a synonymfor
plot([1, 2], ls=(0, (4, 4)))
which means "dash-pattern of4pt-long dashes separated by 4pt spaces, with an offset of 0pt at
start".
Passing None instead of 0 was already not (likely, never) supported for
pdf, ps, or svg (an exception is raised at savefig() time for ps/svg, an
invalid pdf is generated). There isn't much of a point in supporting
None (this also makes e.g. mplcairo more complex because of static
typing in C++ extensions), so just deprecate it.
Goes on top of #15827.
Edit: closes #14996, which is basically the issue described here.
PR Checklist