On Fri, Jun 17, 2022 at 02:50:50AM -0000, Steve Jorgensen wrote: > What are people's impressions of this idea. Is it valuable enough to > pursue writing a PEP?
I don't think it is useful enough to dedicate syntax to it. If you are proposing this idea, it is your job to provide evidence that it is useful. That should be actual, real-world use-cases, not just toy snippets like `(first, second, *) = items` with no context. Examples of where and why people would use it. **Especially** the why part. Examples of the work-arounds people have to use in its place, or reasons why islice won't work. "People don't know about islice" is not a convincing argument -- people won't know about this either. Actual code is much more convincing than made up examples. Code from the stdlib that would benefit from this is a good place to start. > If so, then what should I do in writing the PEP to make sure that it's > somewhat close to something that can potentially be accepted? Perhaps, > there is a guide for doing that? Read the PEPs. Start with the PEP 1, which is exactly the guide you are looking for. Then PEP 5, although it probably won't apply to this. (But it is useful to know regardless.) https://peps.python.org/pep-0001/ https://peps.python.org/pep-0005/ I suggest you read a variety of both successful and unsuccessful PEPs. I recommend PEPs 450, 506 and 584 as *especially* good, not that I'm the least bit biased *wink* This is also a good PEP to read, as it is an example of an extremely controversial (at the time) PEP that nevertheless was successful: https://peps.python.org/pep-0572/ This is another PEP which was, believe it or not, controversial at the time: https://peps.python.org/pep-0285/ This is an example of an excellent PEP that gathered support from stakeholders in the Numpy community before even raising the issue on this mailing list: https://peps.python.org/pep-0465/ There are many more excellent PEPs, I have just mentioned a few of my personal favs. Others may have other opinions. Remember that even the best PEPs may be rejected or deferred, and resist the temptation to attribute all criticism to bad faith and spite. Don't be That Guy. This is an excellent blog post to read: https://www.curiousefficiency.org/posts/2011/04/musings-on-culture-of-python-dev.html I recommend that you gather feedback from a variety of places, starting here. The Ideas topic on Python's Discourse is another good place. You might also try Reddit's r/python and the "Python Forum" here: https://python-forum.io and perhaps the comp.lang.python newsgroup, also available as a mailing list. Be prepared for a ton of bike-shedding. People may hate the syntax even if they like the idea. https://en.wikipedia.org/wiki/Law_of_triviality Good luck! -- Steve _______________________________________________ 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/DCC3DE7OP7OLZFYZTPCGO6MGOY2NS3KH/ Code of Conduct: http://python.org/psf/codeofconduct/
