Add fundamental types to resolvers
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with the default resolver definitions in src/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_xml.py around line 41. Review how the existing builtin collection types are selected, then compare that behavior with collections.abc.Mapping, Sequence, and Set and the other fundamental types mentioned in the issue. Done means the defaults reflect the intended fundamental Python types rather than an arbitrary subset of builtins.
Written by the indexing model from the issue text.
Description
seems like the actual types that define Python behavior like collections.abc.Mapping are missing from the default resolvers, and instead some random collection of builtin types is there:
I say “random” because MappingProxyType, KeysView, … are just as fundamental Python types that are used whenever something as basic as a class is encountered so I can’t think of a reason why they shouldn’t be there when dict is, let alone some Django classes and other stuff!
But as initially said: Python’s behavior is actually defined by collections.abc.* classes, so instead of having random builtin sequences like list, frozenset, … in the defaults, why not just use collections.abc.{Sequence,Mapping,Set} directly?
PS: #825 was closed because its title asked about this being possible. I know it’s possible and ask for it to be changed instead.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 202
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/debugpy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in microsoft/debugpy
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·