On 22 Nov 2020, at 01:01, Greg Ewing greg.ewing@canterbury.ac.nz wrote:
On 21/11/20 3:59 pm, Christopher Barker wrote:
On Fri, Nov 20, 2020 at 4:18 PM Greg Ewing <greg.ewing@canterbury.ac.nz With venvs, it seems like it should be possible to have a very simple tool that just packages up everything in your venv.
conda is similar -- there is even the "conda constructor" that will build an installer for a conda environment that meets your specs. But the fact is that you get a LOT of extra stuff along with what you need.
My thinking is that you would only add things to the venv that your app needs, as and when you discover that they're needed. E.g. you wouldn't add the whole of PyObjC at once, just the submodules you use.
While this would be more work for the developer, it would allow the packaging tool to be far simpler and easier to maintain.
That would be nice to have, but there’s no incentive for developers of packages to do this. Splitting up (large) PyPI packages is work with no clear advantages and results in more work unless you develop the multiple packages in lock step (that is, treat it as a single project other than for the release artefacts on PyPI)
It is probably easier to develop a metadata standard that specifies how packages can be split up by app bundling tools.
Ronald
—
Twitter / micro.blog: @ronaldoussoren Blog: https://blog.ronaldoussoren.net/