[GH-ISSUE #77] 'eel.chrome' has no attribute 'get_instance_path' #73

Closed
opened 2026-02-26 12:20:23 +03:00 by kerem · 4 comments
Owner

Originally created by @DevBefell on GitHub (Nov 2, 2019).
Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/77

Traceback (most recent call last):
File "run.py", line 9, in
apte.run() File "C:\Users-------\Downloads\auto-py-to-exe-2.6.5\auto_py_to_exe_main_.py", line 375, in run
chrome_instance_path = eel.chrome.get_instance_path()AttributeError: module 'eel.chrome' has no attribute 'get_instance_path'

What causes this?

Originally created by @DevBefell on GitHub (Nov 2, 2019). Original GitHub issue: https://github.com/brentvollebregt/auto-py-to-exe/issues/77 Traceback (most recent call last): File "run.py", line 9, in <module> apte.run() File "C:\Users\-------\Downloads\auto-py-to-exe-2.6.5\auto_py_to_exe\__main__.py", line 375, in run chrome_instance_path = eel.chrome.get_instance_path()AttributeError: module 'eel.chrome' has no attribute 'get_instance_path' What causes this?
kerem closed this issue 2026-02-26 12:20:23 +03:00
Author
Owner

@brentvollebregt commented on GitHub (Nov 3, 2019):

What version of auto-py-to-exe and Eel do you have installed?

<!-- gh-comment-id:549093858 --> @brentvollebregt commented on GitHub (Nov 3, 2019): What version of auto-py-to-exe and Eel do you have installed?
Author
Owner

@DevBefell commented on GitHub (Nov 4, 2019):

Latest Versions, just installed Eel and auto-py-to-exe, it works when run by console (python -m auto_py_to_exe), not by running run.py

<!-- gh-comment-id:549201025 --> @DevBefell commented on GitHub (Nov 4, 2019): Latest Versions, just installed Eel and auto-py-to-exe, it works when run by console (python -m auto_py_to_exe), not by running run.py
Author
Owner

@brentvollebregt commented on GitHub (Nov 4, 2019):

I am unable to reproduce this error when executing python run.py. Could you please provide more details?

I remember fixing this issue in a previous commit (3a08aeaa8b) and enforcing that Eel 0.10.0 is used.

I see that samuelhwilliams/Eel@42425c5125 changed get_instance_path to find_path (yet another breaking change made by them) but this would not affect this package as I explicitly state that Eel 0.10.0 must be used. Please make sure you are running Eel 0.10.0 as stated in requirements.txt

<!-- gh-comment-id:549203340 --> @brentvollebregt commented on GitHub (Nov 4, 2019): I am unable to reproduce this error when executing `python run.py`. Could you please provide more details? I remember fixing this issue in a previous commit (3a08aeaa8b9eeae950cee9cd5f1bda168c7077cf) and enforcing that Eel 0.10.0 is used. I see that samuelhwilliams/Eel@42425c512577311053e1357cf96266b7f3fff55b changed `get_instance_path` to `find_path` (yet another breaking change made by them) but this would not affect this package as I explicitly state that Eel 0.10.0 must be used. Please make sure you are running Eel 0.10.0 as stated in [requirements.txt](https://github.com/brentvollebregt/auto-py-to-exe/blob/master/requirements.txt)
Author
Owner

@brentvollebregt commented on GitHub (Nov 13, 2019):

This should be fixed in 2.6.6 for those that installed Eel 0.11.0 instead of the version stated in requirements.txt and setup.py

<!-- gh-comment-id:553578609 --> @brentvollebregt commented on GitHub (Nov 13, 2019): This should be fixed in 2.6.6 for those that installed Eel 0.11.0 instead of the version stated in requirements.txt and setup.py
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/auto-py-to-exe#73
No description provided.