Repository navigation
Namespace packages supported by default? #14057
Description
Activity
The reason why I ask is because in the current state, namespace packages get a second-class experience.
- added a commit that references this issue
on Nov 10, 2022 We chose not to make it the default at the time it was introduced because doing so was very breaking, e.g. all packages with src layout would probably break. It still remains true that most Python packages are not namespace packages, so it feels hard to justify.
(Not present in your report, but I believe the error message should currently suggest using
--explicit-package-bases; let me know if that's not the case)Correct. The suggestion wasn’t apparent when running under pytest-mypy. Once I ran the tests using mypy directly, the suggestion was present and led me to the workaround.
- added 6 commits that reference this issue
on Nov 22, 2022 There seems to be a related bug in Windows where
mypyis not finding the stub files (which are included in the wheel) forbackports.zoneinfoin Python 3.7 and 3.8. The reproduction is pretty simple:pip install mypy backports.zoneinfo mypy -c 'from backports import zoneinfo'This only occurs on Windows. It works fine on Linux and macOS.
@AlexWaygood interested in looking at this issue? I don't have a windows system to reproduce
I can try to have a look, but no promises -- pretty busy at the moment :(
- added a commit that references this issue
on Dec 13, 2022 - added a commit that references this issue
on Dec 21, 2022 - added a commit that references this issue
on Feb 21, 2023 There seems to be a related bug in Windows ...
It may be related, but the bug as reported applies across platforms. It may be worthwhile to open a separate bug for the possibly related Windows-specific issue.
- added a commit that references this issue
on Mar 25, 2023 - added a commit that references this issue
on Apr 11, 2023 - added a commit that references this issue
on Jun 20, 2023 - added a commit that references this issue
on Jun 29, 2023
I notice in the changelog that 0.990 adds support for namespace packages by default.
I've been using mypy on namespace packages (
jaraco,svg,backports, and others) for some time now (jaraco/skeleton@7455f2f).With the release of mypy 0.990, however, tests have started failing across all projects with namespace packages:
The change log indicates that 0.990 adds support for namespace packages by default. Annoyingly, this change has had the opposite effect for my projects. I find that I can restore functionality by adding
explicit_package_bases = Trueto the config file (or equivalent command line). It's slightly annoying to have to add this configuration to all of my projects just to support some projects with namespace packages.Is it possible that
explicit package baseswill become default in the future?