Re: [Development] Technical vision for Qt for Python

2019-08-19 Thread Kevin Kofler
Jason H wrote: > I also have to point out that there was a statement made by Lars to make > QML [more] strongly typed. I had expected that from the beginning, that > Python would be the scripting language of QML, not Javascript[0], I don't see how Python is inherently more strongly typed than Java

Re: [Development] Technical vision for Qt for Python

2019-08-19 Thread Thiago Macieira
On Monday, 19 August 2019 12:34:23 PDT Jason H wrote: > > > Can Qt set a "no private destructor!" rule? > > > > No. > > > > Private destructors have a purpose. > > Would a workable re-wording be "always provide a public means of > destruction"? No, since the purpose is to prevent you from doing

Re: [Development] Technical vision for Qt for Python

2019-08-19 Thread Fabrice Salvaire
Dear all, I am using PyQt since 10 years now and my points are: - It is true that missing bindings is a serious issue to use PySide actually. - I noticed PyQt has simpler wrapper code, but I don't investigated more. - I would dream to have Python instead of JS, but we know how to implement a

Re: [Development] Technical vision for Qt for Python

2019-08-19 Thread Jason H
> > Can Qt set a "no private destructor!" rule? > > No. > > Private destructors have a purpose. Would a workable re-wording be "always provide a public means of destruction"? To be clear, I am not sure what the actual issue is, why it's private, or why shiboken can't handle it. In the immediate

Re: [Development] Technical vision for Qt for Python

2019-08-19 Thread Thiago Macieira
On Monday, 19 August 2019 08:55:45 PDT Jason H wrote: > Can Qt set a "no private destructor!" rule? No. Private destructors have a purpose. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel System Software Products __

Re: [Development] Technical vision for Qt for Python

2019-08-19 Thread Jason H
hmark. That's got me in C++. But I'm also eagerly awaiting for the time I can interop with my python coworkers! > Sent: Monday, August 19, 2019 at 10:36 AM > From: "Cristián Maureira-Fredes" > To: "development@qt-project.org" > Subject: Re: [Development] Techn

Re: [Development] Technical vision for Qt for Python

2019-08-19 Thread Cristián Maureira-Fredes
e the module. Thanks for your comments, Cheers > (snip) > > > >> Sent: Monday, August 19, 2019 at 8:39 AM >> From: "Cristián Maureira-Fredes" >> To: "development@qt-project.org" >> Subject: [Development] Technical vision for Qt fo

Re: [Development] Technical vision for Qt for Python

2019-08-19 Thread Jason H
d me. 1. Since Qt lagged many years in getting an ECMA Script 7 implementation, chasing this evolving standard might not be the best. 2. Why maintain V4? > Sent: Monday, August 19, 2019 at 8:39 AM > From: "Cristián Maureira-Fredes" > To: "development@qt-project.org&q

[Development] Technical vision for Qt for Python

2019-08-19 Thread Cristián Maureira-Fredes
Hello, After the general discussion of the vision for Qt6, we wanted to say a few things regarding Qt for Python. Even though we are talking about a Python module, the whole development is C and C++ related, and due to Python's popularity, we have been getting a lot of attention on Shiboken, the