python-billiard/python-billiard.changes

63 lines
2.5 KiB
Plaintext
Raw Normal View History

-------------------------------------------------------------------
Thu May 17 23:40:18 UTC 2012 - jfunk@funktronics.ca
- Update to 2.7.3.5
* Now always cleans up after sys.exc_info() to avoid cyclic references.
* ExceptionInfo without arguments now defaults to sys.exc_info.
* Forking can now be disabled using the MULTIPROCESSING_FORKING_DISABLE
environment variable.
Also this envvar is set so that the behavior is inherited after execv.
* The semaphore cleanup process started when execv is used now sets a useful
process name if the setproctitle module is installed.
* Sets the FORKED_BY_MULTIPROCESSING environment variable if forking is
disabled.
-------------------------------------------------------------------
Fri Apr 27 22:54:35 UTC 2012 - jfunk@funktronics.ca
- Update to 2.7.3.4
* Added billiard.ensure_multiprocessing() - Raises NotImplementedError if
the platform does not support multiprocessing (e.g. Jython).
-------------------------------------------------------------------
Wed Apr 25 19:09:15 UTC 2012 - jfunk@funktronics.ca
- Generate new spec
- Update to 2.7.3.3
* PyPy now falls back to using its internal _multiprocessing module, so
everything works except for forking_enable(False) (which silently degrades)
* Fixed Python 2.5 compat issues.
* Uses more with statements
* Merged some of the changes from the Python 3 branch.
- 2.7.3.2 - 2012-04-20
* Now installs on PyPy/Jython (but does not work).
- 2.7.3.1 - 2012-04-20
* Python 2.5 support added.
- 2.7.3.0 - 2012-04-20
* Updated from Python 2.7.3
* Python 2.4 support removed, now only supports 2.5, 2.6 and 2.7. (may
consider py3k support at some point).
* Pool improvments from Celery.
* no-execv patch added (http://bugs.python.org/issue8713)
-------------------------------------------------------------------
Fri Nov 25 07:55:37 UTC 2011 - jfunk@funktronics.ca
- Update to 0.3.1
* Fixed broken bool evaluation in supervisor. Thanks to jonozzz
The bug originated from a ``a if x else b`` vs. ``x and a or bz``
confusion when porting code to Python 2.4.
* ``ApplyResult._set`` can't delete the result if it's not been accepted.
This also means ``ApplyResult._ack`` needs to delete the result if the job
has been marked ready.
- 0.3.0
* Added support for accept callbacks.
- 0.2.3
* Python 2.4 support.
-------------------------------------------------------------------
Wed Apr 14 17:16:15 UTC 2010 - jfunk@funktronics.ca
- Initial import