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
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
|
%global _empty_manifest_terminate_build 0
Name: python-duet
Version: 0.2.8
Release: 1
Summary: A simple future-based async library for python.
License: Apache 2
URL: http://github.com/google/duet
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/d2/a2/c60e44fc64d59cb1046162d10c88d6fa954e70a985fe3bbd22f1869ffd64/duet-0.2.8.tar.gz
BuildArch: noarch
Requires: python3-typing-extensions
Requires: python3-black
Requires: python3-isort
Requires: python3-mypy
Requires: python3-pylint
Requires: python3-pytest
Requires: python3-twine
%description
# duet
A simple future-based async library for python
Duet takes inspiration from the amazing [trio](https://trio.readthedocs.io/en/stable/)
library and the [structured concurrency](https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/)
approach to async programming that it uses.
However, duet differs from trio in two major ways:
- Instead of a full-blown implementation of asynchronous IO, duet relies on the
`Future` interface for parallelism, and provides a way to run async/await
coroutines around those `Future`s. This is useful if you are using an API that
returns futures, such as RPC libraries like gRPC. The standard `Future`
interface does not implement `__await__` directly, so `Future` instances must
be wrapped in `duet.AwaitableFuture`.
- duet is re-entrant. At the top level, you run async code by calling
`duet.run(foo)`. Inside `foo` suppose you call a function that has not yet
been fully refactored to be asynchronous, but itself calls `duet.run(bar)`.
Most async libraries, including `trio` and `asyncio`, will raise an exception
if you try to "re-enter" the event loop in this way, but duet allows it. We
have found that this can simplify the process of refactoring code to be
asynchronous because you don't have to completely separate the sync and async
parts of your codebase all at once.
## Installation
Install from pypi:
```
pip install duet
```
## Note
duet is not an official Google project.
%package -n python3-duet
Summary: A simple future-based async library for python.
Provides: python-duet
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-duet
# duet
A simple future-based async library for python
Duet takes inspiration from the amazing [trio](https://trio.readthedocs.io/en/stable/)
library and the [structured concurrency](https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/)
approach to async programming that it uses.
However, duet differs from trio in two major ways:
- Instead of a full-blown implementation of asynchronous IO, duet relies on the
`Future` interface for parallelism, and provides a way to run async/await
coroutines around those `Future`s. This is useful if you are using an API that
returns futures, such as RPC libraries like gRPC. The standard `Future`
interface does not implement `__await__` directly, so `Future` instances must
be wrapped in `duet.AwaitableFuture`.
- duet is re-entrant. At the top level, you run async code by calling
`duet.run(foo)`. Inside `foo` suppose you call a function that has not yet
been fully refactored to be asynchronous, but itself calls `duet.run(bar)`.
Most async libraries, including `trio` and `asyncio`, will raise an exception
if you try to "re-enter" the event loop in this way, but duet allows it. We
have found that this can simplify the process of refactoring code to be
asynchronous because you don't have to completely separate the sync and async
parts of your codebase all at once.
## Installation
Install from pypi:
```
pip install duet
```
## Note
duet is not an official Google project.
%package help
Summary: Development documents and examples for duet
Provides: python3-duet-doc
%description help
# duet
A simple future-based async library for python
Duet takes inspiration from the amazing [trio](https://trio.readthedocs.io/en/stable/)
library and the [structured concurrency](https://vorpus.org/blog/notes-on-structured-concurrency-or-go-statement-considered-harmful/)
approach to async programming that it uses.
However, duet differs from trio in two major ways:
- Instead of a full-blown implementation of asynchronous IO, duet relies on the
`Future` interface for parallelism, and provides a way to run async/await
coroutines around those `Future`s. This is useful if you are using an API that
returns futures, such as RPC libraries like gRPC. The standard `Future`
interface does not implement `__await__` directly, so `Future` instances must
be wrapped in `duet.AwaitableFuture`.
- duet is re-entrant. At the top level, you run async code by calling
`duet.run(foo)`. Inside `foo` suppose you call a function that has not yet
been fully refactored to be asynchronous, but itself calls `duet.run(bar)`.
Most async libraries, including `trio` and `asyncio`, will raise an exception
if you try to "re-enter" the event loop in this way, but duet allows it. We
have found that this can simplify the process of refactoring code to be
asynchronous because you don't have to completely separate the sync and async
parts of your codebase all at once.
## Installation
Install from pypi:
```
pip install duet
```
## Note
duet is not an official Google project.
%prep
%autosetup -n duet-0.2.8
%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-duet -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Sun Apr 23 2023 Python_Bot <Python_Bot@openeuler.org> - 0.2.8-1
- Package Spec generated
|
