Closed baggiponte closed 1 month ago
Ciao @dacorvo - sorry if I went on and opened this PR but I wanted to try this out locally.
With this setup, I can build quanto
locally. I cannot reproduce the metadata bug you mention in the issue I opened. Can you help me create a setup where I can test that? Thanks!
(Also: would you like swapping black
for ruff's native formatter? 🔥)
With this setup, I can build
quanto
locally. I cannot reproduce the metadata bug you mention in the issue I opened. Can you help me create a setup where I can test that? Thanks!
I will try it also, but I might request you to add some specific tests to verify that the extension is correctly detected and built on all platforms (typically, before adding setuptools_scm the non-python files were not be included in the package).
(Also: would you like swapping
black
for ruff's native formatter? 🔥)
I will try it also, but I might request you to add some specific tests to verify that the extension is correctly detected and built on all platforms
Sure! Would you have some suggestions on how to start and run the tests? e.g. should I use dockerfiles or rely on CI/CD?
(typically, before adding setuptools_scm the non-python files were not be included in the package).
I think this should cover us. Are you referring to the files under quanto/ext
?
This PR is stale because it has been open 15 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This PR was closed because it has been stalled for 5 days with no activity.
What does this PR do?
'
with"
for consistency inpyproject.toml
setuptools_scm
from the[build-backend]
section inpyproject.toml
README.md
from thedynamic
sectionsetup.py
Fixes #123
Before submitting
Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag members/contributors who may be interested in your PR.