This package is capable of
Sending a data to a pickled state
Unpickling the pickled data
There are two seperate functions
pickle_data(val1,val2) - Used to pickle the data
–>val1 - Data to be pickled (required) –>Val2 - name of the file to be written to (Optional)
unpickle_data(val1,val2,val3) - used to unpickle the pickled data
–>val1 - name of the pickled file (Required) –>val2 - Set it to ‘True’ if the output has to be written to a file (optional). Default is ‘False’(shell output) –>Val3 - name of the file to be written to (optional)
Metadata
Release files for pickle_process 1.0.0
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 |
|---|---|---|---|---|
| pickle_process-1.0.0.zip | 1.6 kB | Without provenance | Details for pickle_process-1.0.0.zip |
Release files / pickle_process-1.0.0.zip
| Download URL | pickle_process-1.0.0.zip |
|---|---|
| Size | 1.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
13c096dab1870a1d608ac10cf9593523aa2e85446911154eac6e77daa65fd7ee
|
|
BLAKE2b-256 checksum How to use checksums |
e4852ecbb6fd84fe21a6b420239c33821ab1f850face5c7e788b5e36f947309d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for pickle_process 1.0.0
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.