Hello community, here is the log from the commit of package python-Pyro4 for openSUSE:Factory checked in at 2018-06-02 12:07:20 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-Pyro4 (Old) and /work/SRC/openSUSE:Factory/.python-Pyro4.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-Pyro4" Sat Jun 2 12:07:20 2018 rev:1 rq:612083 version:4.72 Changes: -------- New Changes file: --- /dev/null 2018-05-30 11:41:29.140556178 +0200 +++ /work/SRC/openSUSE:Factory/.python-Pyro4.new/python-Pyro4.changes 2018-06-02 12:07:28.734265406 +0200 @@ -0,0 +1,39 @@ +------------------------------------------------------------------- +Thu May 24 17:39:16 UTC 2018 - toddrme2...@gmail.com + +- Update to Pyro 4.72 + * (source files: normalized line endings to LF) + * the -k command line option to supply a HMAC encryption key on the command line for the name server, nsc, + echoserver, flameserver and httpgateway tools is now deprecated (and will print a warning if used). + It is a security issue because the key used is plainly visible. + If you require proper security, use Pyro's 2-way SSL feature. Alternatively, set the HMAC key in the (new) environment + variable PYRO_HMAC_KEY if you still have to use it before launching the aforementioned tools. +- Update to Pyro 4.71 + * updated ``msgpack`` dependency (was ``msgpack-python`` but that name is now deprecated) + * fixed restart and force reload commands of the contrib/init.d/pyro4-nsd script, and changed its port binding + from 9999 back to 9090 which is Pyro's default. + * serpent 1.24 library now required to fix some api deprecation warnings when using Python 3.7 or newer. + * updated sphinx documentation theme +- Update to Pyro 4.70 + * **incompatible API change** for python 3.7 compatibility: renaming of ``async`` function and keyword arguments in the API: + Renamed ``Pyro4.core.async`` to ``Pyro4.core.asyncproxy`` (and its occurrence in ``Pyro4``) + and the ``async`` keyword argument in some methods to ``asynchronous``. + This had to be done because ``async`` (and ``await``) are now parsed as keywords in Python 3.7 and using them otherwise will result + in a SyntaxError when loading the module. + It is suggested you stop using the ``asyncproxy`` function and instead create asynchronous proxies using the ``_pyroAsync`` + method on the regular proxy. + * For existing code running on Python *older than 3.7*, a backwards compatibility feature is present to still provide the + ``async`` function and keyword arguments as they were supported on previous Pyro versions. + But also for that older environments, it's advised to migrate away from them and start using the new names. + * Proxy and Daemon have a new 'connected_socket' parameter. You can set it to a user-supplied connected socket that must + be used by them instead of creating a new socket for you. Connected sockets can be created using the socket.socketpair() + function for instance, and allow for easy and efficient communication over an internal socket between + parent-child processes or threads, using Pyro. Also see the new 'socketpair' example. + * dropped support for Python 3.3 (which has reached end-of-life status). Supported Python versions are now 2.7, and 3.4 or newer. + (the life cycle status of the Python versions can be seen here https://devguide.python.org/#status-of-python-branches) +- spec file cleanups + +------------------------------------------------------------------- +Wed Nov 8 20:42:14 UTC 2017 - toddrme2...@gmail.com + +- Initial version New: ---- Pyro4-4.72.tar.gz python-Pyro4.changes python-Pyro4.spec ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-Pyro4.spec ++++++ # # spec file for package python-Pyro4 # # Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ %{?!python_module:%define python_module() python-%{**} python3-%{**}} Name: python-Pyro4 Version: 4.72 Release: 0 License: MIT Summary: Distributed object middleware for Python (RPC) Url: https://github.com/irmen/Pyro4 Group: Development/Languages/Python Source: https://files.pythonhosted.org/packages/source/P/Pyro4/Pyro4-%{version}.tar.gz BuildRequires: %{python_module devel} BuildRequires: %{python_module setuptools} BuildRequires: fdupes BuildRequires: python-rpm-macros # SECTION test requirements BuildRequires: %{python_module cloudpickle >= 0.4.0} BuildRequires: %{python_module dill >= 0.2.6} BuildRequires: %{python_module msgpack-python >= 0.4.6} BuildRequires: %{python_module serpent >= 1.24} BuildRequires: ca-certificates BuildRequires: python-selectors34 # /SECTION Requires: python-serpent >= 1.24 Recommends: ca-certificates Recommends: python-cloudpickle >= 0.4.0 Recommends: python-dill >= 0.2.6 Recommends: python-msgpack-python >= 0.4.6 %ifpython2 Requires: python-selectors34 %endif BuildArch: noarch Requires(post): update-alternatives Requires(postun): update-alternatives %python_subpackages %description Pyro means PYthon Remote Objects. It is a library that enables you to build applications in which objects can talk to eachother over the network, with minimal programming effort. You can just use normal Python method calls, with almost every possible parameter and return value type, and Pyro takes care of locating the right object on the right computer to execute the method. It is designed to be very easy to use, and to generally stay out of your way. But it also provides a set of powerful features that enables you to build distributed applications rapidly and effortlessly. Pyro is a pure Python library and runs on many different platforms and Python versions. %prep %setup -q -n Pyro4-%{version} sed -i 's/\r$//' LICENSE %build %python_build %install %python_install %python_expand %fdupes %{buildroot}%{$python_sitelib} %python_clone -a %{buildroot}%{_bindir}/pyro4-check-config %python_clone -a %{buildroot}%{_bindir}/pyro4-flameserver %python_clone -a %{buildroot}%{_bindir}/pyro4-httpgateway %python_clone -a %{buildroot}%{_bindir}/pyro4-ns %python_clone -a %{buildroot}%{_bindir}/pyro4-nsc %python_clone -a %{buildroot}%{_bindir}/pyro4-test-echoserver %post %{python_install_alternative pyro4-check-config pyro4-flameserver pyro4-httpgateway pyro4-ns pyro4-nsc pyro4-test-echoserver} %postun %python_uninstall_alternative pyro4-check-config %files %{python_files} %license LICENSE %python_alternative %{_bindir}/pyro4-check-config %python_alternative %{_bindir}/pyro4-flameserver %python_alternative %{_bindir}/pyro4-httpgateway %python_alternative %{_bindir}/pyro4-ns %python_alternative %{_bindir}/pyro4-nsc %python_alternative %{_bindir}/pyro4-test-echoserver %{python_sitelib}/* %changelog
