#461 This episdoe has a typo

Topics covered in this episode:

• PEP 798: Unpacking in Comprehensions
• Pandas 3.0.0rc0
• typos
• A couple testing topics
• Extras
• Joke

Watch on YouTube

About the show

Sponsored by us! Support our work through:

• Our courses at Talk Python Training
• The Complete pytest Course
• Patreon Supporters

Connect with the hosts

• Michael: @[e-mail] / @mkennedy.codes (bsky)
• Brian: @[e-mail] / @brianokken.bsky.social
• Show: @[e-mail] / @pythonbytes.fm (bsky)

Join us on YouTube at pythonbytes.fm/live to be part of the audience. Usually Monday at 10am PT. Older video versions available there too.

Finally, if you want an artisanal, hand-crafted digest of every week of the show notes in email form? Add your name and email to our friends of the show list, we'll never share it.

Michael #1: PEP 798: Unpacking in Comprehensions

• After careful deliberation, the Python Steering Council is pleased to accept PEP 798 – Unpacking in Comprehensions.

• Examples

  [*it for it in its]  # list with the concatenation of iterables in 'its'
  {*it for it in its}  # set with the union of iterables in 'its'
  {**d for d in dicts} # dict with the combination of dicts in 'dicts'
  (*it for it in its)  # generator of the concatenation of iterables in 'its'
  

• Also: The Steering Council is happy to unanimously accept “PEP 810, Explicit lazy imports”

Brian #2: Pandas 3.0.0rc0

• Pandas 3.0.0 will be released soon, and we’re on Release candidate 0
• Here’s What’s new in Pands 3.0.0
  • Dedicated string data type by default
    • Inferred by default for string data (instead of object dtype)
    • The str dtype can only hold strings (or missing values), in contrast to object dtype. (setitem with non string fails)
    • The missing value sentinel is always NaN (np.nan) and follows the same missing value semantics as the other default dtypes.
  • Copy-on-Write
    • The result of any indexing operation (subsetting a DataFrame or Series in any way, i.e. including accessing a DataFrame column as a Series) or any method returning a new DataFrame or Series, always behaves as if it were a copy in terms of user API.
    • As a consequence, if you want to modify an object (DataFrame or Series), the only way to do this is to directly modify that object itself.
  • pd.col syntax can now be used in DataFrame.assign() and DataFrame.loc()
    • You can now do this: df.assign(c = pd.col('a') + pd.col('b'))
  • New Deprecation Policy
  • Plus more
-

Michael #3: typos

• You’ve heard about codespell …