1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
%global _empty_manifest_terminate_build 0
Name: python-django-factory_boy
Version: 1.0.0
Release: 1
Summary: Uses factory_boy to supply test data factory classes for all stock Django models.
License: BSD
URL: http://github.com/rbarrois/django-factory_boy
Source0: https://mirrors.nju.edu.cn/pypi/web/packages/f8/f9/9ecedc33389c173b1b4f81a96302d505a65270940b0d9e4174f7f4a4bad1/django-factory_boy-1.0.0.tar.gz
BuildArch: noarch
%description
When testing a ``django`` app, a common case is to create some data,
then test app behavior around that test data.
This is usually `done with fixtures`_, but `this includes some pain`_.
`factory_boy`_ is useful for concisely creating objects, particularly for test data.
This project will supply factory_boy classes for each model Django ships.
The factories are named after the class it constructs.
For example, a factory for ``django.contrib.auth.models.User`` is available at ``django_factory_boy.auth.UserFactory``.
See ``factory_boy`` for detailed docs, but all fields are given default values which can be overriden by passing keyword arguments to the constructor. For example::
from django_factory_boy import auth as auth_factories
user = auth_factories.UserFactory(first_name="test")
would result in a saved ``User`` instance whose ``first_name`` is set to ``"test"``.
The resulting objects are normal ``django`` model instances, so once they are constructed you can use them in the normal ways.
Not all ``django`` models have been added yet; if you need one, open an issue or a pull request. Currently supported:
- contrib.auth (``UserFactory``, ``GroupFactory``, ``PermissionFactory``)
- contrib.sites (``SiteFactory``)
This project intends to support all Python versions which Django does - 2.6 - 3.4 as of Django 1.6.
It supports all Django versions from 1.6 onwards.
%package -n python3-django-factory_boy
Summary: Uses factory_boy to supply test data factory classes for all stock Django models.
Provides: python-django-factory_boy
BuildRequires: python3-devel
BuildRequires: python3-setuptools
BuildRequires: python3-pip
%description -n python3-django-factory_boy
When testing a ``django`` app, a common case is to create some data,
then test app behavior around that test data.
This is usually `done with fixtures`_, but `this includes some pain`_.
`factory_boy`_ is useful for concisely creating objects, particularly for test data.
This project will supply factory_boy classes for each model Django ships.
The factories are named after the class it constructs.
For example, a factory for ``django.contrib.auth.models.User`` is available at ``django_factory_boy.auth.UserFactory``.
See ``factory_boy`` for detailed docs, but all fields are given default values which can be overriden by passing keyword arguments to the constructor. For example::
from django_factory_boy import auth as auth_factories
user = auth_factories.UserFactory(first_name="test")
would result in a saved ``User`` instance whose ``first_name`` is set to ``"test"``.
The resulting objects are normal ``django`` model instances, so once they are constructed you can use them in the normal ways.
Not all ``django`` models have been added yet; if you need one, open an issue or a pull request. Currently supported:
- contrib.auth (``UserFactory``, ``GroupFactory``, ``PermissionFactory``)
- contrib.sites (``SiteFactory``)
This project intends to support all Python versions which Django does - 2.6 - 3.4 as of Django 1.6.
It supports all Django versions from 1.6 onwards.
%package help
Summary: Development documents and examples for django-factory_boy
Provides: python3-django-factory_boy-doc
%description help
When testing a ``django`` app, a common case is to create some data,
then test app behavior around that test data.
This is usually `done with fixtures`_, but `this includes some pain`_.
`factory_boy`_ is useful for concisely creating objects, particularly for test data.
This project will supply factory_boy classes for each model Django ships.
The factories are named after the class it constructs.
For example, a factory for ``django.contrib.auth.models.User`` is available at ``django_factory_boy.auth.UserFactory``.
See ``factory_boy`` for detailed docs, but all fields are given default values which can be overriden by passing keyword arguments to the constructor. For example::
from django_factory_boy import auth as auth_factories
user = auth_factories.UserFactory(first_name="test")
would result in a saved ``User`` instance whose ``first_name`` is set to ``"test"``.
The resulting objects are normal ``django`` model instances, so once they are constructed you can use them in the normal ways.
Not all ``django`` models have been added yet; if you need one, open an issue or a pull request. Currently supported:
- contrib.auth (``UserFactory``, ``GroupFactory``, ``PermissionFactory``)
- contrib.sites (``SiteFactory``)
This project intends to support all Python versions which Django does - 2.6 - 3.4 as of Django 1.6.
It supports all Django versions from 1.6 onwards.
%prep
%autosetup -n django-factory_boy-1.0.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-factory_boy -f filelist.lst
%dir %{python3_sitelib}/*
%files help -f doclist.lst
%{_docdir}/*
%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 1.0.0-1
- Package Spec generated
|
