Lazy load interactive or static variants of a component individually, rather than loading both variants regardless. This change will improve performance for many applications.

[pngwn]

Description

Lazy load only the interactive or static variant of a component as required rather than loading both. This needs a follow up or two but works well.

Closes: #3360

🎯 PRs Should Target Issues

Before your create a PR, please check to see if there is an existing issue for this change. If not, please create an issue before you create this PR, unless the fix is very small.

Not adhering to this guideline will result in the PR being closed.

Tests

1. PRs will only be merged if tests pass on CI. To run the tests locally, please set up your Gradio environment locally and run the tests: bash scripts/run_all_tests.sh

2. You may need to run the linters: bash scripts/format_backend.sh and bash scripts/format_frontend.sh

[gradio-pr-bot]

🪼 branch checks and previews

•	Name	Status	URL
	Spaces	ready!	Spaces preview
	Website	ready!	Website preview
	Storybook	ready!	Storybook preview
	Visual tests	all good!	Build review
🦄	Changes	detected!	Details

---

Install Gradio from this PR

pip install https://gradio-builds.s3.amazonaws.com/5028cf9dd453c7d5ce34fd396f79b4f3051d406c/gradio-3.40.1-py3-none-any.whl

Install Gradio Python Client from this PR

pip install "gradio-client @ git+https://github.com/gradio-app/gradio@5028cf9dd453c7d5ce34fd396f79b4f3051d406c#subdirectory=client/python"

[gradio-pr-bot]

🦄 change detected

This Pull Request includes changes to the following packages.

Package	Version
@gradio/accordion	patch
@gradio/annotatedimage	patch
@gradio/app	patch
@gradio/audio	patch
@gradio/box	patch
@gradio/chatbot	patch
@gradio/checkbox	patch
@gradio/checkboxgroup	patch
@gradio/code	patch
@gradio/colorpicker	patch
@gradio/dataframe	patch
@gradio/dropdown	patch
@gradio/file	patch
@gradio/gallery	patch
@gradio/highlightedtext	patch
@gradio/html	patch
@gradio/image	patch
@gradio/json	patch
@gradio/label	patch
@gradio/markdown	patch
@gradio/model3d	patch
@gradio/number	patch
@gradio/plot	patch
@gradio/radio	patch
@gradio/slider	patch
@gradio/statustracker	patch
@gradio/timeseries	patch
@gradio/video	patch
gradio	patch

• Maintainers can select this checkbox to manually select packages to update.

With the following changelog entry.

Lazy load interactive or static variants of a component individually, rather than loading both variants regardless. This change will improve performance for many applications.

Maintainers or the PR author can modify the PR title to modify this entry.

Something isn't right?

• Maintainers can change the version label to modify the version bump.
• If the bot has failed to detect any changes, or if this pull request needs to update multiple packages to different versions or requires a more comprehensive changelog entry, maintainers can update the changelog file directly.

[pngwn]

Dno whats going on with the guides, will revert those changes before merging.

[abidlabs]

In the sync you mentioned that this PR still needs some fixes to handle update(interactive=) -- let us know when that's ready, happy to review

[pngwn]

@abidlabs READY FOR REVIEW!!!

[dawoodkhan82]

@pngwn Don't think updating interactive=False is working properly. I tried modifying hello_blocks for example:

import gradio as gr

def greet(name):
    return "Hello " + name + "!", gr.Textbox.update("sorry", interactive=False)

with gr.Blocks() as demo:
    name = gr.Textbox(label="Name")
    output = gr.Textbox(label="Output Box")
    greet_btn = gr.Button("Greet")
    greet_btn.click(fn=greet, inputs=[name], outputs=[output, name], api_name="greet")

if __name__ == "__main__":
    demo.launch()

[pngwn]

I'll take a look!

[aliabid94]

Don't think updating interactive=False is working properly

I think this is because now we're loading the appropriate interactive/static version once at load time, right?

One issue I noticed is that even as an output component, the dataframe component still allows for editing the component. Seems like this issue was introduced before this PR though.

Otherwise looks great!

[pngwn]

I think this is because now we're loading the appropriate interactive/static version once at load time, right?

I added some logic to load new components (if necessary when interactive changes), it just wasn't working all of the time, cos i messed up the order.

@dawoodkhan82 it should work now, if you can retest.

@aliabid94 I think i broke the dataframe in my refactor. Fixed that here as well.

[aliabid94]

Looks great to me!

[dawoodkhan82]

@pngwn tested and it works great now!