Closed stdedos closed 8 months ago
What the status of this issue ? I would like to help if I can
It is mostly waiting on me to claim back my OSS time and do some basic sanity checks 😅 (and my insistence to avoid raising major versions for maximum inclusivity)
I apologize that my (announced?) timeline of "having this finished" would be ~Nov-15th, and I am "breaking that promise".
ok, there is no plan to fix it before v2 ?
According to Pierre's tries, no: https://github.com/pylint-dev/pylint-pytest/pull/23#issuecomment-1828607407
OTOH, the https://github.com/pylint-dev/pylint-pytest/milestone/1 (all v1.1.x versions) is closed ~1.5w ago, and the https://github.com/pylint-dev/pylint-pytest/milestone/2 is next (i.e., all repo modernizations, which includes upgrading Pythons, dropping setup.*
, and dropping EOL Pythons) - which will involve raising major version
If there is a "suitable bugfix" to be done for v1s, we can streamline it now (but it "feels like" https://github.com/pylint-dev/pylint/issues/8298 is not fixable in v1)
I started something in https://github.com/pylint-dev/pylint-pytest/pull/27. Unless there is some breaking change I'm not aware of, It seems like we can work with both major 2 and 3 of pylint
From the issue upstream: https://github.com/pylint-dev/pylint/issues/9144