On Sat, Jun 10, 2017, at 04:32 AM, Nick Coghlan wrote: > 1. Move all artifact naming responsibilities to the frontend. All > backend hooks would just write files in the defined format into the > directory supplied by the frontend (and those directories would have > no defined naming scheme - they're just a staging area for the backend > to pass content to the frontend)
If the 'make a wheel' hook needs to make an unpacked wheel, flit will probably implement this as building a wheel zip file, and then unpacking it into the target directory again. There isn't currently code for building an 'unpacked wheel', and I don't see any of this as performance criticial, since most users will be installing from a pre-built wheel anyway. This is OK if this is what we decide, but I wanted to highlight that at least in flit's case, there's no simplicity or performance benefit from asking for an unpacked wheel. > Assuming we add support for building multiple wheels from a single > source archive in the future, we'd do this through some kind of > declarative API based mechanism like adding a new optional > "wheel_name" parameter to `prepare_wheel_metadata` and > `export_wheel_content` (to tell the backend which wheel the frontend > is interested in), along with an additional field in [build-system] to > tell frontends which secondary wheels are defined by that project. This isn't really my area of expertise, but I would assume that we'd want to ask the backend to build all the wheels it knows about in one shot, not one-by-one. Thomas _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
