module-exports
Single decorator that injects __name__ of object to export into __all__.
from module_exports import export_from_module
@export_from_module
def some_public_function():
return 4
SOME_CONSTANT = 100500
export_from_module.by_name('SOME_CONSTANT')
# __all__ == ['some_public_function', 'SOME_CONSTANT']
1 maintainer
Metadata
1 maintainer
Release files for module-exports 1.2
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 | Actions |
|---|---|---|---|---|
| module_exports-1.2.tar.gz | 1.6 kB | Without provenance | Details for module_exports-1.2.tar.gz |
Release files / module_exports-1.2.tar.gz
| Download URL | module_exports-1.2.tar.gz |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e1080d32ac29cf5d68bca74c37991a249bc8c07ee148d8b00f127a8f8a2576b
|
|
BLAKE2b-256 checksum How to use checksums |
7fb69d946aea93982da21a5217e7bb551ff2300376adcef56646d1944674ad8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.0 setuptools/39.0.1 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.7.1
|
Security for module-exports 1.2
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.
