-
-
Notifications
You must be signed in to change notification settings - Fork 278
Closed
Labels
ENHANCEMENT β‘New Feature/Addition/ImprovementNew Feature/Addition/ImprovementMAINTENANCE ποΈJust sorting things out!Just sorting things out!SOLVED πThis issue/PR is resolved now. Goal Achieved!This issue/PR is resolved now. Goal Achieved!
Milestone
Description
Description
Hey! I've noticed this project doesn't have a py.typed file as per https://peps.python.org/pep-0561/. Unfortunately, pyright is quite unhappy at me for a lacking py.typed, even though type annotations do seem to be present in vidgear's source.
My guess is that it's because the project doesn't adhere to PEP-561's requirement to have an empty py.typed marker file.
Issue Checklist
- I have searched open or closed issues for my problem and found nothing related or helpful.
- I have read the Documentation and found nothing related to my problem.
- I've read the Issue Guidelines and wholeheartedly agree.
Expected behaviour
vidgear type annotations should work with pyright.
Actual behaviour
vidgear types are caught with pyright.
Steps to reproduce
from vidgear.gears import CamGearshould not fail pyright, but it fails regardless (with basedpyright, at least).
Terminal log output
Python Code(Optional)
VidGear Version
0.3.4
Python version
3.14.2
OpenCV version
4.12.0
Operating System version
Darwin 25.2.0 arm64 arm
Any other Relevant Information?
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
ENHANCEMENT β‘New Feature/Addition/ImprovementNew Feature/Addition/ImprovementMAINTENANCE ποΈJust sorting things out!Just sorting things out!SOLVED πThis issue/PR is resolved now. Goal Achieved!This issue/PR is resolved now. Goal Achieved!