Correct Pyqtdeploy project with component plugins

[Patrick Stinson]

Ah! I assumed that the sysroot.toml, sysroot build target dirs, and
component plugins would be in the project root like pyqt-demo. But now I
remember you can specify the location of sysroot.toml in the pyqtdeploy
project. then component plugins should be also stored there. Excellent,
thank you!

On Mon, Oct 17, 2022 at 6:55 AM Phil Thompson <phil at riverbankcomputing.com>
wrote:

> On 17/10/2022 15:38, Patrick Stinson wrote:
> > The pyqt-demo project in the pyqtdeploy source package has both the app
> > source and component plugins in the project root. This can cause name
> > conflicts between the component plugins and their associated python/sip
> > modules when running the app code during development. What is the
> > intended
> > folder / naming schema to avoid this?
> >
> > For example, I have a folder the typing_extensions module in
> > ./lib/site-packages that is a dependency of some other modules I am
> > using.
> > I've added ./lib/site-packages to sys.path in my app main(). AFAIK, the
> > component plugin has to be ./typing_extensions.py, but that file gets
> > imported before the one in site-packages which breaks the modules that
> > simply "import typing_extensions".
> >
> > I'm sure I've missed a basic concept, just couldn't infer this looking
> > at
> > pyqt-demo since it doesn't include custom packages.
>
> I'm not sure what you mean but the default directory for searching for
> plugins is the directory containing sysroot.toml which I would expect to
> be in a sub-directory somewhere away from any application code.
>
> Phil
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20221017/67d46a67/attachment.htm>