Hello community, here is the log from the commit of package python-billiard for openSUSE:Factory checked in at 2013-11-14 08:43:19 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-billiard (Old) and /work/SRC/openSUSE:Factory/.python-billiard.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-billiard" Changes: -------- --- /work/SRC/openSUSE:Factory/python-billiard/python-billiard.changes 2013-10-25 11:11:41.000000000 +0200 +++ /work/SRC/openSUSE:Factory/.python-billiard.new/python-billiard.changes 2013-11-14 08:43:21.000000000 +0100 @@ -1,0 +2,51 @@ +Wed Nov 13 16:56:40 UTC 2013 - [email protected] + +- Update to version 3.3.0.6 + + Now works without C extension again. + + New ``_billiard.read(fd, buffer, [len, ])` function + implements os.read with buffer support (new buffer API) + + New pure-python implementation of ``Connection.send_offset``. +- Changes from 3.3.0.5 + + All platforms except for Windows/PyPy/Jython now requires the C extension. +- Changes from 3.3.0.4 + + Fixed problem with Python3 and setblocking. +- Changes from 3.3.0.3 + + Now works on Windows again. +- Changes from 3.3.0.2 + + ApplyResult.terminate() may be set to signify that the job + must not be executed. It can be used in combination with + Pool.terminate_job. + + Pipe/_SimpleQueue: Now supports rnonblock/wnonblock arguments + to set the read or write end of the pipe to be nonblocking. + + Pool: Log message included exception info but exception happened + in another process so the resulting traceback was wrong. + + Pool: Worker process can now prepare results before they are sent + back to the main process (using ``Worker.prepare_result``). +- Changes from 3.3.0.1 + + Pool: New ``correlation_id`` argument to ``apply_async`` can be + used to set a related id for the ``ApplyResult`` object returned: + >>> r = pool.apply_async(target, args, kwargs, correlation_id='foo') + >>> r.correlation_id + 'foo' + + Pool: New callback `on_process_exit` is called when a pool + process exits, with signature ``(pid, exitcode)``. + + Pool: Improved the too many restarts detection. +- Changes from 3.3.0.0 + + Dual code base now runs on Python 2.6+ and Python 3. + + No longer compatible with Python 2.5 + + Includes many changes from multiprocessing in 3.4. + + Now uses ``time.monotonic`` when available, also including + fallback implementations for Linux and OS X. + + No longer cleans up after receiving SIGILL, SIGSEGV or SIGFPE + + ``Finalize`` and ``register_after_fork`` is now aliases to multiprocessing. + It's better to import these from multiprocessing directly now + so that there aren't multiple registries. + + New `billiard.queues._SimpleQueue` that does not use semaphores. + + Pool: Can now be extended to support using multiple IPC queues. + + Pool: Can now use async I/O to write to pool IPC queues. + + Pool: New ``Worker.on_loop_stop`` handler can be used to add actions + at pool worker process shutdown. + Note that, like all finalization handlers, there is no guarantee that + this will be executed. + +------------------------------------------------------------------- Old: ---- billiard-2.7.3.32.tar.gz New: ---- billiard-3.3.0.6.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-billiard.spec ++++++ --- /var/tmp/diff_new_pack.cG700N/_old 2013-11-14 08:43:21.000000000 +0100 +++ /var/tmp/diff_new_pack.cG700N/_new 2013-11-14 08:43:21.000000000 +0100 @@ -17,7 +17,7 @@ Name: python-billiard -Version: 2.7.3.32 +Version: 3.3.0.6 Release: 0 Url: http://github.com/ask/billiard Summary: Python multiprocessing fork ++++++ billiard-2.7.3.32.tar.gz -> billiard-3.3.0.6.tar.gz ++++++ ++++ 5868 lines of diff (skipped) -- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
