Steven D'Aprano wrote: > Do nothing? > I don't have to suggest a better idea, since its not me proposing a > change. I don't think any change is needed. It is up to you to firstly > justify that a change is needed, and only then justify a specific > response to that need.
[snip] > If you personally would use them, I'm happy for you. But unless there is > likely to be either moderate or widespread use among the community, or > at least some uses in the stdlib, those functions belong in your own > personal toolbox, not the stdlib. +1 to doing nothing here, at least based on the current proposal. Soni, I would strongly recommend spending some more time to come up with specific, concrete use cases for feature proposals in the future (or in this thread). Preferably with some detailed "before and after" examples using *non-trivial* real world code, and some explanations as to why you think it should be included in the standard library instead of just something implemented locally or in a 3rd party package. Without doing the above, it's very likely going to end up being an infinite loop of seeing the same repeated counter-arguments on your proposals. If those points can't be answered and defended, it's highly unlikely the proposal would be accepted in the first place; regardless of how interesting the ideas may seem. On Thu, Apr 16, 2020 at 10:37 PM Steven D'Aprano <st...@pearwood.info> wrote: > > On Thu, Apr 16, 2020 at 01:11:46PM -0300, Soni L. wrote: > > > we can't break setdefault (particularly for tuple keys), do you have a > > better idea? > > Do nothing? > > I don't have to suggest a better idea, since its not me proposing a > change. I don't think any change is needed. It is up to you to firstly > justify that a change is needed, and only then justify a specific > response to that need. > > An anecdote... when I first discovered Python back in 1.5 days, and > specifically the dict.update method, practically the first thing I did > was wonder why update replaced existing keys. What if I wanted it to > keep the existing key, or raise an exception? So I immediately wrote a > pair of functions to do both those things. > > It's been close to 20 years now and so long as I can remember, I have > never, not once, used either of those variants I don't even know > whether I even still have them (not that it would be hard to recreate > them). > > If you personally would use them, I'm happy for you. But unless there is > likely to be either moderate or widespread use among the community, or > at least some uses in the stdlib, those functions belong in your own > personal toolbox, not the stdlib. > > > -- > Steven > _______________________________________________ > Python-ideas mailing list -- python-ideas@python.org > To unsubscribe send an email to python-ideas-le...@python.org > https://mail.python.org/mailman3/lists/python-ideas.python.org/ > Message archived at > https://mail.python.org/archives/list/python-ideas@python.org/message/SPY2DRKUZ3LUX56AYOA2QKEMT4KAZLNP/ > Code of Conduct: http://python.org/psf/codeofconduct/ _______________________________________________ Python-ideas mailing list -- python-ideas@python.org To unsubscribe send an email to python-ideas-le...@python.org https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/python-ideas@python.org/message/RVBUMROZZIDR3DCMDPBG2RTGUSQKSQPN/ Code of Conduct: http://python.org/psf/codeofconduct/
