depenency on python-keyring is problematic

[Zygmunt Krynicki]

Installing lava-tool pulls in python-keyring. Attempting to download it from the network fail (eventually it works but it takes forever). In addition it fails to install on windows (thus preventing us from shipping easy-to-use windows lava.exe to people in all the member companies).

1) fork it
2) improve it
3) call it lava-keyring
4) use it later on in the lava-server world for storing secrets

[Alexander Sack (asac)]

have we checked what else blocks us from lava-tool available on windows?

Why do we need to fork it? Is it dead upstream?

[Zygmunt Krynicki (zyga)]

It has been improved recently. The upstream is not dead, I was questioning the necessity of using the keyring at all.

The windows problem is related to building native extension which is arguably hard on windows (you need to install visual studio 2008). I wanted to be able to ship lava.exe to all windows users and let them interact with all server side pieces without having to do much more.

Currently keyring added support for ctypes-based extension loading on windows and osx. I need to evaluate this again. My intent was to ensure that having python 2.7 installation from python.org and pip-from-source installation, without having the whole microsoft toolchain yields a working and usable lava program.