kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/py-Pyro/PLIST

83 lines
3 KiB
Text
Raw Normal View History

py-Pyro: updated to 4.74 Pyro 4.74 - serpent 1.27 required to avoid regression in previous version - fixed marshal serializer problem that prevented it to even call register() in the name server. Its dumpsCall is now able to use the class_to_dict conversion for unmarshallable types (in simple situations, not recursively). Previously, you would get a ValueError: unmarshallable object. - msgpack, json and marshal serializers now understand how to serialize array.array the same way serpent already did Pyro 4.73 - include LICENSE file in distribution - avoid decode error when dealing with memoryview annotations 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. 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 Pyro 4.70 - bump to version 4.70 to emphasize the following change: - 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.
2018-12-16 15:33:24 +01:00
@comment $NetBSD: PLIST,v 1.8 2018/12/16 14:33:24 adam Exp $
bin/pyro4-check-config-${PYVERSSUFFIX}
bin/pyro4-flameserver-${PYVERSSUFFIX}
bin/pyro4-httpgateway-${PYVERSSUFFIX}
bin/pyro4-ns-${PYVERSSUFFIX}
bin/pyro4-nsc-${PYVERSSUFFIX}
bin/pyro4-test-echoserver-${PYVERSSUFFIX}
update to 4.12 This is a complete rewrite.
2012-02-17 19:32:57 +01:00
${PYSITELIB}/${EGG_INFODIR}/PKG-INFO
${PYSITELIB}/${EGG_INFODIR}/SOURCES.txt
${PYSITELIB}/${EGG_INFODIR}/dependency_links.txt
py-Pyro: update to 4.62 Pyro 4.62: major new feature: SSL/TLS support added - a handful of new config items (‘SSL’ prefixed), supports server-only certificate and also 2-way-ssl (server+client certificates). For testing purposes, self-signed server and client certificates are available in the ‘certs’ directory. SSL/TLS in Pyro is supported on Python 2.7.11+ or Python 3.4.4+ (these versions have various important security related changes such as disabling vulnerable cyphers or protocols by default) added SSL example that shows how to configure 2-way-SSL in Pyro and how to do certificate verification on both sides. added cloudpickle serialization support (https://github.com/cloudpipe/cloudpickle/) added a small extended-pickle example that shows what dill and cloudpickle can do (send actual functions) daemon is now more resilient to exceptions occurring with socket communications (it logs them but is otherwise not interrupted) (this was required to avoid errors occurring in the SSL layer stopping the server) some small bugs fixed (crash when logging certain errors in thread server, invalid protected members showing up on pypy3) the raise data line in a traceback coming from Pyro now has a comment after it, telling you that you probably should inspect the remote traceback as well. note: if you’re using Python 3 only and are interested in a modernized version of Pyro, have a look at Pyro5: https://github.com/irmen/Pyro5 It’s experimental work in progress, but it works pretty well. note: Pyro4 is reaching a state where I consider it “feature complete”: I’m considering not adding more new features but only doing bug-fixes. New features (if any) will then appear only in Pyro5.
2017-10-08 12:21:57 +02:00
${PYSITELIB}/${EGG_INFODIR}/entry_points.txt
update to 4.22 changes: -added IPv6 support -added Python3 support -bugfixes
2013-12-04 17:41:01 +01:00
${PYSITELIB}/${EGG_INFODIR}/requires.txt
update to 4.12 This is a complete rewrite.
2012-02-17 19:32:57 +01:00
${PYSITELIB}/${EGG_INFODIR}/top_level.txt
${PYSITELIB}/Pyro4/__init__.py
${PYSITELIB}/Pyro4/__init__.pyc
${PYSITELIB}/Pyro4/__init__.pyo
${PYSITELIB}/Pyro4/configuration.py
${PYSITELIB}/Pyro4/configuration.pyc
${PYSITELIB}/Pyro4/configuration.pyo
${PYSITELIB}/Pyro4/constants.py
${PYSITELIB}/Pyro4/constants.pyc
${PYSITELIB}/Pyro4/constants.pyo
${PYSITELIB}/Pyro4/core.py
${PYSITELIB}/Pyro4/core.pyc
${PYSITELIB}/Pyro4/core.pyo
${PYSITELIB}/Pyro4/errors.py
${PYSITELIB}/Pyro4/errors.pyc
${PYSITELIB}/Pyro4/errors.pyo
update to 4.22 changes: -added IPv6 support -added Python3 support -bugfixes
2013-12-04 17:41:01 +01:00
${PYSITELIB}/Pyro4/futures.py
${PYSITELIB}/Pyro4/futures.pyc
${PYSITELIB}/Pyro4/futures.pyo
${PYSITELIB}/Pyro4/message.py
${PYSITELIB}/Pyro4/message.pyc
${PYSITELIB}/Pyro4/message.pyo
update to 4.12 This is a complete rewrite.
2012-02-17 19:32:57 +01:00
${PYSITELIB}/Pyro4/naming.py
${PYSITELIB}/Pyro4/naming.pyc
${PYSITELIB}/Pyro4/naming.pyo
py-Pyro: update to 4.62 Pyro 4.62: major new feature: SSL/TLS support added - a handful of new config items (‘SSL’ prefixed), supports server-only certificate and also 2-way-ssl (server+client certificates). For testing purposes, self-signed server and client certificates are available in the ‘certs’ directory. SSL/TLS in Pyro is supported on Python 2.7.11+ or Python 3.4.4+ (these versions have various important security related changes such as disabling vulnerable cyphers or protocols by default) added SSL example that shows how to configure 2-way-SSL in Pyro and how to do certificate verification on both sides. added cloudpickle serialization support (https://github.com/cloudpipe/cloudpickle/) added a small extended-pickle example that shows what dill and cloudpickle can do (send actual functions) daemon is now more resilient to exceptions occurring with socket communications (it logs them but is otherwise not interrupted) (this was required to avoid errors occurring in the SSL layer stopping the server) some small bugs fixed (crash when logging certain errors in thread server, invalid protected members showing up on pypy3) the raise data line in a traceback coming from Pyro now has a comment after it, telling you that you probably should inspect the remote traceback as well. note: if you’re using Python 3 only and are interested in a modernized version of Pyro, have a look at Pyro5: https://github.com/irmen/Pyro5 It’s experimental work in progress, but it works pretty well. note: Pyro4 is reaching a state where I consider it “feature complete”: I’m considering not adding more new features but only doing bug-fixes. New features (if any) will then appear only in Pyro5.
2017-10-08 12:21:57 +02:00
${PYSITELIB}/Pyro4/naming_storage.py
${PYSITELIB}/Pyro4/naming_storage.pyc
${PYSITELIB}/Pyro4/naming_storage.pyo
update to 4.12 This is a complete rewrite.
2012-02-17 19:32:57 +01:00
${PYSITELIB}/Pyro4/nsc.py
${PYSITELIB}/Pyro4/nsc.pyc
${PYSITELIB}/Pyro4/nsc.pyo
${PYSITELIB}/Pyro4/socketserver/__init__.py
${PYSITELIB}/Pyro4/socketserver/__init__.pyc
${PYSITELIB}/Pyro4/socketserver/__init__.pyo
py-Pyro: updated to 4.74 Pyro 4.74 - serpent 1.27 required to avoid regression in previous version - fixed marshal serializer problem that prevented it to even call register() in the name server. Its dumpsCall is now able to use the class_to_dict conversion for unmarshallable types (in simple situations, not recursively). Previously, you would get a ValueError: unmarshallable object. - msgpack, json and marshal serializers now understand how to serialize array.array the same way serpent already did Pyro 4.73 - include LICENSE file in distribution - avoid decode error when dealing with memoryview annotations 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. 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 Pyro 4.70 - bump to version 4.70 to emphasize the following change: - 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.
2018-12-16 15:33:24 +01:00
${PYSITELIB}/Pyro4/socketserver/existingconnectionserver.py
${PYSITELIB}/Pyro4/socketserver/existingconnectionserver.pyc
${PYSITELIB}/Pyro4/socketserver/existingconnectionserver.pyo
update to 4.12 This is a complete rewrite.
2012-02-17 19:32:57 +01:00
${PYSITELIB}/Pyro4/socketserver/multiplexserver.py
${PYSITELIB}/Pyro4/socketserver/multiplexserver.pyc
${PYSITELIB}/Pyro4/socketserver/multiplexserver.pyo
py-Pyro: update to 4.62 Pyro 4.62: major new feature: SSL/TLS support added - a handful of new config items (‘SSL’ prefixed), supports server-only certificate and also 2-way-ssl (server+client certificates). For testing purposes, self-signed server and client certificates are available in the ‘certs’ directory. SSL/TLS in Pyro is supported on Python 2.7.11+ or Python 3.4.4+ (these versions have various important security related changes such as disabling vulnerable cyphers or protocols by default) added SSL example that shows how to configure 2-way-SSL in Pyro and how to do certificate verification on both sides. added cloudpickle serialization support (https://github.com/cloudpipe/cloudpickle/) added a small extended-pickle example that shows what dill and cloudpickle can do (send actual functions) daemon is now more resilient to exceptions occurring with socket communications (it logs them but is otherwise not interrupted) (this was required to avoid errors occurring in the SSL layer stopping the server) some small bugs fixed (crash when logging certain errors in thread server, invalid protected members showing up on pypy3) the raise data line in a traceback coming from Pyro now has a comment after it, telling you that you probably should inspect the remote traceback as well. note: if you’re using Python 3 only and are interested in a modernized version of Pyro, have a look at Pyro5: https://github.com/irmen/Pyro5 It’s experimental work in progress, but it works pretty well. note: Pyro4 is reaching a state where I consider it “feature complete”: I’m considering not adding more new features but only doing bug-fixes. New features (if any) will then appear only in Pyro5.
2017-10-08 12:21:57 +02:00
${PYSITELIB}/Pyro4/socketserver/threadpool.py
${PYSITELIB}/Pyro4/socketserver/threadpool.pyc
${PYSITELIB}/Pyro4/socketserver/threadpool.pyo
update to 4.12 This is a complete rewrite.
2012-02-17 19:32:57 +01:00
${PYSITELIB}/Pyro4/socketserver/threadpoolserver.py
${PYSITELIB}/Pyro4/socketserver/threadpoolserver.pyc
${PYSITELIB}/Pyro4/socketserver/threadpoolserver.pyo
${PYSITELIB}/Pyro4/socketutil.py
${PYSITELIB}/Pyro4/socketutil.pyc
${PYSITELIB}/Pyro4/socketutil.pyo
${PYSITELIB}/Pyro4/test/__init__.py
${PYSITELIB}/Pyro4/test/__init__.pyc
${PYSITELIB}/Pyro4/test/__init__.pyo
${PYSITELIB}/Pyro4/test/echoserver.py
${PYSITELIB}/Pyro4/test/echoserver.pyc
${PYSITELIB}/Pyro4/test/echoserver.pyo
${PYSITELIB}/Pyro4/util.py
${PYSITELIB}/Pyro4/util.pyc
${PYSITELIB}/Pyro4/util.pyo
${PYSITELIB}/Pyro4/utils/__init__.py
${PYSITELIB}/Pyro4/utils/__init__.pyc
${PYSITELIB}/Pyro4/utils/__init__.pyo
${PYSITELIB}/Pyro4/utils/flame.py
${PYSITELIB}/Pyro4/utils/flame.pyc
${PYSITELIB}/Pyro4/utils/flame.pyo
${PYSITELIB}/Pyro4/utils/flameserver.py
${PYSITELIB}/Pyro4/utils/flameserver.pyc
${PYSITELIB}/Pyro4/utils/flameserver.pyo
py-Pyro: update to 4.62 Pyro 4.62: major new feature: SSL/TLS support added - a handful of new config items (‘SSL’ prefixed), supports server-only certificate and also 2-way-ssl (server+client certificates). For testing purposes, self-signed server and client certificates are available in the ‘certs’ directory. SSL/TLS in Pyro is supported on Python 2.7.11+ or Python 3.4.4+ (these versions have various important security related changes such as disabling vulnerable cyphers or protocols by default) added SSL example that shows how to configure 2-way-SSL in Pyro and how to do certificate verification on both sides. added cloudpickle serialization support (https://github.com/cloudpipe/cloudpickle/) added a small extended-pickle example that shows what dill and cloudpickle can do (send actual functions) daemon is now more resilient to exceptions occurring with socket communications (it logs them but is otherwise not interrupted) (this was required to avoid errors occurring in the SSL layer stopping the server) some small bugs fixed (crash when logging certain errors in thread server, invalid protected members showing up on pypy3) the raise data line in a traceback coming from Pyro now has a comment after it, telling you that you probably should inspect the remote traceback as well. note: if you’re using Python 3 only and are interested in a modernized version of Pyro, have a look at Pyro5: https://github.com/irmen/Pyro5 It’s experimental work in progress, but it works pretty well. note: Pyro4 is reaching a state where I consider it “feature complete”: I’m considering not adding more new features but only doing bug-fixes. New features (if any) will then appear only in Pyro5.
2017-10-08 12:21:57 +02:00
${PYSITELIB}/Pyro4/utils/httpgateway.py
${PYSITELIB}/Pyro4/utils/httpgateway.pyc
${PYSITELIB}/Pyro4/utils/httpgateway.pyo
Reference in a new issue Copy permalink