Steven Casagrande

Here's what I'd do, depending on what course of action you want for the implementation: - Implemented without breaking anything else: minor version bump, prioritise 1.0 - Implemented with breaking...

This matplotlib>=1.5 requirement should be listed somewhere in the project. A good place might be under optional requirements in `setup.py`

Right, but matplotlib is an _optional_ requirement and can be listed as such. I also imagine it should be listed in the docs somewhere. Actually, checking just now the matplotlib...

I checked travis, its reporting failures on doctest for both 2.7 and 3.5 3.5: `Could not import extension matplotlib.sphinxext.only_directives`, which was apparently removed in matplotlib 3 https://github.com/matplotlib/matplotlib/pull/11295 2.7: `ImportError: cannot...

My testing so far indicates that the above suggested change also resolves my pyo3 issue.

Since my post I have removed my dependency on `libpython` for my `pyo3` target by enabling the "extension-module" and "abi3-py38" features for `pyo3`. I should have realized that sooner, whoops....

I *just* came up with another solution for myself that completely avoids having `libpython` as a dependency for my `pyo3` target. I should have thought of this ahead of time,...

Yeah, using `dev_dependency=True` is totally fair for a lot of use cases. If we want to keep the `fail` call then perhaps we should update the message to suggest this...

Sadly I don't know much about it yet, but I had a rust developer in my org ask me about it

@criemen did you find a solution here? I am in a similar boat, where I want to download and extract 1 copy of the rust toolchains, using zst compression, hosted...