diff options
Diffstat (limited to 'python-django-deprecate-fields.spec')
| -rw-r--r-- | python-django-deprecate-fields.spec | 229 |
1 files changed, 229 insertions, 0 deletions
diff --git a/python-django-deprecate-fields.spec b/python-django-deprecate-fields.spec new file mode 100644 index 0000000..ab7bd01 --- /dev/null +++ b/python-django-deprecate-fields.spec @@ -0,0 +1,229 @@ +%global _empty_manifest_terminate_build 0 +Name: python-django-deprecate-fields +Version: 0.1.1 +Release: 1 +Summary: This package allows deprecating model fields and allows removing them in a backwards compatible manner. +License: Apache License 2.0 +URL: https://github.com/3YOURMIND/django-deprecate-fields +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/b7/a9/984c8ae3bd7880839c153023fba2cae49824c13e617c7f60a7907e06350d/django-deprecate-fields-0.1.1.tar.gz +BuildArch: noarch + +Requires: python3-Django + +%description +# Django - Deprecate Field + +[](https://pypi.python.org/pypi/django-deprecate-fields/) +[](./LICENSE) +[](https://github.com/3YOURMIND/django-deprecate-fields/pulls) +[](https://www.3yourmind.com/career) +[](https://github.com/3YOURMIND/django-deprecate-fields/stargazers) + +## Installation + +``` +pip install django-deprecate-fields +``` + +## Usage + +Assume the simple following model: +```python +from django.db import models + +class MyModel(models.Model): + field1 = models.CharField() + field2 = models.CharField() +``` + +In order to remove `field1`, it should first be marked as deprecated: +```python +from django.db import models +from django_deprecate_fields import deprecate_field + +class MyModel(models.Model): + field1 = deprecate_field(models.CharField()) + field2 = models.CharField() +``` + +Secondly, `makemigrations` should be called, which will change the field to be nullable. Any lingering references to it +in your code will return `None` (or optionally any value or callable passed to `deprecate_field` as the +`return_instead` argument) + +Lastly, after the changes above have been deployed, `field1` can then safely be removed in the model (plus another +`makemigrations` run) + +## Contributing + +First of all, thank you very much for contributing to this project. Please base +your work on the `master` branch and target `master` in your pull request. + +## License + +`django-deprecate-fields` is released under the [Apache 2.0 License](./LICENSE). + + + + +%package -n python3-django-deprecate-fields +Summary: This package allows deprecating model fields and allows removing them in a backwards compatible manner. +Provides: python-django-deprecate-fields +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-django-deprecate-fields +# Django - Deprecate Field + +[](https://pypi.python.org/pypi/django-deprecate-fields/) +[](./LICENSE) +[](https://github.com/3YOURMIND/django-deprecate-fields/pulls) +[](https://www.3yourmind.com/career) +[](https://github.com/3YOURMIND/django-deprecate-fields/stargazers) + +## Installation + +``` +pip install django-deprecate-fields +``` + +## Usage + +Assume the simple following model: +```python +from django.db import models + +class MyModel(models.Model): + field1 = models.CharField() + field2 = models.CharField() +``` + +In order to remove `field1`, it should first be marked as deprecated: +```python +from django.db import models +from django_deprecate_fields import deprecate_field + +class MyModel(models.Model): + field1 = deprecate_field(models.CharField()) + field2 = models.CharField() +``` + +Secondly, `makemigrations` should be called, which will change the field to be nullable. Any lingering references to it +in your code will return `None` (or optionally any value or callable passed to `deprecate_field` as the +`return_instead` argument) + +Lastly, after the changes above have been deployed, `field1` can then safely be removed in the model (plus another +`makemigrations` run) + +## Contributing + +First of all, thank you very much for contributing to this project. Please base +your work on the `master` branch and target `master` in your pull request. + +## License + +`django-deprecate-fields` is released under the [Apache 2.0 License](./LICENSE). + + + + +%package help +Summary: Development documents and examples for django-deprecate-fields +Provides: python3-django-deprecate-fields-doc +%description help +# Django - Deprecate Field + +[](https://pypi.python.org/pypi/django-deprecate-fields/) +[](./LICENSE) +[](https://github.com/3YOURMIND/django-deprecate-fields/pulls) +[](https://www.3yourmind.com/career) +[](https://github.com/3YOURMIND/django-deprecate-fields/stargazers) + +## Installation + +``` +pip install django-deprecate-fields +``` + +## Usage + +Assume the simple following model: +```python +from django.db import models + +class MyModel(models.Model): + field1 = models.CharField() + field2 = models.CharField() +``` + +In order to remove `field1`, it should first be marked as deprecated: +```python +from django.db import models +from django_deprecate_fields import deprecate_field + +class MyModel(models.Model): + field1 = deprecate_field(models.CharField()) + field2 = models.CharField() +``` + +Secondly, `makemigrations` should be called, which will change the field to be nullable. Any lingering references to it +in your code will return `None` (or optionally any value or callable passed to `deprecate_field` as the +`return_instead` argument) + +Lastly, after the changes above have been deployed, `field1` can then safely be removed in the model (plus another +`makemigrations` run) + +## Contributing + +First of all, thank you very much for contributing to this project. Please base +your work on the `master` branch and target `master` in your pull request. + +## License + +`django-deprecate-fields` is released under the [Apache 2.0 License](./LICENSE). + + + + +%prep +%autosetup -n django-deprecate-fields-0.1.1 + +%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-deprecate-fields -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Mon Apr 10 2023 Python_Bot <Python_Bot@openeuler.org> - 0.1.1-1 +- Package Spec generated |