`->` would not be ambiguous in the proposed cases, but it does already
mean something elsewhere in the language as of 3.5:
def concat(a: str, b: str) -> str:
return a + b
This could potentially cause confusion (as with the % operator being
used for modulo as well as string formatting).
On Tu
print(f'{value!d}') is a lot of symbols and boilerplate to type out just
for a debugging statement that will be deleted later. Especially now that
breakpoint() exists, I can't really see myself using this.
I also don't see the use case of it being within an f-string, because I've
never had to inte
Not totally convinced about this. It would require PEP writers to fully
implement their proposed feature, people can usually get a pretty good idea of
how a feature is supposed to work through PEPs (most of which are extremely
well written), and these "mods" wouldn't be used in production code
One of the features I miss from languages such as C# is namespaces that
work across files - it makes it a lot easier to organize code IMO.
Here's an idea I had - it might not be the best idea, just throwing this
out there: a "within" keyword that lets you execute code inside a
namespace. For examp
