automatic import of python-django-reverse-admin

3 files changed, 416 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..44f8296 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/django_reverse_admin-2.9.6.zip
diff --git a/python-django-reverse-admin.spec b/python-django-reverse-admin.spec
new file mode 100644
index 0000000..1d40896
--- /dev/null
+++ b/python-django-reverse-admin.spec
@@ -0,0 +1,414 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-django-reverse-admin
+Version:	2.9.6
+Release:	1
+Summary:	please add a summary manually as the author left a blank one
+License:	BSD
+URL:		https://pypi.org/project/django-reverse-admin/
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/49/bb/93f756f4d7d4cef3fbc4741272e8a5522565c91ff69f5d820abd6318aca9/django_reverse_admin-2.9.6.zip
+BuildArch:	noarch
+
+
+%description
+# Django Reverse Admin
+
+Module that makes django admin handle OneToOneFields in a better way. A common use case for one-to-one relationships is to "embed" a model inside another one. For example, a Person may have multiple foreign keys pointing to an Address entity, one home address, one business address and so on. Django admin displays those relations using select boxes, letting the user choose which address entity to connect to a person. A more natural way to handle the relationship is using inlines. However, since the foreign key is placed on the owning entity, django admins standard inline classes can't be used. Which is why I created this module that implements "reverse inlines" for this use case.
+
+Fix/extension of:
+* [adminreverse](https://github.com/rpkilby/django-reverse-admin)
+* [reverseadmin](http://djangosnippets.org/snippets/2032/)
+
+[![CircleCI](https://circleci.com/gh/daniyalzade/django_reverse_admin.svg?style=svg)](https://circleci.com/gh/daniyalzade/django_reverse_admin)
+
+# Requirements
+
+* **Python**: 3.4, 3.5, 3.6, 3.7
+* **Django**: 2.0+
+
+From version 2.0 onwards Django Reverse Admin is Python 3 only. If you need to support Python 2.7 use the version 1.0 release.
+
+# Installation
+
+Install using pip:
+
+```sh
+pip install django_reverse_admin
+```
+
+# Testing
+
+Use `tox` for testing.
+
+```sh
+tox
+```
+
+## Testing Manually Using Django Admin
+
+Run the following commands to make sure that db.sqlite3 has all the data that you need
+
+```sh
+cd tests
+python manage.py makemigrations
+python manage.py makemigrations polls
+python manage.py migrate
+python manage.py loaddata fixtures/init_data.json
+python manage.py runserver
+```
+
+Admin user username is `reverse` and password is `reverseadmin`
+
+# Usage
+
+`models.py` file
+
+```py
+from django.db import models
+
+class Address(models.Model):
+    street = models.CharField(max_length=255)
+    zipcode = models.CharField(max_length=10)
+    city = models.CharField(max_length=255)
+    state = models.CharField(max_length=2)
+
+class Person(models.Model):
+    name = models.CharField(max_length=255)
+    business_addr = models.ForeignKey(Address,
+                                      related_name='business_addr')
+    home_addr = models.OneToOneField(Address, related_name='home_addr')
+    other_addr = models.OneToOneField(Address, related_name='other_addr')
+```
+
+`admin.py` file
+
+```py
+from django.contrib import admin
+from django.db import models
+from models import Person
+from django_reverse_admin import ReverseModelAdmin
+
+class PersonAdmin(ReverseModelAdmin):
+    inline_type = 'tabular'
+    inline_reverse = ['business_addr',
+                      ('home_addr', {'fields': ['street', 'city', 'state', 'zipcode']}),
+                      ]
+admin.site.register(Person, PersonAdmin)
+```
+
+inline_type can be either "tabular" or "stacked" for tabular and stacked inlines respectively.
+
+The module is designed to work with Django 2+ Since it hooks into the internals of the admin package, it may not work with later Django versions.
+
+# Demo
+
+Below is what an admin change_view with reverse inline looks like
+![reverse inline](/images/admin_with_reverse_inline_1.png)
+
+Below is what the same change_view would look like WITHOUT reverse inline
+![no reverse inline](/images/admin_without_reverse_inline.png)
+
+# Contribtion
+
+* Make sure that the tests are passing before opening up the PR
+* Create a PR for feature enhancements
+* Once a PR is merged, update version with the following commands:
+
+```
+bumpversion patch
+git push origin master --tags
+```
+
+# Packaging
+
+`tox` creates a package in `.tox/dist`. Use twine to upload it to pypi:
+
+```sh
+twine upload .tox/dist/django_reverse_admin-*.zip
+```
+
+%package -n python3-django-reverse-admin
+Summary:	please add a summary manually as the author left a blank one
+Provides:	python-django-reverse-admin
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-django-reverse-admin
+# Django Reverse Admin
+
+Module that makes django admin handle OneToOneFields in a better way. A common use case for one-to-one relationships is to "embed" a model inside another one. For example, a Person may have multiple foreign keys pointing to an Address entity, one home address, one business address and so on. Django admin displays those relations using select boxes, letting the user choose which address entity to connect to a person. A more natural way to handle the relationship is using inlines. However, since the foreign key is placed on the owning entity, django admins standard inline classes can't be used. Which is why I created this module that implements "reverse inlines" for this use case.
+
+Fix/extension of:
+* [adminreverse](https://github.com/rpkilby/django-reverse-admin)
+* [reverseadmin](http://djangosnippets.org/snippets/2032/)
+
+[![CircleCI](https://circleci.com/gh/daniyalzade/django_reverse_admin.svg?style=svg)](https://circleci.com/gh/daniyalzade/django_reverse_admin)
+
+# Requirements
+
+* **Python**: 3.4, 3.5, 3.6, 3.7
+* **Django**: 2.0+
+
+From version 2.0 onwards Django Reverse Admin is Python 3 only. If you need to support Python 2.7 use the version 1.0 release.
+
+# Installation
+
+Install using pip:
+
+```sh
+pip install django_reverse_admin
+```
+
+# Testing
+
+Use `tox` for testing.
+
+```sh
+tox
+```
+
+## Testing Manually Using Django Admin
+
+Run the following commands to make sure that db.sqlite3 has all the data that you need
+
+```sh
+cd tests
+python manage.py makemigrations
+python manage.py makemigrations polls
+python manage.py migrate
+python manage.py loaddata fixtures/init_data.json
+python manage.py runserver
+```
+
+Admin user username is `reverse` and password is `reverseadmin`
+
+# Usage
+
+`models.py` file
+
+```py
+from django.db import models
+
+class Address(models.Model):
+    street = models.CharField(max_length=255)
+    zipcode = models.CharField(max_length=10)
+    city = models.CharField(max_length=255)
+    state = models.CharField(max_length=2)
+
+class Person(models.Model):
+    name = models.CharField(max_length=255)
+    business_addr = models.ForeignKey(Address,
+                                      related_name='business_addr')
+    home_addr = models.OneToOneField(Address, related_name='home_addr')
+    other_addr = models.OneToOneField(Address, related_name='other_addr')
+```
+
+`admin.py` file
+
+```py
+from django.contrib import admin
+from django.db import models
+from models import Person
+from django_reverse_admin import ReverseModelAdmin
+
+class PersonAdmin(ReverseModelAdmin):
+    inline_type = 'tabular'
+    inline_reverse = ['business_addr',
+                      ('home_addr', {'fields': ['street', 'city', 'state', 'zipcode']}),
+                      ]
+admin.site.register(Person, PersonAdmin)
+```
+
+inline_type can be either "tabular" or "stacked" for tabular and stacked inlines respectively.
+
+The module is designed to work with Django 2+ Since it hooks into the internals of the admin package, it may not work with later Django versions.
+
+# Demo
+
+Below is what an admin change_view with reverse inline looks like
+![reverse inline](/images/admin_with_reverse_inline_1.png)
+
+Below is what the same change_view would look like WITHOUT reverse inline
+![no reverse inline](/images/admin_without_reverse_inline.png)
+
+# Contribtion
+
+* Make sure that the tests are passing before opening up the PR
+* Create a PR for feature enhancements
+* Once a PR is merged, update version with the following commands:
+
+```
+bumpversion patch
+git push origin master --tags
+```
+
+# Packaging
+
+`tox` creates a package in `.tox/dist`. Use twine to upload it to pypi:
+
+```sh
+twine upload .tox/dist/django_reverse_admin-*.zip
+```
+
+%package help
+Summary:	Development documents and examples for django-reverse-admin
+Provides:	python3-django-reverse-admin-doc
+%description help
+# Django Reverse Admin
+
+Module that makes django admin handle OneToOneFields in a better way. A common use case for one-to-one relationships is to "embed" a model inside another one. For example, a Person may have multiple foreign keys pointing to an Address entity, one home address, one business address and so on. Django admin displays those relations using select boxes, letting the user choose which address entity to connect to a person. A more natural way to handle the relationship is using inlines. However, since the foreign key is placed on the owning entity, django admins standard inline classes can't be used. Which is why I created this module that implements "reverse inlines" for this use case.
+
+Fix/extension of:
+* [adminreverse](https://github.com/rpkilby/django-reverse-admin)
+* [reverseadmin](http://djangosnippets.org/snippets/2032/)
+
+[![CircleCI](https://circleci.com/gh/daniyalzade/django_reverse_admin.svg?style=svg)](https://circleci.com/gh/daniyalzade/django_reverse_admin)
+
+# Requirements
+
+* **Python**: 3.4, 3.5, 3.6, 3.7
+* **Django**: 2.0+
+
+From version 2.0 onwards Django Reverse Admin is Python 3 only. If you need to support Python 2.7 use the version 1.0 release.
+
+# Installation
+
+Install using pip:
+
+```sh
+pip install django_reverse_admin
+```
+
+# Testing
+
+Use `tox` for testing.
+
+```sh
+tox
+```
+
+## Testing Manually Using Django Admin
+
+Run the following commands to make sure that db.sqlite3 has all the data that you need
+
+```sh
+cd tests
+python manage.py makemigrations
+python manage.py makemigrations polls
+python manage.py migrate
+python manage.py loaddata fixtures/init_data.json
+python manage.py runserver
+```
+
+Admin user username is `reverse` and password is `reverseadmin`
+
+# Usage
+
+`models.py` file
+
+```py
+from django.db import models
+
+class Address(models.Model):
+    street = models.CharField(max_length=255)
+    zipcode = models.CharField(max_length=10)
+    city = models.CharField(max_length=255)
+    state = models.CharField(max_length=2)
+
+class Person(models.Model):
+    name = models.CharField(max_length=255)
+    business_addr = models.ForeignKey(Address,
+                                      related_name='business_addr')
+    home_addr = models.OneToOneField(Address, related_name='home_addr')
+    other_addr = models.OneToOneField(Address, related_name='other_addr')
+```
+
+`admin.py` file
+
+```py
+from django.contrib import admin
+from django.db import models
+from models import Person
+from django_reverse_admin import ReverseModelAdmin
+
+class PersonAdmin(ReverseModelAdmin):
+    inline_type = 'tabular'
+    inline_reverse = ['business_addr',
+                      ('home_addr', {'fields': ['street', 'city', 'state', 'zipcode']}),
+                      ]
+admin.site.register(Person, PersonAdmin)
+```
+
+inline_type can be either "tabular" or "stacked" for tabular and stacked inlines respectively.
+
+The module is designed to work with Django 2+ Since it hooks into the internals of the admin package, it may not work with later Django versions.
+
+# Demo
+
+Below is what an admin change_view with reverse inline looks like
+![reverse inline](/images/admin_with_reverse_inline_1.png)
+
+Below is what the same change_view would look like WITHOUT reverse inline
+![no reverse inline](/images/admin_without_reverse_inline.png)
+
+# Contribtion
+
+* Make sure that the tests are passing before opening up the PR
+* Create a PR for feature enhancements
+* Once a PR is merged, update version with the following commands:
+
+```
+bumpversion patch
+git push origin master --tags
+```
+
+# Packaging
+
+`tox` creates a package in `.tox/dist`. Use twine to upload it to pypi:
+
+```sh
+twine upload .tox/dist/django_reverse_admin-*.zip
+```
+
+%prep
+%autosetup -n django-reverse-admin-2.9.6
+
+%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-django-reverse-admin -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 2.9.6-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..5c90a9c
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+b4c84c9cacd7295e0fe73f1ae3bc0ddf  django_reverse_admin-2.9.6.zip