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

Gradio 3.35.2 breaks compatibility due to missing components #4564

Closed
1 task done
vladmandic opened this issue Jun 19, 2023 · 3 comments · Fixed by #4566
Closed
1 task done

Gradio 3.35.2 breaks compatibility due to missing components #4564

vladmandic opened this issue Jun 19, 2023 · 3 comments · Fixed by #4566
Assignees
Labels
bug Something isn't working
Milestone

Comments

@vladmandic
Copy link

Describe the bug

Gradio 3.35.2 does not define some components that were previsouly available
This is most likely due to changes in #4487

Currently using Gradio 3.32.0 where such components are available
This is blocking any possible upgrades

Impact is to app ecosystem with 20k+ user installs

Is there an existing issue for this?

  • I have searched the existing issues

Reproduction

import gradio as gr
Form = gr.components.Form
FormComponent = gr.components.FormComponent

Screenshot

No response

Logs

AttributeError: module 'gradio.components' has no attribute 'Form'
AttributeError: module 'gradio.components' has no attribute 'FormComponent'

System Info

Gradio 3.35.2
Chrome 114
Windows 11

Severity

blocking upgrade to latest gradio version

@vladmandic vladmandic added the bug Something isn't working label Jun 19, 2023
@abidlabs
Copy link
Member

Hi @vladmandic thanks for the catch. We'll restore these for backwards compatibility, even though these classes are meant to be used internally. To understand better, what are you using these classes for?

@abidlabs abidlabs added this to the 3.x milestone Jun 19, 2023
@vladmandic
Copy link
Author

To create custom gradio components that work well with forms.
Example: https://github.com/vladmandic/automatic/blob/master/modules/ui_components.py

Even if code is not what it should be, its used by tons of 3rd party extensions and change would have to be done on massive scale - basically locking app down forever to old version of gradio.

@abidlabs
Copy link
Member

Fair enough

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.

2 participants