Hugo
> Which I don't understand, and am not sure if there's something I should be doing to move things forward? See above the comment box: 
> how do you mark it as no-longer-in-draft? Click the "ready for review" button. "Draft" is generally used to indicate "this isn't ready for a final review or merge, just...
CI is failing mostly because commit messages must conform to a strict standard, see: https://github.com/neovim/neovim/blob/master/CONTRIBUTING.md#commit-messages I think commit messages should be prefixed with `fix:` in this case.
Another scenario where this would be useful is for rendering aligned virtual text. When using `cpoptions=n`, virtual lines don't have gutter-padding, so they're all shifted left by quite a bit....
Por lo que veo, si corrés en con el logger en `logging.DEBUG` deberías ver el mensaje entero: https://github.com/mvantellingen/python-zeep/blob/master/src/zeep/transports.py#L59-L71
> In this case (https://github.com/juanpsenn/django-afip/commit/5645421f8ea189780b63b4991c6d38e39664dfc4) I'm testing validating an older receipt (older than the last successfully validated receipt), this should fail but also raises an exception when it shouldn't. Thanks...
Thinking about this further, I think we should drop the `raise_` parameter for `validate()`, and never raise (e.g.: keep the behaviour of `raise_=False`. Raising in this case is a poor...
https://github.com/WhyNotHugo/django-afip/commit/484996d32ab1f11e543abf421326f583ca08111c
To `ReceiptEntry`.
Error message should suggest reading the `validate()` docstring.