Skip to main content

Maya Stubs

Type Annotated Stubs for Autodesk Maya's python APIs

Goals

Provide fully type annotated stubs for maya.cmds and OpenMaya 1.0 & 2.0

Status

Note that is very much in progress and it is unlikely that the stubs will ever be perfect.
At this point, even if some of the maya.cmds annotations are wrong/misleading, I would consider it a better experience than using the stubs from the devkit. The stubs from OpenMaya 1.0 and 2.0 are very minimal and only have *args, **kwargs signatures, which should be pretty close to the devkit stubs.

  • 🚧 maya.cmds: In Progress
    • Stubs for all commands.
    • Accurate Arguments signatures for most commands. Parsed from the HTML Docs or the synopsys from cmds.help("command")
    • Accurate Positional Only Arguments for most command.
    • Accurate Return types on most commands
    • Docstrings.
    • Accurate Arguments signatures all commands.
    • Accurate Return types all most commands
  • 🚧 OpenMaya 1.0: Incomplete
    • Stubs for all members
    • Accurate Argument Signatures
    • Return Types
    • Docstrings.
  • 🚧 OpenMaya 2.0: Incomplete
    • Stubs for all members
    • Accurate Argument Signatures
    • Return Types
    • Docstrings.

Installation

You can get the stubs with one of two ways:

  1. Run pip install maya-stubs from the python executable used by your IDE.
  2. Download them manually from the Github releases and let your IDE know of their location.

Notes

PyCharm maya.cmds completion

PyCharm users may not see code completion for maya.cmds as the editor limits code insight features by default on files over 2.5 MB for performance reasons. Currently the cmds stub is over this limit.

This value can be increased in PyCharm's properties, accessible via the Help > Edit Custom Properties menu.

Code completion should work after adding the line below to the properties file and restarting PyCharm. This example overrides the default value from 2.5 MB to 10 MB. The value may be customized as needed, but keep in mind it can affect editor performance.

idea.max.intellisense.filesize = 10000

Metadata

Release files for maya-stubs 0.4.2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for maya-stubs 0.4.2
File Size Uploaded
maya_stubs-0.4.2.tar.gz 313.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for maya-stubs 0.4.2
File Interpreter ABI Platform
maya_stubs-0.4.2-py3-none-any.whl Python 3 none any Details

Total release size: 572.9 kB

Release files / maya_stubs-0.4.2.tar.gz

Download URL maya_stubs-0.4.2.tar.gz
Size 313.9 kB
Tags Source
SHA-256 checksum
How to use checksums
86eb6901b4e341895c572a94c055d0248903720a42c22a9a507bdcfda52e9da0
BLAKE2b-256 checksum
How to use checksums
83accb12a396f8dad98fa15dae801899e8d1ff39debdaa66fe81cd8d93e4d666
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.9.2

Release files / maya_stubs-0.4.2-py3-none-any.whl

Download URL maya_stubs-0.4.2-py3-none-any.whl
Size 259.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2dd28457af1877293f5b7544eea5a14384ad89b5a59796847c6c68c1a44f0db9
BLAKE2b-256 checksum
How to use checksums
fd39df15b423c029fe7dcdf43814f4776fb689c86e6fc48ab36af3cae63b2732
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.9.2

Release history Release notifications | RSS feed

This release

0.4.2 This release

2 release files

0.4.1

2 release files

0.4.0

2 release files

0.3.1

2 release files

0.3.0

2 release files

0.2.0

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page