summaryrefslogtreecommitdiff
path: root/python-asynq.spec
blob: bf202fad69dcb81c351d08d6265c50fe88de1cbf (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
%global _empty_manifest_terminate_build 0
Name:		python-asynq
Version:	1.4.0
Release:	1
Summary:	Quora's asynq library
License:	Apache Software License
URL:		https://github.com/quora/asynq
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/c4/08/e43ae80f2cee1d2639549c3e4a4c194a566903012780259a5a92d02598e7/asynq-1.4.0.tar.gz

Requires:	python3-Cython
Requires:	python3-qcore
Requires:	python3-pygments

%description
Futures are the basic building blocks of ``asynq``'s programming model. The scheduler keeps track
of futures and attempts to schedule them in an efficient way. ``asynq`` uses its own hierarchy of
Future classes, rooted in ``asynq.FutureBase``. Futures have a ``.value()`` method that computes
their value if necessary and then returns it.
The following are the most important Future classes used in ``asynq``:
- ``AsyncTask``, a Future representing the execution of an asynchronous function (see below).
  Normally created by calling ``.asynq()`` on an asynchronous function.
- ``ConstFuture``, a Future whose value is known at creation time. This is useful when you need
  to pass a Future somewhere, but no computation is actually needed.
- ``BatchBase`` and ``BatchItemBase``, the building blocks for doing batching. See below for
  details.

%package -n python3-asynq
Summary:	Quora's asynq library
Provides:	python-asynq
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
BuildRequires:	python3-cffi
BuildRequires:	gcc
BuildRequires:	gdb
%description -n python3-asynq
Futures are the basic building blocks of ``asynq``'s programming model. The scheduler keeps track
of futures and attempts to schedule them in an efficient way. ``asynq`` uses its own hierarchy of
Future classes, rooted in ``asynq.FutureBase``. Futures have a ``.value()`` method that computes
their value if necessary and then returns it.
The following are the most important Future classes used in ``asynq``:
- ``AsyncTask``, a Future representing the execution of an asynchronous function (see below).
  Normally created by calling ``.asynq()`` on an asynchronous function.
- ``ConstFuture``, a Future whose value is known at creation time. This is useful when you need
  to pass a Future somewhere, but no computation is actually needed.
- ``BatchBase`` and ``BatchItemBase``, the building blocks for doing batching. See below for
  details.

%package help
Summary:	Development documents and examples for asynq
Provides:	python3-asynq-doc
%description help
Futures are the basic building blocks of ``asynq``'s programming model. The scheduler keeps track
of futures and attempts to schedule them in an efficient way. ``asynq`` uses its own hierarchy of
Future classes, rooted in ``asynq.FutureBase``. Futures have a ``.value()`` method that computes
their value if necessary and then returns it.
The following are the most important Future classes used in ``asynq``:
- ``AsyncTask``, a Future representing the execution of an asynchronous function (see below).
  Normally created by calling ``.asynq()`` on an asynchronous function.
- ``ConstFuture``, a Future whose value is known at creation time. This is useful when you need
  to pass a Future somewhere, but no computation is actually needed.
- ``BatchBase`` and ``BatchItemBase``, the building blocks for doing batching. See below for
  details.

%prep
%autosetup -n asynq-1.4.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-asynq -f filelist.lst
%dir %{python3_sitearch}/*

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

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