Drop implicit build support #6
Labels
Affects: Command Line
Affects the command line interface
Affects: Compatibility
Changes with compatibility implications
Affects: Python API
Affects the public Python API of the project
Category: Maintainability
Proposed improvement to project maintainability
Comments
ncoghlan
added
Affects: Python API
ncoghlan
added a commit
that referenced
this issue
Oct 28, 2024
The implicit build support adds a lot of complexity, while also being in inherently bad idea (the local wheel directory support is a much better approach). Closes #6
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The implicit build support isn't a good idea.
If external wheel builds are needed, it's much better to have a dedicated process for making those, and supply the results to
venvstacksvia the local wheel directory support, rather than havingvenvstackscreate them implicitly and rely onpipanduvcaching to carry them forward to future builds.The "local wheel directory" approach also allows for full from-source stack builds via https://github.com/python-wheel-build/fromager, even when a full-fledged internal package hosting server isn't available.
The text was updated successfully, but these errors were encountered: