Alex Waygood

Tip: pprint.pp does the same thing but has better (much less surprising!) defaults

The 3.14 branch is locked for RC1 The 3.14 branch is now locked for all (except release managers and admins) until the 3.14.0 final release (scheduled for 2025-10-07). Reminder from the devguide: A branch preparing for an RC releas...

🥧🪵🔒 The branch is locked and first release candidate of Python 3.14 is being built!
discuss.python.org/t/the-3-14-b...
#Python #Python314 #release #ReleaseCandidate #RC1

TYVM!

Ask not for whom the grant shapps, it shapps for thee

I groaned out loud at the last sentence, thank you

Pydantic is another uv-based project already in that workflow — you might be able to look at that one for reference

Oh, that's very kind of you to ask! Sure — the workflow where we run the cattrs test suite every night is github.com/python/typin... . The workflow is also run on PRs that edit the workflow file itself. A PR updating that workflow would be welcome!

How MI5 piled falsehood on falsehood in court in the case of a spy who abused women Security Service continued to provide misleading evidence even after its lie was exposed, BBC can reveal.

This documentation is absolutely amazing, and does the BBC credit. To publicly dismantle MI5 lies like this is a feat of independent journalism

www.bbc.co.uk/news/article...

The real Salt Path: how a blockbuster book and film were ... Penniless and homeless, the Winns found fame and fortune with the story of their 630-mile walk to salvation. We can reveal that the truth behind it is ve...

Fantastic yarn by @chloehadj.bsky.social this: about the falsehoods at the heart of a bestselling series of nature books:

They're everywhere in Hertfordshire! We see them regularly over our house

gh-112405: Optimise `pathlib.Path.relative_to` by AlexWaygood · Pull Request #112406 · python/cpython On main (Windows machine, PGO-optimised build): >python -m timeit -s "from pathlib import Path; p = Path('a/b/c/d/e/f/g')" "p.relative_to('a/b/c/d')" Running ...

I significantly sped up a pathlib function a while back using it! github.com/python/cpyth...

We're working on it! Sorry for the delay. There were a couple of big changes to extension modules that landed in the last beta which have been tricky to reimplement in Python- build-standalone. But AFAIK we're nearly there

It's fun if you look at different classical composers' methods of writing music. Some composers apparently found it easy/enjoyable, but the famous counter-example is Beethoven. His notebooks are full of bars of music angrily scribbled out as he struggled to express what he wanted

I always felt exactly this way about writing. I loved having written something. Not so much writing it. It's probably a good thing I'm not a journalist anymore 😄

Just finished a new blog post! 🎉 👀

This goes into a deep dive into Python's two new type checkers, Pyrefly by Meta and ty by Astral (the team behind uv and ruff)

Check it out here: blog.edward-li.com/tech/compari...

huge fan of the 70 year old german guy who uploaded this 360 degree interactive panorama of inside a corn flakes bag. it's in the corn flakes article on

We certainly don't want to force typing onto anybody who doesn't want to use it!

Ultimately I'm not sure I have a great answer for you here. But it *is* a problem that we're aware of, and I know we'd love to think of ways to mitigate it once we're a bit further along and we can see just how much of a problem it is for library maintainers.

One of the reasons why there is controversy around standardising too much is it would stifle innovation. We're deliberately doing some things differently to mypy and pyright because we think there's a chance to create a better user experience. A more comprehensive spec would make that harder!

@qexat.com is right that the solution here should be the recently formed Typing Council and the typing spec. But the spec is silent on many things where users would love standardised behaviour. It's still a WIP; lots of things are unfortunately controversial and will take a while to iron out

I feel you. I know all too well from maintaining typeshed that it's a massive pain trying to write code that passes on mypy, pyright and pytype simultaneously. And it's definitely on our minds that adding one more type checker to the mix isn't going to help with that (at least not in the short term)

There were layoffs at MS yesterday and 3 #Python core devs from the Faster CPython team were caught in them. If you know of any jobs, please send them their way (they kind of know Python, CPython, and its internals well 😉):

Eric Snow: https://www.linkedin.com/in/ericsnowcurrently/
Irit Katriel: […]

The Python reddit (www.reddit.com/r/Python/) or the community Python Discord (discord.gg/python) might be good places. (If the latter, make sure you post in an appropriate channel!)

or at least, that's my opinion! There are still sharp edges in Python's typing system, of course, but one of the things we hope to do with ty is to make Python typing easily adoptable and enjoyable to use.

Will typed Python ever be *as* strongly typed as C# or Rust? No; there will always be applications for which that those languages are better suited. For many things, it can be a really good compromise between a completely untyped scripting language and a strictly typed compiled language, however

But, especially if it's a large Python codebase, they also love being able to quickly run a type checker over their tool to spot errors before running their code. They love the security and confidence that this brings them (2/n)

Folks who are into typed Python generally love Python for many of the same reasons as folks who love untyped Python -- they love how clean the syntax is, they love all the dynamic features of the language, and they love how quick it is to prototype ideas in Python (1/n)

It's certainly not our goal to force typing on anybody who doesn't want to use it! If you're not a fan of typing, it sounds like this probably isn't the tool for you :-)

Vote to promote Diego Russo Thank you all for the kind words and support! I’m truly honoured — and honestly a bit overwhelmed — to be joining the CPython core team. I’ve learned so much from this community, and I’m incredibly ...

I’m officially a CPython Core Developer! 🐍

I’ve been using Python since 2006 — contributing back was a dream, and now it’s real.
Huge thanks to everyone who supported me, and to Arm for backing me from day one.

It’s not the destination — it’s the journey. 💙

🔗 discuss.python.org/t/vote-to-pr...

There's still a long way to go on this project, but I'm hugely excited about where we're going with this. Let's make Python typing even more awesome than it already is!