BUG: `pd.test` does not respect passing pandas specific markers

[mroeschke]

xref conda-forge/pandas-feedstock#147

When installing pandas and trying to run pd.test(["-m slow"]), -m slow will not necessarily be respected because our custom markers are defined in pyproject.toml

../_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold/lib/python3.9/site-packages/pandas/tests/io/test_html.py:375
../_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold/lib/python3.9/site-packages/pandas/tests/io/test_html.py:375
  $PREFIX/lib/python3.9/site-packages/pandas/tests/io/test_html.py:375: PytestUnknownMarkWarning: Unknown pytest.mark.slow - is this a typo?  You can register custom marks to avoid this warning - for details, see https://docs.pytest.org/en/stable/how-to/mark.html
    @pytest.mark.slow

Since pd.test runs with pytest.main which doesn't have a way to register the custom markers, pd.test is not fully working when running from a package.

[lithomas1]

I don't think we ship pyproject.toml with wheels. Maybe adding to MANIFEST.in will fix it https://github.com/pandas-dev/pandas/blob/main/MANIFEST.in.

[jakirkham]

Yeah was looking in the Conda packages too and didn't see it

[lithomas1]

If you build from the Github release sdist, than MANIFEST.in is probably the root cause, since the Github release sdist is also uploaded to PyPI IIRC.

[mroeschke]

Yeah since this API is public, I think including pyproject.toml in the wheels would be necessary. Don't think there should be any downsides?

[lithomas1]

Fix has been reverted.