> GitHub specifically flags it as a possible exploit in a couple of cases, but also syntax highlights the return keyword appropriately.
My guess is that Github did patch it afterwards as the paper does list Github as vulnerable > Uhhm..... "weird unicode stuffs"? Please clarify. Wriggly texts just because they appear different Well, it's tool based but maybe compiler checks aka checks from the language side is something that should be insisted upon too to patch inconsistent checks across editors. The reason i was saying it's related to encodings is that when languages are impacted en masse, maybe it hints to a revision in the unicode standards at the very least warnings. As Steven above even before i posted the paper was hinting towards the vulnerability so maybe those in charge of the unicode standards should study and predict angles of attacks. Kind Regards, Abdur-Rahmaan Janhangeer about <https://compileralchemy.github.io/> | blog <https://www.pythonkitchen.com> github <https://github.com/Abdur-RahmaanJ> Mauritius
_______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/UEF6RYKZLVOG2PPSGAMOLDEP6LPEG6UZ/ Code of Conduct: http://python.org/psf/codeofconduct/