pyqtdeploy: Correct entry point naming?

[Patrick Stinson]

No luck moving my project file into my app package. Then I realized that I am using the same dir structure as the pyqtdeploy pyqt-demo. This problem with the Scan button happens there as well.


> On Oct 11, 2020, at 1:40 PM, Patrick Stinson <patrickkidd at gmail.com> wrote:
> 
> Ah, so the pdt file should go into the app package dir and not the project root.
> 
> I used the snapshot tarball currently posted on your website. It isn’t immediately apparent how to use mercurial with knowledge of fit or svn. Let me know the ideal way to do this now and in the future.
> 
>> On Oct 11, 2020, at 1:12 PM, Phil Thompson <phil at riverbankcomputing.com> wrote:
>> 
>> On 11/10/2020 19:39, Patrick Stinson wrote:
>>> This does not appear to be fixed. I used the scan button and it
>>> replaced my top-level package name with the absolute path prefixed
>>> with :/
>> 
>> That is correct if the location of the package is in a different part of the filesystem to the .pdt file.
>> 
>> I assume you tried with a repository copy as tonight's snapshot hasn't been created yet.
>> 
>> Phil
>> 
>> 
>>>>> On Oct 11, 2020, at 10:36 AM, Patrick Stinson <patrickkidd at gmail.com> wrote:
>>>> I suppose I could finally have a look at a snapshot. I’ve been sticking to stable since my project is in release.
>>>>> On Oct 11, 2020, at 7:47 AM, Phil Thompson <phil at riverbankcomputing.com> wrote:
>>>>> I think this (and other issues) are fixed in tonight's snapshot. However I'd like confirmation before releasing v3.1.1.
>>>>> Thanks,
>>>>> Phil
>>>>> On 04/10/2020 19:36, Patrick Stinson wrote:
>>>>>> It appears as though it requires the name of the top level package -
>>>>>> the name of the project folder, not the app package - to be set as the
>>>>>> Name and not the full directory path. But when I click “Scan” it
>>>>>> replaces that Single name with the absolute path of the project
>>>>>> folder. The worker that I am currently using is to edit the project
>>>>>> TOML file after clicking the scan button.
>>>>>> Perhaps it is a bug in the gooey that replaces the top level packet
>>>>>> dish name with that absolute path.
>>>>>>> On Oct 4, 2020, at 6:18 AM, Phil Thompson <phil at riverbankcomputing.com> wrote:
>>>>>>> On 30/09/2020 21:03, Patrick Stinson wrote:
>>>>>>>> What is the correct way to structure an entry point in pyqtdeploy 3?
>>>>>>>> This is not documented.
>>>>>>>> In v2 my entry point for the source tree in the screenshot was
>>>>>>>> familydiagram.pkdiagram.app:main. In pyqtdeploy 3 that entry point
>>>>>>>> string gives the following error:
>>>>>>>> Traceback (most recent call last):
>>>>>>>> File "bootstrap-3.7.0.py", line 983, in _find_and_load
>>>>>>>> File "bootstrap-3.7.0.py", line 953, in _find_and_load_unlocked
>>>>>>>> File "bootstrap-3.7.0.py", line 219, in _call_with_frames_removed
>>>>>>>> File "bootstrap-3.7.0.py", line 983, in _find_and_load
>>>>>>>> File "bootstrap-3.7.0.py", line 953, in _find_and_load_unlocked
>>>>>>>> File "bootstrap-3.7.0.py", line 219, in _call_with_frames_removed
>>>>>>>> File "bootstrap-3.7.0.py", line 983, in _find_and_load
>>>>>>>> File "bootstrap-3.7.0.py", line 965, in _find_and_load_unlocked
>>>>>>>> ModuleNotFoundError: No module named 'familydiagram'
>>>>>>>> Or the following error if I change it to pkdiagram.app:main:
>>>>>>>> Traceback (most recent call last):
>>>>>>>> File "main_app.py", line 1, in <module>
>>>>>>>> File "bootstrap-3.7.0.py", line 983, in _find_and_load
>>>>>>>> File "bootstrap-3.7.0.py", line 965, in _find_and_load_unlocked
>>>>>>>> ModuleNotFoundError: No module named ‘pkdiagram'
>>>>>>>> If use a main script file containing “import pkdiagram.app;
>>>>>>>> pkdiagram.app.main()” instead of an entry point I get the following
>>>>>>>> error:
>>>>>>>> Traceback (most recent call last):
>>>>>>>> File "main_app.py", line 1, in <module>
>>>>>>>> File "bootstrap-3.7.0.py", line 983, in _find_and_load
>>>>>>>> File "bootstrap-3.7.0.py", line 965, in _find_and_load_unlocked
>>>>>>>> ModuleNotFoundError: No module named ‘pkdiagram'
>>>>>>>> What is the right way to do this?
>>>>>>> The handling of entry points in v3 hasn't (knowingly) changed.
>>>>>>> Phil