TJG added the comment:
That last should clearly have said:
Thanks for doing the housekeeping work here
:)
--
___
Python tracker
<https://bugs.python.org/issue34
TJG added the comment:
Thanks, Cheryl. It was getting pretty stale. If I think it's worthwhile
I'll resurrect it.
I suspect what happened was that my cpython fork got borked somehow
between then and now. I probably ditched the repo and re-forked. That's
for doing the houseke
TJG added the comment:
Thanks, Brett. I'll address Serhiy's comment with a new PR and then tidy
yup.
--
nosy: +tjguk
___
Python tracker
<https://bugs.python.o
TJG added the comment:
The error is coming from the extension module's "connect" function
(which is the standard DB API entry point for Python database
interfaces). Presumably from your description, some environmental
situation leaves it with an unconsidered code pat
TJG added the comment:
Excluding for now seems like a simple option. (Basically a reversion to
previous behaviour). And allows us easily to include again later easily.
Messing with setsockopt seems a little more risky.
In short: I'm with you -- exclude fo
TJG added the comment:
It's a compile-time option in socketmodule.c.
https://github.com/python/cpython/blob/3.6/Modules/socketmodule.c#L7466
The MSDN page suggests that it was added for Win10:
https://msdn.microsoft.com/en-us/library/windows/desktop/ms738596(v=vs.85).aspx
Is it pos
TJG added the comment:
If I run your code, it does what I expect: pressing Ctrl-C produces
"Interrupt", doesn't print the data returned from raw_input, and doesn't
produce a stacktrace.
I'm not on Win10 and it's entirely possible that this area of the MS CRT
has be
TJG added the comment:
I don't have Win10 to test with, but can you confirm that the method is
necessary for the code to fail? IOW does this fail equally?
while True:
try: raw_input()
except KeyboardInterrupt: print "Interrupt!"
Also, do I assume that the code si
