Patchwork D7212: fsmonitor: use next() instead of .next()

login
register
mail settings
Submitter phabricator
Date Nov. 4, 2019, 4:28 p.m.
Message ID <1880e14b749fb8cb261d93fd59b1d159@localhost.localdomain>
Download mbox | patch
Permalink /patch/42722/
State Not Applicable
Headers show

Comments

phabricator - Nov. 4, 2019, 4:28 p.m.
Closed by commit rHG2b5aab5e9e36: fsmonitor: use next() instead of .next() (authored by indygreg).
This revision was automatically updated to reflect the committed changes.
This revision was not accepted when it landed; it landed in state "Needs Review".

REPOSITORY
  rHG Mercurial

CHANGES SINCE LAST UPDATE
  https://phab.mercurial-scm.org/D7212?vs=17510&id=17528

CHANGES SINCE LAST ACTION
  https://phab.mercurial-scm.org/D7212/new/

REVISION DETAIL
  https://phab.mercurial-scm.org/D7212

AFFECTED FILES
  hgext/fsmonitor/__init__.py

CHANGE DETAILS




To: indygreg, #hg-reviewers
Cc: mercurial-devel

Patch

diff --git a/hgext/fsmonitor/__init__.py b/hgext/fsmonitor/__init__.py
--- a/hgext/fsmonitor/__init__.py
+++ b/hgext/fsmonitor/__init__.py
@@ -504,9 +504,9 @@ 
     for f in auditfail:
         results[f] = None
 
-    nf = iter(auditpass).next
+    nf = iter(auditpass)
     for st in util.statfiles([join(f) for f in auditpass]):
-        f = nf()
+        f = next(nf)
         if st or f in dmap:
             results[f] = st