[Twisted-Python] What Win32 issues are important to you?
I'm going to set aside some time to work on win32 issues, and was wondering what tickets are particularly important for the folks out there? -- Eric Mangold Twisted/Win32 Maintainer
On 12/7/06, Eric Mangold <teratorn@twistedmatrix.com> wrote:
I'm going to set aside some time to work on win32 issues, and was wondering what tickets are particularly important for the folks out there?
Hey Eric, Thanks for showing the Windows love. The most pressing win32 issue for me is the large number of reactor unclean warnings in the win32event reactor.
Another very important issue is the buildslaves. As a UNIX[1] developer, the buildslaves are my primary point of interaction with the Windows world. This leads to two things: 1. It's hard to care about the win32er and iocp reactors when they are always red.[2] 2. It would be very nice for the "remove-.pyc" step to always work. That's it from me. Thanks again for taking the time to look after win32. cheers, jml [1] I feel justified in calling Mac OS X a UNIX. It helps me sleep. [2] Perhaps we should have two buildbot pages: "supported" and "unsupported". win32er, iocp, tsr, pypy and friends can all hide on "unsupported".
On Thu, 07 Dec 2006 18:16:29 -0600, Jonathan Lange <jml@mumak.net> wrote:
Great, thanks.
I think this is one instance of a bigger problem: it's hard to care about a buildslave that is always red *if you don't know what you changed*. What do you guys think.. If buildbot told us which tests passed/failed since the last build, would that help at all?
2. It would be very nice for the "remove-.pyc" step to always work.
I will see what I can do about this.
That's it from me. Thanks again for taking the time to look after win32.
Thanks for the ideas. -Eric
On 12/7/06, Eric Mangold <teratorn@twistedmatrix.com> wrote:
I'm going to set aside some time to work on win32 issues, and was wondering what tickets are particularly important for the folks out there?
Hey Eric, Thanks for showing the Windows love. The most pressing win32 issue for me is the large number of reactor unclean warnings in the win32event reactor.
Another very important issue is the buildslaves. As a UNIX[1] developer, the buildslaves are my primary point of interaction with the Windows world. This leads to two things: 1. It's hard to care about the win32er and iocp reactors when they are always red.[2] 2. It would be very nice for the "remove-.pyc" step to always work. That's it from me. Thanks again for taking the time to look after win32. cheers, jml [1] I feel justified in calling Mac OS X a UNIX. It helps me sleep. [2] Perhaps we should have two buildbot pages: "supported" and "unsupported". win32er, iocp, tsr, pypy and friends can all hide on "unsupported".
On Thu, 07 Dec 2006 18:16:29 -0600, Jonathan Lange <jml@mumak.net> wrote:
Great, thanks.
I think this is one instance of a bigger problem: it's hard to care about a buildslave that is always red *if you don't know what you changed*. What do you guys think.. If buildbot told us which tests passed/failed since the last build, would that help at all?
2. It would be very nice for the "remove-.pyc" step to always work.
I will see what I can do about this.
That's it from me. Thanks again for taking the time to look after win32.
Thanks for the ideas. -Eric
participants (3)
-
Eric Mangold -
Jean-Paul Calderone -
Jonathan Lange