reportCallIssue with Python 3.15 `frozendict` when called with arguments
- Dominant language
- Python
- Stars
- 15.6k
- Forks
- 1.8k
- Avg merge
- 12h 13m
- Merged PRs (30d)
- 52
Description
**Describe the bug**
I was trying out Python 3.15's new `frozendict` with pre-release Pyright.
While Pyright does come with the correct typeshed-fallback stubs which contain the correct overloaded forms of `frozendict`, it still doesn't recognize the argument forms of `frozendict()` when in use.
**Code or Screenshots**
```python
foo = frozendict() # OK with no arguments
bar = frozendict({}) # Expected 0 positional arguments (reportCallIssue)
baz = frozendict(qux="spam") # No parameter named "qux" (reportCallIssue)
```
**VS Code extension or command-line**
Both VS Code extension (Pylance 2026.3.102 pre-release) and Pyright Playground exhibited the same issue as of today (September 12 2026).
Contributor guide
Research direction
Reproduce the three frozendict calls in the Pyright Playground using Python 3.15 and the reported pre-release typeshed-fallback stubs. Compare the behavior of the no-argument, positional-mapping, and keyword-argument forms in both the Playground and VS Code extension. Done means the argument forms no longer produce reportCallIssue diagnostics while the no-argument form remains valid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100