Skip to content

Sourcery: keep "use-next" check disabled

Tim Jaacks requested to merge keep-use-next-disabled into master

I don't see any benefit in accepting the refactoring suggestions based on this rule. IMO it makes the code harder to read, especially for non- experienced Python developers.

Merge request reports