https://hackmd.io/@pradyunsg/pycon2024-pack-summit Arbitrary package metadata: the key to enabling smaller binaries (Michael Sarahan + Ethan Smith) Slides: bit.ly/pycon-packaging-metadata-2024 Q&A / Discussion Q: Clarification on the use of the word "environment"A: Is less the physical package environment and more the way you pass that around to other people, i.e. a "lock file"Followup: Environment is a very overloaded term, maybe we need a better semantic? Not getting down to the details of an environment?A: Talking about the spec, how do you provide instructions to an installer to install package. Q: Re: tags, if you don't want to put the burden on PyPA maintainers, do you want an approval process or is it anything goes?

I'm trying to list out questions that an audience, that is new to Sphinx, might have. This is roughly based on the audiences we've identified so far in a GitHub issue discussion. Please don't try to answer the questions listed here, that's not what this document is trying to do. Instead, we're trying to figure out roughly the kinds of questions those audiences would ask. Having this list can help us figure out whether our existing documentation makes it easy to answer them, to identify gaps and figure out changes accordingly. To be clear, not all of these questions would need to be answered in a beginner tutorial. Instead, these are roughly "broad" questions that nearly everyone in that audience would have. We'll (maybe) think about some "user journey" for each of these audiences later. If you want to: