The manylinux project does not specify a way to record "environment set up" information required to build wheels from certain packages.
Some packages require that the stock manylinux environment be modified by installing system dependencies, setting environment variables, modifying the filesystem etc prior to building, or the building and bundling will fail. Currently, package authors capture this information in project specific documentation, or not at all. In the event that a wheel is not provided by the author, consumers that want a compiled distribution (users focused on reproducible builds, build efficiency) are required to locate this information in project specific documentation or do research on the internals of the package to gather this information themselves. Currently, package consumers can not easily modify or contribute to this data as it is not standardized. What are everyone's thoughts about adding a section to `pyproject.toml` to capture this information? This allows package consumers to easily find and contribute back to this data, and programs like installers, builders etc can read this data as well. Is this PEP-able or where could this best be contributed? I am interested in (and intend on) contributing to solving this problem if it is accepted as a good idea! Thank you for your input! Something like this: ```toml [manylinux1] system_dependencies: - foo-1.0.0 environment_variables: - FOO=BAR python_packages: - foo==1.0.0 ``` - Chris Antonellis _______________________________________________ Python-ideas mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-ideas.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/WPGI4LYOK4XHDSWFFFRIBBHNVZOKBGFT/ Code of Conduct: http://python.org/psf/codeofconduct/
