Kyle Benesch

I think the worst break was in libtcod 1.6.2 which took out two functions relating to keyboard repeat which wasn't a feature anymore in SDL2. That prevented some older projects...

I'll try to keep this rebased onto master. It'd be easy enough to split this into smaller PR's if you'd prefer that.

The project uses `contextlib` to replace the out/err streams, but that doesn't change much, since it's still `StringIO` for the stream that the running script sees. It still doesn't have...

I've confirmed that Fedora does package this module: https://packages.fedoraproject.org/pkgs/python-pytest-console-scripts/python3-pytest-console-scripts/ It's up to packagers downstream to provide ports of open-source Python packages. Any issues preventing pytest-console-scripts from being packaged should be...

I think it's too much effort to support something non-standard. This could technically be done but the end result would have drawbacks similar to a development install, and at that...

Sorry for disturbing you with my bike-shedding. I'll close this for now since it doesn't make much sense for newer packagers. If someone insisted then I might try to get...

Simple solution: Tell pytest to xfail that test if run locally on Windows. > Or I guess use the magic \\\\?\ shenangians Won't work. I remember the issue was with...

> Exhale could also choose different test directory Using a temp directory should work. Those are usually not nested too deeply. Using `tmp_path` from Pytest for example. It's something I...

In other cases, one can also give a reason with xfail: ```py @pytest.mark.xfail(sys.platform == "win32", reason="Paths my be too long for Windows.") ```

Since a corrected regular expression hasn't been mentioned yet I'd suggest the following: ellipsis with leading whitespace: `^\s*\.\.\.` Can be added to `pyproject.toml` like this: ```toml [tool.coverage.report] exclude_lines = ['^\s*\.\.\.']...