From: 
Subject: Debian changes

The Debian packaging of python-batinfo is maintained in git, using a workflow
similar to the one described in dgit-maint-merge(7).
The Debian delta is represented by this one combined patch; there isn't a
patch queue that can be represented as a quilt series.

A detailed breakdown of the changes is available from their canonical
representation -- git commits in the packaging repository.
For example, to see the changes made by the Debian maintainer in the first
upload of upstream version 1.2.3, you could use:

    % git clone https://git.dgit.debian.org/python-batinfo
    % cd python-batinfo
    % git log --oneline 1.2.3..debian/1.2.3-1 -- . ':!debian'

(If you have dgit, use `dgit clone python-batinfo`, rather than plain `git clone`.)

We don't use debian/source/options single-debian-patch because it has bugs.
Therefore, NMUs etc. may nevertheless have made additional patches.

---

diff --git a/batinfo/battery.py b/batinfo/battery.py
index e1e07df..f536e39 100644
--- a/batinfo/battery.py
+++ b/batinfo/battery.py
@@ -110,7 +110,7 @@ class Batteries(object):
         # Find all the batteries in the bat_root_path folder
         # It's a battery if the file "type" exist
         # and contain "Battery"
-        for dirname in os.listdir(self.bat_root_path):
+        for dirname in sorted(os.listdir(self.bat_root_path)):
             type_file = os.path.join(self.bat_root_path, dirname, "type")
             if (os.path.isfile(type_file)):
                 try:
diff --git a/test_batinfo.py b/test_batinfo.py
index 2477209..de7f6e9 100644
--- a/test_batinfo.py
+++ b/test_batinfo.py
@@ -50,7 +50,7 @@ class TestBatInfo(unittest.TestCase):
         batteries_count = 0
         for bat in self.bat:
             batteries_count += 1
-        self.assertEquals(batteries_count, 2)
+        self.assertEqual(batteries_count, 2)
 
 
 if __name__ == '__main__':
