MNT: put back _hold as read-only attribute on AxesBase#12274
MNT: put back _hold as read-only attribute on AxesBase#12274dstansby merged 1 commit intomatplotlib:masterfrom
_hold as read-only attribute on AxesBase#12274Conversation
This is to un-break the current version of cartopy.
|
attn @dopplershift |
|
basemap was able to manage this last year. See
matplotlib/basemap#328 and
matplotlib/basemap#334
…On Tue, Sep 25, 2018 at 2:06 PM Ryan May ***@***.***> wrote:
***@***.**** approved this pull request.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#12274 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AARy-Jy68OWonQBhCeBiUx3vhemTS8YJks5uenC1gaJpZM4W5FGn>
.
|
|
The issue is that |
|
Should the attribute raise a deprecation warning? |
|
@eric-wieser I lean towards no, because there is nothing that users of the current version of cartopy can do about this and cartopy now knows about this and plans to get rid of it. |
dstansby
left a comment
There was a problem hiding this comment.
I think this is fine without a warning; I think it is generally understood that we are free to do whatever we want with "private" functions/methods/classes that have an underscore at the beginning, and that external libraries shouldn't be using them.
…ibute on AxesBase
…274-on-v3.0.x Backport PR #12274 on branch v3.0.x (MNT: put back `_hold` as read-only attribute on AxesBase)
|
So, how do we feel about putting back |
|
No, I am strongly opposed to putting back ishold(). |
This is to un-break the current version of cartopy.