admin管理员组文章数量:1321057
Is there a canonical way to ensure no build files (temporary or otherwise) are written to the project area when I build?
When I do a python -m build --wheel
for example, I see a build
and dist
directory with various build artifacts.
I tackled this issue a while back and it involved writing custom bdist_wheel, egg_info, and build commands in setup.py (and then overriding the initialize_options) but I have tried this method and my redirects are being ignored.
It seems like these days the build system is calling build_meta backend which is building in the project area without checking the options.
I know I can pass --outdir
to the build command but my build process requires a directory to be generated on the fly so I can't use this unless I write a build script and bypass setup.py and build entirely.
What is the modern way to handle this?
本文标签: Controlling build directories for python wheel buildingStack Overflow
版权声明:本文标题:Controlling build directories for python wheel building - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1742092657a2420360.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论