From e4d3809161fc54d6913c0c2c7f6a7b51eebe223f Mon Sep 17 00:00:00 2001 From: Sebastian Thiel Date: Wed, 21 Jan 2015 18:34:58 +0100 Subject: Added advance usage examples to tutorial and made minor fixes. GIT_PYTHON_TRACE would actually fail (now) if we debugged archive operations. Related to #239 --- git/test/test_remote.py | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'git/test/test_remote.py') diff --git a/git/test/test_remote.py b/git/test/test_remote.py index 110f1fa5..d4a92ed4 100644 --- a/git/test/test_remote.py +++ b/git/test/test_remote.py @@ -451,11 +451,15 @@ class TestRemote(TestBase): remote = Remote.create(bare_rw_repo, *arg_list) assert remote.name == "test_new_one" assert remote in bare_rw_repo.remotes + assert remote.exists() # create same one again self.failUnlessRaises(GitCommandError, Remote.create, bare_rw_repo, *arg_list) Remote.remove(bare_rw_repo, new_name) + assert remote.exists() # We still have a cache that doesn't know we were deleted by name + remote._clear_cache() + assert not remote.exists() # Cache should be renewed now. This is an issue ... for remote in bare_rw_repo.remotes: if remote.name == new_name: -- cgit v1.2.1