automatic import of python-namedentities

3 files changed, 158 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..d18293a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/namedentities-1.9.4.zip
diff --git a/python-namedentities.spec b/python-namedentities.spec
new file mode 100644
index 0000000..ebfc5a1
--- /dev/null
+++ b/python-namedentities.spec
@@ -0,0 +1,156 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-namedentities
+Version:	1.9.4
+Release:	1
+Summary:	Named (and numeric) HTML entities to/from each other or Unicode
+License:	Apache License 2.0
+URL:		http://bitbucket.org/jeunice/namedentities
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/9f/6e/d28dda74e61f53976679ad2f6778dfd1e1780d217e53eb61e50ac5e65b09/namedentities-1.9.4.zip
+BuildArch:	noarch
+
+
+%description
+Python 2::
+    from __future__ import print_function # Python 2/3 compatibiltiy
+    from namedentities import *
+    u = u'both em\u2014and–dashes…'
+    print("named:  ", repr(named_entities(u)))
+    print("numeric:", repr(numeric_entities(u)))
+    print("hex:"   ", repr(hex_entities(u)))
+    print("unicode:", repr(unicode_entities(u)))
+yields::
+    named:   'both em—and–dashes…'
+    numeric: 'both em—and–dashes…'
+    hex:     'both em—and–dashes…'
+    unicode: u'both em\u2014and\u2013dashes\u2026'
+You can do just about the same thing in Python 3, but you have to use a
+``print`` function rather than a ``print`` statement, and prior to 3.3, you
+have to skip the ``u`` prefix that in Python 2 marks string literals as
+being Unicode literals. In Python 3.3 and following, however, you can start
+using the ``u`` marker again, if you like. While all Python 3 strings are
+Unicode, it helps with cross-version code compatibility. (You can use the
+``six`` cross-version compatibility library, as the tests do.)
+One good use for ``unicode_entities`` is to create cross-platform,
+cross-Python-version strings that conceptually contain
+Unicode characters, but spelled out as named (or numeric) HTML entities. For
+example::
+    unicode_entities('This ’thing” is great!')
+This has the advantage of using only ASCII characters and common
+string encoding mechanisms, yet rendering full Unicode strings upon
+reconstitution.  You can use the other functions, say ``named_entities()``,
+to go from Unicode characters to named entities.
+
+%package -n python3-namedentities
+Summary:	Named (and numeric) HTML entities to/from each other or Unicode
+Provides:	python-namedentities
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-namedentities
+Python 2::
+    from __future__ import print_function # Python 2/3 compatibiltiy
+    from namedentities import *
+    u = u'both em\u2014and–dashes…'
+    print("named:  ", repr(named_entities(u)))
+    print("numeric:", repr(numeric_entities(u)))
+    print("hex:"   ", repr(hex_entities(u)))
+    print("unicode:", repr(unicode_entities(u)))
+yields::
+    named:   'both em—and–dashes…'
+    numeric: 'both em—and–dashes…'
+    hex:     'both em—and–dashes…'
+    unicode: u'both em\u2014and\u2013dashes\u2026'
+You can do just about the same thing in Python 3, but you have to use a
+``print`` function rather than a ``print`` statement, and prior to 3.3, you
+have to skip the ``u`` prefix that in Python 2 marks string literals as
+being Unicode literals. In Python 3.3 and following, however, you can start
+using the ``u`` marker again, if you like. While all Python 3 strings are
+Unicode, it helps with cross-version code compatibility. (You can use the
+``six`` cross-version compatibility library, as the tests do.)
+One good use for ``unicode_entities`` is to create cross-platform,
+cross-Python-version strings that conceptually contain
+Unicode characters, but spelled out as named (or numeric) HTML entities. For
+example::
+    unicode_entities('This ’thing” is great!')
+This has the advantage of using only ASCII characters and common
+string encoding mechanisms, yet rendering full Unicode strings upon
+reconstitution.  You can use the other functions, say ``named_entities()``,
+to go from Unicode characters to named entities.
+
+%package help
+Summary:	Development documents and examples for namedentities
+Provides:	python3-namedentities-doc
+%description help
+Python 2::
+    from __future__ import print_function # Python 2/3 compatibiltiy
+    from namedentities import *
+    u = u'both em\u2014and–dashes…'
+    print("named:  ", repr(named_entities(u)))
+    print("numeric:", repr(numeric_entities(u)))
+    print("hex:"   ", repr(hex_entities(u)))
+    print("unicode:", repr(unicode_entities(u)))
+yields::
+    named:   'both em—and–dashes…'
+    numeric: 'both em—and–dashes…'
+    hex:     'both em—and–dashes…'
+    unicode: u'both em\u2014and\u2013dashes\u2026'
+You can do just about the same thing in Python 3, but you have to use a
+``print`` function rather than a ``print`` statement, and prior to 3.3, you
+have to skip the ``u`` prefix that in Python 2 marks string literals as
+being Unicode literals. In Python 3.3 and following, however, you can start
+using the ``u`` marker again, if you like. While all Python 3 strings are
+Unicode, it helps with cross-version code compatibility. (You can use the
+``six`` cross-version compatibility library, as the tests do.)
+One good use for ``unicode_entities`` is to create cross-platform,
+cross-Python-version strings that conceptually contain
+Unicode characters, but spelled out as named (or numeric) HTML entities. For
+example::
+    unicode_entities('This ’thing” is great!')
+This has the advantage of using only ASCII characters and common
+string encoding mechanisms, yet rendering full Unicode strings upon
+reconstitution.  You can use the other functions, say ``named_entities()``,
+to go from Unicode characters to named entities.
+
+%prep
+%autosetup -n namedentities-1.9.4
+
+%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-namedentities -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Mon May 15 2023 Python_Bot <Python_Bot@openeuler.org> - 1.9.4-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..2318767
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+57a12e0a99b5c49752804a1ff6167d73  namedentities-1.9.4.zip