2014-01-25 Guido van Rossum <[email protected]>: > Thanks, Victor. In the end that looks like the best solution.
It looks like Charles-François doesn't like it: http://bugs.python.org/issue20311#msg209213 My latest patch is more generic because it uses also the resolution of the clock. > Are there any open issues left in Tulip that you'd like to be handled > before CPython beta 3? My first week of classes is over and my Tulip > talk is done, so I have a little breathing room this weekend. Hum, yes, something should be done for subprocess. IMO the API of subprocess should be changed. The best would be to provide something like StreamReader and StreamWriter for subprocess. If it's not possible to develop it before Python 3.4 final, a compromise is to ensure that the API allows to develop it later. According to my analysis (see the other dedicated thread on Tulip mailing list), it's not the case with the current API. You may take a look at my two following issues, but they are minor. http://code.google.com/p/tulip/issues/detail?id=110 http://code.google.com/p/tulip/issues/detail?id=112 This bug looks more important: http://code.google.com/p/tulip/issues/detail?id=109 It tries to fix all remaing issues before beta3. Victor
