python-django-cors-headers-3.2.1-bp155.2.12

- Build on Leap by not using the macros

- Update to 3.2.1:
  * Converted setuptools metadata to configuration file.
  * Support Python 3.8.

- Update to 3.1.1:
  * Support the value file:// for origins, which is accidentally
    sent by some versions of Chrome on Android.

- Update to 3.1.0:
  * Drop Python 2 support, only Python 3.5-3.7 is supported now.
  * Fix all links for move from github.com/ottoyiu/django-cors-headers to
    github.com/adamchainz/django-cors-headers.
  * Add a hint to the corsheaders.E013 check to make it more obvious how to resolve it.
  * Allow 'null' in CORS_ORIGIN_WHITELIST check.
  * CORS_ORIGIN_WHITELIST now requires URI schemes, and optionally ports
  * Removed the CORS_MODEL setting, and associated class

- Update to 2.5.3:
  * Tested on Django 2.2. No changes were needed for compatibility.
  * Tested on Python 3.7. No changes were needed for compatibility.

- Update to 2.5.2:
  * Improve inclusion of tests in sdist to ignore .pyc files.

- Add %{?sle15_python_module_pythons}

- Update to v3.13.0
  * Support Python 3.11.
  * Support Django 4.1.
- from v3.12.0 (2022-05-10)
  * Drop support for Django 2.2, 3.0, and 3.1.
- from v3.11.0 (2022-01-10)
  * Drop Python 3.6 support.
- from v3.10.1 (2021-12-05)
  * Prevent a crash when an invalid Origin header is sent.
- from v3.10.0 (2021-10-05)
  * Support Python 3.10.
- from v3.9.0 (2021-09-28)
  * Support Django 4.0.
- from v3.8.0 (2021-08-15)
  * Add type hints.
  * Stop distributing tests to reduce package size

- Skip Tumbleweed Python 3.6 incompatible with Django 4

- Update to 3.7.0
  * Support Django 3.2.
  * Drop Python 3.5 support.
  * Support Python 3.9.
  * Following Django’s example in Ticket #31670 for replacing the
    term “whitelist”, plus an aim to make the setting names more
    comprehensible, the following settings have been renamed:
  * CORS_ORIGIN_WHITELIST -> CORS_ALLOWED_ORIGINS
  * CORS_ORIGIN_REGEX_WHITELIST -> CORS_ALLOWED_ORIGIN_REGEXES
  * CORS_ORIGIN_ALLOW_ALL -> CORS_ALLOW_ALL_ORIGINS
    The old names will continue to work as aliases, with the new
    ones taking precedence.

- Update to 3.4.0
  * Add Django 3.1 support.

- Update to 3.3.0
  * Drop Django 1.11 support. Only Django 2.0+ is supported now.
  * Drop the providing_args argument from Signal to prevent
    a deprecation warning on Django 3.1.

- Build on Leap by not using the macros

- Update to 3.2.1:
  * Converted setuptools metadata to configuration file.
  * Support Python 3.8.

- Update to 3.1.1:
  * Support the value file:// for origins, which is accidentally
    sent by some versions of Chrome on Android.

- Fix build error for Leap.

- Update to 3.1.0:
  * Drop Python 2 support, only Python 3.5-3.7 is supported now.
  * Fix all links for move from github.com/ottoyiu/django-cors-headers to
    github.com/adamchainz/django-cors-headers.
  * Add a hint to the corsheaders.E013 check to make it more obvious how to resolve it.
  * Allow 'null' in CORS_ORIGIN_WHITELIST check.
  * CORS_ORIGIN_WHITELIST now requires URI schemes, and optionally ports
  * Removed the CORS_MODEL setting, and associated class

- Update to 2.5.3:
  * Tested on Django 2.2. No changes were needed for compatibility.
  * Tested on Python 3.7. No changes were needed for compatibility.

- Update to 2.5.2:
  * Improve inclusion of tests in sdist to ignore .pyc files.

- Use PyPI sdist
- Update to v2.5.1
  * Include test infrastructure in sdist

- Remove %bcond and add %check, with 100% coverage
- Update to v2.5.0
  * Drop Django 1.8, 1.9, and 1.10 support. Django 1.11+ is supported.
- from v2.4.1
  * Fix DeprecationWarning from importing collections.abc.Sequence
    on Python 3.7.

- Add Django dependency
- Use %license
- Update to v2.4.0
  * Always add 'Origin' to the 'Vary' header for responses to enabled
    URL's, to prevent caching of responses intended for one origin
    being served for another.
- from v2.3.0
  * Match ``CORS_URLS_REGEX`` to ``request.path_info`` instead of
    ``request.path``, so the patterns can work without knowing the
    site's path prefix at configuration time.
- from v2.2.1
  * Add ``Content-Length`` header to CORS preflight requests.
    This fixes issues with some HTTP proxies and servers,
    e.g. AWS Elastic Beanstalk.
- from v2.2.0
  * Django 2.0 compatibility. Again there were no changes to the
    actual library code, so previous versions probably work.
  * Ensured that ``request._cors_enabled`` is always a ``bool()`` -
    previously it could be set to a regex match object.

- Initial package, version 2.1.0