maxking / maxking/docker-mailman
[BUG] ACCOUNT_AUTHENTICATION_METHOD is deprecated, ACCOUNT_EMAIL_REQUIRED is deprecated
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 278
- Forks
- 121
- PR merge metrics
- No merged PRs in 30d
Description
Tag/version of Container Images
Choose from: 0.5
WARNINGS:
?: settings.ACCOUNT_AUTHENTICATION_METHOD is deprecated, use: settings.ACCOUNT_LOGIN_METHODS = {'username', 'email'}
?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'username*', 'password1*', 'password2*']
- https://github.com/maxking/docker-mailman/blob/main/postorius/mailman-web/settings.py#L242
- https://github.com/maxking/docker-mailman/blob/main/postorius/mailman-web/settings.py#L243
Changed occurred in django-allauth version 65.4.0
The upstream Postorius project pyproject.toml has a dependency on "django-mailman3>=1.3.13"
The upstream django-mailman3 project pyproject.toml has a dependency of "django-allauth[socialaccount,openid]>=65.5"
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with postorius/mailman-web/settings.py at lines 242-243 and compare the deprecated settings with the django-allauth 65.4.0 migration notes. Update the authentication and signup configuration using the replacements shown in the warnings, then verify the 0.5 container no longer emits these deprecation warnings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, docker, python
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100