Sascha Klawohn

Thanks for your input! I have thought about a `with_replacement` optional argument. And if that can be merged, maybe all of them should be. The naming is not great to...

Is this being worked on?

What is the current state on this topic?

Motivation: When working on the `fpm build --tests` feature I had to change the help messages at four(?) different places (in the same file). I thought that an automatic approach...

> Yes I mean compiler flangs. I was confused by the title of this issue. Could it be made more specific?

The strings are also broken in `sacct` and `scontrol`. ``` $ scontrol show job 7750363 ⋮ WorkDir=���*� StdErr=���*�/slurm-7750363.out StdIn=/dev/null StdOut=���*�/slurm-7750363.out ⋮ ```

I switched to branch `slurm-20.11.8` but that did not help. Could it be a mismatch with C string lengths? How can I debug this? `submit_batch_job()` also ignores the option `'time':...

The problem still persist if `work_dir` is included in the job options: ``` Submitted job 7762983 with {'wrap': 'sleep 5', 'work_dir': '/my/work/dir', 'get_user_env_time': -1} 7762983 | PENDING | 2880 |...

> The `time` option from sbatch is actually called `time_limit` in pyslurm. Oh, `time_limit`, thanks. I thought it was `time` as with `sbatch --time` since the docstring for `submit_batch_job` says:...

Are there any new developments concerning this issue? I wanted to test `leastsquares()` for distributed systems but ran into MPI vs MPICH errors. At least one cluster I'm working on...