On 2020-01-16 21:08, Rob Cliffe via Python-ideas wrote:
On 16/01/2020 18:14:18, Random832 wrote:
On Tue, Jan 14, 2020, at 18:15, David Mertz wrote:
For what it's worth, after 20+ years of using Python, forgetting the
colon for blocks remains the most common error I make by a fairly wide
On 16/01/2020 18:14:18, Random832 wrote:
On Tue, Jan 14, 2020, at 18:15, David Mertz wrote:
For what it's worth, after 20+ years of using Python, forgetting the
colon for blocks remains the most common error I make by a fairly wide
margin. Of course, once I see the error message—even being
On 21/12/2019 23:59:27, Chris Angelico wrote:
On Sun, Dec 22, 2019 at 10:46 AM Greg Ewing wrote:
On 22/12/19 9:04 am, Soni L. wrote:
switch (op) {
[...]
case OP_TAILCALL: {
adjust_regs();
some_other_stuff();
/* fallthrough */
}
case OP_CALL: {
The PEP index can be found at https://www.python.org/dev/peps/ and there
isn't any PEP on this.
But honestly, I don't think this sort of thing should be a PEP. Look at
ASGI and how that isn't a PEP and still manages to exist. Since this isn't
a language-related or package-related thing I don't
It's worth noting that I was discouraged from making ASGI a PEP by several
Python core developers, which is why I have not been pursuing that process
any further. I'm not sure I share this view, so I may come back to it in
the future, but there's a reason it's not in the process right now.
As for
WSGI and ASGI are similar to the Python DB-API, in the sense that they
define a standard Python API. The DB-API uses
Type: Informational
for this purpose; and yes, it doesn't go through the standard
PEP process, but instead is discussed and finalized by a SIG.
Since WSGI and (probably soon)
