execnet provides a share-nothing model with channel-send/receive communication
for distributing execution across many Python interpreters across version,
platform and network barriers. It has a minimal and fast API targetting the
following uses:
* Distribute tasks to (many) local or remote CPUs
* Write and deploy hybrid multi-process applications
* Write scripts to administer multiple environments
WWW: http://codespeak.net/execnet/
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
(Only the first 15 lines of the commit message are shown above )
[NEW] sysutils/py3-execnet: Create Python 3.x version of port
The latest www/py-requests update [1] unbundled its dependencies, now
requiring chardet, idna, urllib3 and certifi from ports.
www/py3-requests port was not tested during QA, which would have highlighted
the need for many new py3-* ports (and their dependencies).
This change creates one of those ports.
[1] https://svnweb.freebsd.org/changeset/ports/442565
PR: 219833
