Alessio Bogon

It'd be great also if the lazy fixtures could accept callables, and evaluate them when possible. We do that in pytest-factoryboy: https://github.com/pytest-dev/pytest-factoryboy/blob/ea91d7e7540340f6d758419eca52f3791310139e/pytest_factoryboy/fixture.py#L513-L516

Made a fix in https://github.com/aio-libs/yarl/pull/1023

This is actually a regression of version 1.9.1. Please guys fix this, or at least document it in the changelog as it's quite a breaking change!

Done: https://github.com/aio-libs/yarl/pull/1023

> First off, I would suggest catching the exception in your async code and generate some object or your own exception, which is serializable instead. The response object has its...

I can open a PR if you agree.

Still an issue

I'm experiencing the same problem

You have a few options: - Use `pytest_factoryboy.named_model`: ```python class SubscriptionProductFactory(DjangoModelFactory): class Meta: model = named_model("SubscriptionProduct", SubscriptionProduct) ... ``` - register the parent fixture passing the correct fixture to use...

maybe the SubscriptionProduct class is not a django model? In that case you have to use ModelFactoty instead of DjangoModelFactory. About the PR, I don’t think it’s needed since we...