> I think it is rather unusual to have separate stub files, most projects that I see annotate the code
> directly. I am mildly curious about whether you have reasons for preferring this approach
> - or perhaps it just happened to turn out that way.
I find that inlining the type declarations detracts quite a bit from the readability of the code: I've worked in large codebases using them, and much prefer to have them out-of-line.
Because 'mypy' was happy running against the out-of-date stubs when run inside the 'pkginfo' project,
I hadn't noticed the stubs were stale. The change I added to 'tox.ini' should keep me from letting
them drift again in the future.
> I think it is rather unusual to have separate stub files, most projects that I see annotate the code
> directly. I am mildly curious about whether you have reasons for preferring this approach
> - or perhaps it just happened to turn out that way.
I find that inlining the type declarations detracts quite a bit from the readability of the code: I've worked in large codebases using them, and much prefer to have them out-of-line.
Because 'mypy' was happy running against the out-of-date stubs when run inside the 'pkginfo' project,
I hadn't noticed the stubs were stale. The change I added to 'tox.ini' should keep me from letting
them drift again in the future.