From da755f6d6b5b3bd50dde29d43aed28ca015e3deb Mon Sep 17 00:00:00 2001
From: Alfredo Moralejo <amoralej@redhat.com>
Date: Sep 09 2021 01:21:11 +0000
Subject: Import python-sniffio-1.2.0-2.el9 in CloudSIG xena


---

diff --git a/.python-sniffio.metadata b/.python-sniffio.metadata
new file mode 100644
index 0000000..245299c
--- /dev/null
+++ b/.python-sniffio.metadata
@@ -0,0 +1 @@
+8b195bcc5c3acdd3702df0df2c5c0024599fb926  SOURCES/sniffio-1.2.0.tar.gz
diff --git a/SPECS/python-sniffio.spec b/SPECS/python-sniffio.spec
new file mode 100644
index 0000000..ef700f5
--- /dev/null
+++ b/SPECS/python-sniffio.spec
@@ -0,0 +1,107 @@
+# what it's called on pypi
+%global srcname sniffio
+# what it's imported as
+%global libname sniffio
+# name of egg info directory
+%global eggname sniffio
+# package name fragment
+%global pkgname sniffio
+
+%global common_description %{expand:
+You're writing a library.  You've decided to be ambitious, and support multiple
+async I/O packages, like Trio, and asyncio, and ... You've written a bunch of
+clever code to handle all the differences.  But... how do you know which piece
+of clever code to run?  This is a tiny package whose only purpose is to let you
+detect which async library your code is running under.}
+
+%bcond_without  tests
+
+
+Name:           python-%{pkgname}
+Version:        1.2.0
+Release:        2%{?dist}
+Summary:        Sniff out which async library your code is running under
+License:        MIT or ASL 2.0
+URL:            https://github.com/python-trio/sniffio
+Source0:        %pypi_source
+BuildArch:      noarch
+
+
+%description %{common_description}
+
+
+%package -n python3-%{pkgname}
+Summary:        %{summary}
+BuildRequires:  python3-devel
+BuildRequires:  python3-setuptools
+%if %{with tests}
+BuildRequires:  python3-pytest
+BuildRequires:  python3-curio
+%if 0%{?rhel} && 0%{?rhel} < 9
+BuildRequires:  python3-contextvars
+%endif
+%endif
+
+
+%description -n python3-%{pkgname} %{common_description}
+
+
+%prep
+%autosetup -n %{srcname}-%{version}
+rm -rf %{eggname}.egg-info
+
+
+%build
+%py3_build
+
+
+%install
+%py3_install
+
+
+%if %{with tests}
+%check
+%pytest --verbose
+%endif
+
+
+%files -n python3-%{pkgname}
+%license LICENSE LICENSE.MIT LICENSE.APACHE2
+%doc README.rst
+%{python3_sitelib}/%{libname}
+%{python3_sitelib}/%{eggname}-%{version}-py%{python3_version}.egg-info
+
+
+%changelog
+* Wed Jan 27 2021 Fedora Release Engineering <releng@fedoraproject.org> - 1.2.0-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
+
+* Fri Nov 20 2020 Joel Capitao <jcapitao@redhat.com> - 1.2.0-1
+- Update to 1.2.0 (#1887203)
+
+* Wed Jul 29 2020 Fedora Release Engineering <releng@fedoraproject.org> - 1.1.0-7
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
+
+* Tue May 26 2020 Miro Hrončok <mhroncok@redhat.com> - 1.1.0-6
+- Rebuilt for Python 3.9
+
+* Thu Jan 30 2020 Fedora Release Engineering <releng@fedoraproject.org> - 1.1.0-5
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
+
+* Thu Oct 03 2019 Miro Hrončok <mhroncok@redhat.com> - 1.1.0-4
+- Rebuilt for Python 3.8.0rc1 (#1748018)
+
+* Mon Aug 19 2019 Miro Hrončok <mhroncok@redhat.com> - 1.1.0-3
+- Rebuilt for Python 3.8
+
+* Fri Jul 26 2019 Fedora Release Engineering <releng@fedoraproject.org> - 1.1.0-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
+
+* Tue May 14 2019 Carl George <carl@george.computer> - 1.1.0-1
+- Latest upstream
+
+* Sat Feb 02 2019 Fedora Release Engineering <releng@fedoraproject.org> - 1.0.0-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
+
+* Wed Sep 12 2018 Carl George <carl@george.computer> - 1.0.0-1
+- Initial package