Closed abey79 closed 1 year ago
It would be great if a release could be made with that change :wink:
Just FYI, instead of depending on py
, if the only dependency is the TerminalWriter
, is to import it from from _pytest._io import TerminalWriter
. While it is a private module, might be cleaner than depend on the deprecated py
library.
@nicoddemus what's the difference between those 2 TerminalWriters?
None, we vendored py.io
into pytest a long time ago, and nothing on them has changed since then. 👍
pytest-xdist just did the same thing (importing TerminalWriter
from _pytest._io
).
@nicoddemus alright I've changed to what you've suggested but it turns out there were other issues, not sure if I've fixed correctly, can you take a look at https://github.com/ionelmc/pytest-benchmark/commit/c2e860f628116473e3134aba21492c04650d00a0 ?
At first glance it looks good!
Given there were more changes than just an import, you might consider releasing a hotfix which just adds the py
dependency, and after that make a new release which drops py
completely (with the changes from c2e860f).
Hi, thanks for the quick fix on the issue! When will pytest-benchmark
make the new release?
Just released 4.0.0
.
@ionelmc when will it be on conda-forge? Referring to this specifically: https://github.com/conda-forge/pytest-benchmark-feedstock
@pyrito I don't own that repository not do I know much about conda packaging so that question would be best answered by opening an issue in that repository. I doubt they have notifications for releases so it's best to just ping the maintainers.
The package
py
is used at least here but is not listed in the dependencies.Until version 7.1.x, Pytest would require
py
, but this has been dropped with Pytest 7.2, leading to the following error:This is fixed by explicitly manually installing
py
or addingpy
to the project.