{"id":26019,"date":"2019-07-19T16:34:41","date_gmt":"2019-07-19T20:34:41","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=26019"},"modified":"2019-07-19T16:34:41","modified_gmt":"2019-07-19T20:34:41","slug":"whats-coming-in-python-3-8","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2019\/07\/19\/whats-coming-in-python-3-8\/","title":{"rendered":"What’s Coming in Python 3.8"},"content":{"rendered":"

Jake Edge<\/a> (via Hacker News<\/a>):<\/p>\n

Out of that came a new operator, however, that is often called the “walrus\noperator” due to its visual appearance. Using “:=<\/code>“ in an\nif<\/code> or while<\/code> statement allows assigning a value to a\nvariable while testing \nit.<\/p>

[…]<\/p>

The f-strings (or formatted strings)<\/a> added\ninto Python 3.6 are quite useful, but Pythonistas often found that they\nwere using them the same way in debugging output. So Eric V. Smith proposed<\/a>\nsome additional syntax for f-strings to help with debugging output.<\/p>

[…]<\/p>

Another change for 3.8 affords pure-Python functions the same options for\nparameters that those implemented in C already have. PEP 570<\/a> (“Python\nPositional-Only Parameters”) introduces new syntax that can be used in\nfunction definitions to denote positional-only\narguments<\/a>—parameters that cannot be passed as keyword arguments.<\/p><\/blockquote>\n\n

Previously:<\/p>\n