-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
useless wheel files in plugin !? #1908
Comments
Give me the content of your |
my
I think because of this above line the wheel files (dependencies of coverage) are collected. |
I tried to build a plugin with "coverage" in the
Even if coverage is a "Requirement already satisfied [...] in /opt/metwork-mfext-2.2/opt/python3_devtools", the coverage dependencies (all are also "already satisfied") are collected into the "python3_virtualenv_sources/src/" directory of the plugin as wheel files.... but "coverage" itself is not embedded !?
Now if I build the same plugin without the layer python3_devtools, the coverage's wheel appears:
|
|
I recently migrated from metwork v2.1 to v2.2. So I rebuilt only the plugin with embedded python packages (
local/lib/python3.X/site-packages
) because of the python upgrade from v3.10 to v3.11. It seems useless to me to rebuild the others plugins.But into my plugin built in v2.1, in directory
python3_virtualenv_sources\src\
I found the wheel file:I do not understand why the wheel is embedded in the plugin whereas:
requirements-to-freeze.txt
local/lib/python3.X/site-packages
of the pluginWhat's the purpose of this wheel file into the plugin ?
So my plugin was working on metwork v2.1 and still working on v2.2 without any modification.
But if I install the plugin on metwork v2.2, I face the error caused by the useless wheel (I suppose):
The text was updated successfully, but these errors were encountered: