./net/py-rpyc, Remote Python Call (RPyC), a transparent and symmetric RPC library

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]


Branch: CURRENT, Version: 4.1.2, Package name: py37-rpyc-4.1.2, Maintainer: gde

RPyC (pronounced like are-pie-see), or Remote Python Call, is a transparent
library for symmetrical remote procedure calls, clustering and
distributed-computing.

RPyC makes use of object-proxying, a technique that employs python's dynamic
nature, to overcome the physical boundaries between processes and computers,
so that remote objects can be manipulated as if they were local.


Master sites:

SHA1: 26992eb85c0fcafddcd6ff5cc0f9d7c133004471
RMD160: 3fc87a125fa39a9eb48a0b870ed1cd0604e9537e
Filesize: 55.452 KB

Version history: (Expand)


CVS history: (Expand)


   2020-09-30 02:38:48 by Pierre Pronchery | Files touched by this commit (2) | Package updated
Log message:
py-rpyc: update to version 4.1.2

Release RPyC 4.1.2:

 * Fixed CVE-2019-16328 which was caused by a missing protocol security check.
 * Fixed RPyC over RPyC for mutable parameters and extended unit testing for #346

Release RPyC 4.1.1:

 * Fixed netref.class_factory id_pack usage per #339 and added test cases
 * Name pack casted in _unbox to fix IronPython bug. Fixed #337
 * Increased chunk size to improve multi-client response time and throughput of \ 
large data #329
 * Added warning to _remote_tb when the major version of local and remote \ 
mismatch (#332)
 * OneShotServer termination was fixed by WilliamBruneau (#343)

Release RPyC 4.1.0:

 * Added connection back-off and attempts for congested workloads
 * Fixed minor resource leak for ForkingServer
 * Cross-connection instance check for cached netref classes

Note:

 * Requests/replies are not compatible between >=4.1.0 and earlier versions
   2020-09-30 01:11:52 by Pierre Pronchery | Files touched by this commit (3) | Package updated
Log message:
py-rpyc: update to version 4.0.2

Release rpyc 4.0.2
- fix default hostname for ipv6 in rpyc_classic.py (#277)
- fix ThreadPoolServer not working

Release rpyc 4.0.1
- fix ValueError during install due to absolute PATH in SOURCES.txt (`#276`_)

Release rpyc 4.0.0
This release brings a few minor backward incompatibilities, so be sure to read
on before upgrading. However, fear not: the ones that are most likely relevant
to you have a relatively simple migration path.
   2020-09-30 00:58:36 by Pierre Pronchery | Files touched by this commit (3) | Package updated
Log message:
py-rpyc: update to version 3.4.4

Release rpyc 3.4.4
- Fix refcount leakage when unboxing from cache (#196)
- Fix TypeError when dispatching exceptions on py2 (unicode)
- Respect ``rpyc_protocol_config`` for default Service getattr (#202)
- Support unix domain sockets (#100,#208)
- Use first accessible server in ``connect_by_service`` (#220)
- Fix deadlock problem with logging (#207,#212)

Release rpyc 3.4.3
- Add missing endpoints config in ThreadPoolServer (#222)
- Fix jython support (#156,#171)
- Improve documentation (#158,#185,#189,#198 and more)
   2020-09-30 00:54:13 by Pierre Pronchery | Files touched by this commit (1)
Log message:
py-rpyc: remove TODO file with reference to CVE-2019-16328

After verification, the version shipped in this package does not seem to be
vulnerable to the CVE entry referenced there (or to have been in any version
packaged in pkgsrc).

Thanks leot@ for the heads up!
   2020-09-30 00:49:46 by Pierre Pronchery | Files touched by this commit (3) | Package updated
Log message:
py-rpyc: update to version 3.4.2

Release RPyC 3.4.2:
* Fix ``export_function`` on python 3.6

Release rpyc 3.4.1:
* Fix issue high-cpu polling (#191,#218)
* Fix filename argument in logging (#197)
* Improved log messages (#191,#204)
* Drop support for python 3.2 and py 2.5
   2020-09-29 04:29:08 by Pierre Pronchery | Files touched by this commit (5)
Log message:
py-rpyc: import version 3.3.0

RPyC (pronounced like are-pie-see), or Remote Python Call, is a transparent
library for symmetrical remote procedure calls, clustering and
distributed-computing.

RPyC makes use of object-proxying, a technique that employs python's dynamic
nature, to overcome the physical boundaries between processes and computers,
so that remote objects can be manipulated as if they were local.