Message139912
| Author |
nadeem.vawda |
| Recipients |
nadeem.vawda, orsenthil, python-dev, vstinner |
| Date |
2011年07月06日.00:20:42 |
| SpamBayes Score |
7.712642e-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:43 | nadeem.vawda | set | recipients:
+ nadeem.vawda, orsenthil, vstinner, python-dev |
| 2011年07月06日 00:20:43 | nadeem.vawda | set | messageid: <1309911643.92.0.461432010165.issue10883@psf.upfronthosting.co.za> |
| 2011年07月06日 00:20:43 | nadeem.vawda | link | issue10883 messages |
| 2011年07月06日 00:20:42 | nadeem.vawda | create |
|