automatic import of python-sqlalchemy-utc

1 files changed, 131 insertions, 0 deletions

diff --git a/python-sqlalchemy-utc.spec b/python-sqlalchemy-utc.spec
new file mode 100644
index 0000000..0ac6cf8
--- /dev/null
+++ b/python-sqlalchemy-utc.spec
@@ -0,0 +1,131 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-SQLAlchemy-Utc
+Version:	0.14.0
+Release:	1
+Summary:	SQLAlchemy type to store aware datetime values
+License:	MIT License
+URL:		https://github.com/spoqa/sqlalchemy-utc
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/5c/db/2d8f421cece2758954278bd16e05e3f73ce86c0062577a1ccfd3eb4208cd/SQLAlchemy-Utc-0.14.0.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-setuptools
+Requires:	python3-SQLAlchemy
+
+%description
+This package provides a drop-in replacement of SQLAlchemy's built-in `DateTime`_
+type with ``timezone=True`` option enabled.  Although SQLAlchemy's built-in
+``DateTime`` type provides ``timezone=True`` option, since some vendors like
+SQLite and MySQL don't provide ``timestamptz`` data type, the option doesn't
+make any effect on these vendors.
+``UtcDateTime`` type is equivalent to the built-in ``DateTime`` with
+``timezone=True`` option enabled on vendors that support ``timestamptz``
+e.g. PostgreSQL, but on SQLite or MySQL, it shifts all ``datetime.datetime``
+values to UTC offset before store them, and returns always aware
+``datetime.datetime`` values through result sets.
+Long story short, ``UtcDateTime`` does:
+- take only aware ``datetime.datetime``,
+- return only aware ``datetime.datetime``,
+- never take or return naive ``datetime.datetime``,
+- ensure timestamps in database always to be encoded in UTC, and
+- work as you'd expect.
+A SQLAlchemy helper function, ``utcnow()``, is provided as an alternative
+to ``func.now()`` for generating ``UtcDateTime`` values on the server. For
+example: ``Column('time', UtcDateTime(), default=utcnow())``.
+Written by `Hong Minhee`_ at Spoqa_, and distributed under MIT license.
+
+%package -n python3-SQLAlchemy-Utc
+Summary:	SQLAlchemy type to store aware datetime values
+Provides:	python-SQLAlchemy-Utc
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-SQLAlchemy-Utc
+This package provides a drop-in replacement of SQLAlchemy's built-in `DateTime`_
+type with ``timezone=True`` option enabled.  Although SQLAlchemy's built-in
+``DateTime`` type provides ``timezone=True`` option, since some vendors like
+SQLite and MySQL don't provide ``timestamptz`` data type, the option doesn't
+make any effect on these vendors.
+``UtcDateTime`` type is equivalent to the built-in ``DateTime`` with
+``timezone=True`` option enabled on vendors that support ``timestamptz``
+e.g. PostgreSQL, but on SQLite or MySQL, it shifts all ``datetime.datetime``
+values to UTC offset before store them, and returns always aware
+``datetime.datetime`` values through result sets.
+Long story short, ``UtcDateTime`` does:
+- take only aware ``datetime.datetime``,
+- return only aware ``datetime.datetime``,
+- never take or return naive ``datetime.datetime``,
+- ensure timestamps in database always to be encoded in UTC, and
+- work as you'd expect.
+A SQLAlchemy helper function, ``utcnow()``, is provided as an alternative
+to ``func.now()`` for generating ``UtcDateTime`` values on the server. For
+example: ``Column('time', UtcDateTime(), default=utcnow())``.
+Written by `Hong Minhee`_ at Spoqa_, and distributed under MIT license.
+
+%package help
+Summary:	Development documents and examples for SQLAlchemy-Utc
+Provides:	python3-SQLAlchemy-Utc-doc
+%description help
+This package provides a drop-in replacement of SQLAlchemy's built-in `DateTime`_
+type with ``timezone=True`` option enabled.  Although SQLAlchemy's built-in
+``DateTime`` type provides ``timezone=True`` option, since some vendors like
+SQLite and MySQL don't provide ``timestamptz`` data type, the option doesn't
+make any effect on these vendors.
+``UtcDateTime`` type is equivalent to the built-in ``DateTime`` with
+``timezone=True`` option enabled on vendors that support ``timestamptz``
+e.g. PostgreSQL, but on SQLite or MySQL, it shifts all ``datetime.datetime``
+values to UTC offset before store them, and returns always aware
+``datetime.datetime`` values through result sets.
+Long story short, ``UtcDateTime`` does:
+- take only aware ``datetime.datetime``,
+- return only aware ``datetime.datetime``,
+- never take or return naive ``datetime.datetime``,
+- ensure timestamps in database always to be encoded in UTC, and
+- work as you'd expect.
+A SQLAlchemy helper function, ``utcnow()``, is provided as an alternative
+to ``func.now()`` for generating ``UtcDateTime`` values on the server. For
+example: ``Column('time', UtcDateTime(), default=utcnow())``.
+Written by `Hong Minhee`_ at Spoqa_, and distributed under MIT license.
+
+%prep
+%autosetup -n SQLAlchemy-Utc-0.14.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-SQLAlchemy-Utc -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 0.14.0-1
+- Package Spec generated