You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if there is a way to specify certain folders being selectively included/excluded depending on format (ie: source/wheel). My use case is that I would like to include my tests folder in the source distribution but exclude them when building the wheel. Is this currently possible? Essentially, something like the following:
For sdist:
[tool.flit.sdist]
include = ["docs/", "tests/"]
exclude = ["docs/*.html"]```
and for bdist_wheel:
[tool.flit.bdist_wheel]
include = ["docs/"]
exclude = ["doc/*.html", "tests/"]
I wasn't sure if this was a feature that was already implemented for flit, but I couldn't find anything in the documentation that suggested otherwise.
I would like to include my tests folder in the source distribution but exclude them when building the wheel.
The wheel contains whatever is in the package directory. So if your tests are outside the package directory (typically in a separate top-level tests folder), they'll automatically be excluded from the wheel. It's easy to include this folder in the sdist, and generally a good idea to do so.
On the other hand, if your tests are inside the package directory, as I see they are in xclim at present, that means (from Flit's perspective) that you want them to get installed with your package, for which they need to be in the wheel as well.
Hi,
I'm wondering if there is a way to specify certain folders being selectively included/excluded depending on format (ie: source/wheel). My use case is that I would like to include my
tests
folder in the source distribution but exclude them when building thewheel
. Is this currently possible? Essentially, something like the following:For sdist:
and for bdist_wheel:
I wasn't sure if this was a feature that was already implemented for
flit
, but I couldn't find anything in the documentation that suggested otherwise.Thanks,
Reference: pyOpenSci/software-submission#73 (comment)
The text was updated successfully, but these errors were encountered: