On 08:28 pm, wolfgang....@rohdewald.de wrote:
Am Sonntag, 5. Oktober 2014, 19:58:29 schrieb
exar...@twistedmatrix.com:
For example, following the plan, I would have expected to see perhaps
two patches to port the banana module: one to add the missing test
coverage and one to make any and all changes necessary to get the test
suite to pass on Python 3.
Impossible. test_jelly imports pb, test_pb imports jelly.
That doesn't mean it's impossible. It just means you may also have to
shuffle some files around.
But I can of course reduce the number of tickets related to porting and
put more than one patchfile into them.
Note that my point isn't that we need to reduce the number of tickets
related to porting or that there should be more than one patch to
resolve any one ticket (there shouldn't be).
The point is that the documented porting plan is to port module by
module, not Python 3 incompatible change by Python 3 incompatible
change.
Jean-Paul
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
