ModuleNotFoundError: No module named 'pyllrp'

[moth754]

Receiving the following error when attempting to open CrossMgr Impinj. Version is 3.1.60-20240801165523. On Windows 11 Pro 23H2 22631.3737 on Dell Latitude 5420 Rugged. Relatively clean windows install - reinstalled recently.

Traceback (most recent call last): File "Impinj.py", line 12, in ModuleNotFoundError: No module named 'pyllrp'

During handling of the above exception, another exception occurred:

Traceback (most recent call last): File "CrossMgrImpinj.pyw", line 1, in File "PyInstaller\loader\pyimod02_importers.py", line 419, in exec_module File "MainWin.py", line 15, in File "PyInstaller\loader\pyimod02_importers.py", line 419, in exec_module File "Impinj.py", line 14, in ModuleNotFoundError: No module named 'pyllrp'

[moth754]

CrossMgrImpinj_3_0_21-20240722103412 working ok

[kimble4]

Looks like a problem with the build process. Comparing the GitHub action logs:

For v3.1.59-20240730090420:

Note 'd:\\a\\crossmgr\\crossmgr\\env\\src\\pyllrp',

1678
265 INFO: Module search paths (PYTHONPATH):
1679
['D:\\a\\CrossMgr\\CrossMgr\\env\\Scripts\\pyinstaller.exe',
1680
 'C:\\hostedtoolcache\\windows\\Python\\3.10.11\\x64\\python310.zip',
1681
 'C:\\hostedtoolcache\\windows\\Python\\3.10.11\\x64\\DLLs',
1682
 'C:\\hostedtoolcache\\windows\\Python\\3.10.11\\x64\\lib',
1683
 'C:\\hostedtoolcache\\windows\\Python\\3.10.11\\x64',
1684
 'D:\\a\\CrossMgr\\CrossMgr\\env',
1685
 'D:\\a\\CrossMgr\\CrossMgr\\env\\lib\\site-packages',
1686
 'd:\\a\\crossmgr\\crossmgr\\env\\src\\pyllrp',
1687
 'D:\\a\\CrossMgr\\CrossMgr\\env\\lib\\site-packages\\win32',
1688
 'D:\\a\\CrossMgr\\CrossMgr\\env\\lib\\site-packages\\win32\\lib',
1689
 'D:\\a\\CrossMgr\\CrossMgr\\env\\lib\\site-packages\\Pythonwin',
1690
 'D:\\a\\CrossMgr',
1691
 'D:\\a\\CrossMgr\\CrossMgr\\CrossMgrImpinj']

For v3.1.59-20240731143810: (note absence of pyllrp)

1680
296 INFO: Module search paths (PYTHONPATH):
1681
['D:\\a\\CrossMgr\\CrossMgr\\env\\Scripts\\pyinstaller.exe',
1682
 'C:\\hostedtoolcache\\windows\\Python\\3.10.11\\x64\\python310.zip',
1683
 'C:\\hostedtoolcache\\windows\\Python\\3.10.11\\x64\\DLLs',
1684
 'C:\\hostedtoolcache\\windows\\Python\\3.10.11\\x64\\lib',
1685
 'C:\\hostedtoolcache\\windows\\Python\\3.10.11\\x64',
1686
 'D:\\a\\CrossMgr\\CrossMgr\\env',
1687
 'D:\\a\\CrossMgr\\CrossMgr\\env\\lib\\site-packages',
1688
 'D:\\a\\CrossMgr\\CrossMgr\\env\\lib\\site-packages\\win32',
1689
 'D:\\a\\CrossMgr\\CrossMgr\\env\\lib\\site-packages\\win32\\lib',
1690
 'D:\\a\\CrossMgr\\CrossMgr\\env\\lib\\site-packages\\Pythonwin',
1691
 'D:\\a\\CrossMgr',
1692
 'D:\\a\\CrossMgr\\CrossMgr\\CrossMgrImpinj']

It's not obvious what changed. It appears that pyllrp is installed correctly as part of the environment setup...

[esitarski]

The problem appears with the most recent version of pip, which is deprecating installs from github urls. pip seems to work if you add the --use-pep517 parameter, but it looks like the future is to drop this capability entirely. Can you pass the --use-pep517 argument to pyinstaller? I can't figure this out, and the pip documentation isn't clear.

I managed to figure out how to publish pyllrp to pypi (haven't figured out how to do it automatically from github, but baby steps). This seems to fix the deprecation problem with pip.

The downside is that pyllrp is now available to the world and i expect to get enhancements and support issues ;) Oh well, perhaps for the best.

On Fri, Aug 9, 2024 at 5:44 PM Kim Wall @.***> wrote:

Looks like a problem with the build process. Comparing the GitHub action logs:

For v3.1.59-20240730090420:

Note 'd:\a\crossmgr\crossmgr\env\src\pyllrp',

1678 265 INFO: Module search paths (PYTHONPATH): 1679 ['D:\a\CrossMgr\CrossMgr\env\Scripts\pyinstaller.exe', 1680 'C:\hostedtoolcache\windows\Python\3.10.11\x64\python310.zip', 1681 'C:\hostedtoolcache\windows\Python\3.10.11\x64\DLLs', 1682 'C:\hostedtoolcache\windows\Python\3.10.11\x64\lib', 1683 'C:\hostedtoolcache\windows\Python\3.10.11\x64', 1684 'D:\a\CrossMgr\CrossMgr\env', 1685 'D:\a\CrossMgr\CrossMgr\env\lib\site-packages', 1686 'd:\a\crossmgr\crossmgr\env\src\pyllrp', 1687 'D:\a\CrossMgr\CrossMgr\env\lib\site-packages\win32', 1688 'D:\a\CrossMgr\CrossMgr\env\lib\site-packages\win32\lib', 1689 'D:\a\CrossMgr\CrossMgr\env\lib\site-packages\Pythonwin', 1690 'D:\a\CrossMgr', 1691 'D:\a\CrossMgr\CrossMgr\CrossMgrImpinj']

For v3.1.59-20240731143810: (note absence of pyllrp)

1680 296 INFO: Module search paths (PYTHONPATH): 1681 ['D:\a\CrossMgr\CrossMgr\env\Scripts\pyinstaller.exe', 1682 'C:\hostedtoolcache\windows\Python\3.10.11\x64\python310.zip', 1683 'C:\hostedtoolcache\windows\Python\3.10.11\x64\DLLs', 1684 'C:\hostedtoolcache\windows\Python\3.10.11\x64\lib', 1685 'C:\hostedtoolcache\windows\Python\3.10.11\x64', 1686 'D:\a\CrossMgr\CrossMgr\env', 1687 'D:\a\CrossMgr\CrossMgr\env\lib\site-packages', 1688 'D:\a\CrossMgr\CrossMgr\env\lib\site-packages\win32', 1689 'D:\a\CrossMgr\CrossMgr\env\lib\site-packages\win32\lib', 1690 'D:\a\CrossMgr\CrossMgr\env\lib\site-packages\Pythonwin', 1691 'D:\a\CrossMgr', 1692 'D:\a\CrossMgr\CrossMgr\CrossMgrImpinj']

It's not obvious what changed. It appears that pyllrp is installed correctly as part of the environment setup...

— Reply to this email directly, view it on GitHub https://github.com/esitarski/CrossMgr/issues/139#issuecomment-2278792434, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABGXKKD22ISNNMV5GTTSETZQUZ2HAVCNFSM6AAAAABMIOEADOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZYG44TENBTGQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>

--

Edward Sitarski

[moth754]

Will give it go when I'm back at the windows PC - currently at the wrong end of the country on holiday

[esitarski]

Presumed that pyllrp as a pypy.org module did the trick. Closing.