[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: In-app extensions with pyqtdeploy-3/sip-5
From:       Patrick Stinson <patrickkidd () gmail ! com>
Date:       2020-09-30 17:32:51
Message-ID: E70D9D9A-5107-4B6B-A2A9-C17E0C653F21 () gmail ! com
[Download RAW message or body]

Noted. Though the use case I am putting forward is app-specific C++ code.

> On Sep 30, 2020, at 9:26 AM, Phil Thompson <phil@riverbankcomputing.com> wrote:
> 
> On 30/09/2020 18:07, Patrick Stinson wrote:
> > Phil,
> > I am moving this question form the thread about pyqt6/sip6 snapshots
> > being released.
> > I think pyqtdeploy currently has a conceptual conflict that does not
> > allow for including sip extensions that are part of the app itself -
> > when a PyQt5 application C++ code that extends Qt classes that are
> > used and extended in python app code.
> > Currently, pyqtdeploy component plugins are meant to be part of the
> > sysroot and not part of the app. For example, pyqtdeploy-build has no
> > build phase that merely generates the source code for an extension.
> > The closest thing is AbstractComponent.install(), which is only called
> > from pyqtdeploy-sysroot which is awkward for code developed in tandem
> > with the app itself.
> > What am I missing here?
> 
> Nothing. Conceptually I would argue that an extension module can be used by many \
> apps and so shouldn't be considered as part of any particular app. 
> Phil


[prev in list] [next in list] [prev in thread] [next in thread]