For instance, running with -n:
Starting poppy-sftp.
0 <bound method FileLogObserver.emit of <twisted.python.log.FileLogObserver instance at 0xb347c8c>>
INFO:/tmp/poppy-access.log:---- Server started ----
^CINFO:/tmp/poppy-access.log:---- Server stopped ----
INFO:poppy-sftp.Hooks:Post-processing finished
This shows setStdOut gets 0, so doesn't override the stdout, stderr channels.
For instance, running with -n: .emit of <twisted. python. log.FileLogObse rver instance at 0xb347c8c>> poppy-access. log:--- - Server started ---- /tmp/poppy- access. log:--- - Server stopped ---- sftp.Hooks: Post-processing finished
Starting poppy-sftp.
0 <bound method FileLogObserver
INFO:/tmp/
^CINFO:
INFO:poppy-
This shows setStdOut gets 0, so doesn't override the stdout, stderr channels.
Without -n setStdOut still gets 0.
The setup happens from 'AppLogger.start()'
(Pdb) self._observerF actory getComponent( ILogObserver, None)
(Pdb) application.
so both the proscribed ways of getting a custom observer are failing.