mcalabkova/python-celery-batches
SHA256
1
0
Fork 0
forked from pool/python-celery-batches
Code Pull Requests Activity

Accepting request 665275 from home:jengelh:branches:devel:languages:python

Browse Source 
- Trim bias and use noun phrasing.

OBS-URL: https://build.opensuse.org/request/show/665275
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-celery-batches?expand=0&rev=3
This commit is contained in:
Tomáš Chvátal 2019-01-13 18:16:26 +00:00 committed by Git OBS Bridge
parent 94813bea08
commit 0cb10b359e
2 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
python-celery-batches.changes
View File

@ -1,3 +1,8 @@
-------------------------------------------------------------------
Sun Jan 13 10:49:19 UTC 2019 - Jan Engelhardt <jengelh@inai.de>
- Trim bias and use noun phrasing.
------------------------------------------------------------------- -------------------------------------------------------------------
Wed Jan 2 14:14:35 UTC 2019 - Tomáš Chvátal <tchvatal@suse.com> Wed Jan 2 14:14:35 UTC 2019 - Tomáš Chvátal <tchvatal@suse.com>

11
python-celery-batches.spec
View File

@ -22,7 +22,7 @@
Name: python-%{_pkgname} Name: python-%{_pkgname}
Version: 0.2 Version: 0.2
Release: 0 Release: 0
Summary: Process Multiple Celery Task Requests Together Summary: Django module to process multiple Celery task requests together
License: BSD-3-Clause License: BSD-3-Clause
Group: Development/Languages/Python Group: Development/Languages/Python
URL: https://github.com/percipient/celery-batches URL: https://github.com/percipient/celery-batches
@ -39,10 +39,11 @@ BuildArch: noarch
%python_subpackages %python_subpackages
%description %description
The best way to have Django DRY forms. Build programmatic reusable layouts out An alternate way to have Django DRY forms. The developer can build
of components, having full control of the rendered HTML without writing HTML in programmatic reusable layouts out of components, having control of
templates. All this without breaking the standard way of doing things in the rendered HTML without writing HTML in templates, without breaking
Django, so it plays nice with any other form application. the standard way of doing things in Django, so that it still works
with any other form application.
%prep %prep
%setup -q -n %{_pkgname}-%{version} %setup -q -n %{_pkgname}-%{version}