Daniel Bartley

What's the bar required to green light this? I'd like to contribute but reluctant to do try doing it all without guidance.

I did a test on dagster+. Turns out dagster+ has a hardcoded dependency on setup.py or requirement.txt. The responsible code is here. Not sure if it is justifiably pessimistic about...

@PedramNavid @cmpadden How do you feel about installing on dagster+ with uv to replace pex? https://docs.astral.sh/uv/concepts/tools/ https://github.com/dagster-io/dagster-cloud-action/pull/202 After above PR, I will do PR on dagster-cloud to remove: https://github.com/dagster-io/dagster-cloud/blob/main/dagster-cloud-cli/dagster_cloud_cli/commands/serverless/__init__.py#L534-L545 and...

I'm doing: ``` cargo install ctoml ctoml pyproject.toml tool.hatch.envs.default.installer pip ```

what if the command was `uv run ruff --output-file ruff.uvx` with the -o/--output agument as an indicator to create the binary file rather than execute this tool right now. and...

@jdegenstein it sounds like you want to do `uv tool install my_app` but have it work even if uv is not installed on the client machine.

When installer = "uv" Can path_to_venv please be the uv default behaviour of a directory in cwd?

An explicit statement that config.toml is a global config would help alot. That confused me. I thought it was supposed to be added to the project not the machine.

Note that excludes is flexible. dagster project scaffold --name qs \ --excludes "asset" \ --excludes "test" \ --excludes "setup*"

To me no that would be even better. I assumed the comms to remove them would be involved. My baggage.