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:
- certifi-2022.12.7-py3-none-any.whl
I do not understand why the wheel is embedded in the plugin whereas:
- it is not mentionned in my
requirements-to-freeze.txt
- certifi is provided by metwork
- it is not installed in the
local/lib/python3.X/site-packages of the plugin
What'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 conflict is caused by:
The user requested certifi==2022.12.7
The user requested (constraint) certifi==2023.7.22
To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict
===== BASH STDERR ========================
ERROR: Cannot install certifi==2022.12.7 because these package versions have conflicting dependencies.
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.txtlocal/lib/python3.X/site-packagesof 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):