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

Incompatibility with Python 3.13.0 while using gradio library #9696

Closed
1 task done
samy-FERGUI opened this issue Oct 14, 2024 · 2 comments · Fixed by #9757
Closed
1 task done

Incompatibility with Python 3.13.0 while using gradio library #9696

samy-FERGUI opened this issue Oct 14, 2024 · 2 comments · Fixed by #9757
Assignees
Labels
bug Something isn't working

Comments

@samy-FERGUI
Copy link
Contributor

samy-FERGUI commented Oct 14, 2024

  • I have searched to see if a similar issue already exists.

Is your feature request related to a problem? Please describe.

Yes, the problem is related to Gradio's compatibility with Python 3.13.0. While the documentation mentions that Gradio supports Python versions >= 3.10, it seems that Python 3.13.0, the most recent python release, is not fully compatible due to issues with some dependencies, such as pydub and audioop. Specifically, audioop is not found in Python 3.13.0, which causes a ModuleNotFoundError when running Gradio.

Steps to reproduce:

  1. Install Python 3.13.0.
  2. Create a virtual environment and install Gradio.
  3. Run a basic Gradio app (the exemple given in readme.
  4. Observe the error:
    ModuleNotFoundError: No module named 'audioop'
    

Describe the solution you'd like

For the moment, i would like to update the readme to clearly state this issue.

@samy-FERGUI
Copy link
Contributor Author

@abidlabs i would like to work on this issue, could you assign it to me please ?

@aliabid94
Copy link
Collaborator

Thanks @samy-FERGUI !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants