title: PyGObject on Windows
body: <p>Over the last few days of headaches, I've found 3 possible methods to do this, all of which have issues.</p>
  
  <ul>
  <li><p><a href="https://pygobject.readthedocs.io/en/latest/getting_started.html#pypi" rel="noreferrer">PyGObject's pip</a> install fails due to a lack of Cairo and probably other dependencies. While this would be my preferred method, it would probably be the hardest to fulfill.</p></li>
  <li><p>Using <a href="http://www.msys2.org/" rel="noreferrer">MSYS2</a> allows me to use GObject through the mingw64 python, but using pip to get my other modulues such as pylint fails. I'd like to have an MSYS2 or similar install on my system anyways to make some windows binaries, so I'm very open to this as well.</p>
  
  <ul>
  <li><strong>EDIT:</strong> Got pip to work in MSYS2. Make sure to sync toolchain with pacman.</li>
  </ul></li>
  <li><p><a href="https://sourceforge.net/projects/pygobjectwin32/" rel="noreferrer">PyGObject for Windows</a> seems messy at best and isn't up-to-date. Would require having a second python installation anyways, giving no benefit over MSYS2.</p></li>
  </ul>
  
  <p>Note I'm a complete newbie to Unix and have little experience with CLI's in general, so any help regarding MSYS2 will need to be explained as if to a child. My only other experience with this stuff involved an endless cycle of hell that was installing Arch to a separate partition, breaking said install, then reinstalling again.</p>
  
  <p>I also tried Cygwin, but I couldn't get that to run Python with GObject at all with my "install all the needed packages then pray" method. Creating a Gtk.Window() caused the terminal to use none of the memory it had and explode.</p>