[issue3278] socket's SO_OOBINLINE option does not work

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: A friend confirms that on NetBSD it matches the Linux behavior. "read -> x" is printed before the exception. also fwiw, my OS X version is 10.5.3. IMNSHO not a python bug. open it with FreeBSD and Apple. -- resolution: -> inval

[issue3278] socket's SO_OOBINLINE option does not work

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: further reading reveals that this is the expected behavior. p651 in 24.2: "select indicates an exception condition until the process reads -beyond- the out of band data." ... "the solution is to only select for an exception condition afte

[issue3278] socket's SO_OOBINLINE option does not work

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: p648 of Unix Network Programming third edition: "4. If the process has set the SO_OOBINLINE socket option and then tries to read the out-of-band data by specifying MSG_OOB, EINVAL is returned." so it does not sound like a bug in Python. T

[issue3278] socket's SO_OOBINLINE option does not work

Gregory P. Smith <[EMAIL PROTECTED]> added the comment: This also happens on Linux: read -> x Exception in thread Thread-1: Traceback (most recent call last): File "/home/greg/sandbox/python/trunk/Lib/threading.py", line 523, in __bootstrap_inner self.run() File "/home/greg/sandbox/pytho

[issue3278] socket's SO_OOBINLINE option does not work on OS X and FreeBSD

Changes by Gregory P. Smith <[EMAIL PROTECTED]>: -- assignee: -> gregory.p.smith nosy: +gregory.p.smith priority: -> normal title: socket's SO_OOBINLINE option does not work on FreeBSD -> socket's SO_OOBINLINE option does not work on OS X and FreeBSD _

[issue3278] socket's SO_OOBINLINE option does not work on FreeBSD

Changes by Giampaolo Rodola' <[EMAIL PROTECTED]>: -- title: socket's SO_REUSEADDR option does not work on FreeBSD -> socket's SO_OOBINLINE option does not work on FreeBSD ___ Python tracker <[EMAIL PROTECTED]> _