[issue9782] _multiprocessing.c warnings under 64-bit Windows

2019-09-11 Thread Steve Dower
Change by Steve Dower : -- resolution: -> out of date stage: needs patch -> resolved status: open -> closed ___ Python tracker ___ _

[issue9782] _multiprocessing.c warnings under 64-bit Windows

2019-03-15 Thread Mark Lawrence
Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue9782] _multiprocessing.c warnings under 64-bit Windows

2015-04-27 Thread Davin Potts
Changes by Davin Potts : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org

[issue9782] _multiprocessing.c warnings under 64-bit Windows

2015-03-17 Thread Mark Lawrence
Mark Lawrence added the comment: Where do we currently stand with all compiler warnings, I'm still seeing some but I recall that we've other open issues about this problem? -- nosy: +serhiy.storchaka, steve.dower, zach.ware versions: +Python 3.4, Python 3.5 -Python 3.2

[issue9782] _multiprocessing.c warnings under 64-bit Windows

2014-07-09 Thread Brian Curtin
Changes by Brian Curtin : -- nosy: -brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue9782] _multiprocessing.c warnings under 64-bit Windows

2014-07-09 Thread Mark Lawrence
Mark Lawrence added the comment: I'd assume that these were cleared years ago. -- nosy: +BreamoreBoy ___ Python tracker ___ ___ Python-

[issue9782] _multiprocessing.c warnings under 64-bit Windows

2010-09-13 Thread Jon Anglin
Changes by Jon Anglin : -- nosy: +janglin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue9782] _multiprocessing.c warnings under 64-bit Windows

2010-09-12 Thread Martin v . Löwis
Martin v. Löwis added the comment: It seems that multiprocessing is fairly conservative wrt. 64-bit support. For example, conn_send_string has a string limit of 0x7fff. Therefore, several of the warnings are harmless; the respective lengths fit into int just fine. I recommend that the siz

[issue9782] _multiprocessing.c warnings under 64-bit Windows

2010-09-06 Thread Antoine Pitrou
New submission from Antoine Pitrou : There are various warnings when compiling the _multiprocessing extension in 64-bit mode under Windows. Many seem related to the fact that read() and friends under Windows take "int" size arguments rather than "size_t". 20>-- Build started: Project: _mul