Henry Schreiner

Here's my grep-based summary (of the 17 tests): ``` tests/test_broken_project.py::test_invalid_generator FAILED [ 2%] tests/test_hello_cpp.py::test_hello_develop FAILED [ 22%] tests/test_include_exclude_data.py::test_hello_sdist FAILED [ 26%] tests/test_include_exclude_data.py::test_hello_sdist_with_base FAILED [ 27%] tests/test_issue274_support_default_package_dir.py::test_install_command FAILED [ 27%] tests/test_issue274_support_default_package_dir.py::test_test_command...

Ahh, okay. I'd recommend `-ra` over `-rs`, a summary of failures is really useful, just as or more useful than a summary of skips (and you get both with `-ra`)....

NumPy pins setuptools exactly, which breaks this test. They should not be doing this, but they do. You don't have a binary version of NumPy on your platform, so it's...

I think the best thing to do is to avoid numpy for PEP 518 tests. I'll see if we can drop it.

Could you turn off the deprecated tests? `-m "not deprecated"` will turn off all the "command" tests; they test distutils/setuptools commands, some of which write directly to site-packages. We won't...

Xref: #834

After #837, then this will be: ``` -m "not deprecated and not isolated and not nosetuptoolsscm" ``` Conda-forge should be able to use this too (minus the nosetuptoolsscm one, maybe...

Looks like `pytest_freezegun` (used by pluggy) is abandoned. There's a maintained "pytest-freezer" replacement. I have no idea what's pulling in `pytest_freezegun`, though.

I don't see anything in our dependencies (including `[test]`) that requires `pytest-freezegun`: ``` build==0.9.0 - packaging [required: >=19.0, installed: 21.3] - pyparsing [required: >=2.0.2,!=3.0.5, installed: 3.0.9] - pep517 [required: >=0.9.1,...

The problem is tkfontawesome doesn't have a `pyproject.toml`. Pip now builds in isolated mode by default, which means that it's incorrectly setting up the environment. (In Python 3.12, both distutils...