django-multisite2 2.1.1__tar.gz → 2.1.2__tar.gz

{django-multisite2-2.1.1 → django-multisite2-2.1.2}/.gitignore

@@ -8,6 +8,7 @@ _version.py
 *.pyo
 .cache/
 .eggs/
+*.egg-info/
 .installed.cfg
 bin
 develop-eggs

{django-multisite2-2.1.1 → django-multisite2-2.1.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: django-multisite2
-Version: 2.1.1
+Version: 2.1.2
 Summary: Serve multiple sites from a single Django application
 Home-page: http://github.com/erikvw/django-multisite
 Author: Leonid S Shestera
@@ -32,20 +32,34 @@ Requires-Dist: tldextract
 README
 ======
 
-Install with pip::
+Python 3.11+ Django 4.2+
 
-    pip install django-multisite-edc
+Older versions of Django are supported by the original `django-multisite`_ project.
 
+.. _django-multisite: https://github.com/ecometrica/django-multisite
 
-Quickstart
-----------
 
-Replace your SITE_ID in settings.py to::
+Installation
+============
+
+Install with pip:
+
+.. code-block::
+
+    pip install django-multisite2
+
+
+Replace your ``SITE_ID`` in ``settings.py`` to:
+
+.. code-block::
 
     from multisite import SiteID
     SITE_ID = SiteID(default=1)
 
-Add these to your INSTALLED_APPS::
+
+add to INSTALLED_APPS:
+
+.. code-block::
 
     INSTALLED_APPS = [
         ...
@@ -54,25 +68,10 @@ Add these to your INSTALLED_APPS::
         ...
     ]
 
-Add to your settings.py TEMPLATES loaders in the OPTIONS section::
 
-    TEMPLATES = [
-        ...
-        {
-            ...
-            'DIRS': {...}
-            'OPTIONS': {
-                'loaders': (
-                    'multisite.template.loaders.filesystem.Loader',
-                    'django.template.loaders.app_directories.Loader',
-                )
-            }
-            ...
-        }
-        ...
-    ]
+Edit settings.py MIDDLEWARE:
 
-Edit settings.py MIDDLEWARE::
+.. code-block::
 
     MIDDLEWARE = (
         ...
@@ -80,6 +79,9 @@ Edit settings.py MIDDLEWARE::
         ...
     )
 
+
+Using a custom cache
+--------------------
 Append to settings.py, in order to use a custom cache that can be
 safely cleared::
 
@@ -106,24 +108,6 @@ If you have set CACHE\_MULTISITE\_ALIAS to a custom value, *e.g.*
         },
     }
 
-Development Environments
-------------------------
-Multisite returns a valid Alias when in "development mode" (defaulting to the
-alias associated with the default SiteID.
-
-Development mode is either:
-    - Running tests, i.e. manage.py test
-    - Running locally in settings.DEBUG = True, where the hostname is a top-level name, i.e. localhost
-
-In order to have multisite use aliases in local environments, add entries to
-your local etc/hosts file to match aliases in your applications.  E.g. ::
-
-    127.0.0.1 example.com
-    127.0.0.1 examplealias.com
-
-And access your application at example.com:8000 or examplealias.com:8000 instead of
-the usual localhost:8000.
-
 
 Domain fallbacks
 ----------------
@@ -199,11 +183,11 @@ run::
 
 Post-migrate signal: post_migrate_sync_alias
 --------------------------------------------
-The `post-migrate` signal `post_migrate_sync_alias` is registered in the `apps.py`. `post_migrate_sync_alias`
-ensures the `domain` in multisite's `Alias` model is updated to match that of django's `Site` model. This signal must
-run AFTER any `post-migrate` signals that manipulate Django's `Site` model. If you have an app that manipulates Django's
-`Site` model, place it before `multisite` in `settings. INSTALLED_APPS`. If this is not possible, you may configure `multisite`
-to not connect the `post-migrate` signal in `apps.py` so that you can do it somewhere else in your code.
+The ``post-migrate`` signal ``post_migrate_sync_alias`` is registered in the ``apps.py``. ``post_migrate_sync_alias``
+ensures the ``domain`` in multisite's ``Alias`` model is updated to match that of django's ``Site`` model. This signal must
+run AFTER any ``post-migrate`` signals that manipulate Django's ``Site`` model. If you have an app that manipulates Django's
+``Site`` model, place it before ``multisite`` in `settings. INSTALLED_APPS`. If this is not possible, you may configure ``multisite``
+to not connect the ``post-migrate`` signal in ``apps.py`` so that you can do it somewhere else in your code.
 
 To configure `multisite` to not connect the `post-post_migrate_sync_alias` in the `apps.py`, update your settings::
 
@@ -213,6 +197,24 @@ With the `settings` attribute set to `False`, it is your responsibility to conne
 models after the `Site` model has changed, multisite may not recognize the domain and switch to the fallback view or
 raise a `Http404` error.
 
+Development Environments
+------------------------
+Multisite returns a valid Alias when in "development mode" (defaulting to the
+alias associated with the default SiteID.
+
+Development mode is either:
+    - Running tests, i.e. manage.py test
+    - Running locally in settings.DEBUG = True, where the hostname is a top-level name, i.e. localhost
+
+In order to have multisite use aliases in local environments, add entries to
+your local etc/hosts file to match aliases in your applications.  E.g. ::
+
+    127.0.0.1 example.com
+    127.0.0.1 examplealias.com
+
+And access your application at example.com:8000 or examplealias.com:8000 instead of
+the usual localhost:8000.
+
 Tests
 -----
 
@@ -222,20 +224,20 @@ To run the tests::
 
 
 
-.. |pypi| image:: https://img.shields.io/pypi/v/django-multisite.svg
-    :target: https://pypi.python.org/pypi/django-multisite
+.. |pypi| image:: https://img.shields.io/pypi/v/django-multisite2.svg
+    :target: https://pypi.python.org/pypi/django-multisite2
 
-.. |actions| image:: https://github.com/erikvw/django-multisite/actions/workflows/build.yml/badge.svg
-  :target: https://github.com/erikvw/django-multisite/actions/workflows/build.yml
+.. |actions| image:: https://github.com/erikvw/django-multisite2/actions/workflows/build.yml/badge.svg
+  :target: https://github.com/erikvw/django-multisite2/actions/workflows/build.yml
 
-.. |codecov| image:: https://codecov.io/gh/erikvw/django-multisite/branch/develop/graph/badge.svg
-  :target: https://codecov.io/gh/erikvw/django-multisite
+.. |codecov| image:: https://codecov.io/gh/erikvw/django-multisite2/branch/develop/graph/badge.svg
+  :target: https://codecov.io/gh/erikvw/django-multisite2
 
-.. |downloads| image:: https://pepy.tech/badge/django-multisite
-   :target: https://pepy.tech/project/django-multisite
+.. |downloads| image:: https://pepy.tech/badge/django-multisite2
+   :target: https://pepy.tech/project/django-multisite2
 
-.. |maintainability| image:: https://api.codeclimate.com/v1/badges/d280e92995a883a4f8db/maintainability
-   :target: https://codeclimate.com/github/erikvw/django-multisite/maintainability
+.. |maintainability| image:: https://api.codeclimate.com/v1/badges/4992e131641fc6929b1a/maintainability
+   :target: https://codeclimate.com/github/erikvw/django-multisite2/maintainability
    :alt: Maintainability
 
 .. |black| image:: https://img.shields.io/badge/code%20style-black-000000.svg

{django-multisite2-2.1.1 → django-multisite2-2.1.2}/README.rst

@@ -5,20 +5,34 @@
 README
 ======
 
-Install with pip::
+Python 3.11+ Django 4.2+
 
-    pip install django-multisite-edc
+Older versions of Django are supported by the original `django-multisite`_ project.
 
+.. _django-multisite: https://github.com/ecometrica/django-multisite
 
-Quickstart
-----------
 
-Replace your SITE_ID in settings.py to::
+Installation
+============
+
+Install with pip:
+
+.. code-block::
+
+    pip install django-multisite2
+
+
+Replace your ``SITE_ID`` in ``settings.py`` to:
+
+.. code-block::
 
     from multisite import SiteID
     SITE_ID = SiteID(default=1)
 
-Add these to your INSTALLED_APPS::
+
+add to INSTALLED_APPS:
+
+.. code-block::
 
     INSTALLED_APPS = [
         ...
@@ -27,25 +41,10 @@ Add these to your INSTALLED_APPS::
         ...
     ]
 
-Add to your settings.py TEMPLATES loaders in the OPTIONS section::
 
-    TEMPLATES = [
-        ...
-        {
-            ...
-            'DIRS': {...}
-            'OPTIONS': {
-                'loaders': (
-                    'multisite.template.loaders.filesystem.Loader',
-                    'django.template.loaders.app_directories.Loader',
-                )
-            }
-            ...
-        }
-        ...
-    ]
+Edit settings.py MIDDLEWARE:
 
-Edit settings.py MIDDLEWARE::
+.. code-block::
 
     MIDDLEWARE = (
         ...
@@ -53,6 +52,9 @@ Edit settings.py MIDDLEWARE::
         ...
     )
 
+
+Using a custom cache
+--------------------
 Append to settings.py, in order to use a custom cache that can be
 safely cleared::
 
@@ -79,24 +81,6 @@ If you have set CACHE\_MULTISITE\_ALIAS to a custom value, *e.g.*
         },
     }
 
-Development Environments
-------------------------
-Multisite returns a valid Alias when in "development mode" (defaulting to the
-alias associated with the default SiteID.
-
-Development mode is either:
-    - Running tests, i.e. manage.py test
-    - Running locally in settings.DEBUG = True, where the hostname is a top-level name, i.e. localhost
-
-In order to have multisite use aliases in local environments, add entries to
-your local etc/hosts file to match aliases in your applications.  E.g. ::
-
-    127.0.0.1 example.com
-    127.0.0.1 examplealias.com
-
-And access your application at example.com:8000 or examplealias.com:8000 instead of
-the usual localhost:8000.
-
 
 Domain fallbacks
 ----------------
@@ -172,11 +156,11 @@ run::
 
 Post-migrate signal: post_migrate_sync_alias
 --------------------------------------------
-The `post-migrate` signal `post_migrate_sync_alias` is registered in the `apps.py`. `post_migrate_sync_alias`
-ensures the `domain` in multisite's `Alias` model is updated to match that of django's `Site` model. This signal must
-run AFTER any `post-migrate` signals that manipulate Django's `Site` model. If you have an app that manipulates Django's
-`Site` model, place it before `multisite` in `settings. INSTALLED_APPS`. If this is not possible, you may configure `multisite`
-to not connect the `post-migrate` signal in `apps.py` so that you can do it somewhere else in your code.
+The ``post-migrate`` signal ``post_migrate_sync_alias`` is registered in the ``apps.py``. ``post_migrate_sync_alias``
+ensures the ``domain`` in multisite's ``Alias`` model is updated to match that of django's ``Site`` model. This signal must
+run AFTER any ``post-migrate`` signals that manipulate Django's ``Site`` model. If you have an app that manipulates Django's
+``Site`` model, place it before ``multisite`` in `settings. INSTALLED_APPS`. If this is not possible, you may configure ``multisite``
+to not connect the ``post-migrate`` signal in ``apps.py`` so that you can do it somewhere else in your code.
 
 To configure `multisite` to not connect the `post-post_migrate_sync_alias` in the `apps.py`, update your settings::
 
@@ -186,6 +170,24 @@ With the `settings` attribute set to `False`, it is your responsibility to conne
 models after the `Site` model has changed, multisite may not recognize the domain and switch to the fallback view or
 raise a `Http404` error.
 
+Development Environments
+------------------------
+Multisite returns a valid Alias when in "development mode" (defaulting to the
+alias associated with the default SiteID.
+
+Development mode is either:
+    - Running tests, i.e. manage.py test
+    - Running locally in settings.DEBUG = True, where the hostname is a top-level name, i.e. localhost
+
+In order to have multisite use aliases in local environments, add entries to
+your local etc/hosts file to match aliases in your applications.  E.g. ::
+
+    127.0.0.1 example.com
+    127.0.0.1 examplealias.com
+
+And access your application at example.com:8000 or examplealias.com:8000 instead of
+the usual localhost:8000.
+
 Tests
 -----
 
@@ -195,20 +197,20 @@ To run the tests::
 
 
 
-.. |pypi| image:: https://img.shields.io/pypi/v/django-multisite.svg
-    :target: https://pypi.python.org/pypi/django-multisite
+.. |pypi| image:: https://img.shields.io/pypi/v/django-multisite2.svg
+    :target: https://pypi.python.org/pypi/django-multisite2
 
-.. |actions| image:: https://github.com/erikvw/django-multisite/actions/workflows/build.yml/badge.svg
-  :target: https://github.com/erikvw/django-multisite/actions/workflows/build.yml
+.. |actions| image:: https://github.com/erikvw/django-multisite2/actions/workflows/build.yml/badge.svg
+  :target: https://github.com/erikvw/django-multisite2/actions/workflows/build.yml
 
-.. |codecov| image:: https://codecov.io/gh/erikvw/django-multisite/branch/develop/graph/badge.svg
-  :target: https://codecov.io/gh/erikvw/django-multisite
+.. |codecov| image:: https://codecov.io/gh/erikvw/django-multisite2/branch/develop/graph/badge.svg
+  :target: https://codecov.io/gh/erikvw/django-multisite2
 
-.. |downloads| image:: https://pepy.tech/badge/django-multisite
-   :target: https://pepy.tech/project/django-multisite
+.. |downloads| image:: https://pepy.tech/badge/django-multisite2
+   :target: https://pepy.tech/project/django-multisite2
 
-.. |maintainability| image:: https://api.codeclimate.com/v1/badges/d280e92995a883a4f8db/maintainability
-   :target: https://codeclimate.com/github/erikvw/django-multisite/maintainability
+.. |maintainability| image:: https://api.codeclimate.com/v1/badges/4992e131641fc6929b1a/maintainability
+   :target: https://codeclimate.com/github/erikvw/django-multisite2/maintainability
    :alt: Maintainability
 
 .. |black| image:: https://img.shields.io/badge/code%20style-black-000000.svg

{django-multisite2-2.1.1 → django-multisite2-2.1.2}/django_multisite2.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: django-multisite2
-Version: 2.1.1
+Version: 2.1.2
 Summary: Serve multiple sites from a single Django application
 Home-page: http://github.com/erikvw/django-multisite
 Author: Leonid S Shestera
@@ -32,20 +32,34 @@ Requires-Dist: tldextract
 README
 ======
 
-Install with pip::
+Python 3.11+ Django 4.2+
 
-    pip install django-multisite-edc
+Older versions of Django are supported by the original `django-multisite`_ project.
 
+.. _django-multisite: https://github.com/ecometrica/django-multisite
 
-Quickstart
-----------
 
-Replace your SITE_ID in settings.py to::
+Installation
+============
+
+Install with pip:
+
+.. code-block::
+
+    pip install django-multisite2
+
+
+Replace your ``SITE_ID`` in ``settings.py`` to:
+
+.. code-block::
 
     from multisite import SiteID
     SITE_ID = SiteID(default=1)
 
-Add these to your INSTALLED_APPS::
+
+add to INSTALLED_APPS:
+
+.. code-block::
 
     INSTALLED_APPS = [
         ...
@@ -54,25 +68,10 @@ Add these to your INSTALLED_APPS::
         ...
     ]
 
-Add to your settings.py TEMPLATES loaders in the OPTIONS section::
 
-    TEMPLATES = [
-        ...
-        {
-            ...
-            'DIRS': {...}
-            'OPTIONS': {
-                'loaders': (
-                    'multisite.template.loaders.filesystem.Loader',
-                    'django.template.loaders.app_directories.Loader',
-                )
-            }
-            ...
-        }
-        ...
-    ]
+Edit settings.py MIDDLEWARE:
 
-Edit settings.py MIDDLEWARE::
+.. code-block::
 
     MIDDLEWARE = (
         ...
@@ -80,6 +79,9 @@ Edit settings.py MIDDLEWARE::
         ...
     )
 
+
+Using a custom cache
+--------------------
 Append to settings.py, in order to use a custom cache that can be
 safely cleared::
 
@@ -106,24 +108,6 @@ If you have set CACHE\_MULTISITE\_ALIAS to a custom value, *e.g.*
         },
     }
 
-Development Environments
-------------------------
-Multisite returns a valid Alias when in "development mode" (defaulting to the
-alias associated with the default SiteID.
-
-Development mode is either:
-    - Running tests, i.e. manage.py test
-    - Running locally in settings.DEBUG = True, where the hostname is a top-level name, i.e. localhost
-
-In order to have multisite use aliases in local environments, add entries to
-your local etc/hosts file to match aliases in your applications.  E.g. ::
-
-    127.0.0.1 example.com
-    127.0.0.1 examplealias.com
-
-And access your application at example.com:8000 or examplealias.com:8000 instead of
-the usual localhost:8000.
-
 
 Domain fallbacks
 ----------------
@@ -199,11 +183,11 @@ run::
 
 Post-migrate signal: post_migrate_sync_alias
 --------------------------------------------
-The `post-migrate` signal `post_migrate_sync_alias` is registered in the `apps.py`. `post_migrate_sync_alias`
-ensures the `domain` in multisite's `Alias` model is updated to match that of django's `Site` model. This signal must
-run AFTER any `post-migrate` signals that manipulate Django's `Site` model. If you have an app that manipulates Django's
-`Site` model, place it before `multisite` in `settings. INSTALLED_APPS`. If this is not possible, you may configure `multisite`
-to not connect the `post-migrate` signal in `apps.py` so that you can do it somewhere else in your code.
+The ``post-migrate`` signal ``post_migrate_sync_alias`` is registered in the ``apps.py``. ``post_migrate_sync_alias``
+ensures the ``domain`` in multisite's ``Alias`` model is updated to match that of django's ``Site`` model. This signal must
+run AFTER any ``post-migrate`` signals that manipulate Django's ``Site`` model. If you have an app that manipulates Django's
+``Site`` model, place it before ``multisite`` in `settings. INSTALLED_APPS`. If this is not possible, you may configure ``multisite``
+to not connect the ``post-migrate`` signal in ``apps.py`` so that you can do it somewhere else in your code.
 
 To configure `multisite` to not connect the `post-post_migrate_sync_alias` in the `apps.py`, update your settings::
 
@@ -213,6 +197,24 @@ With the `settings` attribute set to `False`, it is your responsibility to conne
 models after the `Site` model has changed, multisite may not recognize the domain and switch to the fallback view or
 raise a `Http404` error.
 
+Development Environments
+------------------------
+Multisite returns a valid Alias when in "development mode" (defaulting to the
+alias associated with the default SiteID.
+
+Development mode is either:
+    - Running tests, i.e. manage.py test
+    - Running locally in settings.DEBUG = True, where the hostname is a top-level name, i.e. localhost
+
+In order to have multisite use aliases in local environments, add entries to
+your local etc/hosts file to match aliases in your applications.  E.g. ::
+
+    127.0.0.1 example.com
+    127.0.0.1 examplealias.com
+
+And access your application at example.com:8000 or examplealias.com:8000 instead of
+the usual localhost:8000.
+
 Tests
 -----
 
@@ -222,20 +224,20 @@ To run the tests::
 
 
 
-.. |pypi| image:: https://img.shields.io/pypi/v/django-multisite.svg
-    :target: https://pypi.python.org/pypi/django-multisite
+.. |pypi| image:: https://img.shields.io/pypi/v/django-multisite2.svg
+    :target: https://pypi.python.org/pypi/django-multisite2
 
-.. |actions| image:: https://github.com/erikvw/django-multisite/actions/workflows/build.yml/badge.svg
-  :target: https://github.com/erikvw/django-multisite/actions/workflows/build.yml
+.. |actions| image:: https://github.com/erikvw/django-multisite2/actions/workflows/build.yml/badge.svg
+  :target: https://github.com/erikvw/django-multisite2/actions/workflows/build.yml
 
-.. |codecov| image:: https://codecov.io/gh/erikvw/django-multisite/branch/develop/graph/badge.svg
-  :target: https://codecov.io/gh/erikvw/django-multisite
+.. |codecov| image:: https://codecov.io/gh/erikvw/django-multisite2/branch/develop/graph/badge.svg
+  :target: https://codecov.io/gh/erikvw/django-multisite2
 
-.. |downloads| image:: https://pepy.tech/badge/django-multisite
-   :target: https://pepy.tech/project/django-multisite
+.. |downloads| image:: https://pepy.tech/badge/django-multisite2
+   :target: https://pepy.tech/project/django-multisite2
 
-.. |maintainability| image:: https://api.codeclimate.com/v1/badges/d280e92995a883a4f8db/maintainability
-   :target: https://codeclimate.com/github/erikvw/django-multisite/maintainability
+.. |maintainability| image:: https://api.codeclimate.com/v1/badges/4992e131641fc6929b1a/maintainability
+   :target: https://codeclimate.com/github/erikvw/django-multisite2/maintainability
    :alt: Maintainability
 
 .. |black| image:: https://img.shields.io/badge/code%20style-black-000000.svg

{django-multisite2-2.1.1 → django-multisite2-2.1.2}/django_multisite2.egg-info/SOURCES.txt

@@ -17,7 +17,6 @@ django_multisite2.egg-info/not-zip-safe
 django_multisite2.egg-info/requires.txt
 django_multisite2.egg-info/top_level.txt
 multisite/__init__.py
-multisite/__version__.py
 multisite/apps.py
 multisite/exceptions.py
 multisite/forms.py
@@ -28,10 +27,6 @@ multisite/__pycache__/__init__.cpython-310.pyc
 multisite/__pycache__/__init__.cpython-311.pyc
 multisite/__pycache__/__init__.cpython-312.pyc
 multisite/__pycache__/__init__.cpython-39.pyc
-multisite/__pycache__/__version__.cpython-310.pyc
-multisite/__pycache__/__version__.cpython-311.pyc
-multisite/__pycache__/__version__.cpython-312.pyc
-multisite/__pycache__/__version__.cpython-39.pyc
 multisite/__pycache__/apps.cpython-312.pyc
 multisite/__pycache__/exceptions.cpython-312.pyc
 multisite/__pycache__/forms.cpython-310.pyc
@@ -89,6 +84,7 @@ multisite/middleware/__pycache__/dynamic_site_middleware.cpython-312.pyc
 multisite/migrations/0001_initial.py
 multisite/migrations/0002_alter_alias_id_alter_alias_is_canonical.py
 multisite/migrations/0003_alter_alias_options_alter_alias_unique_together_and_more.py
+multisite/migrations/0004_alter_alias_managers.py
 multisite/migrations/__init__.py
 multisite/migrations/__pycache__/0001_initial.cpython-310.pyc
 multisite/migrations/__pycache__/0001_initial.cpython-311.pyc
@@ -100,6 +96,7 @@ multisite/migrations/__pycache__/0002_alter_alias_id_alter_alias_is_canonical.cp
 multisite/migrations/__pycache__/0002_alter_alias_id_alter_alias_is_canonical.cpython-39.pyc
 multisite/migrations/__pycache__/0003_alias_multisite_alias_canon_site_uniq.cpython-311.pyc
 multisite/migrations/__pycache__/0003_alter_alias_options_alter_alias_unique_together_and_more.cpython-312.pyc
+multisite/migrations/__pycache__/0004_alter_alias_managers.cpython-312.pyc
 multisite/migrations/__pycache__/__init__.cpython-310.pyc
 multisite/migrations/__pycache__/__init__.cpython-311.pyc
 multisite/migrations/__pycache__/__init__.cpython-312.pyc

{django-multisite2-2.1.1 → django-multisite2-2.1.2}/multisite/__init__.py

@@ -1,2 +1 @@
-from .__version__ import __version__
 from .threadlocals import SiteDomain, SiteID

django-multisite2-2.1.2/multisite/migrations/0004_alter_alias_managers.py

@@ -0,0 +1,22 @@
+# Generated by Django 4.2.11 on 2024-03-27 04:14
+
+from django.db import migrations
+import multisite.models.managers
+
+
+class Migration(migrations.Migration):
+
+    dependencies = [
+        ("multisite", "0003_alter_alias_options_alter_alias_unique_together_and_more"),
+    ]
+
+    operations = [
+        migrations.AlterModelManagers(
+            name="alias",
+            managers=[
+                ("objects", multisite.models.managers.AliasManager()),
+                ("canonical", multisite.models.managers.CanonicalAliasManager()),
+                ("aliases", multisite.models.managers.NotCanonicalAliasManager()),
+            ],
+        ),
+    ]

{django-multisite2-2.1.1 → django-multisite2-2.1.2}/multisite/tests/tests/test_alias.py

@@ -69,7 +69,6 @@ class AliasTest(TestCase):
             "<Alias: %(domain)s -> %(domain)s>" % site.__dict__,
         )
 
-    @tag("1")
     def test_managers(self):
         site = Site.objects.create(domain="example.com")
         Alias.objects.create(site=site, domain="example.org")

{django-multisite2-2.1.1 → django-multisite2-2.1.2}/multisite/threadlocals.py

@@ -4,19 +4,6 @@ from threading import local
 from django.conf import settings
 from django.core.exceptions import ImproperlyConfigured
 
-_thread_locals = local()
-
-
-# def get_request():
-#     return getattr(_thread_locals, "request", None)
-
-
-# class ThreadLocalsMiddleware(MiddlewareMixin):
-#     """Middleware that saves request in thread local storage"""
-#
-#     def process_request(self, request):
-#         _thread_locals.request = request
-
 
 class SiteID(local):
     """