Skip to content

Missing __init__.pyi in existing folders#391

Merged
bschnurr merged 1 commit into
microsoft:mainfrom
Avasam:Missing-__init__.py
Jun 4, 2026
Merged

Missing __init__.pyi in existing folders#391
bschnurr merged 1 commit into
microsoft:mainfrom
Avasam:Missing-__init__.py

Conversation

@Avasam
Copy link
Copy Markdown
Contributor

@Avasam Avasam commented Dec 5, 2025

Ran stubgen, kept only the __init__.pyi for folders we already had. Then cleaned-up. Closes #389

@Avasam Avasam force-pushed the Missing-__init__.py branch from d6970ee to b748d36 Compare December 5, 2025 03:40
@hunterhogan
Copy link
Copy Markdown

Thank you.

@bschnurr bschnurr merged commit ed12c4a into microsoft:main Jun 4, 2026
1 check passed
@Avasam Avasam deleted the Missing-__init__.py branch June 4, 2026 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Is a missing __init__.pyi in a bundled stub cause a false positive in Pylance?

3 participants