Python plugin is broken in core24 #4942
Labels
Comments
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/CRAFT-3162.
|
tigarmo
added a commit
that referenced
this issue
Jul 31, 2024
Changes to virtual environment handling made our default approach - creating a venv in the build system and then just moving it into the snap - not work for Python 3.12. My understanding of the issue is that the "home" key in the "pyvenv.cfg" file points to a path in the build system, which obviously does not exist at snap-run-time. This apparently works fine *somehow* in core22 - likely there's some fallback logic that makes the interpreter correctly find the bundled Python libraries, but not in core24. So to address this we update this "home" key to point to its final destination in the snap. Fixes #4942
4 tasks
tigarmo
added a commit
that referenced
this issue
Jul 31, 2024
Changes to virtual environment handling made our default approach - creating a venv in the build system and then just moving it into the snap - not work for Python 3.12. My understanding of the issue is that the "home" key in the "pyvenv.cfg" file points to a path in the build system, which obviously does not exist at snap-run-time. This apparently works fine *somehow* in core22 - likely there's some fallback logic that makes the interpreter correctly find the bundled Python libraries, but not in core24. So to address this we update this "home" key to point to its final destination in the snap. Fixes #4942
tigarmo
added a commit
that referenced
this issue
Jul 31, 2024
Changes to virtual environment handling made our default approach - creating a venv in the build system and then just moving it into the snap - not work for Python 3.12. My understanding of the issue is that the "home" key in the "pyvenv.cfg" file points to a path in the build system, which obviously does not exist at snap-run-time. This apparently works fine *somehow* in core22 - likely there's some fallback logic that makes the interpreter correctly find the bundled Python libraries, but not in core24. So to address this we update this "home" key to point to its final destination in the snap. Fixes #4942
|
Fixed in #4946 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
See https://forum.snapcraft.io/t/upgrading-classic-snap-to-core24-using-snapcraft-8-3-causes-python-3-12-errors-at-runtime/41045
In short, it looks like the changes to virtual environments in Python 3.12 are not working with the python plugin.
To Reproduce
.
Environment
.
snapcraft.yaml
.Relevant log output
.Additional context
We still need confirmation but this fix should work and is feasible for us.
The text was updated successfully, but these errors were encountered: