Julian Edwards

I'm seeing the `only=` field completely ignored in my code. It dumps every single field in the nested object. We're working around it for now by using the `exclude=` instead...

Same here. I've overridden Api.representation to use custom schemas for json output, and it gives an error when rendering /api/spec/_/resource_list.json via the spec.html page.

This is quite a problem for my environment; some packages produce around 30-40 hashes and it takes over half an hour for my requirements to generate. Is anyone still working...

I'm using 5.0.0 and it still happens randomly.

> Can't you set this property in the base class? You can't do that because the blueprint is not known/available there. > I guess a more comprehensive code sample would...

Hmm, an ugly hack, :) This could work in some situations, but not all (mostly as you say the objects that the schema returns that don't have `__setattr__` on them)....

I'll see what I can do, I'll have to re-familiarise myself with the problem since it's been over a year.

> You can do something like this to build a single requirements file for both platforms: [#2679 (comment)](https://github.com/astral-sh/uv/issues/2679#issuecomment-2068208602) What about allowing the use of multiple `--platform` flags? Obviously it would...

I noticed `--universal` but I don't want *everything* as it slows down the whole run. I've gone from 1 hour on pip-compile to 5 minutes with UV because of this!

One way that I use the context is to pass information from a parent schema into a nested one for conditional validation. This change has made things quite a bit...