-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spack Create Python: Parse pyproject.toml? #6629
Comments
This is smaller in scope, but I think it's somehow related to #1249 |
This is a bad idea. |
Ok, good to know. I saw several projects adding an extra Anyway, it's just a template proposal we would create from it, of course on can remove non-dependencies again :) |
Modernization of the issue: auto-populate the |
I don't know how common |
some of the more modern python tooling requires the pyproject.toml config file to be used, from experience enabling the use of the pyproject.toml file enforces pep517 which tends to break things in unexpected ways. |
The usage of both |
At some point Spack will probably need to support a new backend (or adapt |
This is related to the discussion in #30795. Basically, we either try to parse |
Wouldn't it be cool if we parsed the
requirements.txt
pyproject.toml
of a python project onspack create
to auto-populate thedepends_on(..., 'build')
packages we propose? :-)The text was updated successfully, but these errors were encountered: