Issue1468

Failing to call close() delays the file being written while ant may
depend on the file being read. This is working correctly for python and jep.

<script language="jython" setbeans="false">
<![CDATA[
import os
os.remove('x')
f = open('x', 'w')
f.write('xyz')
#f.close()
]]>
</script>
<loadfile property="message" srcFile="x"/>
<echo message="${message}"/>
</target>

Can you please provide more context why this is a bug for Jython?

Implementations of languages providing garbage collection without ref 
counting do not provide immediate destruction upon a ref going out of 
scope. This can exhaust resources that are linked to objects, such as 
file resource, or leave them hanging until one or more phases of GC has 
run.

Instead it's necessary to ensure that the resource is closed as soon as 
possible. We recommend you use something like the following:

f = open(...)
try:
    do_something_with_it(f)
finally:
    f.close()

or alternatively

with open(...) as f:
    do_something_with_it(f)

I should have made this more clear:

If we are shipping code that doesn't do this close as indicated, we have 
a bug in Jython. We found a number of these in the standard library, or 
especially tests of the stdlib.

But if there's code in some third component that's not performing the 
close, it's a bug in that system.

Note too that the way to do this in Python implementations 2.5 and up is

from __future__ import with_statement
with open('x', 'w') as f:
    f.write('xyz')

AFAICT not a bug, closing out. Please reopen if there's another underlying 
issue involved