[issue7225] fwrite() compiler warnings

2014-03-12 Thread Benjamin Peterson
Changes by Benjamin Peterson : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue7225] fwrite() compiler warnings

2014-02-03 Thread Mark Lawrence
Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue7225] fwrite() compiler warnings

2013-01-31 Thread Ramchandra Apte
Ramchandra Apte added the comment: I'm pretty sure this is invalid now. -- nosy: +ramchandra.apte ___ Python tracker ___ ___ Python-bug

[issue7225] fwrite() compiler warnings

2010-09-18 Thread Mark Lawrence
Mark Lawrence added the comment: See also #1616 and #1621. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: h

[issue7225] fwrite() compiler warnings

2010-08-03 Thread Mark Lawrence
Mark Lawrence added the comment: I'm assuming that this is still an issue, sorry I don't have gcc 4.3.2 to try it out on. -- nosy: +BreamoreBoy ___ Python tracker ___ __

[issue7225] fwrite() compiler warnings

2010-08-03 Thread Dirkjan Ochtman
Changes by Dirkjan Ochtman : -- nosy: +djc ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue7225] fwrite() compiler warnings

2009-10-27 Thread Benjamin Peterson
New submission from Benjamin Peterson : gcc 4.3.2 is currently coughing up warnings like this: Objects/object.c: In function 'internal_print': Objects/object.c:301