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

List:       pykde
Subject:    Re: Correct Pyqtdeploy project with component plugins
From:       Patrick Stinson <patrickkidd () gmail ! com>
Date:       2022-10-17 16:53:49
Message-ID: CADb17j3U_C6ECymH_xHce2RD8m=NCHSUUvu5CeDfWw_s3OFZ=Q () mail ! gmail ! com
[Download RAW message or body]

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@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
>

[Attachment #3 (text/html)]

<div dir="auto">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!</div><div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Oct 17, 2022 at 6:55 AM \
Phil Thompson &lt;<a \
href="mailto:phil@riverbankcomputing.com">phil@riverbankcomputing.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex">On 17/10/2022 15:38, Patrick \
Stinson wrote:<br> &gt; The pyqt-demo project in the pyqtdeploy source package has \
both the app<br> &gt; source and component plugins in the project root. This can \
cause name<br> &gt; conflicts between the component plugins and their associated \
python/sip<br> &gt; modules when running the app code during development. What is the \
<br> &gt; intended<br>
&gt; folder / naming schema to avoid this?<br>
&gt; <br>
&gt; For example, I have a folder the typing_extensions module in<br>
&gt; ./lib/site-packages that is a dependency of some other modules I am <br>
&gt; using.<br>
&gt; I&#39;ve added ./lib/site-packages to sys.path in my app main(). AFAIK, the<br>
&gt; component plugin has to be ./typing_extensions.py, but that file gets<br>
&gt; imported before the one in site-packages which breaks the modules that<br>
&gt; simply &quot;import typing_extensions&quot;.<br>
&gt; <br>
&gt; I&#39;m sure I&#39;ve missed a basic concept, just couldn&#39;t infer this \
looking <br> &gt; at<br>
&gt; pyqt-demo since it doesn&#39;t include custom packages.<br>
<br>
I&#39;m not sure what you mean but the default directory for searching for <br>
plugins is the directory containing sysroot.toml which I would expect to <br>
be in a sub-directory somewhere away from any application code.<br>
<br>
Phil<br>
</blockquote></div></div>



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