new status output

[Martin Pool]

On 26/10/05, Aaron Bentley <aaron.bentley at utoronto.ca> wrote:

> At the risk of overengineering, maybe we should
> 1. add a Platform object to osutils.  It would have members describing
> the various platform features.
> 2. instantiate an osutils.platform global at import time (it's cheap)
> 3. provide equivalent-sematincs versions of all the functions that vary
> by platform.  (This is easier for us, because we only need specific
> semantics.  Ultimately don't care whether we create a hard link or copy
> a file, for example.)
> 4. override osutils.platform as needed.  (Run scripts/tests on Unix with
> osutils.platform=Win32Platform?)

Testing on Unix with Windows behaviour would be interesting, but it
might complicate things: we could print paths with backslashes, but
couldn't actually use them.  At any rate centralizing the platform
dependencies may be a good idea.

--
Martin