PR: Make sure the library works at import time

[blink1073]

Fixes #59.

[blink1073]

@andfoy, any idea why I'm getting an Appveyor failure even with no effective changes in this PR?

[andfoy]

@blink1073 Let me check what's going on

[ccordoba12]

This is probably failing because of the change in conda-forge to use the MinGW toolchain to compile Winpty.

[blink1073]

I'm not sure what would be different here vs. the import test on conda-forge.

[ccordoba12]

conda-forge was still building the package with VS 14. Please see

conda-forge/pywinpty-feedstock#10

[andfoy]

@ccordoba12 @blink1073 Sorry for being too disconnected to the latest changes. Does the m2w64 helps to solve our issues?

[ccordoba12]

Nop, it's safer to mix MinGW (Winpty) and VS 2008 (Python 2) than our previous arrangement of VS 2015 and VS 2008.

[blink1073]

Right you were, @ccordoba12... so we need to update the feedstock and here to use mingw?

[ccordoba12]

No, if I understood @jjhelmus correctly. We just need to compile pywintpy with the right VS compiler for the Python version it's going to use.

[ccordoba12]

Annnnd things failed in conda-forge, just as they are failing here:

https://ci.appveyor.com/project/conda-forge/pywinpty-feedstock/build/1.0.38

Let's continue the discussion in conda-forge.

[ccordoba12]

I have a working solution for #59, so closing this one.

[ccordoba12]

Sorry for my wording, the right thing to say is that this is superseded by #99.