[Python-ideas] Suggestion: push() method for lists
toddrjen at gmail.com
Sun May 21 22:50:56 EDT 2017
On Sun, May 21, 2017 at 10:43 AM, Paul Laos <paul_laos at outlook.com> wrote:
> It would be nice to have the opposite of the pop() method: a push()
> method. While insert() and append() already exist, neither is the opposite
> of pop(). pop() has a default index parameter -1, but neither insert() nor
> append() has a default index parameter. push(obj) would be equivalent to
> insert(index = -1, object), having -1 as the default index parameter. In
> fact, push() could replace both append() and insert() by unifying them.
> By default push(obj) would insert an object to the end of the list, while
> push(obj, index) would insert the object at index, just like pop() removes
> (and returns) the object at the end of the list, and pop(index) removes
> (and returns) the object at the index.
> I found little discussion on this, just this SO thread
> http://stackoverflow.com/questions/1566266/why-is-pythons-append-not-push which
> lead to a discussion from 20 years ago (1997):
> Some key arguments from the thread:
> >it would be an
> >easy and obvious improvement to make popend an explicit builtin, and
> >that this would make Python even more attractive to newcomers who want
> >to use what they already know and be immediately productive.
> - Terry Reedy
> >append() is a special case of insert(). The inverse of insert() is
> >the del function. The specific inverse of append() is del list[-1].
> - Michael W. Ryan
> >but I'm not a big fan of multiple names for the same operation --
> >sooner or later you're going to read code that uses the other one, so
> >you need to learn both, which is more cognitive load.
> - Guido van Rossum
> So while it has been discussed before, it's worth bringing up again, since
> this was before the release of Python 2.0.
> - Would simplify the language by having a symmetric relation to pop().
> - Would make it easy to use lists as stacks.
> - Saves at least two characters
> - If append()/insert() are being removed and replaced, the complexity of
> lists is slightly reduced.
> - Would blur the line between lists and stacks.
> - The order of the parameters in push(obj, index = -1) would be the
> opposite of the parameters in insert(index, obj), because defaulted
> parameters come last.
> - If append()/insert() are being removed and replaced, backwards
> compatability breaks.
> - If append()/insert() are kept instead of being replaced, the complexity
> of lists is slightly increased.
> While it isn't a necessity, I believe the benefit of push() method
> outweighs its cons.
There is absolutely zero chance that append and insert are going away. That
would break everything.
So with your proposal, we would end up with two methods that do exactly the
same thing, differing only in the defaults and the order of arguments. That
definitely does not make the language simpler.
The big question you need to ask when proposing a new feature for python is
"what is the use-case for this?" What does this do that existing features
can't do, or that existing features are significantly worse at? Since this
literally duplicates the functionality of existing features, it doesn't
have such a use-case
If we were changing things at all, I think the first place to start would
be to either set a default argument for "insert" or add an optional
argument for "append", but in both cases that would again be duplicating
functionality so I don't see the point.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Python-ideas