fixed config test for config.set_multivar

config files have different priorities and only the highest one gets evaluated for set_multivar
This commit is contained in:
Nico von Geyso
2012-11-01 14:47:42 +01:00
parent b961b9218f
commit 971fc2f101
2 changed files with 1 additions and 2 deletions

View File

@@ -84,7 +84,6 @@ Index_add(Index *self, PyObject *args)
{ {
int err; int err;
const char *path; const char *path;
git_index_entry* entry;
if (!PyArg_ParseTuple(args, "s", &path)) if (!PyArg_ParseTuple(args, "s", &path))
return NULL; return NULL;

View File

@@ -151,7 +151,7 @@ class ConfigTest(utils.RepoTestCase):
new_file.write("[this]\n\tthat = foobar\n\tthat = foobeer\n") new_file.write("[this]\n\tthat = foobar\n\tthat = foobeer\n")
new_file.close() new_file.close()
config.add_file(config_filename, 0) config.add_file(config_filename, 5)
self.assertTrue('this.that' in config) self.assertTrue('this.that' in config)
config.set_multivar('this.that', '^.*beer', 'fool') config.set_multivar('this.that', '^.*beer', 'fool')
l = config.get_multivar('this.that', 'fool') l = config.get_multivar('this.that', 'fool')