Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@loathingKernel
Copy link
Contributor

Using pip install . or python -m build fails if this directive it
present. Both of these commands work correctly without the directive by
using a barebones setup.py.

On the other hand, removing this directive breaks
python3 -m setuptools_scm --force-write-version-files which is used
in the workflows to generate rare/_version.py before packaging. In the
case of the workflows though we already override the version using
SETUPTOOLS_SCM_PRETEND_VERSION so it shouldn't be an issue.

Using `pip install .` or `python -m build` fails if this directive it
present. Both of these commands work correctly without the directive by
using a barebones `setup.py`.

On the other hand, removing this directive breaks
`python3 -m setuptools_scm --force-write-version-files` which is used
in the workflows to generate `rare/_version.py` before packaging. In the
case of the workflows though we already override the version using
`SETUPTOOLS_SCM_PRETEND_VERSION` so it shouldn't be an issue.
@loathingKernel loathingKernel merged commit 4fee301 into RareDevs:main Aug 25, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant