ResourceWarning for unclosed files in ssh backend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Duplicity |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Using the duplicity 0.8.04 ssh backend on Debian unstable (Python 3.7.5rc1), I get ResourceWarning messages about unclosed files.
Steps to reproduce:
$ mkdir a
$ touch a/file
$ PASSPHRASE=password duplicity --verbosity 1 --no-print-
/usr/lib/
sshconfig.
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/
sshconfig.
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/
u'logger': self.logger_fp})
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/
u'logger': self.logger_fp})
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/
u'logger': self.logger_fp})
ResourceWarning: Enable tracemalloc to get the object allocation traceback
/usr/lib/
man_outfp.
ResourceWarning: Enable tracemalloc to get the object allocation traceback
affects: | paramiko → duplicity |
Changed in duplicity: | |
status: | Fix Committed → Fix Released |
Please do a couple of things, if possible:
- Check to see if Python is compiled with DEBUG
- Make sure that duplicity shebang does not have -Wall
- Check your environment for PYTHON* variables
You can check the cflags options with:
$ python-config --cflags