…patch-1Ensure file resources are released

This removes a comment noting that a try-finally block had beenpresent (or had been intended), but was removed because someversion of Python had imposed a limitation on yield appearing intry-finally.That comment was obsolete as of58c5b99 (gitpython-developers#326), which wrapped therelevant code in a with-statement, because:1. Since then, the cleanup is done in a manner equivaent to   try-finally.2. It turned out, as noted in that PR, that cleanup had not   always been done automatically. (This was contrary to the   prediction given in the comment.)3. At some point before that, the limitation that had prevented   the use of try-finally no longer affected any supported version   of Python.   Specifically, it appears the only limitation that this could be   was the limitation lifted in Python 2.5, where along with the   addition of the close() method which causes try-finally to be   called (and is itself called when a generator object is   finalized), yield in a try-block with an associated   finally-block became permitted, since the call to close() was   sufficient to run the finally-block (by raising GeneratorExit).   For details, see:https://docs.python.org/3/whatsnew/2.5.html#pep-342-new-generator-features(This obsolete comment was one of the things I discovered whileworking ongitpython-developers#1725, but I didn't include this change there, havingnot yet looked into the history of the code enough to be sure.)

This removes a comment noting that a try-finally block had beenpresent (or had been intended), but was removed because someversion of Python had imposed a limitation on yield appearing intry-finally.That comment was obsolete as of58c5b99 (gitpython-developers#326), which wrapped therelevant code in a with-statement, because:1. Since then, the cleanup is done in a manner equivaent to   try-finally.2. It turned out, as noted in that PR, that cleanup had not   always been done automatically. (This was contrary to the   prediction given in the comment.)3. At some point before that, the limitation that had prevented   the use of try-finally no longer affected any supported version   of Python.   Specifically, it appears the only limitation that this could be   was the limitation lifted in Python 2.5, where along with the   introduction of close(), which is automatically called when a   generator object is finalized, it became permitted for yield to   appear in a try-block with an associated finally-block, on the   grounds that calling close() runs the finally-block (by raising   GeneratorExit).   For details, see:https://docs.python.org/3/whatsnew/2.5.html#pep-342-new-generator-features(This obsolete comment was one of the things I discovered whileworking ongitpython-developers#1725, but I didn't include this change there, havingnot yet looked into the history of the code enough to be sure.)