How to Install and Uninstall python312-celery-batches Package on openSuSE Tumbleweed
Last updated: November 23,2024
1. Install "python312-celery-batches" package
This guide covers the steps necessary to install python312-celery-batches on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python312-celery-batches
Copied
2. Uninstall "python312-celery-batches" package
Please follow the step by step instructions below to uninstall python312-celery-batches on openSuSE Tumbleweed:
$
sudo zypper remove
python312-celery-batches
Copied
3. Information about the python312-celery-batches package on openSuSE Tumbleweed
Information for package python312-celery-batches:
-------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-celery-batches
Version : 0.8.1-1.3
Arch : noarch
Vendor : openSUSE
Installed Size : 64.5 KiB
Installed : No
Status : not installed
Source package : python-celery-batches-0.8.1-1.3.src
Upstream URL : https://github.com/percipient/celery-batches
Summary : Django module to process multiple Celery task requests together
Description :
An alternate way to have Django DRY forms. The developer can build
programmatic reusable layouts out of components, having control of
the rendered HTML without writing HTML in templates, without breaking
the standard way of doing things in Django, so that it still works
with any other form application.
-------------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python312-celery-batches
Version : 0.8.1-1.3
Arch : noarch
Vendor : openSUSE
Installed Size : 64.5 KiB
Installed : No
Status : not installed
Source package : python-celery-batches-0.8.1-1.3.src
Upstream URL : https://github.com/percipient/celery-batches
Summary : Django module to process multiple Celery task requests together
Description :
An alternate way to have Django DRY forms. The developer can build
programmatic reusable layouts out of components, having control of
the rendered HTML without writing HTML in templates, without breaking
the standard way of doing things in Django, so that it still works
with any other form application.