Submitter | Augie Fackler |
---|---|
Date | Dec. 15, 2014, 3:22 p.m. |
Message ID | <2e273b5a679e41066119.1418656965@arthedain.pit.corp.google.com> |
Download | mbox | patch |
Permalink | /patch/7114/ |
State | Superseded |
Headers | show |
Comments
On Mon Dec 15 2014 at 7:23:00 AM Augie Fackler <raf@durin42.com> wrote:
> + assert v != None
I've been told that one should use the 'is' (or 'is not') operator when
comparing with None. Not valid in this case?
On Mon, Dec 15, 2014 at 11:20 AM, Martin von Zweigbergk <martinvonz@google.com> wrote: > On Mon Dec 15 2014 at 7:23:00 AM Augie Fackler <raf@durin42.com> wrote: >> >> + assert v != None > > > I've been told that one should use the 'is' (or 'is not') operator when > comparing with None. Not valid in this case? Nope, completely valid. I blame consistent exposure to C. I'll send a V2 shortly.
Patch
diff --git a/mercurial/manifest.py b/mercurial/manifest.py --- a/mercurial/manifest.py +++ b/mercurial/manifest.py @@ -17,6 +17,9 @@ class manifestdict(dict): flags = {} dict.__init__(self, mapping) self._flags = flags + def __setitem__(self, k, v): + assert v != None + dict.__setitem__(self, k, v) def flags(self, f): return self._flags.get(f, "") def withflags(self):