summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--.gitignore1
-rw-r--r--python-gviz-data-table.spec150
-rw-r--r--sources1
3 files changed, 152 insertions, 0 deletions
diff --git a/.gitignore b/.gitignore
index e69de29..4788e93 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/gviz_data_table-2.0.0.tar.gz
diff --git a/python-gviz-data-table.spec b/python-gviz-data-table.spec
new file mode 100644
index 0000000..fd4e010
--- /dev/null
+++ b/python-gviz-data-table.spec
@@ -0,0 +1,150 @@
+%global _empty_manifest_terminate_build 0
+Name: python-gviz-data-table
+Version: 2.0.0
+Release: 1
+Summary: Python API for Google Visualization
+License: BSD
+URL: https://pypi.org/project/gviz-data-table/
+Source0: https://mirrors.nju.edu.cn/pypi/web/packages/c3/6a/516ba42f4e85c548508a2aee130b0a5531f13e5517a9adab77dd676dcdf6/gviz_data_table-2.0.0.tar.gz
+BuildArch: noarch
+
+
+%description
+Gviz Data Table is a simple Python library for converting Python data types
+to the Google Visualization Data Table JSON format.
+https://developers.google.com/chart/interactive/docs/reference
+The Google Visualization Library itself is a Javascript library that provides
+interactive charts that work in pretty much any browser. The libraries cover
+most use cases including tables, as well as charts, so you can have a chart
+and a table of the same data.
+Gviz Data Table is designed primarily for use with data sources such as
+databases. Usage is supposed to be minimal: you provide a schema, that is a
+list of columns, and the rows of data. A column must have a name and Python
+data type. It can also have a label which will be used for display, otherwise
+the name will be used.
+Each row is a sequence of cells. Although columns are explicit row names are
+always the first cell in a row. Like columns, cells can also have labels.
+Gviz Data Table will validate each cell to make sure that data conforms to
+type specified in the schema and will map Python types to their JSON
+equivalent but it does not coerce any data, i.e. if a column has type `int`
+and a cell's data is a string containing numerical characters only this will
+still raise an exception.
+Gviz Data Table handles data conversion only. You will need to add the
+necessary Javascript to an web page in order for any charts or table to be
+drawn. Tables, columns and cells can all have options which are just
+dictionaries. As there is no further definition of options no validation of
+their items occurs. Unknown items will simply be ignored.
+Gviz Data Table is composed of: one container class ``Table``; two data
+classes, ``Cell`` and ``Column`` and one JSON encoder. Application code should
+probably only ever need to use Table and the encoder.
+
+%package -n python3-gviz-data-table
+Summary: Python API for Google Visualization
+Provides: python-gviz-data-table
+BuildRequires: python3-devel
+BuildRequires: python3-setuptools
+BuildRequires: python3-pip
+%description -n python3-gviz-data-table
+Gviz Data Table is a simple Python library for converting Python data types
+to the Google Visualization Data Table JSON format.
+https://developers.google.com/chart/interactive/docs/reference
+The Google Visualization Library itself is a Javascript library that provides
+interactive charts that work in pretty much any browser. The libraries cover
+most use cases including tables, as well as charts, so you can have a chart
+and a table of the same data.
+Gviz Data Table is designed primarily for use with data sources such as
+databases. Usage is supposed to be minimal: you provide a schema, that is a
+list of columns, and the rows of data. A column must have a name and Python
+data type. It can also have a label which will be used for display, otherwise
+the name will be used.
+Each row is a sequence of cells. Although columns are explicit row names are
+always the first cell in a row. Like columns, cells can also have labels.
+Gviz Data Table will validate each cell to make sure that data conforms to
+type specified in the schema and will map Python types to their JSON
+equivalent but it does not coerce any data, i.e. if a column has type `int`
+and a cell's data is a string containing numerical characters only this will
+still raise an exception.
+Gviz Data Table handles data conversion only. You will need to add the
+necessary Javascript to an web page in order for any charts or table to be
+drawn. Tables, columns and cells can all have options which are just
+dictionaries. As there is no further definition of options no validation of
+their items occurs. Unknown items will simply be ignored.
+Gviz Data Table is composed of: one container class ``Table``; two data
+classes, ``Cell`` and ``Column`` and one JSON encoder. Application code should
+probably only ever need to use Table and the encoder.
+
+%package help
+Summary: Development documents and examples for gviz-data-table
+Provides: python3-gviz-data-table-doc
+%description help
+Gviz Data Table is a simple Python library for converting Python data types
+to the Google Visualization Data Table JSON format.
+https://developers.google.com/chart/interactive/docs/reference
+The Google Visualization Library itself is a Javascript library that provides
+interactive charts that work in pretty much any browser. The libraries cover
+most use cases including tables, as well as charts, so you can have a chart
+and a table of the same data.
+Gviz Data Table is designed primarily for use with data sources such as
+databases. Usage is supposed to be minimal: you provide a schema, that is a
+list of columns, and the rows of data. A column must have a name and Python
+data type. It can also have a label which will be used for display, otherwise
+the name will be used.
+Each row is a sequence of cells. Although columns are explicit row names are
+always the first cell in a row. Like columns, cells can also have labels.
+Gviz Data Table will validate each cell to make sure that data conforms to
+type specified in the schema and will map Python types to their JSON
+equivalent but it does not coerce any data, i.e. if a column has type `int`
+and a cell's data is a string containing numerical characters only this will
+still raise an exception.
+Gviz Data Table handles data conversion only. You will need to add the
+necessary Javascript to an web page in order for any charts or table to be
+drawn. Tables, columns and cells can all have options which are just
+dictionaries. As there is no further definition of options no validation of
+their items occurs. Unknown items will simply be ignored.
+Gviz Data Table is composed of: one container class ``Table``; two data
+classes, ``Cell`` and ``Column`` and one JSON encoder. Application code should
+probably only ever need to use Table and the encoder.
+
+%prep
+%autosetup -n gviz-data-table-2.0.0
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+ find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+ find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+ find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+ find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+ find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-gviz-data-table -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 2.0.0-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..b5279a6
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+895af771f2f3508f9ae5b16546cd349c gviz_data_table-2.0.0.tar.gz