mirror of
https://github.com/proxmoxer/proxmoxer.git
synced 2026-04-24 22:56:01 +03:00
[GH-ISSUE #191] Feature suggestion: Add type annotations to Proxmoxer #104
Labels
No labels
backend:https
backend:local
backend:openssh
backend:ssh_paramiko
pull-request
status:ansible-issue
status:help-wanted
status:info-needed
status:proxmox-issue
status:review-needed
type:bug 🐞
type:dependency ⛓️
type:docs 📝
type:enhancement ⏫
type:maintenance 🛠️
type:meta
type:question ❓
type:request ✋
type:testing 🧪
version:1.x
version:latest
version:py2
version:py3
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/proxmoxer#104
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @igorbga on GitHub (Dec 5, 2024).
Original GitHub issue: https://github.com/proxmoxer/proxmoxer/issues/191
Having the code of Proxmoxer type annotated would be a great addition.
We are currently using Proxmoxer in a project where types are checked with BasedPyright and having no typing in Proxmoxer requires quite a mess in order to always ignore Proxmoxer related type issues.
Besides being more comfortable having type annotations would allow us to make a safer and more confident use of Proxmoxer.
Thanks
@jhollowe commented on GitHub (Dec 13, 2024):
There is some amount of adding type that would be possible, but any typing on the returned data or to validate a API path is not possible.
If you would like type annotations on the proxmoxer objects/classes, PRs are welcome!
@dlucredativ commented on GitHub (Jan 27, 2026):
https://pypi.org/project/proxmoxer-stubs/, feedback is appreciated.