This repository has been archived by the owner on Jul 11, 2022. It is now read-only.
update devel branch #11
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Django 3.0 will not support Python 3.5
It will reach its EOL in March 2019, see https://www.python.org/dev/peps/pep-0429/#release-schedule
R0205 in pylint
Reached its EOL on 2019-04-01 https://www.djangoproject.com/download/#supported-versions
Helps pip decide what version of the library to install. https://packaging.python.org/tutorials/distributing-packages/#python-requires > If your project only runs on certain Python versions, setting the > python_requires argument to the appropriate PEP 440 version specifier > string will prevent pip from installing the project on other Python > versions. https://setuptools.readthedocs.io/en/latest/setuptools.html#new-and-changed-setup-keywords > python_requires > > A string corresponding to a version specifier (as defined in PEP 440) > for the Python version, used to specify the Requires-Python defined in > PEP 345.
* Update example to be PEP8 compliant
Django provides a keyword argument called `using` to the `post_migrate` signal handler. This argument tells the handler which database was migrated. Previously, the `create_anonymous_user()` function would always try to use the default database to create the anonymous user. This change uses the `using` parameter to make sure we use the database that actually underwent the migration. Closes: #630
* Overly optimistic content type queries * Why not
* Simple auto prefetching for vanilla usecases * Added auto prefetch docs * Add cache eviction * Add auto prefetch tests * Ensure only active for User objects * Add Group prefetch support and improve tests
Co-authored-by: Michael K. <michael-k@users.noreply.github.com>
The response.headers interface is added in Django 3.2 django/django@dcb6904
* test: drop python3.6 and python3.7 for django master * test: drop py35 py37 for django master
…(instead of master) (#736) * Django renamed the branch 'master' to 'main' ref PR django/django#14048 * Run tests against Django 3.2 ref https://docs.djangoproject.com/en/3.2/releases/3.2/ * Switch from Travis CI to GitHub Actions * Remove pins from test dependencies * Ensure tests run against versions of Django that support Python 3.9 * Pin version of Ubuntu used by GitHub Actions
* Mention GitHub Actions instead of Travis CI everywhere * [docs] Remove 'recently' Co-authored-by: Adam Dobrawy <ad-m@users.noreply.github.com>
Sorry for missing this twice :/
* Update tested Django versions to latest patch releases * Update tox.ini Django versions * Revert 2.2-3.1 patch version bumps * Revert 2.2-3.1 patch release bumps
In this case we want to reduce the set of objects to those given in the queryset, for use-cases with lots of objects with explicit permissions. See #189
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.