Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Why would this be a solution? If there is a problem with the latest version of matplotlib, it would be good to know what it is, such that it can be fixed. Commented Mar 7, 2018 at 17:33
  • 3
    @ImportanceOfBeingErnest This is the solution. Why? Because the most recent stable release of matplotlib significantly broke backward compatibility by deleting the long-standing public matplotlib.verbose API. This effectively means that all downstream applications (like PyCharm) requiring matplotlib as a third-party dependency now need to blacklist matplotlib 2.2.0 in the hopes that their next stable release will revert this obvious horrifying breakage. In other words, they screwed up. Big time. Commented Mar 9, 2018 at 5:46
  • @CecilCurry I completely agree. My comment was inviting to extend the answer as to why this is a solution. Since that did not happen, I provided an answer myself. Commented Mar 9, 2018 at 9:18
  • 1
    Right. Thanks for chiming in at matplotlib#10716, too. Excellent work, team. Commented Mar 9, 2018 at 9:51