INP001 outputs the code of the file which is part of an implicit namespace package

[adamtheturtle]

ruff 0.4.10 Edit: I pasted wrong! ruff 0.5.1

This makes me think that the code has an error in it, that I am looking for, but that is not the case.

[zanieb]

Hi! Can you share a brief example?

[adamtheturtle]

Sure @zanieb ,

I create:

foo/bar/example.py

with the contents:

STRING = "This code is not relevant"
STRING1 = "This code is not relevant"
STRING2 = "This code is not relevant"
STRING3 = "This code is not relevant"

> ruff check foo/bar/
foo/bar/example.py:1:1: INP001 File `foo/bar/example.py` is part of an implicit namespace package. Add an `__init__.py`.
  |
1 | STRING = "This code is not relevant"
  |  INP001
2 | STRING1 = "This code is not relevant"
3 | STRING2 = "This code is not relevant"
  |

I infer from the output that there is a problem to be fixed on line 1 of the file.

[dhruvmanila]

I think file level diagnostics by default uses an empty range at the start of the file which is what you're seeing here.

[charliermarsh]

Lets omit the code frame for empty files?

[dhruvmanila]

Lets omit the code frame for empty files?

Yeah, that seems reasonable. I think we would want to check for an empty range at byte 0 (TextRange::new(0, 0)) which is where this is being raised.