> Sure. I'll work on this patch. Should I log the bug into SF tracker > as well? I agree that it would be nice to have some sort of overridden > method at that point. The decision just has to be whether or not > t.setDaemon (1) should be the default. The warning is a good idea. I > think the setDeamon default is what previous users expect. I have to admit I'm pretty fuzzy on the details. Running a server interactively and hitting ^C doesn't seem like a very common use case to me. I'm not sure the setDaemon() is right in other situations -- if a server decides to exit gracefully, shouldn't it let a client session run to completion? --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4