Understanding the Adoption of pyproject.toml

00:00 So, do you think that the Python community will move towards pyproject.toml very quickly? Are we there? What stage are we at with adoption here?

00:08 Right, so, as we talked about a bit earlier, there’s a messy history here, but pip has been doing a lot of upgrades the last year or two in supporting the pyproject.toml workflow as it’s defined in this PEP 621.

00:24 So, the cool thing now is that this works on the newest versions of pip. This just runs, and it works for editable installs, which a problem for a while.

00:33 It runs on regular package installs. Yeah, it just works. So what we’re seeing now is that there’s actually several new different build systems, like Flit

00:45 and Poetry, already support the pyproject.toml. The Poetry one will, in version two, it’ll essentially be reusable, the file that we set up.

00:55 So right now, Poetry does support the same type of workflow. Just the pyproject format is slightly different, but they’re making updates so that the format is going to be exactly the same between setuptools and Poetry. Yeah, and the good things with that is essentially things get standardized and it’s easier to switch build systems, but working with Poetry today is already no worries at all.

01:18 It is very simple to use, and it’s kind of exactly the same philosophy. It’s just slightly different syntax.

01:27 This is a really cool and seems to be very widely supported and basically where we’re going with Python. Can this be considered standard? Can I just say this is the standard way to do things? Yes, clearly. It’s all supported by PEPs, which are by definition how Python is standardized.

01:45 So this is the way. Yeah. Fantastic.