Closed loqs closed 1 month ago
Are you sure that this error happens because of my lib?
I think, that this error is correct, because you're trying to access func level fixture in class level fixture.
I think, that this error is correct, because you're trying to access func level fixture in class level fixture.
Any thoughts on what else in https://github.com/loqs/b2-sdk-python/commit/849831babe911bf1d9cb1eb7c1e64210188e497e could be triggering the issue? Have I misunderstood that pytest.lazy_fixture
can be replaced by pytest.lazy_fixtures
?
I do not know how the earlier one worked for you. Because it's the same if you just use a functional fixture in the class. It will be the same mistake. I suggest removing scope="class"
, then there will be no error. Alternatively, specify scope="class"
for in_memory_cache
and auth_info_cache fixtures
.
@loqs hi! Did you tried my suggestions?
I suggest removing scope="class", then there will be no error.
This worked. It also worked with pytest-lazy-fixture 3.5.7 unpatched on python 3.11 and patched for python 3.12 compatibility on 3.12. Would you consider it a latent bug that pytest-lazy-fixtures has detected?
Did you tried my suggestions?
Apologies for the slow response.
Yeah, I think that was a bug. I don't know how it was working previously.
@loqs may I close the issue?
I'm closing an issue
In relation to https://github.com/Backblaze/b2-sdk-python/issues/484 and coverting from from pytest-lazy-fixture to pytest-lazy-fixtures to achieve pytest 8 compatibility using https://github.com/Backblaze/b2-sdk-python
https://github.com/loqs/b2-sdk-python/commit/849831babe911bf1d9cb1eb7c1e64210188e497e
nox -s test-3.11
produced the following errorsIs this expected? If so any suggestions on how to resolve the failures?