Merge pull request #25 from baseplate-admin/patch-2

Use `next` instead of `__next__`
mariocesar · Dec 19, 2024 · 7a33391 · 7a33391
2 parents c5241ab + 4b34578
commit 7a33391
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 3 deletions.
diff --git a/django_ltree/managers.py b/django_ltree/managers.py
@@ -29,5 +29,5 @@ def create_child(self, parent=None, **kwargs):
             skip=paths_in_use.values_list("path", flat=True),
             label_size=getattr(self.model, "label_size"),
         )
-        kwargs["path"] = path_generator.next()
+        kwargs["path"] = next(path_generator)
         return self.create(**kwargs)
diff --git a/django_ltree/paths.py b/django_ltree/paths.py
@@ -24,5 +24,3 @@ def __next__(self):
             path = PathValue(self.path_prefix + [label])
             if path not in self.skip_paths:
                 return path
-
-    next = __next__