fake-bge-module is the collections of the fake Blender Game Engine (BGE) Python API modules for the code completion in commonly used IDEs.
Note: The similar project for Blender is available onfake-bpy-modulewhich targetsBlender.
To realize the long support of this project, your support is helpful. You can support the development of this project via GitHub Sponsors. Seethe contribution documentfor the detail of the support.
Requirements
fake-bge-module uses typing module and type hints which are available from Python 3.7. Check your Python version is >= 3.7.
Install
fake-bge-module can be installed via a pip package, or pre-generated modules. You can also generate and install modules manually.
Install via pip package
Install a latest package
If you install fake-bpy-module for Blender latest build (master branch daily build powered by nutti/upbge-daily-build), run below command.
pip install fake-bge-moduleor, specify version “latest”.
pip install fake-bge-module-latestInstall a version specific package
If you want to install a version specific package, run below command.
pip install fake-bge-module-<version>If you install fake-bge-module for UPBGE 0.2.5, run below command.
pip install fake-bge-module-0.2.5Note: For PyCharm users, change the value ``idea.max.intellisense.filesize`` in ``idea.properties`` file to more than 2600 because some modules have the issue of being too big for intelliSense to work.
Supported UPBGE Version
Version |
PyPI |
|---|---|
0.2.5 |
|
latest |
|
Install via pre-generated modules
Download Pre-generated modules from Release page.
The process of installation via pre-generated modules is different by IDE. See the installation processes as follows for detail.
Generate Modules Manually
You can also generate modules manually. See Generate Modules for detail.
Change Log
See CHANGELOG.md
Bug report / Feature request / Disscussions
If you want to report bug, request features or discuss about this add-on, see ISSUES.md.
Contribution
If you want to contribute to this project, see CONTRIBUTING.md.
1 maintainer
Metadata
1 maintainer
Release files for fake-bge-module 20240101
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| fake-bge-module-20240101.tar.gz | 870.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fake_bge_module-20240101-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.9 MB
Release files / fake-bge-module-20240101.tar.gz
| Download URL | fake-bge-module-20240101.tar.gz |
|---|---|
| Size | 870.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a781cf3035751e63958933a860f771326f8ef6d0b0848088c83b1a8d81896b56
|
|
BLAKE2b-256 checksum How to use checksums |
a771d6bc1d31e54dbbc21b247e7531aff63d32484413f693bde59f1f16fca3b7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.18
|
Release files / fake_bge_module-20240101-py3-none-any.whl
| Download URL | fake_bge_module-20240101-py3-none-any.whl |
|---|---|
| Size | 1.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
22095c8fc1590d69d20ca82b6467967bbd7b9c0e8e42aa76017dd726282c2ef7
|
|
BLAKE2b-256 checksum How to use checksums |
7204b668bdab5cf260e85622c8ebcd1269e43ec9e1777f7c9f1f3672935f7422
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.8.18
|
Security for fake-bge-module 20240101
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
