Types-panda3d

Latest version: v0.4.0

Safety actively analyzes 625831 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

0.4.0

This release most notably updates the stubs for Panda3D 1.10.14. This means that Python 3.12 is now supported and support for 3.7 has been dropped. Other changes to the stubs include:

- C++ wrapper properties that may be set to `None` are now typed as such.
- Stub files for `panda3d` modules have been reformatted. Outside of stylistic changes, this includes writing out individual docstrings for function overloads. PyCharm doesn't have support for overload docstrings, but Pylance (used in the VS Code) does.
- Deprecated functions are now decorated with `typing_extensions.deprecated` (See [PEP 702](https://peps.python.org/pep-0702/)).
- Overloads for `Loader` methods have been expanded to account for more use cases.
- Various other minor improvements and corrections have been made across the stubs.

0.3.3

Most of the work done since the last release has been on the code that generates the stubs for the `panda3d` package. Nevertheless, many miscellaneous corrections and improvements have been added to the stubs themselves, most notably:

- Default arguments that are simple containers are now included in the stubs for `direct`.
- Many uses of `Literal` types have been replaces with the type of the literal, as these can often be more trouble than they're worth.
- Subclasses are now written after their base classes in the stubs for `panda3d` where they are defined in the same file.
- Docstrings for dunder methods are (once again) included in the stubs for `panda3d`.
- Some additional implicit type conversions that will be removed in Panda3D 1.11 are ignored in the stubs.

0.3.2

Significant changes since the last release:

- Many annotations and signatures relating to tasks have been improved and corrected.
- The `direct` stubs now include simple default parameter values where possible in place of `...`.
- With the release of mypy 1.0.0, `typing.Self` is now used where applicable.

0.3.1

In addition to some miscellaneous improvements, this update greatly improves the handling of Panda3D's parameter type coercion. The logic has been updated to better reflect what's accepted at runtime, as well as to decrease unnecessary verbosity across overloads in the stubs. Additionally, some more coercions are now supported:

- Using a Python callable in place of a `CallbackObject`
- Using a Python tuple in place of a vector
- Using a 3x3 matrix in place of a 4x4 one

0.3.0

Notable changes to the stubs since the last release:

- Update to Panda3D version 1.10.13
- Miscellaneous improvements to stubs for the `direct` package.
- Variadic parameters (i.e., `*args` or `**kwargs`) are now written as such in the stubs for the `panda3d` package.
- Some improvements to the stubs for `PointerToArray` classes.
- Utilizing updates to `interrogatedb` in Panda3D 1.10.13, C++ implicit type coercion is now more generally accounted for. A handful of cases (such as converting a number to a vector) are intentionally omitted, though.
- Also utilizing 1.10.13 additions, `__copy__` and `__deepcopy__` methods are now included in the `panda3d` stubs.
- An empty `NodePath` (specifically, one constructed as `NodePath()`) is now typed as `NodePath[typing.Never]`. This means, for example, that a type-checker will flag `NodePath().node()` as not returning, matching runtime behavior.
- All `assign` methods are now typed as returning the same type as `self`.

In addition to the changes to the stubs, numerous improvements have been made to the code that generates stubs for the `panda3d` package (i.e., the C++ part of Panda3D).

0.2.1

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.