Login
You're viewing the mastodon.coffee public feed.
  • arclightarclight@oldbytes.space
    Aug 19, 2026, 4:15 PM

    FYI for anyone getting spurious build failures on recent Python projectsv

    Apparently stripping out all license related fields from pyproject.toml and adding `project.license = 'LicenseRef-Other'` is the only way to get our projects to build without error.

    This has been a nagging problem for a few months and broke our ability to create release packages. It's amazing how simple the user notification could have been to resolve this self-inflicted problem without torching the entire Python user base's workflow but language and utility developer pique is the primary consideration in this ecosystem. There will be a new gratuitous breaking change to replace this soon enough.

    Anyway, hope this resolves someone's unexpected build failures.

    💬 3🔄 1⭐ 0

Replies

  • arclightarclight@oldbytes.space
    Aug 19, 2026, 7:08 PM

    In other news, I poked The Powers That Be to update `pip-tools` so `pip-compile` doesn't explode because of the PEP 517 issue, another piece of breakage I should never have to deal with. Tracking down the source and solution of this problem was not fun.

    💬 0🔄 0⭐ 0
  • Möbius the Ludditemoebius@oldbytes.space
    Aug 19, 2026, 5:03 PM

    @arclight I often have to build Python packages for Enterprise Linux distros. The way setuptools keeps changing this kind of metadata, without supporting the older formats for long enough, is such a pain to deal with. Because developers who do not themselves have to deploy as system packages on older systems are incentivized to just use the latest unnecessary format change ...

    💬 0🔄 0⭐ 0
  • AN/CRM-114flyingsaceur@ioc.exchange
    Aug 19, 2026, 6:32 PM

    @arclight every six months I try to figure out how to choose “All Rights Reserved” and my train of thought goes over a cliff and explodes like the end of BTTF3

    💬 0🔄 0⭐ 0