relax SVN archive

The script print out in scripting mode is now in green if sys.stdout is a TTY.

Added isatty() methods to all of the dummy file objects within relax.

This fixes a number of errors caused by the recent introduction of coloured text.

ANSI escape characters are now turned off forcibly when in GUI mode.

The prompt.interpreter.Interpreter class was being initialised during the import startup phase due to
the gui.interpreter.Interpreter singleton class. This meant that sys.stdout had not been redirected
to the relax controller yet and was still set to the terminal TTY. This hack turns off the relax
prompt colouring forcibly.

Reverted r15756 as the status.text_colouring flag is no longer needed.

The command used was:
svn merge -r15756:r15755 .

.....
r15756 | bugman | 2012-04-17 16:33:03 +0200 (Tue, 17 Apr 2012) | 6 lines
Changed paths:
M /1.3/relax.py
M /1.3/status.py

Added a flag to the status singleton object to signal if text output can be coloured.

This is only activated when sys.stdout has not been changed. Unix redirection and pipes will need
to be handled later (http://mail.python.org/pipermail/python-list/2012-April/1291044.html).
.....

The sys.std*.isatty() methods are now being used to determine if text output should be coloured.

This removes the need for the status.text_colouring flag, and can handle changes in IO redirection
occurring at any point. This was suggested at both
http://mail.python.org/pipermail/python-list/2012-April/1291046.html and
http://mail.python.org/pipermail/python-list/2012-April/1291048.html.

Copyright update.

All RelaxWarnings are now coloured yellow if the status.text_colouring flag is set.

Though this looks more like orange on the Konsole terminal under GNU/Linux.

All RelaxErrors are now coloured red if the status.text_colouring flag is set.

If the status.text_colouring flag is set, then the relax prompts will be coloured blue!

Fix for the initialisation of the Exec_info class for the prompt/script output.

The class was not being initialised at all! Thought the variables were class rather than instance
variables, so the problem was hidden.