<div dir="ltr">We've found using the resource files easier than using paths when distributing with PyInstaller. Also the built-in translation support for files is convenient.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Sep 23, 2020 at 2:19 PM <<a href="mailto:pyqt-request@riverbankcomputing.com">pyqt-request@riverbankcomputing.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Send PyQt mailing list submissions to<br>
<a href="mailto:pyqt@riverbankcomputing.com" target="_blank">pyqt@riverbankcomputing.com</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://www.riverbankcomputing.com/mailman/listinfo/pyqt" rel="noreferrer" target="_blank">https://www.riverbankcomputing.com/mailman/listinfo/pyqt</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:pyqt-request@riverbankcomputing.com" target="_blank">pyqt-request@riverbankcomputing.com</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:pyqt-owner@riverbankcomputing.com" target="_blank">pyqt-owner@riverbankcomputing.com</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of PyQt digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: PyQt6 and SIP v6 Snapshots Available (Detlev Offenbach)<br>
2. Re: PyQt6 and SIP v6 Snapshots Available (Phil Thompson)<br>
3. Re: PyQt6 and SIP v6 Snapshots Available (Grzegorz Bokota)<br>
4. Re: PyQt6 and SIP v6 Snapshots Available (Patrick Stinson)<br>
5. Re: PyQt6 and SIP v6 Snapshots Available (Phil Thompson)<br>
6. Re: PyQt6 and SIP v6 Snapshots Available (Phil Thompson)<br>
7. Re: PyQt6 and SIP v6 Snapshots Available (Eli Schwartz)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 23 Sep 2020 19:33:57 +0200<br>
From: Detlev Offenbach <<a href="mailto:detlev@die-offenbachs.de" target="_blank">detlev@die-offenbachs.de</a>><br>
To: <a href="mailto:pyqt@riverbankcomputing.com" target="_blank">pyqt@riverbankcomputing.com</a><br>
Subject: Re: PyQt6 and SIP v6 Snapshots Available<br>
Message-ID: <<a href="mailto:01b56d5c-2770-c72b-5aa2-a9ac016c64ee@die-offenbachs.de" target="_blank">01b56d5c-2770-c72b-5aa2-a9ac016c64ee@die-offenbachs.de</a>><br>
Content-Type: text/plain; charset=utf-8; format=flowed<br>
<br>
Hi Phil,<br>
<br>
the download page says, that 'pyrcc' has been removed. What will be the <br>
successor? The eric-ide sources use resource files and thus depends on <br>
pyrcc.<br>
<br>
Detlev<br>
<br>
Am 20.09.20 um 18:06 schrieb Phil Thompson:<br>
> PyQt6 and SIP v6 snapshots are now available on their respective <br>
> download pages.<br>
><br>
> Before you get too excited, PyQt6 currently builds against Qt5 but <br>
> does include the planned incompatibilities with PyQt5 (summarised on <br>
> the download page).<br>
><br>
> Phil<br>
<br>
-- <br>
Detlev Offenbach<br>
<a href="mailto:detlev@die-offenbachs.de" target="_blank">detlev@die-offenbachs.de</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 23 Sep 2020 18:42:40 +0100<br>
From: Phil Thompson <<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>><br>
To: Detlev Offenbach <<a href="mailto:detlev@die-offenbachs.de" target="_blank">detlev@die-offenbachs.de</a>><br>
Cc: <a href="mailto:pyqt@riverbankcomputing.com" target="_blank">pyqt@riverbankcomputing.com</a><br>
Subject: Re: PyQt6 and SIP v6 Snapshots Available<br>
Message-ID: <<a href="mailto:e78d21ccd509a15812a655ceb63e2e0c@riverbankcomputing.com" target="_blank">e78d21ccd509a15812a655ceb63e2e0c@riverbankcomputing.com</a>><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed<br>
<br>
On 23/09/2020 18:33, Detlev Offenbach wrote:<br>
> Hi Phil,<br>
> <br>
> the download page says, that 'pyrcc' has been removed. What will be<br>
> the successor? The eric-ide sources use resource files and thus<br>
> depends on pyrcc.<br>
<br>
I don't plan a successor as I don't see the point of resource files in a <br>
Python context.<br>
<br>
What do you use it for?<br>
<br>
Phil<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 23 Sep 2020 21:08:26 +0200<br>
From: Grzegorz Bokota <<a href="mailto:g.bokota@mimuw.edu.pl" target="_blank">g.bokota@mimuw.edu.pl</a>><br>
To: Phil Thompson <<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>><br>
Cc: Detlev Offenbach <<a href="mailto:detlev@die-offenbachs.de" target="_blank">detlev@die-offenbachs.de</a>>, pyqt<br>
<<a href="mailto:pyqt@riverbankcomputing.com" target="_blank">pyqt@riverbankcomputing.com</a>><br>
Subject: Re: PyQt6 and SIP v6 Snapshots Available<br>
Message-ID:<br>
<CADUBGeQA_GNQQg0mb1cqfqr=YPUxjcV0_+PrKxHHiJ=<a href="mailto:Q5tnSLw@mail.gmail.com" target="_blank">Q5tnSLw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
napari use pyrcc to compile svg icons into a python file:<br>
<br>
<a href="https://github.com/napari/napari/blob/79500fe4ae0a8c3d0838d7330f4ac9a706b1bb9e/napari/resources/build_icons.py#L218-L223" rel="noreferrer" target="_blank">https://github.com/napari/napari/blob/79500fe4ae0a8c3d0838d7330f4ac9a706b1bb9e/napari/resources/build_icons.py#L218-L223</a><br>
<br>
It means that it should be rewritten using QtSvg to run with PyQt6?<br>
<br>
Grzegorz Bokota<br>
<br>
<br>
śr., 23 wrz 2020 o 19:43 Phil Thompson <<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>><br>
napisał(a):<br>
<br>
> On 23/09/2020 18:33, Detlev Offenbach wrote:<br>
> > Hi Phil,<br>
> ><br>
> > the download page says, that 'pyrcc' has been removed. What will be<br>
> > the successor? The eric-ide sources use resource files and thus<br>
> > depends on pyrcc.<br>
><br>
> I don't plan a successor as I don't see the point of resource files in a<br>
> Python context.<br>
><br>
> What do you use it for?<br>
><br>
> Phil<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20200923/9d0ee135/attachment-0001.htm" rel="noreferrer" target="_blank">https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20200923/9d0ee135/attachment-0001.htm</a>><br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 23 Sep 2020 11:15:01 -0800<br>
From: Patrick Stinson <<a href="mailto:patrickkidd@gmail.com" target="_blank">patrickkidd@gmail.com</a>><br>
To: Phil Thompson <<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>><br>
Cc: Detlev Offenbach <<a href="mailto:detlev@die-offenbachs.de" target="_blank">detlev@die-offenbachs.de</a>>, PyQt mailing list<br>
<<a href="mailto:pyqt@riverbankcomputing.com" target="_blank">pyqt@riverbankcomputing.com</a>><br>
Subject: Re: PyQt6 and SIP v6 Snapshots Available<br>
Message-ID: <<a href="mailto:023F6970-DAE4-4414-A6D0-22F9BAE733EB@gmail.com" target="_blank">023F6970-DAE4-4414-A6D0-22F9BAE733EB@gmail.com</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
Phil,<br>
<br>
Could you explain what makes the Qt resource system obsolete in a PyQt6 context? The Qt resource system itself seems to play an essential role in the toolkit. If you think it does not provide an essential function, then I am intrigued to hear more.<br>
<br>
But if you do think it plays an essential role, then perhaps you are suggesting that resource files are preprocessed into C++ source via rcc instead of python source via a pyrcc6? If so, I could see that for pyqtdeploy projects but how would one import Qt resources when running a PyQt app from the command line during development?<br>
<br>
-Patrick<br>
<br>
> On Sep 23, 2020, at 9:42 AM, Phil Thompson <<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>> wrote:<br>
> <br>
> On 23/09/2020 18:33, Detlev Offenbach wrote:<br>
>> Hi Phil,<br>
>> the download page says, that 'pyrcc' has been removed. What will be<br>
>> the successor? The eric-ide sources use resource files and thus<br>
>> depends on pyrcc.<br>
> <br>
> I don't plan a successor as I don't see the point of resource files in a Python context.<br>
> <br>
> What do you use it for?<br>
> <br>
> Phil<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 5<br>
Date: Wed, 23 Sep 2020 22:10:08 +0100<br>
From: Phil Thompson <<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>><br>
To: Grzegorz Bokota <<a href="mailto:g.bokota@mimuw.edu.pl" target="_blank">g.bokota@mimuw.edu.pl</a>><br>
Cc: pyqt <<a href="mailto:pyqt@riverbankcomputing.com" target="_blank">pyqt@riverbankcomputing.com</a>><br>
Subject: Re: PyQt6 and SIP v6 Snapshots Available<br>
Message-ID: <<a href="mailto:79ef2b5499a8d289f8f63fda70ad11c3@riverbankcomputing.com" target="_blank">79ef2b5499a8d289f8f63fda70ad11c3@riverbankcomputing.com</a>><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed<br>
<br>
On 23/09/2020 20:08, Grzegorz Bokota wrote:<br>
> napari use pyrcc to compile svg icons into a python file:<br>
> <br>
> <a href="https://github.com/napari/napari/blob/79500fe4ae0a8c3d0838d7330f4ac9a706b1bb9e/napari/resources/build_icons.py#L218-L223" rel="noreferrer" target="_blank">https://github.com/napari/napari/blob/79500fe4ae0a8c3d0838d7330f4ac9a706b1bb9e/napari/resources/build_icons.py#L218-L223</a><br>
> <br>
> It means that it should be rewritten using QtSvg to run with PyQt6?<br>
<br>
Probably along with lots of other things.<br>
<br>
Phil<br>
<br>
<br>
------------------------------<br>
<br>
Message: 6<br>
Date: Wed, 23 Sep 2020 22:14:43 +0100<br>
From: Phil Thompson <<a href="mailto:phil@riverbankcomputing.com" target="_blank">phil@riverbankcomputing.com</a>><br>
To: Patrick Stinson <<a href="mailto:patrickkidd@gmail.com" target="_blank">patrickkidd@gmail.com</a>><br>
Cc: PyQt mailing list <<a href="mailto:pyqt@riverbankcomputing.com" target="_blank">pyqt@riverbankcomputing.com</a>><br>
Subject: Re: PyQt6 and SIP v6 Snapshots Available<br>
Message-ID: <<a href="mailto:0d5734dafd164b239554118ac8b4199f@riverbankcomputing.com" target="_blank">0d5734dafd164b239554118ac8b4199f@riverbankcomputing.com</a>><br>
Content-Type: text/plain; charset=US-ASCII; format=flowed<br>
<br>
On 23/09/2020 20:15, Patrick Stinson wrote:<br>
> Phil,<br>
> <br>
> Could you explain what makes the Qt resource system obsolete in a<br>
> PyQt6 context?<br>
<br>
<a href="https://www.riverbankcomputing.com/static/Docs/pyqtdeploy/pyrcc.html" rel="noreferrer" target="_blank">https://www.riverbankcomputing.com/static/Docs/pyqtdeploy/pyrcc.html</a><br>
<br>
> The Qt resource system itself seems to play an<br>
> essential role in the toolkit. If you think it does not provide an<br>
> essential function, then I am intrigued to hear more.<br>
<br>
If there is something that you cannot do with existing Python techniques <br>
then I'll happily reconsider.<br>
<br>
> But if you do think it plays an essential role, then perhaps you are<br>
> suggesting that resource files are preprocessed into C++ source via<br>
> rcc instead of python source via a pyrcc6? If so, I could see that for<br>
> pyqtdeploy projects but how would one import Qt resources when running<br>
> a PyQt app from the command line during development?<br>
<br>
What is the requirement for creating Qt resources in the first place?<br>
<br>
Phil<br>
<br>
<br>
------------------------------<br>
<br>
Message: 7<br>
Date: Wed, 23 Sep 2020 17:17:42 -0400<br>
From: Eli Schwartz <<a href="mailto:eschwartz@archlinux.org" target="_blank">eschwartz@archlinux.org</a>><br>
To: <a href="mailto:pyqt@riverbankcomputing.com" target="_blank">pyqt@riverbankcomputing.com</a><br>
Subject: Re: PyQt6 and SIP v6 Snapshots Available<br>
Message-ID: <<a href="mailto:15332fc6-cf67-5699-9847-ac7fde90ad94@archlinux.org" target="_blank">15332fc6-cf67-5699-9847-ac7fde90ad94@archlinux.org</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On 9/23/20 1:42 PM, Phil Thompson wrote:<br>
> On 23/09/2020 18:33, Detlev Offenbach wrote:<br>
>> Hi Phil,<br>
>><br>
>> the download page says, that 'pyrcc' has been removed. What will be<br>
>> the successor? The eric-ide sources use resource files and thus<br>
>> depends on pyrcc.<br>
> <br>
> I don't plan a successor as I don't see the point of resource files in a<br>
> Python context.<br>
> <br>
> What do you use it for?<br>
> <br>
> Phil<br>
<br>
+1<br>
<br>
qresource files are intended to embed random data files into<br>
single-executable style software distributions, to reduce the number of<br>
moving parts. This is as opposed to doing proper installation management<br>
unix style, and is of limited use on Windows too, as long as people ship<br>
Qt itself as shared libraries necessitating a directory structure.<br>
<br>
This is all fine and well for C++ programs where qresources get<br>
statically linked into the executable itself, reducing the number of<br>
files to be installed.<br>
<br>
What's the point of it for generating *.py files with that data? You end<br>
up with multiple files to distribute anyway.<br>
<br>
pkg_resources.resource_filename() and its modern equivalent, the stdlib<br>
importlib.resources, allows you to access real files through standard<br>
pythonic mechanisms, without the wrapper abstractions and without an the<br>
rcc compiler. There's no need to handle data blobs as python inline<br>
strings, try to byte-compile something that doesn't really byte-compile<br>
well, etc.<br>
<br>
The resulting files are easily introspectable and modifiable in the<br>
built software bundle (because they are the original files) and only get<br>
read at the time of use.<br>
<br>
Really -- what is the big attraction to using qresources in python?<br>
<br>
-- <br>
Eli Schwartz<br>
Arch Linux Bug Wrangler and Trusted User<br>
<br>
-------------- next part --------------<br>
A non-text attachment was scrubbed...<br>
Name: signature.asc<br>
Type: application/pgp-signature<br>
Size: 1601 bytes<br>
Desc: OpenPGP digital signature<br>
URL: <<a href="https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20200923/84183a1e/attachment.sig" rel="noreferrer" target="_blank">https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20200923/84183a1e/attachment.sig</a>><br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
PyQt mailing list<br>
<a href="mailto:PyQt@riverbankcomputing.com" target="_blank">PyQt@riverbankcomputing.com</a><br>
<a href="https://www.riverbankcomputing.com/mailman/listinfo/pyqt" rel="noreferrer" target="_blank">https://www.riverbankcomputing.com/mailman/listinfo/pyqt</a><br>
<br>
<br>
------------------------------<br>
<br>
End of PyQt Digest, Vol 194, Issue 31<br>
*************************************<br>
</blockquote></div>