| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
|
|
| |
Also needed for bug 448730
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
|
|
| |
Also needed for bug 448730
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux x86_64, signed Manifest commit with key 0x2471eb3e40ac5ac3)
|
|
|
|
| |
(Portage version: 2.1.11.38/cvs/Linux ia64, signed Manifest commit with key F6AD3240)
|
|
|
|
| |
(Portage version: 2.1.11.38/cvs/Linux ia64, signed Manifest commit with key F6AD3240)
|
|
|
|
| |
(Portage version: 2.1.11.38/cvs/Linux ia64, signed Manifest commit with key F6AD3240)
|
|
|
|
| |
(Portage version: 2.1.11.38/cvs/Linux ia64, signed Manifest commit with key F6AD3240)
|
|
|
|
| |
(Portage version: 2.1.11.38/cvs/Linux ia64, signed Manifest commit with key F6AD3240)
|
|
|
|
| |
(Portage version: 2.1.11.38/cvs/Linux ia64, signed Manifest commit with key F6AD3240)
|
|
|
|
|
|
| |
for discovering this issue
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, unsigned Manifest commit)
|
|
|
|
|
|
| |
for discovering this issue
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 8009D6F070EB7916)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 8009D6F070EB7916)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 0x981CA6FC)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 0x981CA6FC)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
|
|
| |
with pyside: rename assistant to help, add script and scripttools (bug 431460 by Arfrever).
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
|
|
| |
with pyside: rename assistant to help, add script and scripttools (bug 431460 by Arfrever).
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 17A85C72)
|
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux ia64, unsigned Manifest commit)
|
|
|
|
| |
(Portage version: 2.1.11.31/cvs/Linux ia64, unsigned Manifest commit)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
(Portage version: 2.1.11.38/cvs/Linux x86_64, signed Manifest commit with key E1DBFAB5)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
(Portage version: 2.1.11.38/cvs/Linux x86_64, signed Manifest commit with key E1DBFAB5)
|
| |
|
| |
|
| |
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 0BBEEA1FEA4843A4)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 0BBEEA1FEA4843A4)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 42B9401D)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux x86_64, signed Manifest commit with key 42B9401D)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux i686, signed Manifest commit with key 0xFDE8EF85AE5719A3)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux i686, signed Manifest commit with key 0xFDE8EF85AE5719A3)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux i686, signed Manifest commit with key 23E9E900)
|
|
|
|
| |
(Portage version: 2.2.0_alpha149/cvs/Linux i686, signed Manifest commit with key 23E9E900)
|
|
|
|
| |
(Portage version: 2.1.11.38/cvs/Linux x86_64, signed Manifest commit with key 072AD062)
|
|
|
|
| |
(Portage version: 2.1.11.38/cvs/Linux x86_64, signed Manifest commit with key 072AD062)
|