You are not logged in.

#1 2012-01-25 02:18:41

arlx_ignacy
Member
Registered: 2011-07-13
Posts: 12

Review my PySide (python 3) package

Hello, I noticed that PySide AUR packages still uses Python 2. Since I cant find their Python 3 counterpart, I might just use it as an opportunity to build my own packages.

This is my first time writing an AUR package, so please review them and give me your thoughts on my work so far.

- - - EDIT - - -

Thank you for trying out in my package, the latest version can be found at my repository:

I'll try to answer any question as fast as I can. Please keep in mind that I cant login to ArchLinux forum regularly at this time, so I might be a little bit late (or maybe waaay too late) to respond if you have any issue. I usually push my changes to bitbucket before going to bed, so people should just check for new commits at my repository instead of posts from me in this thread.

Thank you.

Last edited by arlx_ignacy (2012-09-06 12:16:44)

Offline

#2 2012-01-25 17:26:26

Giniu
Trusted User (TU)
From: Wrocław/Poland
Registered: 2007-04-02
Posts: 61
Website

Re: Review my PySide (python 3) package

I'd say go with naming used almost everywhere in Arch for python packages - I'd say python-pyside and python2-pyside - there is no need to cause any more confusion than there is now (which - again in my opinion - pyqt is part of - I still don't agree with decision that python2-pyqt depends on python 3, this is only reason why I need python package, I'd rather live with single python and this is python2 in my case, but I learned to live with things I don't like)

Also in my opinion, it would be good if both pyside and pyqt provided some virtual package like python-qt and python2-qt, because there are lots of python applications that can work with both both PyQT and PySide just as well and pick one dynamically, so it would be good to put python2-qt into dependencies and let user decide if he wants python2-pyqt or python2-pyside in those cases. But this is more general rambling, my only comment to this particular pyside package is the name really.


My GPG fingerprint: 7170 26A9 D477 9FC5 3940  7266 40F5 57B7 3149 6106

Offline

#3 2012-01-25 19:11:45

msquared
Member
From: Heidelberg, DE
Registered: 2008-05-28
Posts: 3

Re: Review my PySide (python 3) package

From my point of view the only thing to remark is that the original author should get the credits at least as "Contributor". Taking the package, modifying it slighty and publishing it without any reference to the original (inside), can be considered as not fair.
Anyway I am in contact with an developer for integration into [community]. So, stay tuned for an update.

Matthias

Offline

#4 2012-01-25 20:07:23

stefanwilkens
Member
From: Enschede, the Netherlands
Registered: 2008-12-10
Posts: 624

Re: Review my PySide (python 3) package

You might consider changing this:
source=('http://www.pyside.org/files/shiboken-1.1.0.tar.bz2')

to this:
source=(http://www.pyside.org/files/shiboken-$pkgver.tar.bz2)

The same applies to the other PKGBUILDs. This way, version bumping the PKGBUILD will only involve changing the variable definitions. This is fairly common practice.

/usr/bin/python also links to the latest 3.x by default on Arch, I'm not sure is specifically using /usr/bin/python3.2 is the best way to approach this. It would require maintenance as python gets upgraded or if users use specific other versions of python 3.x.

Last edited by stefanwilkens (2012-01-25 20:08:29)


Arch i686 on Phenom X4 | GTX760

Offline

#5 2012-01-26 01:27:37

arlx_ignacy
Member
Registered: 2011-07-13
Posts: 12

Re: Review my PySide (python 3) package

Giniu wrote:

I'd say go with naming used almost everywhere in Arch for python packages - I'd say python-pyside and python2-pyside - there is no need to cause any more confusion than there is now (which - again in my opinion - pyqt is part of - I still don't agree with decision that python2-pyqt depends on python 3, this is only reason why I need python package, I'd rather live with single python and this is python2 in my case, but I learned to live with things I don't like)

Okay, I'll change the naming into python-libshiboken, python-pyside, python-pyside-tools, and python-shibokengenerator.



msquared wrote:

From my point of view the only thing to remark is that the original author should get the credits at least as "Contributor". Taking the package, modifying it slighty and publishing it without any reference to the original (inside), can be considered as not fair.
Anyway I am in contact with an developer for integration into [community]. So, stay tuned for an update.

Matthias

Agreed, I've taken your work as reference and it is fair to put your name (and/or mtorromeo).

However this is just a review for my first package, I haven't put it on AUR yet (I dont even have any package under my name) so this is more like a preview. big_smile

If it *doesn't work* I dont want the reviewer/anyone to bother *you* on something that you dont even know existed, and if it *does work* as intended I'll put your name as credit.



stefanwilkens wrote:

You might consider changing this:
source=('http://www.pyside.org/files/shiboken-1.1.0.tar.bz2')

to this:
source=(http://www.pyside.org/files/shiboken-$pkgver.tar.bz2)

The same applies to the other PKGBUILDs. This way, version bumping the PKGBUILD will only involve changing the variable definitions. This is fairly common practice.

Okay, I'll do that.

stefanwilkens wrote:

/usr/bin/python also links to the latest 3.x by default on Arch, I'm not sure is specifically using /usr/bin/python3.2 is the best way to approach this. It would require maintenance as python gets upgraded or if users use specific other versions of python 3.x.

Alright, I'll change the

_pyver=3.2

to

_pyver=3

Thanks.

Offline

#6 2012-01-28 23:32:46

arlx_ignacy
Member
Registered: 2011-07-13
Posts: 12

Re: Review my PySide (python 3) package

I've put an update on my PKGBUILDs to allow Python 3 version of PySide to co-exist with its Python 2 version.

Offline

#7 2012-02-14 19:19:48

andre.vmatos
Member
Registered: 2010-07-28
Posts: 19

Re: Review my PySide (python 3) package

Hi.
Thanks very much for this effort, since I was waiting for a pyside python3 capable pkgbuild.
From hg repository, python-shibokengenerator and python-libshiboken compiled fine. But python-pyside package failed in make with the following error:

.
.
.
[ 54%] Building CXX object PySide/QtGui/CMakeFiles/QtGui.dir/PySide/QtGui/qtexttablecellformat_wrapper.cpp.o
[ 54%] Building CXX object PySide/QtGui/CMakeFiles/QtGui.dir/PySide/QtGui/qtexttablecell_wrapper.cpp.o
[ 54%] Building CXX object PySide/QtGui/CMakeFiles/QtGui.dir/PySide/QtGui/qtexttableformat_wrapper.cpp.o
In file included from /sec/Dev/PKGBUILDs/pyside_aur/python-pyside/src/build/PySide/QtGui/PySide/QtGui/qtexttableformat_wrapper.cpp:36:0:
/sec/Dev/PKGBUILDs/pyside_aur/python-pyside/src/build/PySide/QtGui/PySide/QtGui/pyside_qtgui_python.h: In function ‘PyTypeObject* Shiboken::SbkType() [with T = QStyleOptionButton, PyTypeObject = _typeobject]’:
/sec/Dev/PKGBUILDs/pyside_aur/python-pyside/src/build/PySide/QtGui/PySide/QtGui/pyside_qtgui_python.h:1181:65: internal compiler error: Falha de segmentação
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
make[2]: ** [PySide/QtGui/CMakeFiles/QtGui.dir/PySide/QtGui/qtexttableformat_wrapper.cpp.o] Erro 1
make[1]: ** [PySide/QtGui/CMakeFiles/QtGui.dir/all] Erro 2
make: ** [all] Erro 2

Can you help fixing it? Thnx again

Offline

#8 2012-02-15 15:06:05

andre.vmatos
Member
Registered: 2010-07-28
Posts: 19

Re: Review my PySide (python 3) package

Hi.
Trying to compile again, but now with pyside for python2 (from aur) installed, python-pyside compiled fine. But, the python libraries were installed into /usr/lib/python2.7. Follow content of package:

[root@midichlorian python-pyside #] tar -tf python-pyside-1.1.0-1-x86_64.pkg.tar.xz 
.PKGINFO
usr/
usr/include/
usr/lib/
usr/share/
usr/share/PySide-py3/
usr/share/PySide-py3/typesystems/
usr/share/PySide-py3/typesystems/typesystem_help.xml
usr/share/PySide-py3/typesystems/typesystem_core_mac.xml
usr/share/PySide-py3/typesystems/typesystem_webkit.xml
usr/share/PySide-py3/typesystems/typesystem_opengl.xml
usr/share/PySide-py3/typesystems/typesystem_xml.xml
usr/share/PySide-py3/typesystems/typesystem_gui_win.xml
usr/share/PySide-py3/typesystems/typesystem_core_win.xml
usr/share/PySide-py3/typesystems/typesystem_gui.xml
usr/share/PySide-py3/typesystems/typesystem_webkit_simulator.xml
usr/share/PySide-py3/typesystems/typesystem_core_common.xml
usr/share/PySide-py3/typesystems/typesystem_svg.xml
usr/share/PySide-py3/typesystems/typesystem_test.xml
usr/share/PySide-py3/typesystems/typesystem_gui_x11.xml
usr/share/PySide-py3/typesystems/typesystem_phonon.xml
usr/share/PySide-py3/typesystems/typesystem_gui_simulator.xml
usr/share/PySide-py3/typesystems/typesystem_network.xml
usr/share/PySide-py3/typesystems/typesystem_declarative.xml
usr/share/PySide-py3/typesystems/typesystem_core_x11.xml
usr/share/PySide-py3/typesystems/typesystem_core.xml
usr/share/PySide-py3/typesystems/typesystem_core_maemo.xml
usr/share/PySide-py3/typesystems/typesystem_sql.xml
usr/share/PySide-py3/typesystems/typesystem_scripttools.xml
usr/share/PySide-py3/typesystems/typesystem_gui_maemo.xml
usr/share/PySide-py3/typesystems/typesystem_multimedia.xml
usr/share/PySide-py3/typesystems/typesystem_gui_mac.xml
usr/share/PySide-py3/typesystems/typesystem_templates.xml
usr/share/PySide-py3/typesystems/typesystem_uitools.xml
usr/share/PySide-py3/typesystems/typesystem_xmlpatterns.xml
usr/share/PySide-py3/typesystems/typesystem_gui_common.xml
usr/share/PySide-py3/typesystems/typesystem_script.xml
usr/lib/libpyside-py3-python2.7.so.1.1.0
usr/lib/cmake/
usr/lib/libpyside-py3-python2.7.so
usr/lib/pkgconfig/
usr/lib/python2.7/
usr/lib/libpyside-py3-python2.7.so.1.1
usr/lib/python2.7/site-packages/
usr/lib/python2.7/site-packages/PySide/
usr/lib/python2.7/site-packages/PySide/phonon.so
usr/lib/python2.7/site-packages/PySide/QtUiTools.so
usr/lib/python2.7/site-packages/PySide/QtXml.so
usr/lib/python2.7/site-packages/PySide/QtMultimedia.so
usr/lib/python2.7/site-packages/PySide/QtScript.so
usr/lib/python2.7/site-packages/PySide/QtSvg.so
usr/lib/python2.7/site-packages/PySide/QtScriptTools.so
usr/lib/python2.7/site-packages/PySide/QtGui.so
usr/lib/python2.7/site-packages/PySide/__init__.py
usr/lib/python2.7/site-packages/PySide/QtNetwork.so
usr/lib/python2.7/site-packages/PySide/QtXmlPatterns.so
usr/lib/python2.7/site-packages/PySide/QtDeclarative.so
usr/lib/python2.7/site-packages/PySide/QtCore.so
usr/lib/python2.7/site-packages/PySide/QtHelp.so
usr/lib/python2.7/site-packages/PySide/QtTest.so
usr/lib/python2.7/site-packages/PySide/QtWebKit.so
usr/lib/python2.7/site-packages/PySide/QtOpenGL.so
usr/lib/python2.7/site-packages/PySide/QtSql.so
usr/lib/pkgconfig/pyside-py3.pc
usr/lib/cmake/PySide-py3-1.1.0/
usr/lib/cmake/PySide-py3-1.1.0/PySideConfig.cmake
usr/lib/cmake/PySide-py3-1.1.0/PySideConfig-python2.7.cmake
usr/lib/cmake/PySide-py3-1.1.0/PySideConfigVersion.cmake
usr/include/PySide-py3/
usr/include/PySide-py3/QtGui/
usr/include/PySide-py3/QtNetwork/
usr/include/PySide-py3/pysidemetafunction.h
usr/include/PySide-py3/dynamicqmetaobject.h
usr/include/PySide-py3/phonon/
usr/include/PySide-py3/pysideconversions.h
usr/include/PySide-py3/QtXmlPatterns/
usr/include/PySide-py3/pysideweakref.h
usr/include/PySide-py3/pysidemacros.h
usr/include/PySide-py3/QtCore/
usr/include/PySide-py3/QtDeclarative/
usr/include/PySide-py3/QtScriptTools/
usr/include/PySide-py3/destroylistener.h
usr/include/PySide-py3/pysideproperty.h
usr/include/PySide-py3/QtMultimedia/
usr/include/PySide-py3/QtSvg/
usr/include/PySide-py3/QtScript/
usr/include/PySide-py3/QtWebKit/
usr/include/PySide-py3/pyside.h
usr/include/PySide-py3/globalreceiver.h
usr/include/PySide-py3/QtOpenGL/
usr/include/PySide-py3/QtHelp/
usr/include/PySide-py3/pysidesignal.h
usr/include/PySide-py3/pysideqflags.h
usr/include/PySide-py3/pyside_global.h
usr/include/PySide-py3/QtUiTools/
usr/include/PySide-py3/signalmanager.h
usr/include/PySide-py3/QtXml/
usr/include/PySide-py3/pysideclassinfo.h
usr/include/PySide-py3/QtSql/
usr/include/PySide-py3/QtTest/
usr/include/PySide-py3/QtTest/pyside_qttest_python.h
usr/include/PySide-py3/QtSql/pyside_qtsql_python.h
usr/include/PySide-py3/QtXml/pyside_qtxml_python.h
usr/include/PySide-py3/QtUiTools/pyside_qtuitools_python.h
usr/include/PySide-py3/QtHelp/pyside_qthelp_python.h
usr/include/PySide-py3/QtOpenGL/pyside_qtopengl_python.h
usr/include/PySide-py3/QtWebKit/pyside_qtwebkit_python.h
usr/include/PySide-py3/QtScript/pyside_qtscript_python.h
usr/include/PySide-py3/QtSvg/pyside_qtsvg_python.h
usr/include/PySide-py3/QtMultimedia/pyside_qtmultimedia_python.h
usr/include/PySide-py3/QtScriptTools/pyside_qtscripttools_python.h
usr/include/PySide-py3/QtDeclarative/pyside_qtdeclarative_python.h
usr/include/PySide-py3/QtCore/pyside_qtcore_python.h
usr/include/PySide-py3/QtXmlPatterns/pyside_qtxmlpatterns_python.h
usr/include/PySide-py3/phonon/pyside_phonon_python.h
usr/include/PySide-py3/QtNetwork/pyside_qtnetwork_python.h
usr/include/PySide-py3/QtGui/pyside_qtgui_python.h
usr/include/PySide-py3/QtGui/qpytextobject.h

Thnx again.

Offline

#9 2012-02-23 11:40:29

arlx_ignacy
Member
Registered: 2011-07-13
Posts: 12

Re: Review my PySide (python 3) package

First I'm sorry for the late reply, I'm one of those (rare) people who check their e-mails once every two week or so.

andre.vmatos wrote:

Hi.
Thanks very much for this effort, since I was waiting for a pyside python3 capable pkgbuild.
From hg repository, python-shibokengenerator and python-libshiboken compiled fine. But python-pyside package failed in make with the following error:

.
.
.
[ 54%] Building CXX object PySide/QtGui/CMakeFiles/QtGui.dir/PySide/QtGui/qtexttablecellformat_wrapper.cpp.o
[ 54%] Building CXX object PySide/QtGui/CMakeFiles/QtGui.dir/PySide/QtGui/qtexttablecell_wrapper.cpp.o
[ 54%] Building CXX object PySide/QtGui/CMakeFiles/QtGui.dir/PySide/QtGui/qtexttableformat_wrapper.cpp.o
In file included from /sec/Dev/PKGBUILDs/pyside_aur/python-pyside/src/build/PySide/QtGui/PySide/QtGui/qtexttableformat_wrapper.cpp:36:0:
/sec/Dev/PKGBUILDs/pyside_aur/python-pyside/src/build/PySide/QtGui/PySide/QtGui/pyside_qtgui_python.h: In function ‘PyTypeObject* Shiboken::SbkType() [with T = QStyleOptionButton, PyTypeObject = _typeobject]’:
/sec/Dev/PKGBUILDs/pyside_aur/python-pyside/src/build/PySide/QtGui/PySide/QtGui/pyside_qtgui_python.h:1181:65: internal compiler error: Falha de segmentação
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
make[2]: ** [PySide/QtGui/CMakeFiles/QtGui.dir/PySide/QtGui/qtexttableformat_wrapper.cpp.o] Erro 1
make[1]: ** [PySide/QtGui/CMakeFiles/QtGui.dir/all] Erro 2
make: ** [all] Erro 2

Can you help fixing it? Thnx again

As for your problem, I cannot re-produce this. I just remove my python-shiboken* + python-pyside* packages, rebuild them using AUR scripts from my bitbucket, and I manage to install them (yet again) successfully. Please provide more detail on your system.

andre.vmatos wrote:

Hi.
Trying to compile again, but now with pyside for python2 (from aur) installed, python-pyside compiled fine. But, the python libraries were installed into /usr/lib/python2.7. Follow content of package:

[root@midichlorian python-pyside #] tar -tf python-pyside-1.1.0-1-x86_64.pkg.tar.xz 
.PKGINFO
usr/
usr/include/
usr/lib/
usr/share/
usr/share/PySide-py3/
usr/share/PySide-py3/typesystems/
usr/share/PySide-py3/typesystems/typesystem_help.xml
usr/share/PySide-py3/typesystems/typesystem_core_mac.xml
usr/share/PySide-py3/typesystems/typesystem_webkit.xml
usr/share/PySide-py3/typesystems/typesystem_opengl.xml
usr/share/PySide-py3/typesystems/typesystem_xml.xml
usr/share/PySide-py3/typesystems/typesystem_gui_win.xml
usr/share/PySide-py3/typesystems/typesystem_core_win.xml
usr/share/PySide-py3/typesystems/typesystem_gui.xml
usr/share/PySide-py3/typesystems/typesystem_webkit_simulator.xml
usr/share/PySide-py3/typesystems/typesystem_core_common.xml
usr/share/PySide-py3/typesystems/typesystem_svg.xml
usr/share/PySide-py3/typesystems/typesystem_test.xml
usr/share/PySide-py3/typesystems/typesystem_gui_x11.xml
usr/share/PySide-py3/typesystems/typesystem_phonon.xml
usr/share/PySide-py3/typesystems/typesystem_gui_simulator.xml
usr/share/PySide-py3/typesystems/typesystem_network.xml
usr/share/PySide-py3/typesystems/typesystem_declarative.xml
usr/share/PySide-py3/typesystems/typesystem_core_x11.xml
usr/share/PySide-py3/typesystems/typesystem_core.xml
usr/share/PySide-py3/typesystems/typesystem_core_maemo.xml
usr/share/PySide-py3/typesystems/typesystem_sql.xml
usr/share/PySide-py3/typesystems/typesystem_scripttools.xml
usr/share/PySide-py3/typesystems/typesystem_gui_maemo.xml
usr/share/PySide-py3/typesystems/typesystem_multimedia.xml
usr/share/PySide-py3/typesystems/typesystem_gui_mac.xml
usr/share/PySide-py3/typesystems/typesystem_templates.xml
usr/share/PySide-py3/typesystems/typesystem_uitools.xml
usr/share/PySide-py3/typesystems/typesystem_xmlpatterns.xml
usr/share/PySide-py3/typesystems/typesystem_gui_common.xml
usr/share/PySide-py3/typesystems/typesystem_script.xml
usr/lib/libpyside-py3-python2.7.so.1.1.0
usr/lib/cmake/
usr/lib/libpyside-py3-python2.7.so
usr/lib/pkgconfig/
usr/lib/python2.7/
usr/lib/libpyside-py3-python2.7.so.1.1
usr/lib/python2.7/site-packages/
usr/lib/python2.7/site-packages/PySide/
usr/lib/python2.7/site-packages/PySide/phonon.so
usr/lib/python2.7/site-packages/PySide/QtUiTools.so
usr/lib/python2.7/site-packages/PySide/QtXml.so
usr/lib/python2.7/site-packages/PySide/QtMultimedia.so
usr/lib/python2.7/site-packages/PySide/QtScript.so
usr/lib/python2.7/site-packages/PySide/QtSvg.so
usr/lib/python2.7/site-packages/PySide/QtScriptTools.so
usr/lib/python2.7/site-packages/PySide/QtGui.so
usr/lib/python2.7/site-packages/PySide/__init__.py
usr/lib/python2.7/site-packages/PySide/QtNetwork.so
usr/lib/python2.7/site-packages/PySide/QtXmlPatterns.so
usr/lib/python2.7/site-packages/PySide/QtDeclarative.so
usr/lib/python2.7/site-packages/PySide/QtCore.so
usr/lib/python2.7/site-packages/PySide/QtHelp.so
usr/lib/python2.7/site-packages/PySide/QtTest.so
usr/lib/python2.7/site-packages/PySide/QtWebKit.so
usr/lib/python2.7/site-packages/PySide/QtOpenGL.so
usr/lib/python2.7/site-packages/PySide/QtSql.so
usr/lib/pkgconfig/pyside-py3.pc
usr/lib/cmake/PySide-py3-1.1.0/
usr/lib/cmake/PySide-py3-1.1.0/PySideConfig.cmake
usr/lib/cmake/PySide-py3-1.1.0/PySideConfig-python2.7.cmake
usr/lib/cmake/PySide-py3-1.1.0/PySideConfigVersion.cmake
usr/include/PySide-py3/
usr/include/PySide-py3/QtGui/
usr/include/PySide-py3/QtNetwork/
usr/include/PySide-py3/pysidemetafunction.h
usr/include/PySide-py3/dynamicqmetaobject.h
usr/include/PySide-py3/phonon/
usr/include/PySide-py3/pysideconversions.h
usr/include/PySide-py3/QtXmlPatterns/
usr/include/PySide-py3/pysideweakref.h
usr/include/PySide-py3/pysidemacros.h
usr/include/PySide-py3/QtCore/
usr/include/PySide-py3/QtDeclarative/
usr/include/PySide-py3/QtScriptTools/
usr/include/PySide-py3/destroylistener.h
usr/include/PySide-py3/pysideproperty.h
usr/include/PySide-py3/QtMultimedia/
usr/include/PySide-py3/QtSvg/
usr/include/PySide-py3/QtScript/
usr/include/PySide-py3/QtWebKit/
usr/include/PySide-py3/pyside.h
usr/include/PySide-py3/globalreceiver.h
usr/include/PySide-py3/QtOpenGL/
usr/include/PySide-py3/QtHelp/
usr/include/PySide-py3/pysidesignal.h
usr/include/PySide-py3/pysideqflags.h
usr/include/PySide-py3/pyside_global.h
usr/include/PySide-py3/QtUiTools/
usr/include/PySide-py3/signalmanager.h
usr/include/PySide-py3/QtXml/
usr/include/PySide-py3/pysideclassinfo.h
usr/include/PySide-py3/QtSql/
usr/include/PySide-py3/QtTest/
usr/include/PySide-py3/QtTest/pyside_qttest_python.h
usr/include/PySide-py3/QtSql/pyside_qtsql_python.h
usr/include/PySide-py3/QtXml/pyside_qtxml_python.h
usr/include/PySide-py3/QtUiTools/pyside_qtuitools_python.h
usr/include/PySide-py3/QtHelp/pyside_qthelp_python.h
usr/include/PySide-py3/QtOpenGL/pyside_qtopengl_python.h
usr/include/PySide-py3/QtWebKit/pyside_qtwebkit_python.h
usr/include/PySide-py3/QtScript/pyside_qtscript_python.h
usr/include/PySide-py3/QtSvg/pyside_qtsvg_python.h
usr/include/PySide-py3/QtMultimedia/pyside_qtmultimedia_python.h
usr/include/PySide-py3/QtScriptTools/pyside_qtscripttools_python.h
usr/include/PySide-py3/QtDeclarative/pyside_qtdeclarative_python.h
usr/include/PySide-py3/QtCore/pyside_qtcore_python.h
usr/include/PySide-py3/QtXmlPatterns/pyside_qtxmlpatterns_python.h
usr/include/PySide-py3/phonon/pyside_phonon_python.h
usr/include/PySide-py3/QtNetwork/pyside_qtnetwork_python.h
usr/include/PySide-py3/QtGui/pyside_qtgui_python.h
usr/include/PySide-py3/QtGui/qpytextobject.h

Thnx again.

I see you are running as root, I dont know if this related to the problem.. maybe you should try running makepkg as normal user?

As for the files .. they are going to the right locations. It seems your system uses Python 2 modules (usr/lib/libpyside-py3-python2.7.so) when building pyside, this should not happen if python-shibokengenerator installed.
Are you sure you have python-shibokengenerator and python-libshiboken installed before building python-pyside? Most likely the cmake failed to detect your python 3 module. If you have python-shibokengenerator (which uses Python 3) installed it will tell cmake to use your python 3 interpreter.

As a comparision, this is how I install my pyside packages:

  1. build python-shibokengenerator

  2. build python-libshiboken

  3. install python-shibokengenerator

  4. install python-libshiboken

  5. build python-pyside

  6. install python-pyside

  7. build python-pyside-tools

  8. install python-pyside-tools


Thanks.

Offline

#10 2012-03-02 18:14:02

andre.vmatos
Member
Registered: 2010-07-28
Posts: 19

Re: Review my PySide (python 3) package

Ahh, thanks very much. Worked fine here.
If python2 packages (libshiboken, shibokengenerator) are installed, even if python3 also, python-pyside compile with python2 support only. But, uninstalling python2 packages, python-pyside compiled with python3 support fine.
Thanks for the help.

Offline

#11 2012-06-27 08:16:21

sagattarii
Member
Registered: 2008-11-10
Posts: 18

Re: Review my PySide (python 3) package

Nice packages, working fine here. Maybe add them to the AUR? Python3 should be now default for new projects, same as PySide instead of PyQt (Larger, community driven development, better licence) maybe it will hit extra some day...

Offline

#12 2012-08-14 12:43:57

NekySerbia
Member
Registered: 2008-01-12
Posts: 40

Re: Review my PySide (python 3) package

How would I download your package?

Offline

#13 2012-09-06 12:03:26

arlx_ignacy
Member
Registered: 2011-07-13
Posts: 12

Re: Review my PySide (python 3) package

Apologies everyone, I'm sorry for not being able to visit this forum regularly.

sagattarii wrote:

Nice packages, working fine here. Maybe add them to the AUR? Python3 should be now default for new projects, same as PySide instead of PyQt (Larger, community driven development, better licence) maybe it will hit extra some day...

Yes maybe I'll do that now.

NekySerbia wrote:

How would I download your package?

Sorry the first post is a bit outdated, I'm going to update it soon. To get the latest version of this AUR package you can go to the repository:

or, if you just want to download it you can grab a zip or tar file from:

You can find the instructions to build it, written in broken English (sorry roll), at the repository wiki.

Offline

#14 2012-09-08 04:15:51

arlx_ignacy
Member
Registered: 2011-07-13
Posts: 12

Re: Review my PySide (python 3) package

For people who interested, last night I just update my PKGBUILD to compile and install PySide 1.1.2 (codenamed "Alaursa") on ArchLinux's Python 2 and Python 3. Strangely the PySide guys have 1.1.2 announced on the mailing list since August but as of today the website still says 1.1.1 as latest release. hmm

Offline

#15 2012-09-14 00:51:40

andre.vmatos
Member
Registered: 2010-07-28
Posts: 19

Re: Review my PySide (python 3) package

Hi. Can you, please, update pyside-tools to 0.2.14? Changing only pkgver and md5, failed at patching.
Thanks

Offline

#16 2012-09-14 07:05:56

arlx_ignacy
Member
Registered: 2011-07-13
Posts: 12

Re: Review my PySide (python 3) package

Ah...! I'm sorry I missed that, the PySide download page uses "0.2.13" as the link label, it seems they also forgot to update the symbolic link for pyside-tools-latest.tar.bz2 to pyside-tools-0.2.14.tar.bz2. Probably the PySide.org website administrator/operator is absent or something because there is so little information (or hints) about this release outside the mailing list.

Anyway, I just update the PKGBUILD for pyside-tools 0.2.14 .

Offline

#17 2012-10-02 08:58:09

yodermk
Member
Registered: 2012-07-17
Posts: 58

Re: Review my PySide (python 3) package

Thanks much, I need this myself. Unfortunately, for pyside:

-- Found Qt4: /usr/bin/qmake (found suitable version "4.8.3", required is "4.5.0") 
-- Detected OS: x11
CMake Error at CMakeLists.txt:148 (message):
  Could not detect Python module installation directory.


-- Configuring incomplete, errors occurred!
==> ERROR: A failure occurred in package_python2-pyside().
    Aborting...

Anyone know how to get around this?

Offline

#18 2012-10-08 09:47:23

yodermk
Member
Registered: 2012-07-17
Posts: 58

Re: Review my PySide (python 3) package

All right, I got it! Turns out it was barfing on an old compilation I had. I thought I had removed all the files from it but there were some in /usr/local/lib ....

Thanks for the packages! Wish they would get integrated into Arch proper - this seems like a really important project for the future.

Offline

#19 2012-10-09 09:18:04

yodermk
Member
Registered: 2012-07-17
Posts: 58

Re: Review my PySide (python 3) package

Question: when Python 3.3 is pushed out, is this all going to break? If so, will simply re-building the packages fix it? Or will we need to wait for updated scripts from arlx?

Offline

#20 2012-10-21 17:53:20

Tomin
Member
Registered: 2012-10-21
Posts: 15

Re: Review my PySide (python 3) package

I tried to build python-pyside, but I can't get it working. I used the one from aur as base but changed the url (I used a mirror: https://distfiles.macports.org/py-pyside/) as pyside.org is no longer online. I also tried to change version to the latest (1.1.2), which didn't make any difference.

==> Starting build()...
-- Using default python: .cpython-32mu
-- libshiboken built for Release
-- Detected OS: x11
CMake Error at CMakeLists.txt:148 (message):
  Could not detect Python module installation directory.


-- Configuring incomplete, errors occurred!

Why it's using .cpython-32mu as my Python is now 3.3? Is that the reason it's failing. Right now I'm using VirtualBox and Ubuntu to do my work, but it'd nice to use Arch on bare-metal.

I also would like to get python-pysqlite which was recently replaced by python2-pysqlite (probably belongs to another discussion) (sqlite3 != pysqlite)

Last edited by Tomin (2012-10-22 19:59:37)

Offline

#21 2012-10-23 12:47:15

arlx_ignacy
Member
Registered: 2011-07-13
Posts: 12

Re: Review my PySide (python 3) package

I'm sorry for another late reply, real life priorities and work kept me away from my ArchLinux box for a while.

yodermk wrote:

Question: when Python 3.3 is pushed out, is this all going to break? If so, will simply re-building the packages fix it? Or will we need to wait for updated scripts from arlx?

Tomin wrote:

I tried to build python-pyside, but I can't get it working. I used the one from aur as base but changed the url (I used a mirror: https://distfiles.macports.org/py-pyside/) as pyside.org is no longer online. I also tried to change version to the latest (1.1.2), which didn't make any difference.

==> Starting build()...
-- Using default python: .cpython-32mu
-- libshiboken built for Release
-- Detected OS: x11
CMake Error at CMakeLists.txt:148 (message):
  Could not detect Python module installation directory.


-- Configuring incomplete, errors occurred!

Why it's using .cpython-32mu as my Python is now 3.3? Is that the reason it's failing. Right now I'm using VirtualBox and Ubuntu to do my work, but it'd nice to use Arch on bare-metal.

I also would like to get python-pysqlite which was recently replaced by python2-pysqlite (probably belongs to another discussion) (sqlite3 != pysqlite)


It seems the PySide developers still uses Python 3.2. If you look at the shiboken CMake file that is responsible for python interpreter lookup at line 30, the last time I look at it (ie. just now, today), they use a simple lookup loop up to "3.2".

The solution for this if you are using Python 3.3 is to add a "3.3" on this line, for example:

	FOREACH(_CURRENT_VERSION 3.3 3.2 3.1 3.0)

and rebuild by running:

	$ makepkg -e -f

on the shiboken/ directory, after that one should also rebuild and re-install pyside and pyside-tools to use the new shiboken for python 3.3. Unfortunately this small change is neccessary at least until the upstream developers add support for Python 3.3 too.

I made a small patch for shiboken PKGBUILD to automate this, I have also make changes on all PKGBUILDs to download files from the macports.org mirror because the pyside.org is unavailable at this moment. Feel free to clone/pull latest changes from the repository.

Offline

#22 2012-10-28 05:39:51

yodermk
Member
Registered: 2012-07-17
Posts: 58

Re: Review my PySide (python 3) package

Worked like a champ, thanks much!

I'd sure love this to make it into Arch proper.  I suppose for that to happen would require a significant project to be built with it, not?  I suppose it's just a matter of time until that happens.

Offline

#23 2012-10-30 09:09:06

arlx_ignacy
Member
Registered: 2011-07-13
Posts: 12

Re: Review my PySide (python 3) package

yodermk wrote:

Worked like a champ, thanks much!

I'd sure love this to make it into Arch proper.  I suppose for that to happen would require a significant project to be built with it, not?  I suppose it's just a matter of time until that happens.

You're welcome.

It seems like PySide, like many Qt-related projects, is in a transition state, with the change in corporate backing from Nokia to Digia some projects are being put on back seat at least until Qt (the main C++ project) settle down. I might be wrong but that is the impression that I get. Progress is slow, and much of the developers focus is on Qt moving towards Qt 5 so we might have a different PySide soon.

I can't blame the ArchLinux maintainers to see that it need to "settle down" a bit and get some big projects to use it. I also haven't seen any noteworthy open-source project(s) using PySide to justify its adoption anyway. So yes I would love to see it in Arch's community/extra repo but I'm realistic.

Offline

#24 2012-10-30 15:38:29

yodermk
Member
Registered: 2012-07-17
Posts: 58

Re: Review my PySide (python 3) package

Just noticed it is in Ubuntu's Quantal Quetzal archives.  Even the python3 version.

Yeah I also notice that the PySide project seems to be in a state of confusion.  The web pages are obviously way out of date, and they can't even keep their download links working.  I sure hope they can get things together shortly after Qt5 comes out -- this will really rock!

Offline

#25 2012-10-30 20:19:52

Tomin
Member
Registered: 2012-10-21
Posts: 15

Re: Review my PySide (python 3) package

I think there is one thing to notice. PySide were the offical Python bindings for Qt when Nokia still owned it. Probably it will be in future, too. However PyQt, which is made by another company, is the one that's in Arch's repositories and maybe more used among open source software (I don't really know). I personally continue using PySide, unless Digia gives me a good reason not to. I also look forward to Qt 5, which seems to have quite nice things when it comes to QML and multitouch. Hopefully my phone (Nokia N9) will be supported at least by community (I'm quite confident).

Offline

Board footer

Powered by FluxBB