Nov-19-2022, 06:25 PM
I suppose it was slightly possible that this originally had some undocumented behavior that was later "fixed" to match the documentation. But that doesn't seem to be true either. I ran it on Python 2.3 and it produces the same error.