Comment 26 for bug 314507

Re. #24
Based on what you've taught me, the Windows issue is probably just insufficient documentation as opposed to missing functionality, but as I won't be running Windows for some weeks, I won't be following up. As I pointed out, the Install instructions for launchpadlib cover only apt-get on Ubuntu and UNIX shell commands, i.e. no Windows installation instructions. Reasonable (but apparently incorrect) to conclude from that that launchpadlib is not supported on Windows.

R3. #25
Regarding the question move, the relationships between some of the projects, like the semi-present "python-launchpadlib in ubuntu" baffles me, but it looks like you moved my question to an orphaned location. I intended to post the question originally to the launchpadlib project, but as I explained in #13 above, Answers is disabled for that project. Is seems that you've moved the question to https://answers.launchpad.net/launchpadlib/+question/137470 , but if you click on Answers from there, you see that that new parent project has no Answers, so I think the question is now not reachable through site navigation. Fine with me to leave it orphaned though.

Re. Windows tools, it's not that one couldn't attempt it, it is that installation instructions are glaringly missing for Windows, and supplied artifacts give the impression of being designed for UNIX/Windows, and this all gives one little confidence that it would work on Windows. Neither "$ sudo apt-get..." nor "$sudo ./setup.py..." will work on a typical Windows installation, and those are the alternatives offered.

I can put my headers in any order I want to, but whereas changing param sequences fixes the consumer key recognition problem, it doesn't fix my problem that the correctly "recognized" consumer key is incorrectly being rejected. I'll register a new bug on that if it persists after the fix here goes live. I just hope that that turn-around doesn't eat up too many days.