This change was necessary to ensure parmap keyword arguments do not collide with your mapped function arguments. If your named arguments in your function don't start with pm_ you are safe of any future argument I add to parmap (so it's just to avoid potential future problems)
pmelchior
commented
2 years ago
Since parmap 1.5.0, parmap allows to have keyword arguments passed to the function, besides positional arguments.
On that version I (parmap author) had to deprecate
poolandchunksizearguments replacing them withpm_poolandpm_chunksizerespectively.parmap changelog:
https://github.com/zeehio/parmap/blob/2640864449afc94fad1e1af32b4ef43ac0a3f80c/ChangeLog#L16
This change was necessary to ensure parmap keyword arguments do not collide with your mapped function arguments. If your named arguments in your function don't start with
pm_you are safe of any future argument I add to parmap (so it's just to avoid potential future problems)I hope it helps