From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] FreeCAD fails since python 3.8.1
Date: Sun, 19 Jan 2020 21:20:28 +0100 [thread overview]
Message-ID: <20200119202028.wDAaxKI6QUKi23BzjFJd6LoO8Z2b52QyfgnHPOU3Yrc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18353@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 3066 bytes --]
Closed issue by yopito on void-packages repository
https://github.com/void-linux/void-packages/issues/18353
Description:
<!-- FreeCAD fails since python 3.8.1 -->
### System
* xuname: same traceback on both glibc and musl:
- `Void 5.4.12_1 x86_64 GenuineIntel uptodate rrFF`
- `Void 5.4.11_1 x86_64-musl GenuineIntel uptodate rrnFFF`
* packages:
* `freecad-0.18.4_2`
* `libpyside2-python3-5.11.2_3`
* `libshiboken2-5.11.2_4`
* `python3-3.8.1_1`
* `python3-pyside2-5.11.2_3`
* `qt5-5.13.2_2`
### Expected behavior
FreeCAD is usable and FreeCAD self-tests are fine too.
### Actual behavior
Launch self-tests for instance:
```
$ FreeCAD -t 0
FreeCAD 0.18.4, Libs: 0.18.4R2_voidlinux
© Juergen Riegel, Werner Mayer, Yorik van Havre 2001-2019
##### #### ### ####
# # # # # #
# ## #### #### # # # # #
#### # # # # # # # ##### # #
# # #### #### # # # # #
# # # # # # # # # ## ## ##
# # #### #### ### # # #### ## ## ##
No module named 'WebGui'
Traceback (most recent call last):
File "<string>", line 38, in <module>
File "/usr/lib/freecad/Mod/Test/TestApp.py", line 27, in <module>
import unittest
File "/usr/lib/python3.8/unittest/__init__.py", line 60, in <module>
from .async_case import IsolatedAsyncioTestCase
File "/usr/lib/python3.8/unittest/async_case.py", line 1, in <module>
import asyncio
File "/usr/lib/python3.8/asyncio/__init__.py", line 8, in <module>
from .base_events import *
File "/usr/lib/python3.8/asyncio/base_events.py", line 18, in <module>
import concurrent.futures
File "/usr/lib/python3.8/concurrent/futures/__init__.py", line 8, in <module>
from concurrent.futures._base import (FIRST_COMPLETED,
File "/usr/lib/python3.8/concurrent/futures/_base.py", line 7, in <module>
import logging
File "/usr/lib/python3.8/logging/__init__.py", line 28, in <module>
from string import Template
File "/usr/lib/python3.8/string.py", line 80, in <module>
class Template(metaclass=_TemplateMetaclass):
<class 'TypeError'>: 'Shiboken.ObjectType' object is not iterable
```
### Steps to reproduce the behavior
see command above
### Packaging constraints
* only pyside 5.14.0 supports python 3.8.1 (see [1])
* pyside 5.14.0 supports only Qt 5.14.0: Qt 5.13.2 is not supported, see [2]
* Qt 5.14 is not yet available in VoidLinux (PR #15310 in progress)
[1] https://bugreports.qt.io/browse/PYSIDE-939
[2] https://bugreports.qt.io/browse/PYSIDE-1191
### Ways to fix
1. wait for Qt 5.14.0 and pyside 5.14.0 in distribution ; in the meantime, FreeCAD is still broken
2. update pyside from 5.11 to 5.13.2 and remove all specificities of Qt 5.14 support from it : it will then support Qt 5.13.2 (last previous Qt revision).
Might be tricky to achieve and time consuming for a short-live workaround ?
Will be ready before Qt 5.14 ?
prev parent reply other threads:[~2020-01-19 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 22:48 [ISSUE] " voidlinux-github
2020-01-19 20:20 ` voidlinux-github [this message]
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=20200119202028.wDAaxKI6QUKi23BzjFJd6LoO8Z2b52QyfgnHPOU3Yrc@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).