How to Install and Uninstall python3-django-appconf.noarch Package on Fedora 38
Last updated: November 29,2024
1. Install "python3-django-appconf.noarch" package
In this section, we are going to explain the necessary steps to install python3-django-appconf.noarch on Fedora 38
$
sudo dnf update
Copied
$
sudo dnf install
python3-django-appconf.noarch
Copied
2. Uninstall "python3-django-appconf.noarch" package
Please follow the step by step instructions below to uninstall python3-django-appconf.noarch on Fedora 38:
$
sudo dnf remove
python3-django-appconf.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the python3-django-appconf.noarch package on Fedora 38
Last metadata expiration check: 5:40:49 ago on Sat Mar 16 16:59:57 2024.
Available Packages
Name : python3-django-appconf
Version : 1.0.6
Release : 1.fc38
Architecture : noarch
Size : 179 k
Source : python-django-appconf-1.0.6-1.fc38.src.rpm
Repository : updates
Summary : An app to handle configuration defaults of packaged Django apps gracefully
URL : http://pypi.python.org/pypi/django-appconf/
License : BSD-3-Clause
Description : A helper class for handling configuration defaults of packaged Django apps
: gracefully.
:
: Note:
: This app precedes Django's own AppConfig classes that act as "objects [to] store
: metadata for an application" inside Django's app loading mechanism. In other
: words, they solve a related but different use case than django-appconf and can't
: easily be used as a replacement. The similarity in name is purely coincidental.
Available Packages
Name : python3-django-appconf
Version : 1.0.6
Release : 1.fc38
Architecture : noarch
Size : 179 k
Source : python-django-appconf-1.0.6-1.fc38.src.rpm
Repository : updates
Summary : An app to handle configuration defaults of packaged Django apps gracefully
URL : http://pypi.python.org/pypi/django-appconf/
License : BSD-3-Clause
Description : A helper class for handling configuration defaults of packaged Django apps
: gracefully.
:
: Note:
: This app precedes Django's own AppConfig classes that act as "objects [to] store
: metadata for an application" inside Django's app loading mechanism. In other
: words, they solve a related but different use case than django-appconf and can't
: easily be used as a replacement. The similarity in name is purely coincidental.