|
|
@ -9,15 +9,13 @@
|
|
|
|
%global srcname execnet
|
|
|
|
%global srcname execnet
|
|
|
|
|
|
|
|
|
|
|
|
Name: python-%{srcname}
|
|
|
|
Name: python-%{srcname}
|
|
|
|
Version: 1.0.9
|
|
|
|
Version: 1.1
|
|
|
|
Release: 3%{?dist}
|
|
|
|
Release: 1%{?dist}
|
|
|
|
Summary: Elastic Python Deployment
|
|
|
|
Summary: Elastic Python Deployment
|
|
|
|
Group: Development/Languages
|
|
|
|
Group: Development/Languages
|
|
|
|
License: GPLv2+ and MIT
|
|
|
|
License: GPLv2+ and MIT
|
|
|
|
URL: http://codespeak.net/execnet
|
|
|
|
URL: http://codespeak.net/execnet
|
|
|
|
Source0: http://pypi.python.org/packages/source/e/%{srcname}/%{srcname}-%{version}.zip
|
|
|
|
Source0: http://pypi.python.org/packages/source/e/%{srcname}/%{srcname}-%{version}.zip
|
|
|
|
# upstream changeset 1a63deea3424
|
|
|
|
|
|
|
|
Patch0: execnet-debugfilename.patch
|
|
|
|
|
|
|
|
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
|
|
|
|
BuildRoot: %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)
|
|
|
|
BuildArch: noarch
|
|
|
|
BuildArch: noarch
|
|
|
|
BuildRequires: python-devel
|
|
|
|
BuildRequires: python-devel
|
|
|
@ -36,16 +34,14 @@ Conflicts: python-py < 1.1.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
%description
|
|
|
|
%description
|
|
|
|
The execnet package allows to:
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
|
|
|
* instantiate local/remote Python Interpreters
|
|
|
|
* distribute tasks to (many) local or remote CPUs
|
|
|
|
* send code for execution to one or many Interpreters
|
|
|
|
* write and deploy hybrid multi-process applications
|
|
|
|
* send and receive data between codeInterpreters through channels
|
|
|
|
* write scripts to administer multiple environments
|
|
|
|
|
|
|
|
|
|
|
|
execnet performs zero-install bootstrapping into other interpreters;
|
|
|
|
|
|
|
|
package installation is only required at the initiating side. execnet
|
|
|
|
|
|
|
|
enables interoperation between CPython 2.4-3.1, Jython 2.5 and PyPy
|
|
|
|
|
|
|
|
1.1 and works well on Windows, Linux and OSX systems.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
%if 0%{?with_python3}
|
|
|
|
%if 0%{?with_python3}
|
|
|
@ -56,22 +52,19 @@ Requires: python3-setuptools
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
%description -n python3-execnet
|
|
|
|
%description -n python3-execnet
|
|
|
|
The execnet package allows to:
|
|
|
|
execnet provides a share-nothing model with channel-send/receive
|
|
|
|
|
|
|
|
communication for distributing execution across many Python
|
|
|
|
* instantiate local/remote Python Interpreters
|
|
|
|
interpreters across version, platform and network barriers. It has a
|
|
|
|
* send code for execution to one or many Interpreters
|
|
|
|
minimal and fast API targetting the following uses:
|
|
|
|
* send and receive data between codeInterpreters through channels
|
|
|
|
|
|
|
|
|
|
|
|
* distribute tasks to (many) local or remote CPUs
|
|
|
|
execnet performs zero-install bootstrapping into other interpreters;
|
|
|
|
* write and deploy hybrid multi-process applications
|
|
|
|
package installation is only required at the initiating side. execnet
|
|
|
|
* write scripts to administer multiple environments
|
|
|
|
enables interoperation between CPython 2.4-3.1, Jython 2.5 and PyPy
|
|
|
|
|
|
|
|
1.1 and works well on Windows, Linux and OSX systems.
|
|
|
|
|
|
|
|
%endif # with_python3
|
|
|
|
%endif # with_python3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
%prep
|
|
|
|
%prep
|
|
|
|
%setup -q -n %{srcname}-%{version}
|
|
|
|
%setup -q -n %{srcname}-%{version}
|
|
|
|
%patch0 -p1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
# remove shebangs and fix permissions
|
|
|
|
# remove shebangs and fix permissions
|
|
|
|
find . -type f -a \( -name '*.py' -o -name 'py.*' \) \
|
|
|
|
find . -type f -a \( -name '*.py' -o -name 'py.*' \) \
|
|
|
@ -112,8 +105,7 @@ rm doc/_build/html/.buildinfo
|
|
|
|
PYTHONPATH=$(pwd) py.test-%{python_version} -r s
|
|
|
|
PYTHONPATH=$(pwd) py.test-%{python_version} -r s
|
|
|
|
%if 0%{?with_python3}
|
|
|
|
%if 0%{?with_python3}
|
|
|
|
pushd %{py3dir}
|
|
|
|
pushd %{py3dir}
|
|
|
|
# see http://bugs.python.org/issue12591
|
|
|
|
PYTHONPATH=$(pwd) py.test-%{python3_version} -r s
|
|
|
|
PYTHONPATH=$(pwd) py.test-%{python3_version} -r s -k-test_subprocess_interaction
|
|
|
|
|
|
|
|
popd
|
|
|
|
popd
|
|
|
|
%endif # with_python3
|
|
|
|
%endif # with_python3
|
|
|
|
|
|
|
|
|
|
|
@ -139,6 +131,11 @@ rm -rf %{buildroot}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
%changelog
|
|
|
|
%changelog
|
|
|
|
|
|
|
|
* Fri Jun 22 2012 Thomas Moschny <thomas.moschny@gmx.de> - 1.1-1
|
|
|
|
|
|
|
|
- Update to 1.1.
|
|
|
|
|
|
|
|
- Update description.
|
|
|
|
|
|
|
|
- Remove patch applied upstream.
|
|
|
|
|
|
|
|
|
|
|
|
* Tue Jan 17 2012 Thomas Moschny <thomas.moschny@gmx.de> - 1.0.9-3
|
|
|
|
* Tue Jan 17 2012 Thomas Moschny <thomas.moschny@gmx.de> - 1.0.9-3
|
|
|
|
- Add upstream patch for failing test.
|
|
|
|
- Add upstream patch for failing test.
|
|
|
|
|
|
|
|
|
|
|
|