@dhalbert these changes get Sphinx past the api.rst title error, but then fails on a TypeError for struct.pack using constants set with a const(<int>). Auto mocking struct doesn't resolve the the TypeError, and casting to an integer doesn't either (raises a different one on int, actually)...
A quick grep showed that struct as the only usage of the affected constants, but they seem like they could be used in the future. Otherwise, you could just hardcode the integer or un-const them...
Thanks! I didn't see this until later, and ended up doing a lot of the same kinds of things with some other commits.. It passes now. This was totally painful.
@dhalbert these changes get Sphinx past the
api.rst title
error, but then fails on a TypeError forstruct.pack
using constants set with aconst(<int>)
. Auto mockingstruct
doesn't resolve the the TypeError, and casting to an integer doesn't either (raises a different one onint
, actually)...A quick grep showed that struct as the only usage of the affected constants, but they seem like they could be used in the future. Otherwise, you could just hardcode the integer or un-
const
them...