tree db31a77eb0f6afec122315b46c74597f1f4f9441
parent 5d1f32d33ba24d0aa87235ae40207bb57778388b
author Lysandros Nikolaou <lisandrosnik@gmail.com> 1588033415 +0300
committer GitHub <noreply@github.com> 1588033415 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJep3eHCRBK7hj4Ov3rIwAAdHIIAIAys5rqKl39mlgsE/AXm0q0
 C9YlxTj0+HarAYYCknHYNAcioICUwM5MgzO05wqlvpnJCWQ8si2+LifoY78ltlBC
 RF/vHjJ5ewuBoyZDkxAxvbEQUQgKBoD7M0nLeZrs3/Eo++p06g9C8zfTYduw4TFE
 YcajzIxsXim9b3segvXK2yhKVrPDE12FXIvdnhTI2ra5OxCiWAWVnCEmxYSm6eUt
 6MvFFB02NfGY70gIRMMLn4NbDMWQHteYRE7IVQkEBK2ST3VdNLcMMbJ4A1931MZR
 C9FR6ogDuvHEza79VNKTlqDbXqWhBW9Uwp1EEA4npHAho60KfHe0K2+vx31b4AQ=
 =moBo
 -----END PGP SIGNATURE-----
 

bpo-40334: Catch E_EOF error, when the tokenizer returns ERRORTOKEN (GH-19743)

An E_EOF error was only being caught after the parser exited before this commit. There are some cases though, where the tokenizer returns ERRORTOKEN *and* has set an E_EOF error (like when EOF directly follows a line continuation character) which weren't correctly handled before.