[MacPorts] #65145: py39-matplotlib @3.5.2_0: plotting problem in IPython with %matplotlib

[MacPorts]

#65145: py39-matplotlib @3.5.2_0: plotting problem in IPython with %matplotlib
----------------------------+------------------------
  Reporter:  aaronm6        |      Owner:  reneeotten
      Type:  defect         |     Status:  assigned
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.7.2
Resolution:                 |   Keywords:
      Port:  py-matplotlib  |
----------------------------+------------------------

Comment (by reneeotten):

 Replying to [comment:3 aaronm6]:
 > Thanks for checking.  Admittedly, I have not tried it with packages
 installed via e.g. conda; but if you have and you also see this issue,
 then that does suggest it's not a problem specific to MacPorts.  I suspect
 the ipython devs will care more about this than the matplotlib devs; in
 any case, I will file a ticket there and update this thread with anything
 I learn.

 To be clear, I didn't try and install the packages through {{{conda}}} to
 see if the problem exists there as well. If you have the time to try that
 please do (otherwise I'll get to that at some point). I can poke around in
 the the {{{matplotlib}}} GitHub a bit to see if there is anything that
 suggest what has changed between the two versions.

 > Regarding your final question: the packages are otherwise identical. I'm
 using `port activate` to toggle back and forth between 3.5.2 and 3.5.1.
 The problem arose when I did a `port upgrade outdated`, so a few packages
 were updated.  However, toggling the matplotlib version was the only thing
 I could find that would impact the observed behavior.

 okay, thank you for clarifying that. We can certainly check to see if
 upstream (either `matploblib` or `ipython`) has any bug reports and/or a
 possible fix that we can backport in MacPorts.

-- 
Ticket URL: <https://trac.macports.org/ticket/65145#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS