Sam Lendle

For posterity, as a workaround I've been adding `torch1` to the default-groups config. Which works fine when I want torch1, but when working with torch 2, `uv sync --no-group torch1...

The same issue happens with extras ``` [project] name = "example" version = "0.1.0" requires-python = ">=3.10" dependencies = [ "rich>=14.0.0", "torch", ] [project.optional-dependencies] torch1 = ["torch=2"] [tool.uv] conflicts =...

@charliermarsh it looks like #9012 is specifically about `remove`? This issue also affects `add`, so I'm not sure it's a dupe

IMO it would be best to not enable this by default. It runs counter to the idea that dataframes are lazy by default, unless `spark.sql.repl.eagerEval.enabled` is set.

Bump. This is really hard to read and I am getting old. Even in the [docs](https://pytorch-lightning.readthedocs.io/en/2.5.1/pytorch/cli/lightning_cli_advanced_3.html) on the pytorch-lightning site, which are light themed, have dark code snippets. Same is...

I reported a similar or the same issue a few weeks ago though I have not received any response: https://github.com/databricks/databricks-vscode/issues/1688 @julianwucn I'm not affiliated with databricks but FYI your issue...