setup.py test is deprecated and broken. AFAIU it still uses
easy_install, which doesn't pay attention to python_requires of
dependencies, so when a transitive dependency drops Python 2.7 support
with a python_requires, pip can handle that, but easy_install can't.
I did not spend too much time investigating why exactly setup.py test
breaks: life's too short. It's deprecated and that's reason enough to
stop using it.
I'm going to use pytest instead (because nose is also deprecated, lol).
I'm not going to switch to pytest wholesale because that would break
Windows builds (see #92).
I've only started seeing this error today, only on Appveyor (but not on
my Windows Jenkins instance), and only on Python 2.7.
Somehow the sdist archive mentions the top-level directory name twice,
once with a slash, and once without. Possibly my own preprocessors
could've been adding the second entry. Anyway, strip it.
Again, I've no idea how I never saw this before. Did Appveyor update
their Python or something? Maybe a newer setuptools caused this?
It's a small package with no external depencencies. It'll be more
convenient for users who have pyproject.toml. And this way I can go
back to 100% test coverage without figuring out how to test both the
"toml is missing during import time" and "toml is present during import
time" branches in the code.
PEP 518 has introduced of pyproject.toml and it has been adopted by
other tools as the standard location for tooling configuration. This
allows for the check-manifest configuration to also be loaded from the
pyproject.toml file. Note this requires ``toml`` to be installed,
which is added as an optional extra.