Paul Watson <[EMAIL PROTECTED]> writes: [...] > How "ill" will things be when large bodies of code cannot run > successfully on a future version of Python or a non-CPython > implementation which does not close files. Might as well put file > closing on exit into the specification. [...]
There are many, many ways of making a large body of code "ill". Closing off this particular one would make it harder to get benefit of non-C implementations of Python, so it has been judged "not worth it". I think I agree with that judgement. John -- http://mail.python.org/mailman/listinfo/python-list
