Upgrade to new upstream release 0.16.0
3 unresolved threads
3 unresolved threads
To create these changes, I did:
# download orig.tar.gz
git-dpm import-new-upstream --rebase ../python-future_0.16.0.orig.tar.gz
# fix conflicts
git-dpm update-patches
pristine-tar commit ../python-future_0.16.0.orig.tar.gz upstream
git-dpm dch -- -v 0.16.0-1 "new upstream version 0.16.0"
So there are also corresponding upstream and pristine-tar branches in my fork of this repository.
Note that this resolves https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863215.
I ran the tests and did not see any failures: https://salsa.debian.org/saraedum-guest/python-future/-/jobs/14758
I am new to debian/python-future, so I am very happy to get any feedback :)
Edited by Julian Rüth
Merge request reports
Activity
13 --- a/tests/test_future/test_bytes.py 14 +++ b/tests/test_future/test_bytes.py 15 @@ -7,6 +7,8 @@ from __future__ import absolute_import, unicode_literals, print_function 16 from future.builtins import * 17 from future import utils 18 19 +import sys 20 + 21 from numbers import Integral 22 from future.tests.base import unittest, expectedFailurePY2 23 24 @@ -552,103 +554,105 @@ class TestBytes(unittest.TestCase): 25 self.assertRaises(ValueError, bytes.maketrans, b'abc', b'xyzq') 26 self.assertRaises(TypeError, bytes.maketrans, 'abc', 'def') 27 28 - # def test_mod(self): Upstream commented out these tests in https://github.com/PythonCharmers/python-future/commit/ecf112163ce9aaa7715c1d777a79e1c66d509e8f#diff-844c93dfd92e3c3447e61e5ffe981150
1 From 1c13f543c652141f38fb8f13ea264c548d7079c5 Mon Sep 17 00:00:00 2001 1 From 6e3c0d5f332a2f591c36d477e5c254849b7d40f5 Mon Sep 17 00:00:00 2001 @onovy hello, I don't know if you gets merge requests emails... can you please have a look?
thanks for the upload!
Please register or sign in to reply