From alexander.blasche at qt.io Mon Feb 13 13:25:25 2017 From: alexander.blasche at qt.io (Alex Blasche) Date: Mon, 13 Feb 2017 12:25:25 +0000 Subject: [PySide] [pyside-dev] Re: Bringing pyside back to Qt Project In-Reply-To: References: <376b24cd-84b7-4687-8113-de898579f412@googlegroups.com> Message-ID: Hi, > -----Original Message----- > From: chgans at googlemail.com [mailto:chgans at googlemail.com] On Behalf Of > Ch'Gans > Sent: Saturday, 4 February 2017 23:16 > To: pyside-dev at googlegroups.com > Subject: Re: [pyside-dev] Re: Bringing pyside back to Qt Project > > On 5 February 2017 at 04:01, Tony Benoy wrote: > > Is there any update? > > I would be interested too, to hear about the current status. For now the only > way to get an idea is to look at the git log and the bug tracker and the weekly > "technical" progress log at > http://wiki.qt.io/PySide2 (thanks for keeping that one up-to-date). > > Could someone provide a quick status (in words, not git hash or JIRA ref)? eg., > how mature has PySide2 became, how far from "feature complete", any ETA for > a technology preview, online doc deployment on doc.qt.io, ... We are trying to get Pyside integrated into our automated testing infrastructure. Essentially we want every patch to go through the tests before they are accepted into the repository. That's a practise we use in Qt too. This task is bigger than we anticipated and will still take some time. The second task is to replace the shiboken parser. The old parser is not C++11 ready. Since Qt 5.6 is the last non-C++11 release of Qt, Pyside is currently stuck on this Qt version. We aim to replace the shiboken parser with the clang parser. This is a large task and will take a significant amount of time. Furthermore, we have investigated the QML support in Pyside. There were quite a few issues which prevented corner cases to not work. This task was recently concluded. In the past we also fixed a lot of bugs bugs. If you find a bug please file it under https://bugreports.qt.io/browse/PYSIDE The Pyside 2 bugs are tracked under the "dev" version tag. Apart from that the mentioned progress log on http://wiki.qt.io/PySide2 is indeed the best update channel. -- Alex From fredrik at averpil.com Mon Feb 13 21:08:24 2017 From: fredrik at averpil.com (Fredrik Averpil) Date: Mon, 13 Feb 2017 20:08:24 +0000 Subject: [PySide] [pyside-dev] Re: Bringing pyside back to Qt Project In-Reply-To: References: <376b24cd-84b7-4687-8113-de898579f412@googlegroups.com> Message-ID: Hi Alex, Are the build environments/scripts available somewhere and will it be possible to contribute to them? Some time ago I set up a couple of build environments for Travis CI/Docker which builds PySide2 and wheels, although hardly usable as the resulting wheels aren't portable and will require Qt installed locally: https://github.com/fredrikaverpil/pyside2-wheels // Fredrik -------------- next part -------------- An HTML attachment was scrubbed... URL: From renaudtalon at fusefx.com Mon Feb 13 22:58:17 2017 From: renaudtalon at fusefx.com (Renaud Talon) Date: Mon, 13 Feb 2017 21:58:17 +0000 Subject: [PySide] [pyside-dev] Re: Bringing pyside back to Qt Project In-Reply-To: References: <376b24cd-84b7-4687-8113-de898579f412@googlegroups.com> Message-ID: Hi Fredrik ! I believe the wheels are portable (sort of) as long as you set this environment variable to point to the platform DLL on the machine your installing the wheel on. For example: QT_QPA_PLATFORM_PLUGIN_PATH = "C:\Python35\Lib\site-packages\PySide2\plugins\platforms" I created a ticket regarding the deployment issue : https://bugreports.qt.io/browse/PYSIDE-465 Renaud From: PySide [mailto:pyside-bounces+renaudtalon=fusefx.com at qt-project.org] On Behalf Of Fredrik Averpil Sent: Monday, February 13, 2017 12:08 PM To: Alex Blasche ; pyside-dev at googlegroups.com; pyside at qt-project.org Subject: Re: [PySide] [pyside-dev] Re: Bringing pyside back to Qt Project Hi Alex, Are the build environments/scripts available somewhere and will it be possible to contribute to them? Some time ago I set up a couple of build environments for Travis CI/Docker which builds PySide2 and wheels, although hardly usable as the resulting wheels aren't portable and will require Qt installed locally: https://github.com/fredrikaverpil/pyside2-wheels // Fredrik -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.blasche at qt.io Tue Feb 14 08:46:25 2017 From: alexander.blasche at qt.io (Alex Blasche) Date: Tue, 14 Feb 2017 07:46:25 +0000 Subject: [PySide] [pyside-dev] Re: Bringing pyside back to Qt Project In-Reply-To: References: <376b24cd-84b7-4687-8113-de898579f412@googlegroups.com> , Message-ID: Hi Fredrik, >From: Fredrik Averpil >Are the build environments/scripts available somewhere and will it be possible to contribute to them? Pyside follows the same contribution guide lines as Qt using codereview.qt-project.org. You push it to gerrit and somebody else must approve it. A quick intro can be found under: https://wiki.qt.io/Gerrit-Introduction There are no secret code paths. -- Alex From dc.loco at gmail.com Mon Feb 20 14:48:07 2017 From: dc.loco at gmail.com (Kevin Cole) Date: Mon, 20 Feb 2017 08:48:07 -0500 Subject: [PySide] [pyside-dev] Re: Bringing pyside back to Qt Project In-Reply-To: References: <376b24cd-84b7-4687-8113-de898579f412@googlegroups.com> Message-ID: As someone who does not know C++, and is still struggling a lot with PySide, my big concern is documentation: The current documentation often leaves me with quite a few questions, as it seems often auto-generated from the C++ documentation. So, my hope is that whatever is evolving is evolving with its own 'native" documentation. From felix.schwarz at oss.schwarz.eu Mon Feb 20 15:03:24 2017 From: felix.schwarz at oss.schwarz.eu (Felix Schwarz) Date: Mon, 20 Feb 2017 15:03:24 +0100 Subject: [PySide] [pyside-dev] Re: Bringing pyside back to Qt Project In-Reply-To: References: <376b24cd-84b7-4687-8113-de898579f412@googlegroups.com> Message-ID: <45de26cb-6e24-39dc-6d9c-ad53875e63a0@oss.schwarz.eu> Am 20.02.2017 um 14:48 schrieb Kevin Cole: > As someone who does not know C++, and is still struggling a lot with > PySide, my big concern is documentation: The current documentation > often leaves me with quite a few questions, as it seems often > auto-generated from the C++ documentation. > > So, my hope is that whatever is evolving is evolving with its own > 'native" documentation. Even though I don't claim any authority on pyside I think that is unlikely to happen: The goal of PySide (and other bindings like PyQT/PyGobject+GTK) is to expose pretty much the native API just in a different language with only very little pythonic sugar. The upside is that you can use a lot of QT documentation regarding C++ almost verbatim and if you look for answers always also look for C++ questions. While I understand this might be intimidating I found that given a sufficiently complex PySide/QT application I needed to understand QTs way of working anyway (sometimes by looking at QT's source code). Or put differently: Even in Python a serious QT application requires a significant amount of work so learning a bit of C++ syntax is just a minor addition in terms of time required.