[issue2944] asyncore doesn't handle connection refused correctly

Alexander Shigin <[EMAIL PROTECTED]> added the comment: I've got the same error in r64768. ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2944> ___ ___

[issue2944] asyncore doesn't handle connection refused correctly

Changes by Alexander Shigin <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file10401/asyncore-connect-patch.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2944] asyncore doesn't handle connection refused correctly

Alexander Shigin <[EMAIL PROTECTED]> added the comment: Here is a new patch against r64768 The new patch raise an exception if asynchronous connect fails. Added file: http://bugs.python.org/file10856/asyncore-connect-patch.diff ___ Python tracker &

[issue2944] asyncore doesn't handle connection refused correctly

Alexander Shigin <[EMAIL PROTECTED]> added the comment: Oh, fine. May be handle_error should have been called, but anyway not handle_connect. But in my mind, handle_expt is better. __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2944] asyncore doesn't handle connection refused correctly

Alexander Shigin <[EMAIL PROTECTED]> added the comment: Oh, I've just realised that FreeBSD is too fast. test_async_connect.py works fine on linux box, but on FreeBSD i need to change localhost to another host :( I haven't got any idea how to make a test case which work

[issue2944] asyncore doesn't handle connection refused correctly

Alexander Shigin <[EMAIL PROTECTED]> added the comment: Patch against r63534 fix the issue. -- keywords: +patch Added file: http://bugs.python.org/file10401/asyncore-connect-patch.diff __ Tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue2944] asyncore doesn't handle connection refused correctly

New submission from Alexander Shigin <[EMAIL PROTECTED]>: Unix select returns socket in read fd set and write fd set if nonblocking socket attempts to connect to unaviable address. asyncore should check this case by calling getsockopt with SO_ERROR optname. If return value is 0 it

[issue1981] operator "is"

Alexander Shigin added the comment: I think it's good idea to make a note in Comparisons section or make some reference to data model section. """ The operators is and is not test for object identity: x is y is true if and only if x and y are the same object. x is not

[issue1981] operator "is"

New submission from Alexander Shigin: Hello, The operator "is" works strange with methods, i.e.: >>> a = 1 >>> a.__abs__ is a.__abs__ False If this is the preferred behavior by some reasons, I think documentation should explain it. It was tested on python 2