On Fri, Apr 1, 2022 at 2:06 AM Victor Stinner wrote:
> Hi,
>
> Update on this issue: I merged my 2 PRs.
> https://bugs.python.org/issue46850
>
> The following APIs have been moved to the internal C API:
>
> - _PyFrameEvalFunction type
> - _PyInterpreterState_GetEvalFrameFunc()
> - _PyInterpreterS
On 4/4/22 10:52, Coyot Linden (Glenn Glazer) wrote:
> On 4/4/22 Guido wondered:
>> How did we get from a specific issue with docstrings and the unittest
package's test
>> reporting to multi-line comments?
>
> Apologies, as I said earlier, I meant to write multiline /string/, not
multiline /comm
"Well, that escalated quickly." :-)
How did we get from a specific issue with docstrings and the
unittest package's test reporting to multi-line comments? If
this was Discourse that entire subdiscussion would have been
flagged as
On 4/4/2022 11:19 AM, Petr Viktorin wrote:
On 03. 02. 22 1:40, Guido van Rossum wrote:
[...]
I understand the CPython is stuck supporting the de-facto standard C
API for a long time. But unless we pick a "north star" (as people call
it nowadays) of what we want to support in say 5-10 years, t
"Well, that escalated quickly." :-)
How did we get from a specific issue with docstrings and the unittest
package's test reporting to multi-line comments? If this was Discourse that
entire subdiscussion would have been flagged as off-topic and moved to its
own thread.
On Mon, Apr 4, 2022 at 10:12
On Mon, Apr 04, 2022 at 09:27:46AM -0700, Coyot Linden (Glenn Glazer) wrote:
> On 4/4/22 09:25, Paul Moore wrote:
> >On Mon, 4 Apr 2022 at 17:22, Coyot Linden (Glenn Glazer)
> > wrote:
> >>>I would welcome a multiline comment format that didn't involve
> >>>docstrings.
> >>Err, sorry, I meant mult
On 4/4/2022 11:07 AM, Coyot Linden (Glenn Glazer) wrote:
I would like to point out another use case of triple quotes outside of
docstrings.
A docstring is *any* string literal, regardless of quotes, that is a
statement in itself and is the *first* statement in the body of a
module, class, or
On 4/4/22 09:25, Paul Moore wrote:
On Mon, 4 Apr 2022 at 17:22, Coyot Linden (Glenn Glazer)
wrote:
I would welcome a multiline comment format that didn't involve docstrings.
Err, sorry, I meant multiline string format.
I'm confused, what's wrong with """..."""? Triple quoted strings are
not e
On Mon, 4 Apr 2022 at 17:22, Coyot Linden (Glenn Glazer)
wrote:
> > I would welcome a multiline comment format that didn't involve docstrings.
>
> Err, sorry, I meant multiline string format.
I'm confused, what's wrong with """..."""? Triple quoted strings are
not exclusively for docstrings...
Pa
I would welcome a multiline comment format that didn't involve docstrings.
Err, sorry, I meant multiline string format.
Best,
coyot
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https
On 03. 02. 22 1:40, Guido van Rossum wrote:
[...]
I understand the CPython is stuck supporting the de-facto standard C API
for a long time. But unless we pick a "north star" (as people call it
nowadays) of what we want to support in say 5-10 years, the situation
will never improve.
My point
I would like to point out another use case of triple quotes outside of
docstrings. We do a lot of SQL here and so doing a parameterized query like:
"""SELECT foo
FROM bar
WHERE baz = %s"""
is a whole lot cleaner and more natural than
("SELECT foo" +
"FROM bar" +
"WHERE baz = %s")
For this toy
12 matches
Mail list logo