%global _empty_manifest_terminate_build 0
Name:		python-django-hosts
Version:	5.2
Release:	1
Summary:	Dynamic and static host resolving for Django. Maps hostnames to URLconfs.
License:	BSD
URL:		https://django-hosts.readthedocs.io/
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/83/9f/632b3c0605f87a5f853876f63f0c211c89934437dfcaa87741fa7623c58d/django-hosts-5.2.tar.gz
BuildArch:	noarch


%description
This Django app routes requests for specific hosts to different URL schemes
defined in modules called "hostconfs".
For example, if you own ``example.com`` but want to serve specific content
at ``api.example.com`` and ``beta.example.com``, add the following to a
``hosts.py`` file:
    from django_hosts import patterns, host
    host_patterns = patterns('path.to',
        host(r'api', 'api.urls', name='api'),
        host(r'beta', 'beta.urls', name='beta'),
    )
This causes requests to ``{api,beta}.example.com`` to be routed to their
corresponding URLconf. You can use your ``urls.py`` as a template for these
hostconfs.
Patterns are evaluated in order. If no pattern matches, the request is
processed in the usual way, ie. using the standard ``ROOT_URLCONF``.
The patterns on the left-hand side are regular expressions. For example,
the following ``ROOT_HOSTCONF`` setting will route ``foo.example.com``
and ``bar.example.com`` to the same URLconf.
    from django_hosts import patterns, host
    host_patterns = patterns('',
        host(r'(foo|bar)', 'path.to.urls', name='foo-or-bar'),
    )
  Remember:
  * Patterns are matched against the extreme left of the requested host
  * It is implied that all patterns end either with a literal full stop
    (ie. ".") or an end of line metacharacter.
  * As with all regular expressions, various metacharacters need quoting.

%package -n python3-django-hosts
Summary:	Dynamic and static host resolving for Django. Maps hostnames to URLconfs.
Provides:	python-django-hosts
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-django-hosts
This Django app routes requests for specific hosts to different URL schemes
defined in modules called "hostconfs".
For example, if you own ``example.com`` but want to serve specific content
at ``api.example.com`` and ``beta.example.com``, add the following to a
``hosts.py`` file:
    from django_hosts import patterns, host
    host_patterns = patterns('path.to',
        host(r'api', 'api.urls', name='api'),
        host(r'beta', 'beta.urls', name='beta'),
    )
This causes requests to ``{api,beta}.example.com`` to be routed to their
corresponding URLconf. You can use your ``urls.py`` as a template for these
hostconfs.
Patterns are evaluated in order. If no pattern matches, the request is
processed in the usual way, ie. using the standard ``ROOT_URLCONF``.
The patterns on the left-hand side are regular expressions. For example,
the following ``ROOT_HOSTCONF`` setting will route ``foo.example.com``
and ``bar.example.com`` to the same URLconf.
    from django_hosts import patterns, host
    host_patterns = patterns('',
        host(r'(foo|bar)', 'path.to.urls', name='foo-or-bar'),
    )
  Remember:
  * Patterns are matched against the extreme left of the requested host
  * It is implied that all patterns end either with a literal full stop
    (ie. ".") or an end of line metacharacter.
  * As with all regular expressions, various metacharacters need quoting.

%package help
Summary:	Development documents and examples for django-hosts
Provides:	python3-django-hosts-doc
%description help
This Django app routes requests for specific hosts to different URL schemes
defined in modules called "hostconfs".
For example, if you own ``example.com`` but want to serve specific content
at ``api.example.com`` and ``beta.example.com``, add the following to a
``hosts.py`` file:
    from django_hosts import patterns, host
    host_patterns = patterns('path.to',
        host(r'api', 'api.urls', name='api'),
        host(r'beta', 'beta.urls', name='beta'),
    )
This causes requests to ``{api,beta}.example.com`` to be routed to their
corresponding URLconf. You can use your ``urls.py`` as a template for these
hostconfs.
Patterns are evaluated in order. If no pattern matches, the request is
processed in the usual way, ie. using the standard ``ROOT_URLCONF``.
The patterns on the left-hand side are regular expressions. For example,
the following ``ROOT_HOSTCONF`` setting will route ``foo.example.com``
and ``bar.example.com`` to the same URLconf.
    from django_hosts import patterns, host
    host_patterns = patterns('',
        host(r'(foo|bar)', 'path.to.urls', name='foo-or-bar'),
    )
  Remember:
  * Patterns are matched against the extreme left of the requested host
  * It is implied that all patterns end either with a literal full stop
    (ie. ".") or an end of line metacharacter.
  * As with all regular expressions, various metacharacters need quoting.

%prep
%autosetup -n django-hosts-5.2

%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-django-hosts -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Mon Apr 10 2023 Python_Bot <Python_Bot@openeuler.org> - 5.2-1
- Package Spec generated