Slurminade

What's Changed
* v1.1.0 by d-krupke in https://github.com/d-krupke/slurminade/pull/23

Slurminade can now also be called from iPython! In this case, it will just use the defining file as entry point. This will still have problems with relative imports, though.

**Full Changelog**: https://github.com/d-krupke/slurminade/compare/v1.0.1...v1.1.0

What's Changed

Instead of JobIds (ints), the dispatcher will now return JobReferences which will allow to do fancier stuff in the near future.

* v1.0.1 by d-krupke in https://github.com/d-krupke/slurminade/pull/22


**Full Changelog**: https://github.com/d-krupke/slurminade/compare/v0.10.1...v1.0.1

What's Changed
* FIX: Don't call setup on listfuncs by d-krupke in https://github.com/d-krupke/slurminade/pull/21


**Full Changelog**: https://github.com/d-krupke/slurminade/compare/v0.10.0...v0.10.1

What's Changed
* v0.10.0 by d-krupke in https://github.com/d-krupke/slurminade/pull/20

**Full Changelog**: https://github.com/d-krupke/slurminade/compare/v0.9.0...v0.10.0

Batch is now named JobBundling. There is a method join for easier synchronization. exec allows to executed commands just like srun and sbatch, but uniform syntax with other slurmified functions. Functions can now also be called with distribute_and_wait. If you call python3 -m slurminade.check --partition YOUR_PARTITION --constraint YOUR_CONSTRAINT you can check if your slurm configuration is running correctly.

Contains a set of improvements. Further improvements are planned but may be breaking changes. Still thinking about the best way to do it.

This is just a tiny improvement when calling `wait_for` with an empty list. This is often in combination with a `batch.flush()` outside the context (as the batch gets automatically flushed at the end of the context and all further flushes will be empty.