Hi team, I created a custom component from the Dataset template. I completed the configuration and ran "gradio cc build" without any errors. However, when I installed the component, it turned out to be exactly the same as the original Dataset component. I tried making some minor changes like the background color style, but it still didn't work, even though the build section completed successfully.
Have you searched existing issues? π
[X] I have searched and found no existing issues
Reproduction
[build-system]
requires = [
"hatchling",
"hatch-requirements-txt",
"hatch-fancy-pypi-readme>=22.5.0",
]
build-backend = "hatchling.build"
[project]
name = "gradio_dataset"
version = "0.0.2"
description = "Python library for easily interacting with trained machine learning models"
readme = "README.md"
license = "Apache-2.0"
requires-python = ">=3.8"
authors = [{ name = "thenHung", email = "email" }]
keywords = [
"gradio-custom-component",
"gradio-template-Dataset"
]
# Add dependencies here
dependencies = ["gradio>=4.44.1,<5.0", "gradio-modal-component>=0.0.4,<1.0"]
classifiers = [
'Development Status :: 3 - Alpha',
'Operating System :: OS Independent',
'Programming Language :: Python :: 3',
'Programming Language :: Python :: 3 :: Only',
'Programming Language :: Python :: 3.8',
'Programming Language :: Python :: 3.9',
'Programming Language :: Python :: 3.10',
'Programming Language :: Python :: 3.11',
'Topic :: Scientific/Engineering',
'Topic :: Scientific/Engineering :: Artificial Intelligence',
'Topic :: Scientific/Engineering :: Visualization',
]
# The repository and space URLs are optional, but recommended.
# Adding a repository URL will create a badge in the auto-generated README that links to the repository.
# Adding a space URL will create a badge in the auto-generated README that links to the space.
# This will make it easy for people to find your deployed demo or source code when they
# encounter your project in the wild.
# [project.urls]
# repository = "your github repository"
# space = "your space url"
[project.optional-dependencies]
dev = ["build", "twine"]
[tool.hatch.build]
artifacts = ["/backend/gradio_dataset/templates", "*.pyi"]
[tool.hatch.build.targets.wheel]
packages = ["/backend/gradio_dataset"]
Screenshot
No response
Logs
π¦ Building package in dataset_component β
β π’ Package will use version 0.0.2 defined in pyproject.toml file. Set --bump-version to automatically bump the version number. β
β β Documentation generated in demo/space.py and README.md. Pass --no-generate-docs to disable auto documentation. β
β π¨ Building frontend β
β β Build succeeded! β
β π· Building... (/home/lthun/anaconda3/envs/gradio3/bin/python3 -m build /home/lthun/linux_workspace/gradio_lib/dataset_component) β
β β Build succeeded! β
β π‘ Wheel located in /home/lthun/linux_workspace/gradio_lib/dataset_component/dist β
β°βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Describe the bug
Hi team, I created a custom component from the Dataset template. I completed the configuration and ran "gradio cc build" without any errors. However, when I installed the component, it turned out to be exactly the same as the original Dataset component. I tried making some minor changes like the background color style, but it still didn't work, even though the build section completed successfully.
Have you searched existing issues? π
Reproduction
Screenshot
No response
Logs
System Info
Severity
I can work around it