I'm not a Windows expert, but looking that the API description [1] the patch is not entirely correct. 

The API takes an integer with 3 valid values, the patch effectively passes the value 1 (which means the application claims to be DPI aware, but won't scale itself when the DPI changes for some reason).  

The API can fail, but that shouldn't cause an exception as ctypes won't automaticly convert error return values to exceptions.

P.S. The pull request seems to contain an unrelated change as well.

[1] https://msdn.microsoft.com/en-us/library/windows/desktop/dn302122(v=vs.85).aspx