Installing python packages that require C bindings on Windows is pretty straightforward, provided that: - you have exact MSVC version, that was used to build y

Installing python packages that require C bindings on Windows is pretty straightforward, provided that: - you have exact MSVC version, that was used to build your python (and yes, they are ancient, and no, you cannot purchase them anymore), - it is possible at all to build the given package by the required MSVC version (see also: icu, boost, qt5 and the minimum MSVC version required), - there are no dependencies on many additional libraries (i.e. building GDAL for Windows python is a real pain), - the extension does not use some kind of home-brew build system that the author never tried to run on Windows (hello, py2cairo), - you don't need some other compiler (scipy, I'm looking at you and your fortran). But for simple extensions like psycopg2, it is a piece of cake. It is building packages, that are not native in Windows, but you have them in dependency chain, that are the problem.