python-repoze.who/python-repoze.who.spec

79 lines
2.6 KiB
RPMSpec

#
# spec file for package python-repoze.who
#
# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.
# Please submit bugfixes or comments via http://bugs.opensuse.org/
#
%{?!python_module:%define python_module() python-%{**} python3-%{**}}
Name: python-repoze.who
%global modname repoze.who
Version: 2.3
Release: 0
Url: http://www.repoze.org
Summary: Identification and authentication framework for WSGI
License: SUSE-Repoze
Group: Development/Languages/Python
Source: https://pypi.io/packages/source/r/%{modname}/%{modname}-%{version}.tar.gz
BuildRoot: %{_tmppath}/%{name}-%{version}-build
BuildRequires: %{python_module Paste}
BuildRequires: %{python_module Sphinx}
BuildRequires: %{python_module WebOb}
BuildRequires: %{python_module devel}
BuildRequires: %{python_module devel}
BuildRequires: %{python_module repoze.sphinx.autointerface}
BuildRequires: %{python_module setuptools}
BuildRequires: %{python_module zope.interface}
BuildRequires: fdupes
BuildRequires: python-rpm-macros
Requires: python-Paste
Requires: python-WebOb
Requires: python-zope.interface
BuildArch: noarch
%python_subpackages
%description
repoze.who is an identification and authentication framework
for arbitrary WSGI applications. repoze.who can be configured
either as WSGI middleware or as an API for use by an application.
repoze.who is inspired by Zope 2's Pluggable Authentication
Service (PAS) (but repoze.who is not dependent on Zope in any
way; it is useful for any WSGI application). It provides no facility
for authorization (ensuring whether a user can or cannot perform the
operation implied by the request). This is considered to be the
domain of the WSGI application.
%prep
%setup -q -n %{modname}-%{version}
%build
%python_build
cd docs && make html && rm -r .build/html/.buildinfo
%install
%python_install
%python_expand %fdupes %{buildroot}%{$python_sitelib}/
%check
%python_exec setup.py test
%files %{python_files}
%defattr(-,root,root,-)
%doc *.txt docs/.build/html
%{python_sitelib}/*
%changelog