quick and dirty lib for submitting jobs to slurm via python2/python3.
from slurmpy import Slurm
s = Slurm("job-name", {"account": "my-account", "partition": "my-parition"})
s.run("""
do
lots
of
stuff
""")
The above will submit the job to sbatch automatically write the script to scripts/
and automatically write logs/{name}.err and logs/{name}.out. It will have today's
date in the log and script names.
The script to run() can also contain $variables which are filled with the cmd_kwarg dict.
E.g. echo $name could be filled with cmd_kwargs={'name': 'sally'}
A command can be tested (not sent to queue) by setting the _cmd are to run as e.g. "ls".
The default is sbatch which submits jobs to slurm.
Dependencies
Each time slurmpy.Slurm().run() is called, it returns the job-id of the submitted job. This
can then be sent to a subsequent job:
s = Slurm()
s.run(..., depends_on=[job_id])
to indicate that this job should not run until the the job with job_id has finished successfully.
Install
pip install slurmpy --user
Metadata
Release files for slurmpy 0.0.8
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 |
|---|---|---|---|---|
| slurmpy-0.0.8.tar.gz | 3.8 kB | Without provenance | Details for slurmpy-0.0.8.tar.gz |
Release files / slurmpy-0.0.8.tar.gz
| Download URL | slurmpy-0.0.8.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17da07cb9b46cb02fa21cc6d076f6baac6f5b351b79fb1a1f23a857b6161e470
|
|
BLAKE2b-256 checksum How to use checksums |
6ecf58c9e6575affc4fc7fb9a0cd0b246b612898b621650f8734770c33c52e35
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.1.1.post20200322 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.7.6
|
Security for slurmpy 0.0.8
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.