Victorien

The issue is valid, I just wanted to point out the relevant conformance test showing the same issue. However, a ticket raising the same issue might already exist.

> Please make sure that if the `__new__` return is untyped (returns `Any`) then it uses the class type implicitly. Not sure if that is already covered, but I suspect...

@intgr I'm not familiar with the mypy internal stuff, so I can't really figure out where this implicit class type usage could be implemented. Do you have any ideas about...

Should `stub`/`stub_batch` be typed to return `StubObject`? Still better than `Any`. Other than that, having this PR merged would be really useful, as you can't really make use of the...

> I'm not sure. StubObject is generic container, and from type-checking perspective it's empty, so you cannot access any attributes. Yes but at least people would know what object it...

Gentle bump @francoisfreitag considering how many people requested it

@CameronNemo: https://docs.pydantic.dev/latest/usage/pydantic_settings/ / https://docs.pydantic.dev/latest/migration/#basesettings-has-moved-to-pydantic-settings

Ah yes sorry misunderstood, `BaseSettings` has indeed moved to a separate package, but also got a massive rewrite. Maybe you can use the compat code from `pydantic.v1`? (available with pydantic...

I started looking into this a while ago by first fixing https://github.com/HypothesisWorks/hypothesis/issues/3356. However, the implementation is not perfect and some annotated types are not yet supported. If I find some...

@Zac-HD (sorry for the ping), when we implemented `annotated-types` to `hypothesis`, we roughly went for a way to map `at.BaseMetadata` -> `BaseStrategy.filter` condition. While Pydantic uses mostly the `BaseMetadata` subclasses...