Description of problem: PySide supports Python 3 since 1.0.1, but Mageia ships PySide 1.2.1 only for Python 2.7. Python 3 has been out for quite a while already, so why not ship PySide support for it? Version-Release number of selected component (if applicable): 1.2.1-3 How reproducible: 100% Steps to Reproduce: 1. Install pyside package 2. Try to import PySide in python 3 3. Result: ImportError: No module named 'PySide' Reproducible: Steps to Reproduce:
Hardware: i586 => x86_64
for python3-pyside, we first need python3-shiboken
CC: (none) => makowski.mageia
python3-pyside and python3-shiboken (need to build python3-pyside) are in Cauldron (mga5). I let the maintainer backport it to mga4 if needed.
Assignee: bugsquad => shikamaru
CC: makowski.mageia => (none)
(In reply to Philippe Makowski from comment #2) > python3-pyside and python3-shiboken (need to build python3-pyside) are in > Cauldron (mga5). > I let the maintainer backport it to mga4 if needed. The maintainer went MIA, assigning back to Bug Squad
CC: (none) => marja11Assignee: shikamaru => bugsquad
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: NEW => RESOLVEDResolution: (none) => OLD