python-futures-3.2.0-bp152.2.18

- specfile:
  * removed CHANGES from %doc (not in tar-ball anymore), added README.rst
- update to version 3.2.0:
  * The ThreadPoolExecutor class constructor now accepts an optional
    thread_name_prefix argument to make it possible to customize the
    names of the threads created by the pool. Upstream contribution by
    Gregory P. Smith in https://bugs.python.org/issue27664.
  * Backported fixes from upstream (thanks Lisandro Dalcin):
    + python/cpython#1560
    + python/cpython#3270
    + python/cpython#3830

- Skip building oh python3 subpackage as it is not supported

- update to 3.1.1:
- Backported sanity checks for the ``max_workers`` constructor argument for ThreadPoolExecutor and
  ProcessPoolExecutor
- Set the default value of ``max_workers`` in ThreadPoolExecutor to ``None``, as in upstream code
  (computes the thread pool size based on the number of CPUs)
- Added support for old-style exception objects
- Switched to the PSF license

- Update %python_module redefinition, fixing %fdupes call

- Update to singlespec.

- update to 3.0.5:
  - Fixed OverflowError with ProcessPoolExecutor on Windows (regression introduced in 3.0.4)
  - Fixed inability to forcibly terminate the process if there are pending workers
  - Fixed AttributeErrors on exit on Python 2.x
  - remove upstreamed fix-testsuite.patch

- Package required in SLE12 due to fate#319400

- Disable tests for SLE 11, the testsuite uses Python 2.7 constructs

- Enable and fix test suite (fix-testsuite.patch)

- Update to 3.0.2:
  * Made multiprocessing optional again on implementations other than just Jython

- update to version 3.0.1:
  * Made Executor.map() non-greedy
- additional changes from version 3.0.0:
  * Dropped Python 2.5 and 3.1 support
  * Removed the deprecated "futures" top level package
  * Applied patch for issue 11777 (Executor.map does not submit
    futures until iter.next() is called)
  * Applied patch for issue 15015 (accessing an non-existing
    attribute)
  * Applied patch for issue 16284 (memory leak)
  * Applied patch for issue 20367 (behavior of
    concurrent.futures.as_completed() for duplicate arguments)
- remove CFLAGS: this is a python only module
- remove futures from package files: not provided anymore

- update to version 2.2.0:
  - Added the set_exception_info() and exception_info() methods to Future
    to enable extraction of tracebacks on Python 2.x
  - Added support for Future.set_exception_info() to ThreadPoolExecutor

- Updated to 2.1.6
  - Fixed a problem with files missing from the source distribution
- Updated to 2.1.5
  - Fixed Jython compatibility
  - Added metadata for wheel support
- Updated to 2.1.4
  - Ported the library again from Python 3.2.5 to get the latest bug fixes

- license update: BSD-2-Clause
  See LICENSE file

- Initial version