automatic import of python-django-calopeneuler20.03

3 files changed, 474 insertions, 0 deletions

diff --git a/.gitignore b/.gitignore
index e69de29..e75ce97 100644
--- a/.gitignore
+++ b/.gitignore
@@ -0,0 +1 @@
+/django_cal-0.4.2.tar.gz
diff --git a/python-django-cal.spec b/python-django-cal.spec
new file mode 100644
index 0000000..e621821
--- /dev/null
+++ b/python-django-cal.spec
@@ -0,0 +1,472 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-django-cal
+Version:	0.4.2
+Release:	1
+Summary:	Django app to enable exporting of events to iCalendar files.
+License:	Copyright (c) statesofpop and individual contributors. All rights reserved.  Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.  3. Neither the name of Django nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
+URL:		https://github.com/statesofpop/django-cal/
+Source0:	https://mirrors.aliyun.com/pypi/web/packages/a4/45/77f9d6f51d91e35509c18eeb6e10776d19093c189540602060857f47f268/django_cal-0.4.2.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-dateutil
+Requires:	python3-vobject
+Requires:	python3-black
+Requires:	python3-bumpver
+Requires:	python3-flake8
+Requires:	python3-isort
+Requires:	python3-pre-commit
+Requires:	python3-pytest
+Requires:	python3-pytest-django
+Requires:	python3-pyupgrade
+
+%description
+# django-cal #
+
+Django app to enable exporting of events to iCalendar files.
+Imitates behavior of django.contrib.syndication and is based upon
+[vobject](https://eventable.github.io/vobject/). Heavy inspiration came from
+[Christian Joergensen](http://www.technobabble.dk/2008/mar/06/exposing-calendar-events-using-icalendar-django/)
+and [Derek Willis](http://blog.thescoop.org/archives/2007/07/31/django-ical-and-vobject/).
+
+This project is loosely maintained and contributions will be happily accepted, but no feature
+developments are planned. New maintainers are welcome.
+
+`django-cal` requires at least Django 3.2 and Python 3.8.
+
+## Documentation ##
+
+### Overview ###
+
+Please see Django's syndication feed framework documentation, django_cal imitates its
+behavior: <https://docs.djangoproject.com/en/dev/ref/contrib/syndication/>.
+
+## Installation ##
+
+    pip install django-cal
+
+## Setting it up ##
+
+Define a custom Events class, and then wire it up directly in your `urls.py`.
+
+```
+    from testapp.events import Testevents
+
+    urlpatterns = patterns(
+    "",
+    (r"^ical$", Testevents()),
+    )
+```
+
+
+### Defining event properties ###
+
+The following parameters work analogous to how they're implemented in
+django.contrib.syndication. That means, the framework checks in the following
+order: `self.$param(obj)`, `self.$param()`, `self.$param`; `obj` being the object
+returned by `self.get_object`.
+
+    items           Returns the list of events.
+                    Must be set.
+    filename        Filename of the file returned in the view.
+                    Optional, defaults to 'events.ics'.
+    cal_name        Name of the calendar.
+                    Optional, defaults to None.
+    cal_desc        Description of the calendar.
+                    Optional, defaults to None.
+
+    item_summary    The "title" of the item.
+                    Optional, defaults to unicode representation of item.
+
+    item_end        Duration or end time of item.
+    item_duration   Optional, defaults to None. Must not define both.
+
+    item_rruleset   Optional, defaults to None.
+                    Should return dateutil.rruleset instance
+                    for recurrent events.
+
+    item_url        Optional, default calls item.get_absolute_url()
+                    Should return a URL with the fully-qualified domain and
+                    protocol (e.g. 'http://www.example.com/blog/') or an
+                    absolute path (e.g. '/events/'). If only a path is
+                    present, the 'django.contrib.sites' app will be used
+                    to insert the domain of the current site.
+                    Note: To find the current site, 'django.contrib.sites'
+                          must be in your settings.INSTALLED_APPS (it is
+                          there by default)
+
+    item_uid        All correspond to their vEvent equivalents.
+    item_start      All optional, all default to None.
+    item_description
+    item_categories
+    item_comment
+    item_location
+    item_last_modified
+    item_created
+
+### Duration of events ###
+
+django-cal imitates vobject behavior regarding start and end of events. In short:
+Use Date objects for all-day events, DateTime for more granular control.
+Define either duration or end time, never both.
+
+## Timezones ###
+
+If you need timezone support, use `pytz.timezone` to create an "aware" datetime object for
+`item_start` and `item_end` and set it to UTC. A user reported that Gmail, Outlook,
+Apple Mail, etc. are properly displaying it in the user's local timezone upon receipt.
+
+Example::
+```
+from pytz import timezone
+
+# dt is a naive datetime object known to represent US/Eastern time
+loc_dt = timezone('US/Eastern').localize(dt)
+utc = timezone('UTC')
+aware_datetime = loc_dt.astimezone(utc)
+```
+
+### Complex behavior ###
+
+`self.get_object` can be overridden to allow for more complex events, as is possible for
+[syndication feeds](https://docs.djangoproject.com/en/dev/ref/contrib/syndication/#a-complex-example).
+
+# Contributor notes
+
+## Set up dev environment
+
+In a virtual env:
+
+    $ pip install .[tests]
+    $ pre-commit install
+
+## Upload a new version
+
+Uploading a new wheel happens with `hatchling` and `twine`:
+
+First, update version number in `pyproject.toml`.
+
+    $ bumpver update --patch
+    $ python3 -m pip install --upgrade build twine
+    $ rm dist/* && python3 -m build
+    $ python3 -m twine upload dist/*
+    $ git push --tags
+
+
+%package -n python3-django-cal
+Summary:	Django app to enable exporting of events to iCalendar files.
+Provides:	python-django-cal
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-django-cal
+# django-cal #
+
+Django app to enable exporting of events to iCalendar files.
+Imitates behavior of django.contrib.syndication and is based upon
+[vobject](https://eventable.github.io/vobject/). Heavy inspiration came from
+[Christian Joergensen](http://www.technobabble.dk/2008/mar/06/exposing-calendar-events-using-icalendar-django/)
+and [Derek Willis](http://blog.thescoop.org/archives/2007/07/31/django-ical-and-vobject/).
+
+This project is loosely maintained and contributions will be happily accepted, but no feature
+developments are planned. New maintainers are welcome.
+
+`django-cal` requires at least Django 3.2 and Python 3.8.
+
+## Documentation ##
+
+### Overview ###
+
+Please see Django's syndication feed framework documentation, django_cal imitates its
+behavior: <https://docs.djangoproject.com/en/dev/ref/contrib/syndication/>.
+
+## Installation ##
+
+    pip install django-cal
+
+## Setting it up ##
+
+Define a custom Events class, and then wire it up directly in your `urls.py`.
+
+```
+    from testapp.events import Testevents
+
+    urlpatterns = patterns(
+    "",
+    (r"^ical$", Testevents()),
+    )
+```
+
+
+### Defining event properties ###
+
+The following parameters work analogous to how they're implemented in
+django.contrib.syndication. That means, the framework checks in the following
+order: `self.$param(obj)`, `self.$param()`, `self.$param`; `obj` being the object
+returned by `self.get_object`.
+
+    items           Returns the list of events.
+                    Must be set.
+    filename        Filename of the file returned in the view.
+                    Optional, defaults to 'events.ics'.
+    cal_name        Name of the calendar.
+                    Optional, defaults to None.
+    cal_desc        Description of the calendar.
+                    Optional, defaults to None.
+
+    item_summary    The "title" of the item.
+                    Optional, defaults to unicode representation of item.
+
+    item_end        Duration or end time of item.
+    item_duration   Optional, defaults to None. Must not define both.
+
+    item_rruleset   Optional, defaults to None.
+                    Should return dateutil.rruleset instance
+                    for recurrent events.
+
+    item_url        Optional, default calls item.get_absolute_url()
+                    Should return a URL with the fully-qualified domain and
+                    protocol (e.g. 'http://www.example.com/blog/') or an
+                    absolute path (e.g. '/events/'). If only a path is
+                    present, the 'django.contrib.sites' app will be used
+                    to insert the domain of the current site.
+                    Note: To find the current site, 'django.contrib.sites'
+                          must be in your settings.INSTALLED_APPS (it is
+                          there by default)
+
+    item_uid        All correspond to their vEvent equivalents.
+    item_start      All optional, all default to None.
+    item_description
+    item_categories
+    item_comment
+    item_location
+    item_last_modified
+    item_created
+
+### Duration of events ###
+
+django-cal imitates vobject behavior regarding start and end of events. In short:
+Use Date objects for all-day events, DateTime for more granular control.
+Define either duration or end time, never both.
+
+## Timezones ###
+
+If you need timezone support, use `pytz.timezone` to create an "aware" datetime object for
+`item_start` and `item_end` and set it to UTC. A user reported that Gmail, Outlook,
+Apple Mail, etc. are properly displaying it in the user's local timezone upon receipt.
+
+Example::
+```
+from pytz import timezone
+
+# dt is a naive datetime object known to represent US/Eastern time
+loc_dt = timezone('US/Eastern').localize(dt)
+utc = timezone('UTC')
+aware_datetime = loc_dt.astimezone(utc)
+```
+
+### Complex behavior ###
+
+`self.get_object` can be overridden to allow for more complex events, as is possible for
+[syndication feeds](https://docs.djangoproject.com/en/dev/ref/contrib/syndication/#a-complex-example).
+
+# Contributor notes
+
+## Set up dev environment
+
+In a virtual env:
+
+    $ pip install .[tests]
+    $ pre-commit install
+
+## Upload a new version
+
+Uploading a new wheel happens with `hatchling` and `twine`:
+
+First, update version number in `pyproject.toml`.
+
+    $ bumpver update --patch
+    $ python3 -m pip install --upgrade build twine
+    $ rm dist/* && python3 -m build
+    $ python3 -m twine upload dist/*
+    $ git push --tags
+
+
+%package help
+Summary:	Development documents and examples for django-cal
+Provides:	python3-django-cal-doc
+%description help
+# django-cal #
+
+Django app to enable exporting of events to iCalendar files.
+Imitates behavior of django.contrib.syndication and is based upon
+[vobject](https://eventable.github.io/vobject/). Heavy inspiration came from
+[Christian Joergensen](http://www.technobabble.dk/2008/mar/06/exposing-calendar-events-using-icalendar-django/)
+and [Derek Willis](http://blog.thescoop.org/archives/2007/07/31/django-ical-and-vobject/).
+
+This project is loosely maintained and contributions will be happily accepted, but no feature
+developments are planned. New maintainers are welcome.
+
+`django-cal` requires at least Django 3.2 and Python 3.8.
+
+## Documentation ##
+
+### Overview ###
+
+Please see Django's syndication feed framework documentation, django_cal imitates its
+behavior: <https://docs.djangoproject.com/en/dev/ref/contrib/syndication/>.
+
+## Installation ##
+
+    pip install django-cal
+
+## Setting it up ##
+
+Define a custom Events class, and then wire it up directly in your `urls.py`.
+
+```
+    from testapp.events import Testevents
+
+    urlpatterns = patterns(
+    "",
+    (r"^ical$", Testevents()),
+    )
+```
+
+
+### Defining event properties ###
+
+The following parameters work analogous to how they're implemented in
+django.contrib.syndication. That means, the framework checks in the following
+order: `self.$param(obj)`, `self.$param()`, `self.$param`; `obj` being the object
+returned by `self.get_object`.
+
+    items           Returns the list of events.
+                    Must be set.
+    filename        Filename of the file returned in the view.
+                    Optional, defaults to 'events.ics'.
+    cal_name        Name of the calendar.
+                    Optional, defaults to None.
+    cal_desc        Description of the calendar.
+                    Optional, defaults to None.
+
+    item_summary    The "title" of the item.
+                    Optional, defaults to unicode representation of item.
+
+    item_end        Duration or end time of item.
+    item_duration   Optional, defaults to None. Must not define both.
+
+    item_rruleset   Optional, defaults to None.
+                    Should return dateutil.rruleset instance
+                    for recurrent events.
+
+    item_url        Optional, default calls item.get_absolute_url()
+                    Should return a URL with the fully-qualified domain and
+                    protocol (e.g. 'http://www.example.com/blog/') or an
+                    absolute path (e.g. '/events/'). If only a path is
+                    present, the 'django.contrib.sites' app will be used
+                    to insert the domain of the current site.
+                    Note: To find the current site, 'django.contrib.sites'
+                          must be in your settings.INSTALLED_APPS (it is
+                          there by default)
+
+    item_uid        All correspond to their vEvent equivalents.
+    item_start      All optional, all default to None.
+    item_description
+    item_categories
+    item_comment
+    item_location
+    item_last_modified
+    item_created
+
+### Duration of events ###
+
+django-cal imitates vobject behavior regarding start and end of events. In short:
+Use Date objects for all-day events, DateTime for more granular control.
+Define either duration or end time, never both.
+
+## Timezones ###
+
+If you need timezone support, use `pytz.timezone` to create an "aware" datetime object for
+`item_start` and `item_end` and set it to UTC. A user reported that Gmail, Outlook,
+Apple Mail, etc. are properly displaying it in the user's local timezone upon receipt.
+
+Example::
+```
+from pytz import timezone
+
+# dt is a naive datetime object known to represent US/Eastern time
+loc_dt = timezone('US/Eastern').localize(dt)
+utc = timezone('UTC')
+aware_datetime = loc_dt.astimezone(utc)
+```
+
+### Complex behavior ###
+
+`self.get_object` can be overridden to allow for more complex events, as is possible for
+[syndication feeds](https://docs.djangoproject.com/en/dev/ref/contrib/syndication/#a-complex-example).
+
+# Contributor notes
+
+## Set up dev environment
+
+In a virtual env:
+
+    $ pip install .[tests]
+    $ pre-commit install
+
+## Upload a new version
+
+Uploading a new wheel happens with `hatchling` and `twine`:
+
+First, update version number in `pyproject.toml`.
+
+    $ bumpver update --patch
+    $ python3 -m pip install --upgrade build twine
+    $ rm dist/* && python3 -m build
+    $ python3 -m twine upload dist/*
+    $ git push --tags
+
+
+%prep
+%autosetup -n django_cal-0.4.2
+
+%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-cal -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Jun 20 2023 Python_Bot <Python_Bot@openeuler.org> - 0.4.2-1
+- Package Spec generated
diff --git a/sources b/sources
new file mode 100644
index 0000000..55a10b4
--- /dev/null
+++ b/sources
@@ -0,0 +1 @@
+6c8705fbc094504f75591bc2cd99275a  django_cal-0.4.2.tar.gz