Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
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
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters
bdd5a3b
tod84c9ba
Comparephobson approved these changesAug 15, 2017
dstansby pushed a commit to dstansby/matplotlib that referenced this pull requestAug 16, 2017
API: Deprecate axes collision
This was referencedSep 16, 2017
Closed
3 tasks
6 tasks
7 tasks
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.
6 tasks
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.
7 tasks
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
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Extends#9034. See discussion at#9024.
Feel free to push or force-push additional fixes to this PR.
PR Summary
PR Checklist