can I work on this?

can I work on this?

No objections from me 🙂

Just hit this as well. I think the right solution would be to allow trailing commas. It's a bit more obvious with TOML and shouldn't really differ in ini, UX-wise.

I haven't checked, but my hunch is that configparser might be reading this entire value as a giant string, like file1,file2,file3,, splitting it by comma. And then, the last element is an empty string. This translates to just calling MyPy in terminal and passing an empty string on CLI.

I have confirmed that passing that empty string as another file breaks in exactly the same way:

$ MYPY_PATH=src/ mypy --explicit-package-bases myproject/package1 myproject/package2 myproject/module1.py myproject/module2.py ''

Additionally, I've found that you can call it with a double empty string:

$ MYPY_PATH=src/ mypy --explicit-package-bases '' ''

and it would explode the same...

Interestingly, a single empty string argument seems fine:

$ MYPY_PATH=src/ mypy --explicit-package-bases ''

So it seems to me that there are 2 bugs here:

1. MyPy's argument processing breaks when there's more than one file path argument passed and at least one of those paths is an empty string — this deserves a clear error output, regardless of whether it's coming from a config or a CLI arg
2. The configparser-based reader should normalize the INI format to allow for trailing commas and disallow empty strings so that it behaves the same as TOML from the user perspective.

@hauntsaninja could you please change the label from documentation to bug? Also, this is probably a good-first-issue.

It just occurred to me that the config parsing bug may affect other settings that are being interpreted as lists. Perhaps, that's worth checking by whoever gets to work on this.

Hi!, Can I take this up?

@hauntsaninja thanks for the labels! Could you assign the issue to me and @x612skm? I'll help him navigate the process.

@x612skm @webknjaz Feel free to work on this! (we generally don't assign issues)

You can check out CONTRIBUTING.md and the Developer Guides for contributing guidelines and tips on where to start. Thanks!

Just for the fyi - I've started brainstorming into this and soon will be hitting a PR after a discussion with @webknjaz . Thanks!

@brianschubert I've got some feedback for you.

We've found a weakness in the contributing docs. I asked Soubhik to write some tests and since it was a new module, the first idea was to start with something simple, like a test function. It took some time to notice that it wasn't being picked up by pytest. This was when I asked to push the change w/o a fix to the PR (#18472) to make sure it's failing, and it didn't.

I was able to find the respective pytest config that disables the default test collection, but I don't believe that a less experienced person would know where to look. Still, it was quite frustrating to troubleshoot.

I checked the contrib and other docs — there seems to be no mention of needing to use classes in test modules.

So the action item is to document this somewhere, the closer to the section on invoking the tests the better.