Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: object has no attribute 'should_paint' #60

Closed
Wandalen opened this issue Jun 6, 2024 · 7 comments
Closed

Bug: object has no attribute 'should_paint' #60

Wandalen opened this issue Jun 6, 2024 · 7 comments
Assignees

Comments

@Wandalen
Copy link

Wandalen commented Jun 6, 2024

Hello! I have issue with

  File "C:\Users\kosli\AppData\Roaming\Python\Python312\site-packages\gpt_computer_assistant\gpt_computer_assistant.py", line 226, in paintEvent
    if not self.should_paint:
           ^^^^^^^^^^^^^^^^^
AttributeError: 'MainWindow' object has no attribute 'should_paint'

How to fix that? Do I miss something?

@onuratakan
Copy link
Member

onuratakan commented Jun 6, 2024

Hi can you upgrade?

pip3 install gpt-computer-assistant --upgrade

@onuratakan onuratakan self-assigned this Jun 6, 2024
@onuratakan
Copy link
Member

@Wandalen Is it fixed?

@Wandalen
Copy link
Author

Wandalen commented Jun 6, 2024

Tried to do that, but that didn't help.

image

@onuratakan
Copy link
Member

Actualy pip doesnt upgrade in the first time of run. Please run again the update command. or

pip3 install gpt-computer-assistant==0.8.9

@BenjaminMichaelis
Copy link

I am getting this error as well

@vietnguyengit
Copy link
Contributor

Eventually, everyone starting this project from scratch will encounter this issue. Dependencies defined in requirements.txt left unpinned can lead to conflicts, especially with dependencies of dependencies. Project owners should consider implementing a better dependency management tool such as poetry, check out the following sample: https://github.com/openai/openai-python/blob/main/pyproject.toml

@Mideky-hub
Copy link
Contributor

@onuratakan that was fixed in my patch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants