Test and Code: 119: Editable Python Installs, Packaging Standardization, and pyproject.toml - Brett Cannon

There's stuff going on in Python packaging and pyproject.toml.

Brett and I talk about some upcoming work on Python packaging, such as:

• editable installs
  • the need for standardization
  • is a feature of setuptools that's so
  • tools like flit can create stub setup.py files for editable installs
• configuration of other tools in pyproject.toml
  • originally not supposed to happen, was supposed to be only a build tool
  • black and other tools use it anyway
  • now it's ok

And then get off on tangents and talk about:

• why it's good to have packages like pip, toml, setuptools, wheel, etc not part of the standard library
• should we remove some stuff from the standard library
• the standard library using unittest for testing the standard library
  • why not hypothesis
  • I didn't bring up "why not pytest?" but you know I was thinking it.
• why CPython and not C++Python
• and more

Special Guest: Brett Cannon.

Sponsored By:

• CircleCI: Continuous integration and deployment with faster performance, complete control, and unparalleled flexibility.
• Datadog: Modern monitoring & security. See inside any stack, any app, at any scale, anywhere.

Support Test & Code : Python Testing for Software Engineering

Links:

• episode 52: pyproject.toml : the future of Python packaging - Brett Cannon
• Python Packaging Authority
• PEP 517 -- A build-system independent format for source trees
• PEP 518 -- Specifying Minimum Build System Requirements for Python Projects
• What the heck is pyproject.toml?
• Flit
• Poetry
• enscons
• toml
• setuptools
• distutils
• pip
• HTTPX

<p>There&#39;s stuff going on in Python packaging and pyproject.toml.</p> <p>Brett and I talk about some upcoming work on Python packaging, such as:</p> <ul> <li>editable installs <ul> <li>the need for standardization</li> <li>is a feature of setuptools that&#39;s so </li> <li>tools like flit can create stub setup.py files for editable installs</li> </ul></li> <li>configuration of other tools in pyproject.toml <ul> <li>originally not supposed to happen, was supposed to be only a build tool</li> <li>black and other tools use it anyway</li> <li>now it&#39;s ok</li> </ul></li> </ul> <p>And then get off on tangents and talk about:</p> <ul> <li>why it&#39;s good to have packages like pip, toml, setuptools, wheel, etc not part of the standard library</li> <li>should we remove some stuff from the standard library</li> <li>the standard library using unittest for testing the standard library <ul> <li>why not hypothesis</li> <li>I didn&#39;t bring up &quot;why not pytest?&quot; but you know I was thinking it.</li> </ul></li> <li>why CPython and not C++Python</li> <li>and more</li> </ul><p>Special Guest: Brett Cannon.</p><p>Sponsored By:</p><ul><li><a href="https://circle.ci/testcode" rel="nofollow">CircleCI</a>: <a href="https://circle.ci/testcode" rel="nofollow">Continuous integration and deployment with faster performance, complete control, and unparalleled flexibility.</a></li><li><a href="https://ift.tt/3eBYfEe" rel="nofollow">Datadog</a>: <a href="https://ift.tt/3eBYfEe" rel="nofollow">Modern monitoring & security. See inside any stack, any app, at any scale, anywhere. </a></li></ul><p><a href="https://ift.tt/2tzXV5e" rel="payment">Support Test & Code : Python Testing for Software Engineering</a></p><p>Links:</p><ul><li><a href="https://ift.tt/2OuLddQ" title="episode 52: pyproject.toml : the future of Python packaging - Brett Cannon" rel="nofollow">episode 52: pyproject.toml : the future of Python packaging - Brett Cannon</a></li><li><a href="https://ift.tt/1UctjN7" title="Python Packaging Authority" rel="nofollow">Python Packaging Authority</a></li><li><a href="https://ift.tt/2rtg6IK" title="PEP 517 -- A build-system independent format for source trees" rel="nofollow">PEP 517 -- A build-system independent format for source trees</a></li><li><a href="https://ift.tt/258Zzrc" title="PEP 518 -- Specifying Minimum Build System Requirements for Python Projects" rel="nofollow">PEP 518 -- Specifying Minimum Build System Requirements for Python Projects</a></li><li><a href="https://ift.tt/3dKqxMP" title="What the heck is pyproject.toml?" rel="nofollow">What the heck is pyproject.toml?</a></li><li><a href="https://ift.tt/2wlJRx1" title="Flit " rel="nofollow">Flit </a></li><li><a href="https://ift.tt/35nTF8g" title="Poetry" rel="nofollow">Poetry</a></li><li><a href="https://ift.tt/2bsy421" title="enscons" rel="nofollow">enscons</a></li><li><a href="https://ift.tt/2MghLaH" title="toml" rel="nofollow">toml</a></li><li><a href="https://ift.tt/31SNB5q" title="setuptools" rel="nofollow">setuptools</a></li><li><a href="https://ift.tt/1BQfmaq" title="distutils" rel="nofollow">distutils</a></li><li><a href="https://ift.tt/2x1I9lW" title="pip" rel="nofollow">pip</a></li><li><a href="https://ift.tt/2T5tEXJ" title="HTTPX" rel="nofollow">HTTPX</a></li></ul>

from Planet Python
via read more