namespace-packages option stopped working in a recent update

[gokay05]

When running Ruff with version 0.1.11, namespace-packages option excluded INP001 from being thrown. I recently updated Ruff to 0.1.13 and even though my ruff.toml hasnt changed, I am getting a bunch of INP001 from my test folders and such. I checked the website and I dont see anything change in terms of how the option works, so I think there might be a bug in the new version that effectively breaks namespace-packages.

[charliermarsh]

Hmm, I don't think we changed anything there in this version range. Are you able to share an example, including the configuration? It's possible that your old setup was working due to caching, since the INP rules have a bug related to caching (and upgrading your Ruff version would clear the cache).

[gokay05]

Here is a small example that reproduces the issue: https://github.com/gokay05/namespace-test

When I run ruff check --config ruff.toml on this repo, I get the errors about the two folders that are in namespace-packages.

[charliermarsh]

Thanks so much for putting together a repro! I'll take a look.

[charliermarsh]

Hm, something about specifying the config explicitly?

namespace-test on  main
❯ ruff check . -n
namespace-test on  main
❯ ruff check . --config ruff.toml -n
namespacepackages/namespacepackages/folder2/file2.py:1:1: INP001 File `namespacepackages/namespacepackages/folder2/file2.py` is part of an implicit namespace package. Add an `__init__.py`.
nonpackage/nonpackagefile.py:1:1: INP001 File `nonpackage/nonpackagefile.py` is part of an implicit namespace package. Add an `__init__.py`.
Found 2 errors.

[charliermarsh]

Ah sorry, this is indeed a bug, my fault. Thank you so much for filing!

[charliermarsh]

Fixed in #9603, will go out in the next release.

[gokay05]

Thanks so much!!

[charliermarsh]

Thank you, I will always fix when there's a clear repro!