Inconsistent naming of stubs

Open
#315 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start by reviewing the repository's source tree and inventorying how stub names use or omit the -stubs prefix. Check whether the naming convention affects Pylance integration, then define the affected scope and verify that all relevant stub names follow one consistent convention.

Written by the indexing model from the issue text.

Description

Not a big issue, but it might be a good idea to be consistent about using (or not using) the -stubs prefix for stubs in source code.
Unless there's an odd reason with Pylance integration I'm not aware of.

Dominant language
Python
Stars
304
Forks
104
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/python-type-stubs

All issues in microsoft/python-type-stubs

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.