%global _empty_manifest_terminate_build 0
Name:		python-django-modelcluster
Version:	6.0
Release:	1
Summary:	Django extension to allow working with 'clusters' of models as a single unit, independently of the database
License:	BSD
URL:		https://github.com/wagtail/django-modelcluster
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/80/f6/f9583d4b78da566fe5f2bd05e5d79c1172e68e8268944082105267d08560/django-modelcluster-6.0.tar.gz
BuildArch:	noarch

Requires:	python3-pytz
Requires:	python3-django
Requires:	python3-django-taggit

%description
If you had a data model like this:
 class Band(models.Model):
     name = models.CharField(max_length=255)
 class BandMember(models.Model):
     band = models.ForeignKey('Band', related_name='members', on_delete=models.CASCADE)
     name = models.CharField(max_length=255)
wouldn't it be nice if you could construct bundles of objects like this, independently of the database:
 beatles = Band(name='The Beatles')
 beatles.members = [
     BandMember(name='John Lennon'),
     BandMember(name='Paul McCartney'),
 ]
Unfortunately, you can't. Objects need to exist in the database for foreign key relations to work:
 IntegrityError: null value in column "band_id" violates not-null constraint
But what if you could? There are all sorts of scenarios where you might want to work with a 'cluster' of related objects, without necessarily holding them in the database: maybe you want to render a preview of the data the user has just submitted, prior to saving. Maybe you need to construct a tree of things, serialize them and hand them off to some external system. Maybe you have a workflow where your models exist in an incomplete 'draft' state for an extended time, or you need to handle multiple revisions, and you don't want to redesign your database around that requirement.
**django-modelcluster** extends Django's foreign key relations to make this possible. It introduces a new type of relation, *ParentalKey*, where the related models are stored locally to the 'parent' model until the parent is explicitly saved. Up to that point, the related models can still be accessed through a subset of the QuerySet API:
 from modelcluster.models import ClusterableModel
 from modelcluster.fields import ParentalKey
 class Band(ClusterableModel):
     name = models.CharField(max_length=255)
 class BandMember(models.Model):
     band = ParentalKey('Band', related_name='members', on_delete=models.CASCADE)
     name = models.CharField(max_length=255)
 >>> beatles = Band(name='The Beatles')
 >>> beatles.members = [
 >>> [member.name for member in beatles.members.all()]
 ['John Lennon', 'Paul McCartney']
 >>> beatles.members.add(BandMember(name='George Harrison'))
 >>> beatles.members.count()
 3
 >>> beatles.save()  # only now are the records written to the database
For more examples, see the unit tests.

%package -n python3-django-modelcluster
Summary:	Django extension to allow working with 'clusters' of models as a single unit, independently of the database
Provides:	python-django-modelcluster
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-django-modelcluster
If you had a data model like this:
 class Band(models.Model):
     name = models.CharField(max_length=255)
 class BandMember(models.Model):
     band = models.ForeignKey('Band', related_name='members', on_delete=models.CASCADE)
     name = models.CharField(max_length=255)
wouldn't it be nice if you could construct bundles of objects like this, independently of the database:
 beatles = Band(name='The Beatles')
 beatles.members = [
     BandMember(name='John Lennon'),
     BandMember(name='Paul McCartney'),
 ]
Unfortunately, you can't. Objects need to exist in the database for foreign key relations to work:
 IntegrityError: null value in column "band_id" violates not-null constraint
But what if you could? There are all sorts of scenarios where you might want to work with a 'cluster' of related objects, without necessarily holding them in the database: maybe you want to render a preview of the data the user has just submitted, prior to saving. Maybe you need to construct a tree of things, serialize them and hand them off to some external system. Maybe you have a workflow where your models exist in an incomplete 'draft' state for an extended time, or you need to handle multiple revisions, and you don't want to redesign your database around that requirement.
**django-modelcluster** extends Django's foreign key relations to make this possible. It introduces a new type of relation, *ParentalKey*, where the related models are stored locally to the 'parent' model until the parent is explicitly saved. Up to that point, the related models can still be accessed through a subset of the QuerySet API:
 from modelcluster.models import ClusterableModel
 from modelcluster.fields import ParentalKey
 class Band(ClusterableModel):
     name = models.CharField(max_length=255)
 class BandMember(models.Model):
     band = ParentalKey('Band', related_name='members', on_delete=models.CASCADE)
     name = models.CharField(max_length=255)
 >>> beatles = Band(name='The Beatles')
 >>> beatles.members = [
 >>> [member.name for member in beatles.members.all()]
 ['John Lennon', 'Paul McCartney']
 >>> beatles.members.add(BandMember(name='George Harrison'))
 >>> beatles.members.count()
 3
 >>> beatles.save()  # only now are the records written to the database
For more examples, see the unit tests.

%package help
Summary:	Development documents and examples for django-modelcluster
Provides:	python3-django-modelcluster-doc
%description help
If you had a data model like this:
 class Band(models.Model):
     name = models.CharField(max_length=255)
 class BandMember(models.Model):
     band = models.ForeignKey('Band', related_name='members', on_delete=models.CASCADE)
     name = models.CharField(max_length=255)
wouldn't it be nice if you could construct bundles of objects like this, independently of the database:
 beatles = Band(name='The Beatles')
 beatles.members = [
     BandMember(name='John Lennon'),
     BandMember(name='Paul McCartney'),
 ]
Unfortunately, you can't. Objects need to exist in the database for foreign key relations to work:
 IntegrityError: null value in column "band_id" violates not-null constraint
But what if you could? There are all sorts of scenarios where you might want to work with a 'cluster' of related objects, without necessarily holding them in the database: maybe you want to render a preview of the data the user has just submitted, prior to saving. Maybe you need to construct a tree of things, serialize them and hand them off to some external system. Maybe you have a workflow where your models exist in an incomplete 'draft' state for an extended time, or you need to handle multiple revisions, and you don't want to redesign your database around that requirement.
**django-modelcluster** extends Django's foreign key relations to make this possible. It introduces a new type of relation, *ParentalKey*, where the related models are stored locally to the 'parent' model until the parent is explicitly saved. Up to that point, the related models can still be accessed through a subset of the QuerySet API:
 from modelcluster.models import ClusterableModel
 from modelcluster.fields import ParentalKey
 class Band(ClusterableModel):
     name = models.CharField(max_length=255)
 class BandMember(models.Model):
     band = ParentalKey('Band', related_name='members', on_delete=models.CASCADE)
     name = models.CharField(max_length=255)
 >>> beatles = Band(name='The Beatles')
 >>> beatles.members = [
 >>> [member.name for member in beatles.members.all()]
 ['John Lennon', 'Paul McCartney']
 >>> beatles.members.add(BandMember(name='George Harrison'))
 >>> beatles.members.count()
 3
 >>> beatles.save()  # only now are the records written to the database
For more examples, see the unit tests.

%prep
%autosetup -n django-modelcluster-6.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-django-modelcluster -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Sun Apr 23 2023 Python_Bot <Python_Bot@openeuler.org> - 6.0-1
- Package Spec generated