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

Deprecate axes collision#9037

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

Conversation

anntzer
Copy link
Contributor

Extends#9034. See discussion at#9024.

Feel free to push or force-push additional fixes to this PR.

PR Summary

PR Checklist

  • Has Pytest style unit tests
  • Code is PEP 8 compliant
  • New features are documented, with examples if plot related
  • Documentation is sphinx and numpydoc compliant
  • Added an entry to doc/users/next_whats_new/ if major new feature (follow instructions in README.rst there)
  • Documented in doc/api/api_changes.rst if API changed in a backward-incompatible way

@anntzeranntzerforce-pushed thedeprecate-axes-collision branch frombdd5a3b tod84c9baCompareAugust 15, 2017 11:54
@tacaswelltacaswell merged commit3769792 intomatplotlib:masterAug 15, 2017
@anntzeranntzer deleted the deprecate-axes-collision branchAugust 15, 2017 23:08
@QuLogicQuLogic added this to the2.1 (next point release) milestoneAug 16, 2017
dstansby pushed a commit to dstansby/matplotlib that referenced this pull requestAug 16, 2017
This was referencedSep 16, 2017
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestNov 19, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.Functions that create new axes (`axes`, `add_axes`, `subplot`, etc.)will now always create new axes, regardless of whether the kwargspassed to them match already existing axes.Passing kwargs to `gca` is deprecated. If `gca` is called withkwargs that do not match the current axes, then an exception israised.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestNov 19, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.Functions that create new axes (`axes`, `add_axes`, `subplot`, etc.)will now always create new axes, regardless of whether the kwargspassed to them match already existing axes.Passing kwargs to `gca` is deprecated. If `gca` is called withkwargs that do not match the current axes, then an exception israised.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestNov 19, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.Functions that create new axes (`axes`, `add_axes`, `subplot`, etc.)will now always create new axes, regardless of whether the kwargspassed to them match already existing axes.Passing kwargs to `gca` is deprecated. If `gca` is called withkwargs that do not match the current axes, then an exception israised.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestNov 19, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.Functions that create new axes (`axes`, `add_axes`, `subplot`, etc.)will now always create new axes, regardless of whether the kwargspassed to them match already existing axes.Passing kwargs to `gca` is deprecated. If `gca` is called withkwargs that do not match the current axes, then an exception israised.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestNov 19, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.Functions that create new axes (`axes`, `add_axes`, `subplot`, etc.)will now always create new axes, regardless of whether the kwargspassed to them match already existing axes.Passing kwargs to `gca` is deprecated. If `gca` is called withkwargs that do not match the current axes, then an exception israised.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestNov 19, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.Functions that create new axes (`axes`, `add_axes`, `subplot`, etc.)will now always create new axes, regardless of whether the kwargspassed to them match already existing axes.Passing kwargs to `gca` is deprecated. If `gca` is called withkwargs that do not match the current axes, then an exception israised.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestDec 6, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.Functions that create new axes (`axes`, `add_axes`, `subplot`, etc.)will now always create new axes, regardless of whether the kwargspassed to them match already existing axes.Passing kwargs to `gca` is deprecated. If `gca` is called withkwargs that do not match the current axes, then an exception israised.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestDec 19, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestDec 19, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestDec 19, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestDec 20, 2020
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestJan 7, 2021
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestJan 11, 2021
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestJan 19, 2021
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestJan 19, 2021
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestJan 19, 2021
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestJan 19, 2021
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
lpsinger added a commit to lpsinger/matplotlib that referenced this pull requestJan 21, 2021
In Matplotlib 2.1, the behavior of reusing existing axes whencreated with the same arguments was deprecated (seematplotlib#9037). Thisbehavior is now removed.The behavior of the functions to create new axes (`pyplot.axes`,`pyplot.subplot`, `figure.Figure.add_axes`,`figure.Figure.add_subplot`) has changed. In the past, thesefunctions would detect if you were attempting to create Axes withthe same keyword arguments as already-existing axes in the currentfigure, and if so, they would return the existing Axes. Now, thesefunctions will always create new Axes. A special exception is`pyplot.subplot`, which will reuse any existing subplot with amatching subplot spec. However, if there is a subplot with amatching subplot spec, then that subplot will be returned, even ifthe keyword arguments with which it was created differ.Correspondingly, the behavior of the functions to get the currentAxes (`pyplot.gca`, `figure.Figure.gca`) has changed. In the past,these functions accepted keyword arguments. If the keywordarguments matched an already-existing Axes, then that Axes wouldbe returned, otherwise new Axes would be created with thosekeyword arguments. Now, the keyword arguments are only consideredif there are no axes at all in the current figure. In a futurerelease, these functions will not accept keyword arguments at all.Fixesmatplotlib#18832.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@phobsonphobsonphobson approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v2.1
Development

Successfully merging this pull request may close these issues.

4 participants
@anntzer@phobson@tacaswell@QuLogic

[8]ページ先頭

©2009-2025 Movatter.jp