In this case I'd much prefer to use Sphinx/RST. Developers already need to use this for the user-manual. We know how to write extensions for this system and it it avoids introducing yet-another…
Closing as - in practice I don't think typing zero before other numbers is especially useful, when the user can simply type in the number without the preceding zero.
Note that this is not a mistake in the code, support for this was never added, for many of Blender's internal API's the step value isn't so useful (collections of objects for e.g.). Pixel access…
From discussion outside this PR, none of my requests require and extra iteration, accepting.
Also use __func__ instead of __FILE__, generally more useful in allocation messages.
Requesting changes although these are mostly details, overall this seems to work well - further improvements can be iterated on in the main branch.
Unhelpful comment, assume it's from up-stream? If so, note that the upstream code considers this important but it's not known why it's needed. (or better, note why it's needed).
As slow_packer isn't a named packer. Suggest default (slower) packer.
Does this help? I would have thought in the case of packing/rasterizing - there wouldn't be much/any advantage.