My understanding is that for a sql prefix the most valuable part is to be able
to know that it was created from a literal. No other magic, definitely not
auto-executing. Then it would be legal to write
result = conn.execute(sql"SELECT * FROM people WHERE id=?",
user_
My understanding is that for a sql prefix the most valuable part is to be able
to know that it was created from a literal. No other magic, definitely not
auto-executing. Then it would be legal to write
result = conn.execute(sql"SELECT * FROM people WHERE id=?",
user_
> How does one get a value into locals()["re~"]?
You're right, I didn't think about that. I agree with Steven's
interpretation that the user is not expected to modify locals
herself, still the immutable nature of locals presents a
considerable challenge.
So I'm thinking that perhaps we could chan
> There's no such thing, though, any more than there's such a thing as a
> "raw string". There are only two types of string in Python - text and
> bytes. You can't behave differently based on whether you were given a
> triple-quoted, raw, or other string literal.
A simple implementation could be s
> I can’t think of any uses other than Optional.
Also, in IPython and Jupyter Lab `?smth` displays help for symbol `smth`.
___
Python-ideas mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail
> Don't say that this proposal won't be abused. Every one of the OP's
> motivating examples is an abuse of the syntax, returning non-strings
> from something that looks like a string.
If you strongly believe that if something looks like a string it ought to quack
like a string too, then we can
