On Friday, May 3, 2019, Vojtech Juranek <vjuranek@redhat.com> wrote:
>> >>  /* read_lockspace */
>> >>  PyDoc_STRVAR(pydoc_read_lockspace, "\
>> >>
>> >> -read_lockspace(path, offset=0, align=ALIGN1M, sector=SECTOR512)\n ->
>> >> dict\n\
>> >> -Read the lockspace information from a device at a specific offset.");
>> >> +read_lockspace(path, offset=0, align=1048576, sector=512)\n -> dict\n\
>> >> +Read the lockspace information from a device at a specific offset.\n\
>> >> +Align can be one of (1048576, 2097152, 4194304, 8388608).\n\
>> >> +Sector can be one of (512, 4096).");
>
>> Reveal the missing docstring changes:
>>
>>     read_lockspace(...)
>>         read_lockspace(path, offset=0, align=ALIGN1M, sector=SECTOR512)
>>
>> Should be now align=1048576, setor=512
>
> that's strange, it's part of the patch, see above (and same for other doc
> strings)

Looks like I tested stale sanlock module from python/ instead of .tox/.