Ronny Pfannschmidt
Ronny Pfannschmidt
https://github.com/mitsuhiko/werkzeug/blame/3c9905f9a490b245dff7fa1d9d60e4b371c02608/werkzeug/utils.py#L658 blames to 2007 the commit is from 2009 i wonder of @mitsuhiko came up with it while experimenting with the descriptor protocol, or if it arose differently i vaguely...
so far it hasnt come up in my work anymore as well
since the python property is a data-property, that would mean always having a slow implementation the properties with annotations/ttl however look like a good candidate for that
It's what i currently do, I do prefer to minimise the linter ignores per project
it indeed is a real bug, however disallowing the syntax without the equal sign is unfortunately going to be a pretty painful breaking change thats likely not sitting well with...
Please try with the latest releases which has a bugfix wrt conftests finding
the pytest fixture parser should raise an error if either the fuction or the wrapped function has markers applied
we should check both, fixture, and at fixture parsing time, as we currently still need to catch stuff like ```python @pytest.mark.usefixtures('client') @pytest.fixture def user_tom(): print('user jessie') ```
@bluetech would it be sensible to introduce a generic protocol here ?
im happy to have 2 types for that, the fixture decorator could even apply it based on params and/or a flag for the param type required then mypy would fail...