Extensions Platform: support bundling wheels (.whl) #119681

New Issue

Campbell Barton · 2024-03-20T01:11:41+01:00

Campbell Barton commented

2024-03-20 01:11:41 +01:00

Python developers often depend on Python modules from the Python package index: https://pypi.org, therefor it is important to provide a way for add-ons to depend on these packages.

This can be supported by bundling wheels (.whl files) which are a zipped module.

This task doesn't go into details about the rationale and is mainly to keep track of related tasks.

Initial wheel support:

An extension should be able to include a .whl file which is installed & available to that extension.
Shared wheels:

Multiple extensions must be able to share a wheel which is removed when none of the installed extensions depend on that wheel.
Handle version conflicts:

Since the wheels are shared in Python's main module name-space,
there is no practical way we can have both versions installed at once.

Installing an extension with a conflicting version will fail with an error.

Note that we could consider allowing an extension to specify a version range, to avoid hard-failing in the case of a version conflict.
Binary wheel support:

Support bundling multiple architectures in an extension, extracting the appropriate wheel for the target system.

Note that we might not need this if system-architecture is handled by optionally splitting a single extension by architecture.
Document the process of bundling wheels with an extension.

Python developers often depend on Python modules from the Python package index: https://pypi.org, therefor it is important to provide a way for add-ons to depend on these packages. This can be supported by bundling wheels (`.whl` files) which are a zipped module. This task doesn't go into details about the rationale and is mainly to keep track of related tasks. - [ ] Initial wheel support: An extension should be able to include a `.whl` file which is installed & available to that extension. - [ ] Shared wheels: Multiple extensions must be able to share a wheel which is removed when none of the installed extensions depend on that wheel. - [ ] Handle version conflicts: Since the wheels are shared in Python's main module name-space, there is no practical way we can have both versions installed at once. Installing an extension with a conflicting version will fail with an error. _Note that we could consider allowing an extension to specify a version range, to avoid hard-failing in the case of a version conflict._ - [ ] Binary wheel support: Support bundling multiple architectures in an extension, extracting the appropriate wheel for the target system. _Note that we might not need this if system-architecture is handled by optionally splitting a single extension by architecture._ - [ ] Document the process of bundling wheels with an extension.

❤️ 4

Campbell Barton added the

Type

To Do

label 2024-03-20 01:11:41 +01:00

Campbell Barton referenced this issue

2024-03-20 01:12:05 +01:00

Extensions Platform: beta launch #119521

Sign in to join this conversation.