Github messages for voidlinux
 help / color / mirror / Atom feed
From: oldlaptop <oldlaptop@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Uranium (and therefore cura) is broken with Python 3.12
Date: Sat, 21 Oct 2023 06:22:28 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46808@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]

New issue by oldlaptop on void-packages repository

https://github.com/void-linux/void-packages/issues/46808

Description:
### Is this a new report?

Yes

### System Info

Void 6.5.7_1 x86_64-musl AuthenticAMD notuptodate rrFFFFFF

### Package(s) Affected

Uranium-4.13.1_3 cura-4.13.1_3

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

cura should (presumably) launch.

### Actual behaviour

cura fails to launch with the following traceback:
```
$ cura
Traceback (most recent call last):
  File "/usr/bin/cura", line 27, in <module>
    from cura.CrashHandler import CrashHandler
  File "/usr/lib/python3.12/site-packages/cura/CrashHandler.py", line 29, in <module>
    from UM.Application import Application
  File "/usr/lib/python3.12/site-packages/UM/Application.py", line 9, in <module>
    from UM.Controller import Controller
  File "/usr/lib/python3.12/site-packages/UM/Controller.py", line 4, in <module>https://github.com/Ultimaker/Uranium/issues/765
    from UM.Scene.Scene import Scene
  File "/usr/lib/python3.12/site-packages/UM/Scene/Scene.py", line 13, in <module>
    from UM.Mesh.ReadMeshJob import ReadMeshJob  # To reload a mesh when its file was changed.
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.12/site-packages/UM/Mesh/ReadMeshJob.py", line 8, in <module>
    from UM.FileHandler.ReadFileJob import ReadFileJob
  File "/usr/lib/python3.12/site-packages/UM/FileHandler/ReadFileJob.py", line 5, in <module>
    from UM.FileHandler.FileHandler import FileHandler
  File "/usr/lib/python3.12/site-packages/UM/FileHandler/FileHandler.py", line 12, in <module>
    from UM.PluginRegistry import PluginRegistry
  File "/usr/lib/python3.12/site-packages/UM/PluginRegistry.py", line 4, in <module>
    import imp
ModuleNotFoundError: No module named 'imp'
```

The `imp` module was [removed in Python 3.12](https://docs.python.org/3.12/whatsnew/3.12.html#imp). It doesn't appear upstream has [fixed this yet](https://github.com/Ultimaker/Uranium/issues/765).

### Steps to reproduce

Install cura and attempt to launch it.

             reply	other threads:[~2023-10-21  4:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21  4:22 oldlaptop [this message]
2023-10-21 15:35 ` destructatron
2023-10-21 16:09 ` oldlaptop
2023-10-27 11:57 ` Vinfall
2023-11-03 16:22 ` zlice
2023-11-03 17:16 ` zlice
2023-11-03 17:22 ` zlice
2023-11-03 21:59 ` zlice
2024-05-23  0:19 ` haunma
2024-05-23  2:47 ` zlice
2024-05-23 13:39 ` karl-nilsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46808@inbox.vuxu.org \
    --to=oldlaptop@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).