[Development] Technical vision for Qt for Python

Thiago Macieira thiago.macieira at intel.com
Mon Aug 19 22:49:32 CEST 2019


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 that. That's usually a 
singleton, though not always.

> 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 case PyQt provides the class
> so there seems to be some way around the issue...

>From knowledge of past code generators, they try to derive from every class, 
so any class that is final or has only private constructors or has a private 
destructor will fail. It needs a different strategy.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products





More information about the Development mailing list