[Python-Dev] Stdlib Logging questions (PEP 337 SoC) (original) (raw)
Jeremy Hylton jeremy at alum.mit.edu
Tue Jun 6 16:36:59 CEST 2006
- Previous message: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)
- Next message: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/6/06, Fredrik Lundh <fredrik at pythonware.com> wrote:
Jim Jewett wrote:
> For pkgutil in particular, the change is that instead of writing to > stderr (which can scroll off and get lost), it will write to the > errorlog. In a truly default setup, that still ends up writing to > stderr. umm. if pkgutil fails to open a pkg file, isn't it rather likely that the program will terminate with an ImportError a few milliseconds later?
Maybe a mean time of a few milliseconds later. It really depends on the operating system's scheduler. If the failure occurs just at the end of a scheduler quantum, the process may not run again for some time. This would happen regardless of whether the operating system was modern.
Jeremy
- Previous message: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)
- Next message: [Python-Dev] Stdlib Logging questions (PEP 337 SoC)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]