The use case is a bit debatable as it's ill-defined, but I caught that because an (old) test suite unwittingly made use of that property: if an re.sub callback returns a None, the behaviour is (apparently) the same as returning an empty string. However GraalPython raises a TypeError instead.
The use case is a bit debatable as it's ill-defined, but I caught that because an (old) test suite unwittingly made use of that property: if an
re.sub
callback returns aNone
, the behaviour is (apparently) the same as returning an empty string. However GraalPython raises aTypeError
instead.