Alessio Bogon

I don't understand why applying the `usefixtures` marker to a fixture should result in an error. Fixtures can already use other fixtures by declaring them in the signature: ```python @pytest.fixture...

Sorry, I meant to say "What is the reason of **not** supporting the equivalent way with usefixtures?". So I am all about supporting it, not the other way around 😅.

So if I understand correctly this is just about making it resulting into an error, but the maintainers are not against this feature per-se, correct?

Ok, I'll give it a look then.

If anyone is still interested, I actually figured out a workaround for this. You can find it here, in this function that dynamically generates fixture functions: https://github.com/pytest-dev/pytest-factoryboy/blob/62474a25a80de3400d862d68d929c0a42a650f7c/pytest_factoryboy/fixturegen.py Basically I replace...

I started a project, [types-factory-boy](https://github.com/youtux/types-factory-boy), to add type annotations to factory boy. It is in early stage, and it most probably needs a plugin to automatically discover and create type...

Hello, I see that both sqlalchemy and mako provide wheels now, would it be possible to upload the wheels also for alembic? It cuts down some build time when installing...

https://github.com/pytest-dev/pytest-bdd/pull/540 should fix this

Fixed by https://github.com/pytest-dev/pytest-bdd/pull/548

I think that the parser treats everything within the Scenario as a "description", until the first "Given" is encountered. We should make sure that there is at least a "When"...