zero323

By principle I don't see a problem here. My only concern is if some of the contributors have access (I cannot say if mine is still active) to Pluralsight, which...

I stay behind my previous comment ‒ if one of the maintainers is willing to check the content and vouch for it, I am OK with that. But if not,...

Yeah, we should probably remove these and a few more. I am not sure what is the best approach here though. When we discussed removals for the first time I...

@eliasah Now we [have one](https://github.com/awesome-spark/awesome-spark/blob/main/DEPRECATED.md), it is just a matter of making a sweep, though there are some things that can go directly into trash bin I guess (like Berkley...

This is a nice idea, but I have a few concerns. > This probably requires more knowledge of the internals than I currently have, but I think it might make...

> Why not just use `mypy`'s test then? Good question. I guess that depends on the use case. I used mypy tests in the past, and accumulated a lot of...

I guess that the real question is, why this part might be needed: https://github.com/typeddjango/pytest-mypy-plugins/blob/a2d4adde12b0024e62f2e1661fd0dd5abb4f9191/pytest_mypy_plugins/item.py#L302-L304 Are there any cases, where test case cache can leak to files not identified by simply...

Just thinking out loud: - Current `find_dependent_paths` logic should be dropped completely. It cannot be relied on. If anything, we might want to look at `cross_refs` (see below). - Possibly,...

ping @eliasah

Makes sense. Let's leave it open anyway ‒ its time will come one day!