> Windows 8 launches Oct 26; Python is frankly just not ready, and no one but Martin L and a few others seem to care (or even notice).
Part of the problem is that you could count on one hand the number of contributors who have worked on non-trivial Windows issues in CPython in the last 12 months (probably even 24). I think we're pretty aware of this, but there are still only 24 hours in a day.
In fact, my new SSD should be arriving today to complete the build of my new machine, and Martin's work on WinRT probably jumps ahead on my todo list.
I don't think the main issue from OP is that WinRT support is not ready yet: windows 8 is not even out yet. The fact that he will have to migrate to python 3 to get there seems to be the main issue.
This lack of contributors would not have been as a serious problem without the insistence to break backwards compatibility and fork efforts for five (and counting) years: it sounds like the work got done, it is just for the "wrong version" (the one few people can use) of Python.
Part of the problem is that you could count on one hand the number of contributors who have worked on non-trivial Windows issues in CPython in the last 12 months (probably even 24). I think we're pretty aware of this, but there are still only 24 hours in a day.
In fact, my new SSD should be arriving today to complete the build of my new machine, and Martin's work on WinRT probably jumps ahead on my todo list.