away in the alpha 4 development cycle. |
away in the alpha 4 development cycle. |
|
|
- Added 'commands.lookupCommand()' to look up a command shortcut or URL, ala |
- Added 'commands.lookupCommand()' to look up a command shortcut or URL, ala |
the `peak` script or `commands.Bootstrap` class. Also added various |
the 'peak' script or 'commands.Bootstrap' class. Also added various |
`commands.ErrorSubcommand` subclasses to make it easier to issue errors |
'commands.ErrorSubcommand' subclasses to make it easier to issue errors |
from subcommands. |
from/for subcommands. |
|
|
- Added 'peak.core' as a minimal subset of 'peak.api'. 'peak.core' offers |
- Added 'peak.core' as a minimal subset of 'peak.api'. 'peak.core' offers |
only "core" API packages and primitives, not the full set of available |
only "core" API packages and primitives, not the full set of available |
- Added 'IMainLoop.setExitCode()' and 'IMainLoop.childForked()' methods, to |
- Added 'IMainLoop.setExitCode()' and 'IMainLoop.childForked()' methods, to |
allow reactor-driven components to control the mainloop's exit code. |
allow reactor-driven components to control the mainloop's exit code. |
|
|
- DEPRECATED 'peak.util.signal_stack'. Instead, bind to a |
- Added 'running.ISignalManager' and a default implementation. Use its |
'running.ISignalManager' and use its 'addHandler()/removeHandler()' methods. |
'addHandler()/removeHandler()' methods to add or remove signal handlers. |
This has the same effect as 'pushSignals()' and 'popSignals()', except that |
Signal handlers define methods like 'def SIGCHLD(self,signum,frame):' that |
you do not have to remove handlers in the same order as you add them, and |
will be called when the associated signal is received. All active handlers |
*all* active handlers are invoked for a given signal that they handle. |
for a given signal are invoked, so you can easily have multiple components |
|
listen for 'SIGCHLD', for example. |
|
|
- Added 'IBasicReactor.crash()', which forces an immediate reactor loop exit, |
- Added 'IBasicReactor.crash()', which forces an immediate reactor loop exit, |
ignoring pending scheduled calls. |
ignoring pending scheduled calls. |
instead of 'PropertySet' instances. |
instead of 'PropertySet' instances. |
|
|
- DEPRECATED the 'config.PropertySet' class; please convert to using |
- DEPRECATED the 'config.PropertySet' class; please convert to using |
'config.Namespace', as it will disappear in the 0.5alpha4 release cycle. |
'config.Namespace', as 'PropertySet' will disappear in the 0.5alpha4 release |
|
cycle. |
|
|
- SQL connection objects now get their type converters from a distinct |
- SQL connection objects now get their type converters from a distinct |
property namespace for each DBAPI driver. For example a driver using the |
property namespace for each DBAPI driver. For example a driver using the |
'naming.IBasicContext', which does something very different. |
'naming.IBasicContext', which does something very different. |
|
|
- 'binding.Obtain()' (formerly 'binding.bindTo()' and 'binding.bindSequence()') |
- 'binding.Obtain()' (formerly 'binding.bindTo()' and 'binding.bindSequence()') |
now pre-adapt their arguments to 'IComponentKey', to speed lookups at |
now pre-adapt their arguments to 'IComponentKey', to speed up lookups at |
runtime, and to ensure that errors due to an unusable parameter type occur |
runtime, and to ensure that errors due to an unusable parameter type occur |
at class creation time instead of waiting until lookup time. |
at class creation time instead of waiting until lookup time. |
|
|
property ('peak.running.reactor.checkInterval') to determine how long it |
property ('peak.running.reactor.checkInterval') to determine how long it |
should run 'select()' calls for, when there are no scheduled tasks. |
should run 'select()' calls for, when there are no scheduled tasks. |
|
|
- 'peak.running.scheduler.UntwistedReactor' now supports using a "signal |
- 'peak.running.scheduler.MainLoop' now supports using a "signal |
manager" component (via the 'peak.running.signalManager' property) to |
handler" component (via the 'peak.running.mainLoop.signalHandler' property) |
process signals while a 'run()' loop is in progress. Signal managers can |
to process signals while a 'run()' loop is in progress. Signal handlers can |
also be added or removed at any time via the new 'peak.util.signal_stack' |
also be added or removed at any time via the 'running.ISignalManager' |
module. |
service. |
|
|
- 'peak.running.commands.AbstractCommand' now offers a '_run()' method that |
- 'peak.running.commands.AbstractCommand' now offers a '_run()' method that |
can be overridden in subclasses, instead of 'run()'. If you override the |
can be overridden in subclasses, instead of 'run()'. If you override the |