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
Starting with PEP 621 - Storing project metadata in pyproject.toml, the Python community selected pyproject.toml as a standard way of specifying project metadata. Setuptools has adopted this standard and will use the information contained in this file as an input in the build process.
The scaffold project includes pyproject.toml, setup.cfg and setup.py.
All the data in setup.cfg and setup.py can be configured in pyproject.toml.
For the quickstart, most of it is already configured in pyproject.toml.
A scaffold template with two fewer files would be simpler for new users getting started with dagster.
Have extended the idea to generically skip files from the template to enable
dagster project scaffold quickstart --skip-files setup* --skip-files test
For the record, as a matter of taste, I prefer: dagster project scaffold quickstart --exclude setup* --exclude test
dbrtly
changed the title
Simplify scaffold project by removing duplicated code
Simplify scaffold project with option to exclude setup.cfg and setup.py
Oct 12, 2024
dbrtly
changed the title
Simplify scaffold project with option to exclude setup.cfg and setup.py
Simplify scaffold project with option to exclude files from the template
Oct 12, 2024
…tes (#25245)
PEP 621 (Nov 2020) introduced pyproject.toml.
Setuptools is fully compatible with pyroject.
All the config in setup.cfg and setup.py will also be in pyproject.toml
project template if this is merged.
Minimalist config to make adopting dagster easy.
## Summary & Motivation
See #25244
## How I Tested These Changes
![image](https://github.com/user-attachments/assets/75473daa-a282-4564-93fd-db1d95cf2691)
Last time I tried the run the test suite it failed because my macbook
has an intel chipset.
## Changelog
(CLI)
`dagster project scaffold`: Add option to create dagster projects from
templates with excluded files/filepaths
`dagster project scaffold-code-location`: Refactored to leverage
scaffold command with excludes flag. Deprecated.
---------
Co-authored-by: Colton Padden <[email protected]>
What's the use case?
Starting with PEP 621 - Storing project metadata in pyproject.toml, the Python community selected pyproject.toml as a standard way of specifying project metadata. Setuptools has adopted this standard and will use the information contained in this file as an input in the build process.
The scaffold project includes pyproject.toml, setup.cfg and setup.py.
All the data in setup.cfg and setup.py can be configured in pyproject.toml.
For the quickstart, most of it is already configured in pyproject.toml.
PEP621 was formally accepted in Nov 2020.
A scaffold template with two fewer files would be simpler for new users getting started with dagster.
Have extended the idea to generically skip files from the template to enable
dagster project scaffold quickstart --skip-files setup* --skip-files test
For the record, as a matter of taste, I prefer:
dagster project scaffold quickstart --exclude setup* --exclude test
Ideas of implementation
see PR #25245
Additional information
I would like to make the code contribution
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
The text was updated successfully, but these errors were encountered: