Configure Windows at import time to use the 32-bit kerbeors on a 32-bit python

[asheshv]

This change will allow python-gssapi on a 32-bit python application.

[frozencemetery]

Hi, thanks for your interest in this project. This seems useful, so I do intend to merge support. Couple things first:

• You'll need to pass CI (doesn't look like anything major is broken).
• Your commit message subject is too long. I can fix this before merging, but if you'd like to yourself, I suggest reading this post for an idea.

[asheshv]

Hi, thanks for your interest in this project. This seems useful, so I do intend to merge support. Couple things first:

• You'll need to pass CI (doesn't look like anything major is broken).
  I've checked last CI, something was broken in the last commit.

It have fixed that as well.

• Your commit message subject is too long. I can fix this before merging, but if you'd like to yourself, I suggest reading this post for an idea.

That will help.

[frozencemetery]

@aiudirog Since we don't have a way to test 32-bit Windows in CI right now, would you mind double-checking this?

[aiudirog]

This looks good to me, but I think we should add CI support for 32bit, at least on Windows. I think it actually should be fairly easy with a slight modification to the matrix. Give me few moments to try something.

[aiudirog]

I can't push directly to this branch, so we'll go old school with a patch file.

0001-CI-Build-and-release-on-32bit-Windows-Python.txt

---

Also, GitHub, why do you not support .patch/.diff files....?

[frozencemetery]

Thanks, applied it. I think 8 is probably overkill for Windows - let me see if I can pare that down...

[aiudirog]

Looks like the i386 folder isn't available when kerberos is installed through chocolatey. Maybe we need to find a 32bit specific one?

[frozencemetery]

Beyond me, sorry. I think adding 32-bit CI isn't a bad idea if it can be made to work. I think you can open a separate PR using the commit here as basis?

[aiudirog]

That should work, I'll see what I can do.