Is there a reason being list.append
evaluating to false? Or is it just the C convention of returning 0 when successful that comes into play?
>>> u = []
>>> not u.append(6)
True
Most Python methods that mutate a container in-place return None
-- an application of the principle of Command-query separation. (Python's always reasonably pragmatic about things, so a few mutators do return a usable value when getting it otherwise would be expensive or a mess -- the pop
method is a good example of this pragmatism -- but those are definitely the exception, not the rule, and there's no reason to make append
an exception).
Method append
modifies the list in-place and the return value None
In your case, you are creating an array — [6] — on the fly, then discarding it. The variable b ends up with the return value of None.
Why?
This comply with the principle of Command–query separation devised by Bertrand Meyer.
It states that every method should either be a command that performs an action, or a query that returns data to the caller, but not both.
In your example:
u.append(6)
append
modified the state of []
, so it’s not a best practice to return a value compliance with the principle.
In theoretical terms, this establishes a measure of sanity, whereby one can reason about a program's state without simultaneously modifying that state.
CQS is well-suited to the object-oriented methodology such as python.
Builder
pattern .. so we can dou.append(6).append(7). ..
This is annoying. - WestCoastProjectsu.extend((6, 7))
? - Stefan Pochmannappend()
andextend()
have different effects and are not interchangeable - WestCoastProjects