Package: python-debian Version: 0.1.29 Severity: normal
We wrote a python system to manipulate Debian CDs and resolve dependencies based on local caches. We started out having our ouwn "debianPackage" class, but about 4 months ago, I came across the python-debian code. After reading the documentation, we downgraded our debianPackage class to be a wrapper around the python-debian classes. After applying this, we started getting reports of a significant slowdown; we planned to look at it "later". This week, when working on a new system, we started getting failures with 'too many filehandles'. When inspecting deeper, ArFile kept a filehandle open for every package that is added to the (local) debian Pool that is being processed (I assume it gets the data on request instead of caching it in the objects). As a result, we re-implemented the relevant parts to avoid this file handle leak (?). -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-debian depends on: ii python-chardet 2.3.0-2 ii python-six 1.10.0-3 pn python:any <none> Versions of packages python-debian recommends: ii python-apt 1.1.0~beta5 Versions of packages python-debian suggests: ii gpgv 2.1.15-3 -- no debconf information This message is subject to the following terms and conditions: MAIL DISCLAIMER<http://www.barco.com/en/maildisclaimer>
