Hayden Richards

I ran into a similar issue in my CI, which I fixed by setting the `HATCH_PYTHON` environment variable to the appropriate path: https://github.com/SupImDos/pydantic-argparse/pull/67 It seems like there should be a...

> do you have a minimal reproduction for this? 😊 Hi @patrick91, yes - see the unit tests in the branch / commit below, which contains 2 unit tests that...

@patrick91 I've put together a draft PR in an attempt to fix this: #3832. I'm not 100% sure that this is the right way to handle this (or whether there's...

> Dear @SupImDos, is there any possible update soon? Unfortunately I've been very busy lately, so its hard to put a timeline on things at the moment. I would say...

> I just found out that pydanticv2 might support the functionality already: [pydantic-settings](https://docs.pydantic.dev/2.8/concepts/pydantic_settings/#subcommands-and-positional-arguments) @noootch Oh wow, that's great! In that case, maybe this package should pivot to just supporting Pydantic...

> I wonder if we can maybe scope the cache to the schema? Or maybe when applying the extensions we make a copy of the field? > > Just think...

@patrick91 & @bellini666 Sorry for the immediate follow-up, but I've got some extra context that might influence our decision / implementation. I looked into copying fields in my project, and...

Hi @patrick91 & @bellini666 In the short term I ended up working around this issue by avoiding the need for two schemas. However, I think think the original issue in...

I've discovered that this functionality appears to (maybe incidentally) be possible when you use Relay. For reference, take the following example: ```python @strawberry_django.type(MyParentModel) class MyParentType(relay.Node) name: strawberry.auto @classmethod def get_queryset(cls,...

@bellini666 Thanks, we're glad you agree! At the moment, this issue isn’t at the top of our priority list, but we're happy to look into opening a PR when we...