ruff-ecosystem results

Linter (stable)

✅ ecosystem check detected no linter changes.

Linter (preview)

ℹ️ ecosystem check detected linter changes. (+15 -0 violations, +0 -0 fixes in 3 projects; 47 projects unchanged)

ruff check --no-cache --exit-zero --ignore RUF9 --output-format concise --preview --select ALL

+ airflow/plugins_manager.py:361:5: FURB154 [*] Use of repeated consecutive `global`
+ airflow/plugins_manager.py:422:5: FURB154 [*] Use of repeated consecutive `global`
+ airflow/plugins_manager.py:476:5: FURB154 [*] Use of repeated consecutive `global`
+ airflow/plugins_manager.py:503:5: FURB154 [*] Use of repeated consecutive `global`
+ airflow/providers/weaviate/hooks/weaviate.py:418:13: FURB154 [*] Use of repeated consecutive `nonlocal`
+ airflow/settings.py:194:5: FURB154 [*] Use of repeated consecutive `global`
+ airflow/settings.py:299:5: FURB154 [*] Use of repeated consecutive `global`
+ airflow/settings.py:426:5: FURB154 [*] Use of repeated consecutive `global`

ruff check --no-cache --exit-zero --ignore RUF9 --output-format concise --preview --select ALL

+ tests/unit/bokeh/document/test_callbacks__document.py:168:13: FURB154 [*] Use of repeated consecutive `nonlocal`

ruff check --no-cache --exit-zero --ignore RUF9 --output-format concise --preview --select ALL

+ zerver/data_import/slack.py:532:9: FURB154 [*] Use of repeated consecutive `nonlocal`
+ zerver/data_import/slack.py:604:9: FURB154 [*] Use of repeated consecutive `nonlocal`
+ zerver/lib/cache.py:63:5: FURB154 [*] Use of repeated consecutive `global`
+ zerver/lib/markdown/__init__.py:2727:5: FURB154 [*] Use of repeated consecutive `global`
+ zerver/lib/templates.py:106:5: FURB154 [*] Use of repeated consecutive `global`
+ zerver/tests/test_auth_backends.py:7644:13: FURB154 [*] Use of repeated consecutive `nonlocal`

Since globals and nonlocals are rare, could we try instead running this rule on every global and nonlocal statement, and then, for each statement, mapping back to the containing Suite and looking for global statements that follow it repeatedly?

In other words... instead of iterating over every body / statement, can we instead run this for each global? You can look at traversal::next_sibling or traversal::suite (and their usages) for an example.

Since globals and nonlocals are rare, could we try instead running this rule on every global and nonlocal statement, and then, for each statement, mapping back to the containing Suite and looking for global statements that follow it repeatedly?

In other words... instead of iterating over every body / statement, can we instead run this for each global? You can look at traversal::next_sibling or traversal::suite (and their usages) for an example.

@charliermarsh done.
Just a note: now the algorithm is quadratic on len(suite) for each suite containing global or nonlocal. Instead of linear (and should be auto vectorized) for each suite.

Thanks @alex-700. Blocked on me, will review shortly.

CodSpeed Performance Report

Merging #11187 will degrade performances by 9.38%

_{Comparing alex-700:latyshev/furb154 (d66b3f1) with alex-700:latyshev/furb154 (333b7f4)}

Summary

⚡ 9 improvements
❌ 8 regressions
✅ 13 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

I'm confused by the CodSpeed results but my guess is it's just confused by the branch being dated? We didn't touch the parser or lexer here of course.