[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Changes by Berker Peksag : -- stage: commit review -> resolved ___ Python tracker ___

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Changes by Gregory P. Smith : -- resolution: -> fixed stage: needs patch -> commit review status: open -> closed ___ Python tracker ___

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Roundup Robot added the comment: New changeset a4c0208b10df by Gregory P. Smith in branch '2.7': issue25931: document that socketserver.Forking* are unavailable on platforms https://hg.python.org/cpython/rev/a4c0208b10df -- ___ Python tracker

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Roundup Robot added the comment: New changeset 015b86646d8e by Gregory P. Smith in branch 'default': issue25931: document that socketserver.Forking* are unavailable on platforms https://hg.python.org/cpython/rev/015b86646d8e -- ___ Python tracker

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Gregory P. Smith added the comment: It may be worth rolling back the above two commits. I'm not sure. I'd like to see if anything else falls out of this during the beta phases. There is a chance that some library has code similar to that found in test_socketserver.py that defines classes

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Roundup Robot added the comment: New changeset 3145242bc81f by Gregory P. Smith in branch 'default': Issue25931: fix tests broken by the conditional define of socketserver.Forking* https://hg.python.org/cpython/rev/3145242bc81f -- ___ Python tracker

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Martin Panter added the comment: This broke test_socketserver: http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/7709/steps/test/logs/stdio 0:08:57 [193/400/1] test_socketserver failed test test_socketserver crashed -- Traceback (most recent call last): File

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

R. David Murray added the comment: Well, defined for 3.6, and "functional" for 2.7 and 3.5 docs. -- ___ Python tracker ___

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

R. David Murray added the comment: Your news entry says "don't defining". The doc note can say that the classes are only defined if the platform supports fork. -- ___ Python tracker

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Gregory P. Smith added the comment: I made the change to not export the Forking names on Windows or other non-os.fork() supporting platforms in 3.6 only as it is arguably an API change, even though the names it removes would effectively be unusable on those platforms anyways. the docs still

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Roundup Robot added the comment: New changeset d772400a1211 by Gregory P. Smith in branch 'default': Issue #25931: Don't defining socketserver.Forking* names on platforms such https://hg.python.org/cpython/rev/d772400a1211 -- nosy: +python-dev ___

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

R. David Murray added the comment: They aren't currently defined conditionally, though, and haven't ever been, so I'm not sure it is worth chaning that. However, we should probably add an 'availability' line, since they aren't (effectively) available on Windows. -- assignee: ->

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Changes by SilentGhost : -- versions: -Python 3.4 ___ Python tracker ___ ___

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Changes by supriyanto maftuh,st : -- nosy: +supriyanto maftuh versions: +Python 3.4 ___ Python tracker ___

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Changes by Anthony S Valencia : -- nosy: +antvalencia ___ Python tracker ___ ___

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Changes by Davin Potts : -- nosy: +davin ___ Python tracker ___ ___

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

New submission from Sam Lobel: I ran into this bug while using multiprocessing in Flask, which deep down uses the SocketServer.py module. There's a call to os.fork() in the windows version , which obviously doesn't work. So SocketServer.py can't be used on windows. Maybe replace it with

[issue25931] os.fork() command distributed in windows Python27 (in SocketServer module)

Eryk Sun added the comment: Starting a Windows process is expensive. Who not use threading, e.g. SocketServer.ThreadingTCPServer? It seems to me that it's a bug to even define ForkingMixIn, ForkingTCPServer, and ForkingUDPServer on Windows. Those should be conditionally defined depending on