Hi, now that the py3k warnings are fixed (see http://bugs.python.org/issue7092) we should run the tests on the trunk buildbots with the -3 flags, in order to check if new warnings are introduced and possibly to uncover other ones. It might be a good idea to add the -Wd flag too, both on trunk and py3k. -Ezio
On Wed, Mar 31, 2010 at 07:58, Ezio Melotti <ezio.melotti@gmail.com> wrote:
Hi, now that the py3k warnings are fixed (see http://bugs.python.org/issue7092) we should run the tests on the trunk buildbots with the -3 flags, in order to check if new warnings are introduced and possibly to uncover other ones. It might be a good idea to add the -Wd flag too, both on trunk and py3k.
+1 from me. -Brett
2010/3/31 Brett Cannon:
On Wed, Mar 31, 2010 at 07:58, Ezio Melotti wrote:
Hi, now that the py3k warnings are fixed (see http://bugs.python.org/issue7092) we should run the tests on the trunk buildbots with the -3 flags, in order to check if new warnings are introduced and possibly to uncover other ones. It might be a good idea to add the -Wd flag too, both on trunk and py3k.
+1 from me.
I agree, it could help to catch unexpected warnings or bugs earlier in the process. -- Florent
now that the py3k warnings are fixed (see http://bugs.python.org/issue7092) we should run the tests on the trunk buildbots with the -3 flags, in order to check if new warnings are introduced and possibly to uncover other ones. It might be a good idea to add the -Wd flag too, both on trunk and py3k.
Not sure what you are asking for. If you want confirmation that this change is desirable, it seems you got that already. If you are asking for someone to make that change - go ahead and make it yourself. You just need to change the buildbottest target. Regards, Martin
participants (4)
-
"Martin v. Löwis" -
Brett Cannon -
Ezio Melotti -
Florent Xicluna