%global _empty_manifest_terminate_build 0
Name:		python-aiohttp-sentry
Version:	0.6.0
Release:	1
Summary:	An aiohttp middleware for reporting errors to Sentry
License:	MIT License
URL:		https://github.com/underyx/aiohttp-sentry
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/78/33/b0053af4c7027e88606e8ff2498a7f4fe8c36397619bfcd07b5a20f5ffc5/aiohttp-sentry-0.6.0.tar.gz
BuildArch:	noarch

Requires:	python3-raven-aiohttp
Requires:	python3-raven

%description
If you want to customize error reporting,
you can use the optional ``sentry_kwargs`` parameter,
which is a ``dict`` of kwargs passed to the lower-level Sentry library, ``raven``.
With this, you can specify environment details, filter out specific exceptions, and so on:
    from aiohttp import web
    from aiohttp_sentry import SentryMiddleware
    app = web.Application(
        middlewares=(
            SentryMiddleware({
                'environment': 'foo',
                'release': 'bar',
                'ignore_exceptions': 'aiohttp.HTTPClientError'
            }),
            # ...
        ),
    )
If you are using the standard library's ``logging`` module,
we have a convenient parameter to patch it for you,
to have logger calls send events to Sentry automatically:
    This modifies your logging configuration globally
    when you instantiate the middleware.
    Even if you don't end up using the middleware instance for a request,
    all your logs will be sent to Sentry.
    import logging
    from aiohttp import web
    from aiohttp_sentry import SentryMiddleware
    app = web.Application(
        middlewares=[SentryMiddleware(patch_logging=True, sentry_log_level=logging.WARNING)],
    )

%package -n python3-aiohttp-sentry
Summary:	An aiohttp middleware for reporting errors to Sentry
Provides:	python-aiohttp-sentry
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-aiohttp-sentry
If you want to customize error reporting,
you can use the optional ``sentry_kwargs`` parameter,
which is a ``dict`` of kwargs passed to the lower-level Sentry library, ``raven``.
With this, you can specify environment details, filter out specific exceptions, and so on:
    from aiohttp import web
    from aiohttp_sentry import SentryMiddleware
    app = web.Application(
        middlewares=(
            SentryMiddleware({
                'environment': 'foo',
                'release': 'bar',
                'ignore_exceptions': 'aiohttp.HTTPClientError'
            }),
            # ...
        ),
    )
If you are using the standard library's ``logging`` module,
we have a convenient parameter to patch it for you,
to have logger calls send events to Sentry automatically:
    This modifies your logging configuration globally
    when you instantiate the middleware.
    Even if you don't end up using the middleware instance for a request,
    all your logs will be sent to Sentry.
    import logging
    from aiohttp import web
    from aiohttp_sentry import SentryMiddleware
    app = web.Application(
        middlewares=[SentryMiddleware(patch_logging=True, sentry_log_level=logging.WARNING)],
    )

%package help
Summary:	Development documents and examples for aiohttp-sentry
Provides:	python3-aiohttp-sentry-doc
%description help
If you want to customize error reporting,
you can use the optional ``sentry_kwargs`` parameter,
which is a ``dict`` of kwargs passed to the lower-level Sentry library, ``raven``.
With this, you can specify environment details, filter out specific exceptions, and so on:
    from aiohttp import web
    from aiohttp_sentry import SentryMiddleware
    app = web.Application(
        middlewares=(
            SentryMiddleware({
                'environment': 'foo',
                'release': 'bar',
                'ignore_exceptions': 'aiohttp.HTTPClientError'
            }),
            # ...
        ),
    )
If you are using the standard library's ``logging`` module,
we have a convenient parameter to patch it for you,
to have logger calls send events to Sentry automatically:
    This modifies your logging configuration globally
    when you instantiate the middleware.
    Even if you don't end up using the middleware instance for a request,
    all your logs will be sent to Sentry.
    import logging
    from aiohttp import web
    from aiohttp_sentry import SentryMiddleware
    app = web.Application(
        middlewares=[SentryMiddleware(patch_logging=True, sentry_log_level=logging.WARNING)],
    )

%prep
%autosetup -n aiohttp-sentry-0.6.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-aiohttp-sentry -f filelist.lst
%dir %{python3_sitelib}/*

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

%changelog
* Wed May 31 2023 Python_Bot <Python_Bot@openeuler.org> - 0.6.0-1
- Package Spec generated