Samuel Colvin

Bump. I think this is kind of important.

@Dreamsorcerer I see where you're coming from, but that doesn't help us with cases like https://github.com/pypi/support/issues/6382 where they've already name-squatted `pydantic2` and `pydantic3`. Of course you can say we should...

oh I see, makes sense 👍 .

@adityaraute if you want another model or provider, please create another issue.

@igor-silveira you have permission to create a fork and create a pull request from there - that's how GitHub works.

We have a separate issue about bedrock: #118. Mistral models are already supported by groq, and will be supported by #112. If you need something more, please create a new...

We haven't made a release yet, will do tomorrow. You can always install from main if you're impatient.

it made a release last night.

from https://github.com/samuelcolvin/rtoml/pull/85 it seems like the process is: * create a `.python-version` file if you don't want to use 3.13 by default * start adding dev dependencies `uv add --dev...

`Unset` sounds great, but it doesn't replace the need for `__fields_set__` i.g. if you want a useful default, and to know which fields have been set. You could accomplish this...