New Select Module
There is now select support in the [http://www.jython.org/Project/download.html jython distribution], as of version 2.2rc1.
The new module presents an API which is as close as possible to the [http://www.python.org/doc/lib/module-select.html cpython select module], Jython supports both the
- select.select function
[http://www.python.org/doc/lib/poll-objects.html select.poll objects].
When using the select module, you should be guided by the cpython documentation: any deviation from the behaviour described in that documentation, except for the the considerations mentioned below, should be considered a bug and [http://www.jython.org/bugs reported] as such.
If you are starting a new project, it is recommended that you use select.poll objects, because
Poll objects are the most efficient mechanism to multiplex sockets on jython, being fairly much a direct mapping to [http://java.sun.com/j2se/1.4.2/docs/api/java/nio/channels/Selector.html java.nio.channel.Selector objects].
- The select.select function is implemented using a poll object, which means that sockets are de/registered every single time, which is slightly less efficient.
Always close poll objects
When a socket has been registered with a select.poll object, it remains registered until explicitly deregistered. This has the following implications
- Sockets cannot be placed in blocking mode while they are still registered with poll objects
- The reference from the poll object to the socket might interfere with garbage collection
Therefore, it is recommended that you always explicitly close poll objects, using an idiom such as
def my_polling_func(sockets): poll_object = select.poll() try: for s in sockets: poll_object.register(s) finally: poll_object.close()
Closing a poll object cancels all registrations of sockets.
Differences between cpython and jython
Due to fundamental differences in the behaviour of java and C on various platforms, there are differences between the cpython and jython select modules which are not possible to code around. Those differences will be listed here.
Only sockets in non-blocking mode can be multiplexed
On cpython, when a socket is passed to select.select or select.poll, it can either be in blocking or non-blocking mode.
However, [http://java.sun.com/j2se/1.4.2/docs/api/java/nio/channels/SelectableChannel.html#register(java.nio.channels.Selector,%20int) java will only permit multiplex operations on sockets that are in non-blocking mode]. Because jython must respect this java restriction, any attempt in jython to pass a socket in blocking mode to either select.select or select.poll().register will fail with an exception.
- You must set a socket in non-blocking mode before passing it to the select function or registering it with a poll object
- Any attempt to register a blocking socket for multiplex will raise a select.error exception, with an error code of errno.ESOCKISBLOCKING
- If a socket is currently registered with a select.poll object, an attempt to change it to blocking mode will give rise to the same exception.
A socket can only be placed in blocking mode if it is not registered with a select.poll object.
This issue could be problematic if you want to use a cpython module which relies on select. Such cpython modules do not set their sockets in non-blocking mode before passing them to select.select. In order to support such cpython modules, the following workaround is available.
The cpython-compatible select function
A special version of the select function is provided, to provide cpython compatible select functionality. This function works by
- Recording the blocking mode of all sockets that are passed to the function
- Setting non-blocking mode on all sockets
- Calling the normal jython select.select function (which requires non-blocking sockets)
- Restoring the previously-saved blocking mode for all sockets
- Returning the results of the wrapped select function
This function should only be used when you are working with code that has been written for cpython select, i.e. when the code is passing blocking-sockets to the select function.
How to enable cpython compatible select processing
Here is a code sample which shows how to use the cpython-compatible select function as a replacement for the standard jython select function
from select import cpython_compatible_select as select # Make use of the select function here
- If using the cpython_compatible_select function, you must be aware that the function will modify the blocking mode of your sockets for the duration of the call. If you are carrying out socket operations on that socket in another thread, then those socket operations may fail or raise exceptions.
This function will still not cover all possible uses of select.select by cpython modules. If a cpython module tries to multiplex the sys.stdin or sys.stdout streams, then registration of the channels will fail, because the InputStream and OutputStream representing sys.stdin and sys.stdout are not SelectableChannels.
Receiving urgent data can cause select to lie (Windows implementation)
Bug 1773955 describes the scenario. It is caused by a bug in the Sun Java implementation and there is no known Jython fix. A partial workaround is to call setOOBInline(True) on the jsocket within the Jython socket. This will cause the urgent data to be merged into the regular stream and will keep from confusing select() however you will have to ignore the urgent data at the application level.
Addendum: Support for socket options has been checked into the repo at [http://fisheye3.atlassian.com/changelog/jython/?cs=4493 revision 4494]. See NewSocketModule for more details on the options available.
With the new support, you don't need to call the java API on the underlying socket; you can set the OOBINLINE flag using python syntax, like this
mysock.setsockopt(socket.SOL_SOCKET, socket.SO_OOBINLINE, 1)
But there is still no workaround for the lack of support for TCP Urgent Data on java.