Hello community, here is the log from the commit of package python-django-cors-headers for openSUSE:Factory checked in at 2020-08-06 10:38:51 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-django-cors-headers (Old) and /work/SRC/openSUSE:Factory/.python-django-cors-headers.new.3399 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-django-cors-headers" Thu Aug 6 10:38:51 2020 rev:8 rq:818313 version:3.4.0 Changes: -------- --- /work/SRC/openSUSE:Factory/python-django-cors-headers/python-django-cors-headers.changes 2020-06-10 00:50:59.463349153 +0200 +++ /work/SRC/openSUSE:Factory/.python-django-cors-headers.new.3399/python-django-cors-headers.changes 2020-08-06 10:38:59.510026027 +0200 @@ -1,0 +2,6 @@ +Wed Jul 1 11:31:03 UTC 2020 - Marketa Calabkova <mcalabk...@suse.com> + +- Update to 3.4.0 + * Add Django 3.1 support. + +------------------------------------------------------------------- Old: ---- django-cors-headers-3.3.0.tar.gz New: ---- django-cors-headers-3.4.0.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-django-cors-headers.spec ++++++ --- /var/tmp/diff_new_pack.yoPzwR/_old 2020-08-06 10:39:01.042026795 +0200 +++ /var/tmp/diff_new_pack.yoPzwR/_new 2020-08-06 10:39:01.046026797 +0200 @@ -19,7 +19,7 @@ %{?!python_module:%define python_module() python-%{**} python3-%{**}} %define skip_python2 1 Name: python-django-cors-headers -Version: 3.3.0 +Version: 3.4.0 Release: 0 Summary: A Django App that adds CORS headers to responses License: MIT @@ -49,6 +49,7 @@ %python_expand %fdupes %{buildroot}%{$python_sitelib} %check +export PYTHONPATH=$PWD export DJANGO_SETTINGS_MODULE=tests.settings %pytest ++++++ django-cors-headers-3.3.0.tar.gz -> django-cors-headers-3.4.0.tar.gz ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/django-cors-headers-3.3.0/HISTORY.rst new/django-cors-headers-3.4.0/HISTORY.rst --- old/django-cors-headers-3.3.0/HISTORY.rst 2020-05-18 16:21:19.000000000 +0200 +++ new/django-cors-headers-3.4.0/HISTORY.rst 2020-06-15 13:04:34.000000000 +0200 @@ -1,6 +1,11 @@ History ======= +3.3.0 (2020-06-15) +------------------ + +* Add Django 3.1 support. + 3.3.0 (2020-05-18) ------------------ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/django-cors-headers-3.3.0/PKG-INFO new/django-cors-headers-3.4.0/PKG-INFO --- old/django-cors-headers-3.3.0/PKG-INFO 2020-05-18 16:21:38.927424200 +0200 +++ new/django-cors-headers-3.4.0/PKG-INFO 2020-06-15 13:04:55.347104300 +0200 @@ -1,6 +1,6 @@ Metadata-Version: 2.1 Name: django-cors-headers -Version: 3.3.0 +Version: 3.4.0 Summary: django-cors-headers is a Django application for handling the server headers required for Cross-Origin Resource Sharing (CORS). Home-page: https://github.com/adamchainz/django-cors-headers Author: Otto Yiu @@ -9,6 +9,7 @@ Maintainer-email: m...@adamj.eu License: MIT License Project-URL: Changelog, https://github.com/adamchainz/django-cors-headers/blob/master/HISTORY.rst +Project-URL: Twitter, https://twitter.com/adamchainz Description: django-cors-headers =================== @@ -392,295 +393,6 @@ check_request_enabled.connect(cors_allow_api_to_everyone) - History - ======= - - 3.3.0 (2020-05-18) - ------------------ - - * 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. - - 3.2.1 (2020-01-04) - ------------------ - - * Update LICENSE file to Unix line endings, fixing issues with license checker - ``pip-licenses`` (`Issue - #477 <https://github.com/adamchainz/django-cors-headers/issues/477>`__). - - 3.2.0 (2019-11-15) - ------------------ - - * Converted setuptools metadata to configuration file. This meant removing the - ``__version__`` attribute from the package. If you want to inspect the - installed version, use - ``importlib.metadata.version("django-cors-headers")`` - (`docs <https://docs.python.org/3.8/library/importlib.metadata.html#distribution-versions>`__ / - `backport <https://pypi.org/project/importlib-metadata/>`__). - * Support Python 3.8. - - 3.1.1 (2019-09-30) - ------------------ - - * Support the value `file://` for origins, which is accidentally sent by some - versions of Chrome on Android. - - 3.1.0 (2019-08-13) - ------------------ - - * 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``. - - 3.0.2 (2019-05-28) - ------------------ - - * Add a hint to the ``corsheaders.E013`` check to make it more obvious how to - resolve it. - - 3.0.1 (2019-05-13) - ------------------ - - * Allow 'null' in ``CORS_ORIGIN_WHITELIST`` check. - - 3.0.0 (2019-05-10) - ------------------ - - * ``CORS_ORIGIN_WHITELIST`` now requires URI schemes, and optionally ports. - This is part of the CORS specification - (`Section 3.2 <https://tools.ietf.org/html/rfc6454#section-3.2>`_) that was - not implemented in this library, except from with the - ``CORS_ORIGIN_REGEX_WHITELIST`` setting. It fixes a security issue where the - CORS middleware would allow requests between schemes, for example from - insecure ``http://`` Origins to a secure ``https://`` site. - - You will need to update your whitelist to include schemes, for example from - this: - - .. code-block:: python - - CORS_ORIGIN_WHITELIST = ['example.com'] - - ...to this: - - .. code-block:: python - - CORS_ORIGIN_WHITELIST = ['https://example.com'] - - * Removed the ``CORS_MODEL`` setting, and associated class. It seems very few, - or no users were using it, since there were no bug reports since its move to - abstract in version 2.0.0 (2017-01-07). If you *are* using this - functionality, you can continue by changing your model to not inherit from - the abstract one, and add a signal handler for ``check_request_enabled`` that - reads from your model. Note you'll need to handle the move to include schemes - for Origins. - - 2.5.3 (2019-04-28) - ------------------ - - * Tested on Django 2.2. No changes were needed for compatibility. - * Tested on Python 3.7. No changes were needed for compatibility. - - 2.5.2 (2019-03-15) - ------------------ - - * Improve inclusion of tests in ``sdist`` to ignore ``.pyc`` files. - - 2.5.1 (2019-03-13) - ------------------ - - * Include test infrastructure in ``sdist`` to allow consumers to use it. - - 2.5.0 (2019-03-05) - ------------------ - - * Drop Django 1.8, 1.9, and 1.10 support. Only Django 1.11+ is supported now. - - 2.4.1 (2019-02-28) - ------------------ - - * Fix ``DeprecationWarning`` from importing ``collections.abc.Sequence`` on - Python 3.7. - - 2.4.0 (2018-07-18) - ------------------ - - * 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. - - 2.3.0 (2018-06-27) - ------------------ - - * 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. - - 2.2.1 (2018-06-27) - ------------------ - - * Add ``Content-Length`` header to CORS preflight requests. This fixes issues - with some HTTP proxies and servers, e.g. AWS Elastic Beanstalk. - - 2.2.0 (2018-02-28) - ------------------ - - * 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. - - 2.1.0 (2017-05-28) - ------------------ - - * Django 1.11 compatibility. There were no changes to the actual library code, - so previous versions probably work, though they weren't properly tested on - 1.11. - - 2.0.2 (2017-02-06) - ------------------ - - * Fix when the check for ``CORS_MODEL`` is done to allow it to properly add - the headers and respond to ``OPTIONS`` requests. - - 2.0.1 (2017-01-29) - ------------------ - - * Add support for specifying 'null' in ``CORS_ORIGIN_WHITELIST``. - - 2.0.0 (2017-01-07) - ------------------ - - * Remove previously undocumented ``CorsModel`` as it was causing migration - issues. For backwards compatibility, any users previously using ``CorsModel`` - should create a model in their own app that inherits from the new - ``AbstractCorsModel``, and to keep using the same data, set the model's - ``db_table`` to 'corsheaders_corsmodel'. Users not using ``CorsModel`` - will find they have an unused table that they can drop. - * Make sure that ``Access-Control-Allow-Credentials`` is in the response if the - client asks for it. - - 1.3.1 (2016-11-09) - ------------------ - - * Fix a bug with the single check if CORS enabled added in 1.3.0: on Django - < 1.10 shortcut responses could be generated by middleware above - ``CorsMiddleware``, before it processed the request, failing with an - ``AttributeError`` for ``request._cors_enabled``. Also clarified the docs - that ``CorsMiddleware`` should be kept as high as possible in your middleware - stack, above any middleware that can generate such responses. - - 1.3.0 (2016-11-06) - ------------------ - - * Add checks to validate the types of the settings. - * Add the 'Do Not Track' header ``'DNT'`` to the default for - ``CORS_ALLOW_HEADERS``. - * Add 'Origin' to the 'Vary' header of outgoing requests when not allowing all - origins, as per the CORS spec. Note this changes the way HTTP caching works - with your CORS-enabled responses. - * Check whether CORS should be enabled on a request only once. This has had a - minor change on the conditions where any custom signals will be called - - signals will now always be called *before* ``HTTP_REFERER`` gets replaced, - whereas before they could be called before and after. Also this attaches the - attribute ``_cors_enabled`` to ``request`` - please take care that other - code you're running does not remove it. - - 1.2.2 (2016-10-05) - ------------------ - - * Add ``CorsModel.__str__`` for human-readable text - * Add a signal that allows you to add code for more intricate control over when - CORS headers are added. - - 1.2.1 (2016-09-30) - ------------------ - - * Made settings dynamically respond to changes, and which allows you to import - the defaults for headers and methods in order to extend them. - - 1.2.0 (2016-09-28) - ------------------ - - * Drop Python 2.6 support. - * Drop Django 1.3-1.7 support, as they are no longer supported. - * Confirmed Django 1.9 support (no changes outside of tests were necessary). - * Added Django 1.10 support. - * Package as a universal wheel. - - 1.1.0 (2014-12-15) - ------------------ - - * django-cors-header now supports Django 1.8 with its new application loading - system! Thanks @jpadilla for making this possible and sorry for the delay in - making a release. - - 1.0.0 (2014-12-13) - ------------------ - - django-cors-headers is all grown-up :) Since it's been used in production for - many many deployments, I think it's time we mark this as a stable release. - - * Switching this middleware versioning over to semantic versioning - * #46 add user-agent and accept-encoding default headers - * #45 pep-8 this big boy up - - 0.13 (2014-08-14) - ----------------- - - * Add support for Python 3 - * Updated tests - * Improved documentation - * Small bugfixes - - 0.12 (2013-09-24) - ----------------- - - * Added an option to selectively enable CORS only for specific URLs - - 0.11 (2013-09-24) - - * Added the ability to specify a regex for whitelisting many origin hostnames - at once - - 0.10 (2013-09-05) - ----------------- - - * Introduced port distinction for origin checking - * Use ``urlparse`` for Python 3 support - * Added testcases to project - - 0.06 (2013-02-18) - ----------------- - - * Add support for exposed response headers - - 0.05 (2013-01-26) - ----------------- - - * Fixed middleware to ensure correct response for CORS preflight requests - - 0.04 (2013-01-25) - ----------------- - - * Add ``Access-Control-Allow-Credentials`` control to simple requests - - 0.03 (2013-01-22) - ----------------- - - * Bugfix to repair mismatched default variable names - - 0.02 (2013-01-19) - ----------------- - - * Refactor/pull defaults into separate file - - 0.01 (2013-01-19) - ----------------- - - * Initial release - Keywords: django,cors,middleware,rest,api Platform: UNKNOWN Classifier: Development Status :: 5 - Production/Stable @@ -690,6 +402,7 @@ Classifier: Framework :: Django :: 2.1 Classifier: Framework :: Django :: 2.2 Classifier: Framework :: Django :: 3.0 +Classifier: Framework :: Django :: 3.1 Classifier: Intended Audience :: Developers Classifier: License :: OSI Approved :: MIT License Classifier: Operating System :: OS Independent @@ -699,6 +412,7 @@ Classifier: Programming Language :: Python :: 3.6 Classifier: Programming Language :: Python :: 3.7 Classifier: Programming Language :: Python :: 3.8 +Classifier: Programming Language :: Python :: 3.9 Classifier: Topic :: Software Development :: Libraries :: Application Frameworks Classifier: Topic :: Software Development :: Libraries :: Python Modules Requires-Python: >=3.5 diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/django-cors-headers-3.3.0/setup.cfg new/django-cors-headers-3.4.0/setup.cfg --- old/django-cors-headers-3.3.0/setup.cfg 2020-05-18 16:21:38.928370700 +0200 +++ new/django-cors-headers-3.4.0/setup.cfg 2020-06-15 13:04:55.347989000 +0200 @@ -1,8 +1,8 @@ [metadata] name = django-cors-headers -version = 3.3.0 +version = 3.4.0 description = django-cors-headers is a Django application for handling the server headers required for Cross-Origin Resource Sharing (CORS). -long_description = file: README.rst, HISTORY.rst +long_description = file: README.rst long_description_content_type = text/x-rst author = Otto Yiu author_email = o...@live.ca @@ -11,6 +11,7 @@ url = https://github.com/adamchainz/django-cors-headers project_urls = Changelog = https://github.com/adamchainz/django-cors-headers/blob/master/HISTORY.rst + Twitter = https://twitter.com/adamchainz license = MIT License keywords = django @@ -26,6 +27,7 @@ Framework :: Django :: 2.1 Framework :: Django :: 2.2 Framework :: Django :: 3.0 + Framework :: Django :: 3.1 Intended Audience :: Developers License :: OSI Approved :: MIT License Operating System :: OS Independent @@ -35,6 +37,7 @@ Programming Language :: Python :: 3.6 Programming Language :: Python :: 3.7 Programming Language :: Python :: 3.8 + Programming Language :: Python :: 3.9 Topic :: Software Development :: Libraries :: Application Frameworks Topic :: Software Development :: Libraries :: Python Modules license_file = LICENSE diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/django-cors-headers-3.3.0/src/django_cors_headers.egg-info/PKG-INFO new/django-cors-headers-3.4.0/src/django_cors_headers.egg-info/PKG-INFO --- old/django-cors-headers-3.3.0/src/django_cors_headers.egg-info/PKG-INFO 2020-05-18 16:21:38.000000000 +0200 +++ new/django-cors-headers-3.4.0/src/django_cors_headers.egg-info/PKG-INFO 2020-06-15 13:04:55.000000000 +0200 @@ -1,6 +1,6 @@ Metadata-Version: 2.1 Name: django-cors-headers -Version: 3.3.0 +Version: 3.4.0 Summary: django-cors-headers is a Django application for handling the server headers required for Cross-Origin Resource Sharing (CORS). Home-page: https://github.com/adamchainz/django-cors-headers Author: Otto Yiu @@ -9,6 +9,7 @@ Maintainer-email: m...@adamj.eu License: MIT License Project-URL: Changelog, https://github.com/adamchainz/django-cors-headers/blob/master/HISTORY.rst +Project-URL: Twitter, https://twitter.com/adamchainz Description: django-cors-headers =================== @@ -392,295 +393,6 @@ check_request_enabled.connect(cors_allow_api_to_everyone) - History - ======= - - 3.3.0 (2020-05-18) - ------------------ - - * 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. - - 3.2.1 (2020-01-04) - ------------------ - - * Update LICENSE file to Unix line endings, fixing issues with license checker - ``pip-licenses`` (`Issue - #477 <https://github.com/adamchainz/django-cors-headers/issues/477>`__). - - 3.2.0 (2019-11-15) - ------------------ - - * Converted setuptools metadata to configuration file. This meant removing the - ``__version__`` attribute from the package. If you want to inspect the - installed version, use - ``importlib.metadata.version("django-cors-headers")`` - (`docs <https://docs.python.org/3.8/library/importlib.metadata.html#distribution-versions>`__ / - `backport <https://pypi.org/project/importlib-metadata/>`__). - * Support Python 3.8. - - 3.1.1 (2019-09-30) - ------------------ - - * Support the value `file://` for origins, which is accidentally sent by some - versions of Chrome on Android. - - 3.1.0 (2019-08-13) - ------------------ - - * 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``. - - 3.0.2 (2019-05-28) - ------------------ - - * Add a hint to the ``corsheaders.E013`` check to make it more obvious how to - resolve it. - - 3.0.1 (2019-05-13) - ------------------ - - * Allow 'null' in ``CORS_ORIGIN_WHITELIST`` check. - - 3.0.0 (2019-05-10) - ------------------ - - * ``CORS_ORIGIN_WHITELIST`` now requires URI schemes, and optionally ports. - This is part of the CORS specification - (`Section 3.2 <https://tools.ietf.org/html/rfc6454#section-3.2>`_) that was - not implemented in this library, except from with the - ``CORS_ORIGIN_REGEX_WHITELIST`` setting. It fixes a security issue where the - CORS middleware would allow requests between schemes, for example from - insecure ``http://`` Origins to a secure ``https://`` site. - - You will need to update your whitelist to include schemes, for example from - this: - - .. code-block:: python - - CORS_ORIGIN_WHITELIST = ['example.com'] - - ...to this: - - .. code-block:: python - - CORS_ORIGIN_WHITELIST = ['https://example.com'] - - * Removed the ``CORS_MODEL`` setting, and associated class. It seems very few, - or no users were using it, since there were no bug reports since its move to - abstract in version 2.0.0 (2017-01-07). If you *are* using this - functionality, you can continue by changing your model to not inherit from - the abstract one, and add a signal handler for ``check_request_enabled`` that - reads from your model. Note you'll need to handle the move to include schemes - for Origins. - - 2.5.3 (2019-04-28) - ------------------ - - * Tested on Django 2.2. No changes were needed for compatibility. - * Tested on Python 3.7. No changes were needed for compatibility. - - 2.5.2 (2019-03-15) - ------------------ - - * Improve inclusion of tests in ``sdist`` to ignore ``.pyc`` files. - - 2.5.1 (2019-03-13) - ------------------ - - * Include test infrastructure in ``sdist`` to allow consumers to use it. - - 2.5.0 (2019-03-05) - ------------------ - - * Drop Django 1.8, 1.9, and 1.10 support. Only Django 1.11+ is supported now. - - 2.4.1 (2019-02-28) - ------------------ - - * Fix ``DeprecationWarning`` from importing ``collections.abc.Sequence`` on - Python 3.7. - - 2.4.0 (2018-07-18) - ------------------ - - * 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. - - 2.3.0 (2018-06-27) - ------------------ - - * 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. - - 2.2.1 (2018-06-27) - ------------------ - - * Add ``Content-Length`` header to CORS preflight requests. This fixes issues - with some HTTP proxies and servers, e.g. AWS Elastic Beanstalk. - - 2.2.0 (2018-02-28) - ------------------ - - * 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. - - 2.1.0 (2017-05-28) - ------------------ - - * Django 1.11 compatibility. There were no changes to the actual library code, - so previous versions probably work, though they weren't properly tested on - 1.11. - - 2.0.2 (2017-02-06) - ------------------ - - * Fix when the check for ``CORS_MODEL`` is done to allow it to properly add - the headers and respond to ``OPTIONS`` requests. - - 2.0.1 (2017-01-29) - ------------------ - - * Add support for specifying 'null' in ``CORS_ORIGIN_WHITELIST``. - - 2.0.0 (2017-01-07) - ------------------ - - * Remove previously undocumented ``CorsModel`` as it was causing migration - issues. For backwards compatibility, any users previously using ``CorsModel`` - should create a model in their own app that inherits from the new - ``AbstractCorsModel``, and to keep using the same data, set the model's - ``db_table`` to 'corsheaders_corsmodel'. Users not using ``CorsModel`` - will find they have an unused table that they can drop. - * Make sure that ``Access-Control-Allow-Credentials`` is in the response if the - client asks for it. - - 1.3.1 (2016-11-09) - ------------------ - - * Fix a bug with the single check if CORS enabled added in 1.3.0: on Django - < 1.10 shortcut responses could be generated by middleware above - ``CorsMiddleware``, before it processed the request, failing with an - ``AttributeError`` for ``request._cors_enabled``. Also clarified the docs - that ``CorsMiddleware`` should be kept as high as possible in your middleware - stack, above any middleware that can generate such responses. - - 1.3.0 (2016-11-06) - ------------------ - - * Add checks to validate the types of the settings. - * Add the 'Do Not Track' header ``'DNT'`` to the default for - ``CORS_ALLOW_HEADERS``. - * Add 'Origin' to the 'Vary' header of outgoing requests when not allowing all - origins, as per the CORS spec. Note this changes the way HTTP caching works - with your CORS-enabled responses. - * Check whether CORS should be enabled on a request only once. This has had a - minor change on the conditions where any custom signals will be called - - signals will now always be called *before* ``HTTP_REFERER`` gets replaced, - whereas before they could be called before and after. Also this attaches the - attribute ``_cors_enabled`` to ``request`` - please take care that other - code you're running does not remove it. - - 1.2.2 (2016-10-05) - ------------------ - - * Add ``CorsModel.__str__`` for human-readable text - * Add a signal that allows you to add code for more intricate control over when - CORS headers are added. - - 1.2.1 (2016-09-30) - ------------------ - - * Made settings dynamically respond to changes, and which allows you to import - the defaults for headers and methods in order to extend them. - - 1.2.0 (2016-09-28) - ------------------ - - * Drop Python 2.6 support. - * Drop Django 1.3-1.7 support, as they are no longer supported. - * Confirmed Django 1.9 support (no changes outside of tests were necessary). - * Added Django 1.10 support. - * Package as a universal wheel. - - 1.1.0 (2014-12-15) - ------------------ - - * django-cors-header now supports Django 1.8 with its new application loading - system! Thanks @jpadilla for making this possible and sorry for the delay in - making a release. - - 1.0.0 (2014-12-13) - ------------------ - - django-cors-headers is all grown-up :) Since it's been used in production for - many many deployments, I think it's time we mark this as a stable release. - - * Switching this middleware versioning over to semantic versioning - * #46 add user-agent and accept-encoding default headers - * #45 pep-8 this big boy up - - 0.13 (2014-08-14) - ----------------- - - * Add support for Python 3 - * Updated tests - * Improved documentation - * Small bugfixes - - 0.12 (2013-09-24) - ----------------- - - * Added an option to selectively enable CORS only for specific URLs - - 0.11 (2013-09-24) - - * Added the ability to specify a regex for whitelisting many origin hostnames - at once - - 0.10 (2013-09-05) - ----------------- - - * Introduced port distinction for origin checking - * Use ``urlparse`` for Python 3 support - * Added testcases to project - - 0.06 (2013-02-18) - ----------------- - - * Add support for exposed response headers - - 0.05 (2013-01-26) - ----------------- - - * Fixed middleware to ensure correct response for CORS preflight requests - - 0.04 (2013-01-25) - ----------------- - - * Add ``Access-Control-Allow-Credentials`` control to simple requests - - 0.03 (2013-01-22) - ----------------- - - * Bugfix to repair mismatched default variable names - - 0.02 (2013-01-19) - ----------------- - - * Refactor/pull defaults into separate file - - 0.01 (2013-01-19) - ----------------- - - * Initial release - Keywords: django,cors,middleware,rest,api Platform: UNKNOWN Classifier: Development Status :: 5 - Production/Stable @@ -690,6 +402,7 @@ Classifier: Framework :: Django :: 2.1 Classifier: Framework :: Django :: 2.2 Classifier: Framework :: Django :: 3.0 +Classifier: Framework :: Django :: 3.1 Classifier: Intended Audience :: Developers Classifier: License :: OSI Approved :: MIT License Classifier: Operating System :: OS Independent @@ -699,6 +412,7 @@ Classifier: Programming Language :: Python :: 3.6 Classifier: Programming Language :: Python :: 3.7 Classifier: Programming Language :: Python :: 3.8 +Classifier: Programming Language :: Python :: 3.9 Classifier: Topic :: Software Development :: Libraries :: Application Frameworks Classifier: Topic :: Software Development :: Libraries :: Python Modules Requires-Python: >=3.5 diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/django-cors-headers-3.3.0/src/django_cors_headers.egg-info/SOURCES.txt new/django-cors-headers-3.4.0/src/django_cors_headers.egg-info/SOURCES.txt --- old/django-cors-headers-3.3.0/src/django_cors_headers.egg-info/SOURCES.txt 2020-05-18 16:21:38.000000000 +0200 +++ new/django-cors-headers-3.4.0/src/django_cors_headers.egg-info/SOURCES.txt 2020-06-15 13:04:55.000000000 +0200 @@ -34,18 +34,21 @@ tests/__pycache__/test_checks.cpython-37-pytest-5.2.2.pyc tests/__pycache__/test_checks.cpython-38-pytest-5.2.2.pyc tests/__pycache__/test_checks.cpython-38-pytest-5.3.2.pyc +tests/__pycache__/test_checks.cpython-38-pytest-5.4.2.pyc tests/__pycache__/test_conf.cpython-36-pytest-5.1.2.pyc tests/__pycache__/test_conf.cpython-37-pytest-5.1.2.pyc tests/__pycache__/test_conf.cpython-37-pytest-5.2.1.pyc tests/__pycache__/test_conf.cpython-37-pytest-5.2.2.pyc tests/__pycache__/test_conf.cpython-38-pytest-5.2.2.pyc tests/__pycache__/test_conf.cpython-38-pytest-5.3.2.pyc +tests/__pycache__/test_conf.cpython-38-pytest-5.4.2.pyc tests/__pycache__/test_middleware.cpython-36-pytest-5.1.2.pyc tests/__pycache__/test_middleware.cpython-37-pytest-5.1.2.pyc tests/__pycache__/test_middleware.cpython-37-pytest-5.2.1.pyc tests/__pycache__/test_middleware.cpython-37-pytest-5.2.2.pyc tests/__pycache__/test_middleware.cpython-38-pytest-5.2.2.pyc tests/__pycache__/test_middleware.cpython-38-pytest-5.3.2.pyc +tests/__pycache__/test_middleware.cpython-38-pytest-5.4.2.pyc tests/__pycache__/urls.cpython-36.pyc tests/__pycache__/urls.cpython-37.pyc tests/__pycache__/urls.cpython-38.pyc Binary files old/django-cors-headers-3.3.0/tests/__pycache__/__init__.cpython-38.pyc and new/django-cors-headers-3.4.0/tests/__pycache__/__init__.cpython-38.pyc differ Binary files old/django-cors-headers-3.3.0/tests/__pycache__/settings.cpython-38.pyc and new/django-cors-headers-3.4.0/tests/__pycache__/settings.cpython-38.pyc differ Binary files old/django-cors-headers-3.3.0/tests/__pycache__/test_checks.cpython-38-pytest-5.4.2.pyc and new/django-cors-headers-3.4.0/tests/__pycache__/test_checks.cpython-38-pytest-5.4.2.pyc differ Binary files old/django-cors-headers-3.3.0/tests/__pycache__/test_conf.cpython-38-pytest-5.4.2.pyc and new/django-cors-headers-3.4.0/tests/__pycache__/test_conf.cpython-38-pytest-5.4.2.pyc differ Binary files old/django-cors-headers-3.3.0/tests/__pycache__/test_middleware.cpython-38-pytest-5.4.2.pyc and new/django-cors-headers-3.4.0/tests/__pycache__/test_middleware.cpython-38-pytest-5.4.2.pyc differ Binary files old/django-cors-headers-3.3.0/tests/__pycache__/urls.cpython-38.pyc and new/django-cors-headers-3.4.0/tests/__pycache__/urls.cpython-38.pyc differ Binary files old/django-cors-headers-3.3.0/tests/__pycache__/utils.cpython-38.pyc and new/django-cors-headers-3.4.0/tests/__pycache__/utils.cpython-38.pyc differ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/django-cors-headers-3.3.0/tests/urls.py new/django-cors-headers-3.4.0/tests/urls.py --- old/django-cors-headers-3.3.0/tests/urls.py 2020-02-24 17:30:45.000000000 +0100 +++ new/django-cors-headers-3.4.0/tests/urls.py 2020-05-24 10:01:58.000000000 +0200 @@ -1,5 +1,5 @@ -from django.conf.urls import url from django.http import Http404, HttpResponse +from django.urls import path def test_view(request): @@ -19,8 +19,8 @@ urlpatterns = [ - url(r"^$", test_view), - url(r"^foo/$", test_view), - url(r"^test-401/$", test_view_http401), - url(r"^delete-is-enabled/$", test_view_that_deletes_is_enabled), + path("", test_view), + path("foo/", test_view), + path("test-401/", test_view_http401), + path("delete-is-enabled/", test_view_that_deletes_is_enabled), ]