Calldules!
No more from <module> import <Module>!
Wouldn’t be nice if…
>>> import pprint
>>> pprint("hello")
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
TypeError: 'module' object is not callable
Was possible? Well:
Add special sauce:
>>> import calldules
Import module(s), call:
>>> import pprint >>> pprint("hello")????
'hello'
PROFIT!!!
Also works with such modules as flask, codecs, array, datetime, decimal, random, and many more!
No responsibility is taken for any grievous harm caused either by irresponsible or responsible use of calldules.
Inspired by Richard Jones’ talk Don’t Do This.
Metadata
Release files for calldules 1.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distributions (sdists)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| calldules-1.0.1.zip | 5.6 kB | Without provenance | Details for calldules-1.0.1.zip | |
| calldules-1.0.1.tar.gz | 3.0 kB | Without provenance | Details for calldules-1.0.1.tar.gz |
Release files / calldules-1.0.1.zip
| Download URL | calldules-1.0.1.zip |
|---|---|
| Size | 5.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ecb7656647708afeef9fb6180093363340d28d14e0b84321618d6504b8d4ba76
|
|
BLAKE2b-256 checksum How to use checksums |
bb40e2ed0dab99706e1bc82dd715048b10deca0416bbf0ade6e3fe9178c69676
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / calldules-1.0.1.tar.gz
| Download URL | calldules-1.0.1.tar.gz |
|---|---|
| Size | 3.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13077009a0723b239e19fbdd6d031a1c2aad4d8f91d95b2b9199b3a15e8cc66e
|
|
BLAKE2b-256 checksum How to use checksums |
d18655e5d4866e8be2f49c58185a7f04ed51db1ba1895bfa91d42652016d0d66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for calldules 1.0.1
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.