This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nadeem.vawda
Recipients nadeem.vawda, orsenthil, python-dev, vstinner
Date 2011-07-06.00:20:42
SpamBayes Score 7.71264e-06
Marked as misclassified No
Message-id <1309911643.92.0.461432010165.issue10883@psf.upfronthosting.co.za>
In-reply-to
Content
The problem seems to be that CacheFTPHandler inherits ftp_open() from
FTPHandler - FTPHandler.ftp_open() marks the ftpwrapper object to be closed as
soon as the current transfer is complete. So CacheFTPHandler's cache ends up
full of closed ftpwrappers. I don't have time to put together a solution now,
but I'll work on something over the weekend.

Another thing: CacheFTPHandler.clear_cache() sometimes breaks the cache,
because it fails to clear self.timeout. Is there any reason why the timeouts
need to be in a separate dict from the cached connections themselves? It seems
like a very ugly and error-prone way of organizing things.
History
Date User Action Args
2011-07-06 00:20:43nadeem.vawdasetrecipients: + nadeem.vawda, orsenthil, vstinner, python-dev
2011-07-06 00:20:43nadeem.vawdasetmessageid: <1309911643.92.0.461432010165.issue10883@psf.upfronthosting.co.za>
2011-07-06 00:20:43nadeem.vawdalinkissue10883 messages
2011-07-06 00:20:42nadeem.vawdacreate