Alastair Maw

> What should we do now that we are arriving the end of the deprecation period? Should we simply transform the warnings in errors? Would that be too disruptive in...

This now works for me with @BurntSushi's suggestion of adding the explicit conflicts for the lib to the top-level app. Thanks Andrew. 👍🏻 ``` [tool.uv] conflicts = [ [ {...

> For your own projects why are you depending on setuptools and note a more modern build system? (e.g. flit, hatchling, PDM, poetry_core, and soon uv_build). We're depending on uv,...

> > We're depending on uv, but uv in a CI environment apparently installs the latest setuptools as part of the bootstrap process for its build environment. > > It...

> We don't want to break other tools. What you are _still_ missing here despite the hundreds of thousands of man hours of disruption you caused globally yesterday is that...

> I was hopping that we could find a way to identify when it is safe to assume the field was intended to be consumed by setuptools You have two...

Thanks for looking at this. I'm using the CUE standard library from a tool file with `yaml.MarshalStream`. Would you like me to make you a PR to add an experiment...

> Do you have any further info in terms of which style should be the default and why? There is no one true style here, and I submit that this...

Did you have a chance to make a decision on this one? I'm running a custom fork of CUE at the moment to solve this problem, which is going to...