-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Franz Steinhaeusler wrote:
| Not really soo useful, because most syntax and also indentation errors | are actually detected by invoking python, i.e. the command compile. | But as combination for this: yes why not. | I looked for Stanis spe editor, which uses a combination of these two.
Just because Python compiles and runs something does not mean that there are no indentation errors. tabnanny works great because it removes all ambiguous cases so you never have to worry about it. We use it as part of our test suite to guard against misconfigured editors.
(again using '.' instead of space) Why would you want to allow '.\tprint foo' in Python source when you could clean it up to be the totally unambigous '........print foo'. As a more rational example, would you want to allow '....\tprint foo', which will totally confuse someone with their editor misconfigured with 4 char tabs?
- -- Stuart Bishop <[EMAIL PROTECTED]> http://www.stuartbishop.net/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFByp4nAfqZj7rGN0oRAoq9AJ4scAe0A3aFnx7jRZuqtRXXaxAcRgCfYkVf FbH2HBFA4/44KgZfpiPuvNU= =nyQt -----END PGP SIGNATURE----- -- http://mail.python.org/mailman/listinfo/python-list
