Ampoule

Latest version: v24.10.0

Safety actively analyzes 682229 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

22.5.0

===========================

- Various packaging metadata fixes to work better with current versions of
pip-tools (as well as other packaging tools).

19.12.0

============================

- Replace all uses of twisted.python.log with twisted.logger.
- Don't return an already-dead worker to the ready pool.

19.6.0

===========================

- Fix a process leak when a process exits non-zero on recycling.

0.3.1

==========================

- Restored to original name after maintenance handover.
- Updated home page to new source code location.
- Minor python 2 compatibility issue in the tests (introduced in 0.3.0) fixed.

Ampoul3 0.3.0 (2017-12-10)
==========================

Changes
-------

- Python 3 support.
- Pyflakes fixes.
- No more trailing whitespace :).
- Migrated to Git.
- (Hopefully temporary) package name change while I wait for Valentino to
give me access to PyPI...

0.2.0

==========================

Changes
--------
- Fixed bug 317287: Twisted was required by setup.py due to import
of application code to get the version number. The setup.py now
tries to do the same thing but if it fails it uses a separate
hardcoded version.
- Fixed bug 317077: Ampoule didn't work on windows xp due to childFD
customization, now on windows ampoule uses the standard 0,1,2 fds.
- Added pyOpenSSL as an explicit dependency since Twisted doesn't
require it but AMP does.
- Greatly simplify setup.py and support plain distutils too.
- Bootstrap code now supports context managers
- Support for execution deadline on child calls
- Parametrize the timeout signal to send to the child
- Pass arguments directly from the ProcessPool object for the child
process creation.

0.1

==========================

Changes
--------

- Fixed bug 276841: Add timeout for subprocess calls.
The ProcessPool constructor now supports an additional timeout
argument that specifies a pool level timeout, in seconds, before
which every call ever made should return. Alternatively there is
also a per-call mechanism. Currently this second per-call system
is not available when using the remote pool service, so be sure
to set the timeout command line parameter at an high enough level
to satisfy all the possible commands. If a command doesn't require
an answer the timeout doesn't apply, of course.

The error returned when a call is timedout is 'error.ProcessTerminated'.
On *nix systems the process is terminated with signal 9, on windows
ampoule uses SIGTERM and returns error code 255.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.