| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NEWS
~~~~
- Pyro4.test.echoserver now correctly runs the NS’s broadcast server as well
- unix domain socket creation no longer fails when bind or connect address is
unicode instead of str
- docs: added more info on dealing with new serialization configuration in
existing code
- docs: improved name server documentation on registering objects
- docs: various small updates
Package-Manager: portage-2.2.8-r1/cvs/Linux x86_64
Manifest-Sign-Key: 0xF0134531E1DBFAB5
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.7/cvs/Linux x86_64
RepoMan-Options: --include-arches="ppc"
Manifest-Sign-Key: 0x7194459F
|
|
|
|
|
| |
Package-Manager: portage-2.2.8/cvs/Linux x86_64
Manifest-Sign-Key: 0xA188FBD4
|
|
|
|
|
| |
Package-Manager: portage-2.2.7/cvs/Linux x86_64
Manifest-Sign-Key: 0xF0134531E1DBFAB5
|
|
|
|
|
| |
Package-Manager: portage-2.2.7/cvs/Linux x86_64
Manifest-Sign-Key: 0xF0134531E1DBFAB5
|
|
|
|
|
|
|
| |
eclass.
Package-Manager: portage-2.2.7/cvs/Linux x86_64
Manifest-Sign-Key: 0xF0134531E1DBFAB5
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.7/cvs/Linux x86_64
RepoMan-Options: --include-arches="x86"
Manifest-Sign-Key: 0x7194459F
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.1/cvs/Linux ppc64
RepoMan-Options: --include-arches="ppc"
Manifest-Sign-Key: 0x7194459F
|
|
|
|
|
| |
Package-Manager: portage-2.2.7/cvs/Linux x86_64
Manifest-Sign-Key: 0x1F357D42
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
NEWS
~~~~
Pyro 4.22
- support added in daemon to accept multiple serializers in incoming messages
- new config item added for that: SERIALIZERS_ACCEPTED (defaults to ‘safe’
serializers)
- wire protocol header changed. Not backwards compatible! New protocol
version: 46.
- wire protocol: header now contains serializer used for the data payload
- wire protocol: header is extensible with optional ‘annotations’. One is
used for the HMAC digest that used to be in all messages even when the hmac
option wasn’t enabled.
- refactored core.MessageFactory: new submodule Pyro4.message. If you used
MessageFactory in your own code you’ll need to refactor it to use the new
Pyro4.message.Message API instead.
- disconnects example client code updated to reflect this API change
- you can now write the protocol in URIs in lowercase if you want
(“pyro:...”) (will still be converted to uppercase)
- fixed poll server loop() not handling self.clients which caused crashes
with a custom loopCondition
- fixed some unit test hang/timeout/crash issues
- improved unit tests for jython, disabled ipv6 tests for jython because of
too many issues.
- improved unit tests for ironpython.
Pyro 4.21
- fixed denial of service vulnerabilities in socket servers
- MSG_PING message type added (internal server ping mechanism)
- disconnects example added that uses MSG_PING
- more exception types recognised in the serializers (such as GeneratorExit)
- fixed async regression when dealing with errors (properly serialize
exceptionwrapper)
- fixed warehouse and stockmarket tutorials to work with new serializer logic
- fixed examples that didn’t yet work with new serializer logic
- fixed unit tests to use unittest2 on Python 2.6
- no longer supports jython 2.5. You’ll have to upgrade to jython 2.7.
- got rid of some byte/str handling cruft (because we no longer need to deal
with jython 2.5)
- implemented autoproxy support for serpent and json serializers. It is not
possible to do this for marshal.
- fixed serpent serialization problem with backslash escapes in unicode
strings (requires serpent >= 1.3)
Package-Manager: portage-2.2.7/cvs/Linux x86_64
Manifest-Sign-Key: 0xF0134531E1DBFAB5
|
|
|
|
|
| |
Package-Manager: portage-2.2.7/cvs/Linux x86_64
Manifest-Sign-Key: 0xF0134531E1DBFAB5
|
|
|
|
|
| |
Package-Manager: portage-2.2.1/cvs/Linux x86_64
Manifest-Sign-Key: 0xEFB4464E!
|
|
|
|
|
| |
Package-Manager: portage-2.2.1/cvs/Linux x86_64
Manifest-Sign-Key: 0xEFB4464E!
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.11/cvs/Linux x86_64
Manifest-Sign-Key: 0xF0134531E1DBFAB5
|
|
|
|
|
|
|
| |
aidecoe
Package-Manager: portage-2.1.11.63/cvs/Linux x86_64
Manifest-Sign-Key: 0xB8072B0D
|
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.2/cvs/Linux ppc64
RepoMan-Options: --include-arches="ppc"
Manifest-Sign-Key: 0x7194459F
|
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.9/cvs/Linux x86_64
RepoMan-Options: --include-arches="amd64"
Manifest-Sign-Key: 0x7194459F
|
|
|
|
|
|
| |
Package-Manager: portage-2.1.12.9/cvs/Linux x86_64
RepoMan-Options: --include-arches="x86"
Manifest-Sign-Key: 0x7194459F
|
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha177/cvs/Linux x86_64
Manifest-Sign-Key: 0x0BBEEA1FEA4843A4
|
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha176/cvs/Linux x86_64
Manifest-Sign-Key: 0x8009D6F070EB7916
|
|
|
|
|
| |
Package-Manager: portage-2.1.11.52/cvs/Linux x86_64
Manifest-Sign-Key: 0xF0134531E1DBFAB5
|
|
|
|
| |
Package-Manager: portage-2.1.11.31/cvs/Linux ppc64
|
|
|
|
| |
Package-Manager: portage-2.1.11.31/cvs/Linux x86_64
|
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha161/cvs/Linux i686
Manifest-Sign-Key: 0x23E9E900
|
|
|
|
|
|
|
| |
flameeyes.
Package-Manager: portage-2.1.11.50/cvs/Linux x86_64
Manifest-Sign-Key: 0xE1DBFAB5
|
|
|
|
|
|
|
| |
fixes Bug #454686 by flameeyes
Package-Manager: portage-2.1.11.40/cvs/Linux x86_64
Manifest-Sign-Key: 0xB8072B0D
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Pyro 4.17
- Fixed possible IndentationError problem with sending modules in Flame
- Can now deal with exceptions that can’t be serialized: they’re raised as
generic PyroError instead, with appropriate message
- Added new config item FLAME_ENABLED, to enable/disable the use of Pyro
Flame on the server. Default is false (disabled).
- Moved futures from core to new futures module. Code using Pyro4.Future will
still work.
- Added python version info to configuration dump
- Made it more clear in the manual that you need to have the same major
Python version on both sides
Pyro 4.16
- New implementation for the threadpool server: job queue with self-adjusting
number of workers. The workaround that was in place (fixed pool size) has
been removed.
- Minor api doc fix: corrected reference of Pyro4 package members
Pyro 4.15
- Minimum threadpool size increased to 20 (from 4) to give a bit more
breathing room while the threadpool scaling still needs to be fixed
- Binding a proxy will no longer release an existing connection first,
instead it will just do nothing if the proxy has already been bound to its
uri
- Resolved a race condition related to releasing and binding a proxy,
improved unit test
- Documentation contains new homepage link
- No longer gives a warning about version incompatibility on Jython 2.5
- Optimize bytecode flag no longer added in setup script when using jython,
this used to crash the setup.py install process on jython
- Fixed a gc issue due to a circular dependency
- IronPython: improved suggesting a free port number in
socketutil.findProbablyUnusedPort
- IronPython: threadpoolserver no longer attempts to join the worker threads
because not all threads seemed to actually exit on IronPython, thereby
hanging the process when shutting down a daemon.
- Added a paragraph to tips&tricks about MSG_WAITALL
- socket.MSG_WAITALL is no longer deleted by importing Pyro on systems that
have a broken MSG_WAITALL (Windows). You’ll have to check for this yourself
now, but I wanted to get rid of this side effect of importing Pyro.
Package-Manager: portage-2.1.11.38/cvs/Linux x86_64
Manifest-Sign-Key: 0xE1DBFAB5
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha115/cvs/Linux i686
|
|
|
|
| |
Package-Manager: portage-2.1.10.49/cvs/Linux i686
|
|
|
|
| |
Package-Manager: portage-2.1.10.49/cvs/Linux ppc64
|
|
|
|
| |
Package-Manager: portage-2.1.10.49/cvs/Linux ppc64
|
|
|
|
| |
Package-Manager: portage-2.1.10.64/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.10.63/cvs/Linux x86_64
|
|
|
|
|
|
| |
older version.
Package-Manager: portage-2.1.10.63/cvs/Linux x86_64
|
|
|
|
|
|
|
|
|
|
| |
This version comes with several bug fixes and one workaround for threadpool
scaling problem. I have restricted the test for this version because it fails
anyway because of the latest problem which is not fully solved:
FAIL: testPoolGrowth (PyroTests.test_threadpool.ThreadpoolTests)
Package-Manager: portage-2.1.10.63/cvs/Linux x86_64
|
|
|
|
|
|
| |
in the slot 4.
Package-Manager: portage-2.1.10.63/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.10.63/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.10.63/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.10.63/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.10.49/cvs/Linux ppc64
|
|
|
|
| |
Package-Manager: portage-2.1.10.49/cvs/Linux ppc64
|
|
|
|
| |
Package-Manager: portage-2.1.10.49/cvs/Linux i686
|
|
|
|
| |
Package-Manager: portage-2.1.10.49/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.1.10.60/cvs/Linux x86_64
|
|
|
|
|
|
|
|
|
|
|
| |
NEWS
~~~~
- connecting a proxy socket now also honors a timeout set by
proxy._setTimeout()
- fix setNoInherit on 64-bits Python on Windows (see
http://tech.oyster.com/cherrypy-ctypes-and-being-explicit/)
Package-Manager: portage-2.1.10.60/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha100/cvs/Linux x86_64
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha100/cvs/Linux x86_64
|
|
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha96/cvs/Linux i686
RepoMan-Options: --force
Manifest-Sign-Key: 0xAE5719A3
|
| |
|
|
|
|
| |
Package-Manager: portage-2.2.0_alpha90/cvs/Linux x86_64
|