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
194
195
|
%global _empty_manifest_terminate_build 0
Name: python-Flask-Melodramatiq
Version: 1.0
Release: 1
Summary: A Flask extension that adds support for the "dramatiq" task processing library
License: MIT
URL: https://github.com/epandurski/flask_melodramatiq
Source0: https://mirrors.aliyun.com/pypi/web/packages/c3/f7/b4e4a2ae66f954cd4c3520488eb35a93d98e8f708dc443999ed6a604501d/Flask-Melodramatiq-1.0.tar.gz
BuildArch: noarch
%description
**Flask-Melodramatiq** is a `Flask`_ extension that adds support for
the `Dramatiq`_ task processing library.
`Dramatiq`_ is a great library, and Flask-Melodramatiq tries hard not
to force you to change the way you interact with
it. Flask-Melodramatiq defines thin wrappers around the broker types
available in Dramatiq, so that all the power of Dramatiq's API remains
available to you.
For example::
import dramatiq
from flask import Flask
from flask_melodramatiq import RabbitmqBroker
app = Flask(__name__)
broker = RabbitmqBroker(app)
dramatiq.set_broker(broker)
@dramatiq.actor
def task():
print('Snakes appreciate good theatrical preformace.')
or, if you prefer the Flask application factory pattern::
import dramatiq
from flask import Flask
from flask_melodramatiq import RabbitmqBroker
broker = RabbitmqBroker()
dramatiq.set_broker(broker)
@dramatiq.actor
def task():
print('Snakes appreciate good theatrical preformace.')
def create_app():
app = Flask(__name__)
broker.init_app(app)
return app
In those examples, the ``broker`` instance that we created (we call it
a "lazy broker") is a genuine `Dramatiq`_ broker, and can be used
anywhere where a "native" broker can be used. (It has
``dramatiq.brokers.rabbitmq.RabbitmqBroker`` as a superclass!) Lazy
brokers are thin wrappers which add several important features:
1. They honor the settings in the Flask application configuration.
2. ``init_app`` can be called on them *before or after* the
actors have been defined.
3. The Flask application context is correctly set during the execution
of the tasks.
4. They add few convenience methods. (The ``Broker.actor`` decorator
for example.)
%package -n python3-Flask-Melodramatiq
Summary: A Flask extension that adds support for the "dramatiq" task processing library
Provides: python-Flask-Melodramatiq
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-Flask-Melodramatiq
**Flask-Melodramatiq** is a `Flask`_ extension that adds support for
the `Dramatiq`_ task processing library.
`Dramatiq`_ is a great library, and Flask-Melodramatiq tries hard not
to force you to change the way you interact with
it. Flask-Melodramatiq defines thin wrappers around the broker types
available in Dramatiq, so that all the power of Dramatiq's API remains
available to you.
For example::
import dramatiq
from flask import Flask
from flask_melodramatiq import RabbitmqBroker
app = Flask(__name__)
broker = RabbitmqBroker(app)
dramatiq.set_broker(broker)
@dramatiq.actor
def task():
print('Snakes appreciate good theatrical preformace.')
or, if you prefer the Flask application factory pattern::
import dramatiq
from flask import Flask
from flask_melodramatiq import RabbitmqBroker
broker = RabbitmqBroker()
dramatiq.set_broker(broker)
@dramatiq.actor
def task():
print('Snakes appreciate good theatrical preformace.')
def create_app():
app = Flask(__name__)
broker.init_app(app)
return app
In those examples, the ``broker`` instance that we created (we call it
a "lazy broker") is a genuine `Dramatiq`_ broker, and can be used
anywhere where a "native" broker can be used. (It has
``dramatiq.brokers.rabbitmq.RabbitmqBroker`` as a superclass!) Lazy
brokers are thin wrappers which add several important features:
1. They honor the settings in the Flask application configuration.
2. ``init_app`` can be called on them *before or after* the
actors have been defined.
3. The Flask application context is correctly set during the execution
of the tasks.
4. They add few convenience methods. (The ``Broker.actor`` decorator
for example.)
%package help
Summary: Development documents and examples for Flask-Melodramatiq
Provides: python3-Flask-Melodramatiq-doc
%description help
**Flask-Melodramatiq** is a `Flask`_ extension that adds support for
the `Dramatiq`_ task processing library.
`Dramatiq`_ is a great library, and Flask-Melodramatiq tries hard not
to force you to change the way you interact with
it. Flask-Melodramatiq defines thin wrappers around the broker types
available in Dramatiq, so that all the power of Dramatiq's API remains
available to you.
For example::
import dramatiq
from flask import Flask
from flask_melodramatiq import RabbitmqBroker
app = Flask(__name__)
broker = RabbitmqBroker(app)
dramatiq.set_broker(broker)
@dramatiq.actor
def task():
print('Snakes appreciate good theatrical preformace.')
or, if you prefer the Flask application factory pattern::
import dramatiq
from flask import Flask
from flask_melodramatiq import RabbitmqBroker
broker = RabbitmqBroker()
dramatiq.set_broker(broker)
@dramatiq.actor
def task():
print('Snakes appreciate good theatrical preformace.')
def create_app():
app = Flask(__name__)
broker.init_app(app)
return app
In those examples, the ``broker`` instance that we created (we call it
a "lazy broker") is a genuine `Dramatiq`_ broker, and can be used
anywhere where a "native" broker can be used. (It has
``dramatiq.brokers.rabbitmq.RabbitmqBroker`` as a superclass!) Lazy
brokers are thin wrappers which add several important features:
1. They honor the settings in the Flask application configuration.
2. ``init_app`` can be called on them *before or after* the
actors have been defined.
3. The Flask application context is correctly set during the execution
of the tasks.
4. They add few convenience methods. (The ``Broker.actor`` decorator
for example.)
%prep
%autosetup -n Flask-Melodramatiq-1.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-Flask-Melodramatiq -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri Jun 09 2023 Python_Bot <Python_Bot@openeuler.org> - 1.0-1
- Package Spec generated
|
