Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pin django-registration-redux to latest version 2.2 #36

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pyup-bot
Copy link
Contributor

@pyup-bot pyup-bot commented Feb 9, 2018

django-registration-redux is not pinned to a specific version.

I'm pinning it to the latest version 2.2 for now.

These links might come in handy: PyPI | Changelog | Repo

Changelog

2.2


  • Bugfix: Updates Russian translation messages. -
    321 <https://github.com/macropin/django-registration/pull/321>_

2.1


  • Bugfix: Fix formatting issues in documentation.
    319 <https://github.com/macropin/django-registration/pull/319>_
  • Bugfix: Use get_username() instead of directly accessing the username to
    support subclasses of AbstractBaseUser
    318 <https://github.com/macropin/django-registration/pull/318>_

2.0


  • BACKWARDS-INCOMPATIBLE CHANGE: Remove support for Django < 1.11.
  • BACKWARDS-INCOMPATIBLE CHANGE: Remove registration/urls.py in favor of
    registration/backends/default/urls.py
  • Feature: Add compatibility for Django 2.0.

1.9


  • Bugfix: Fix SupervisedRegistrationProfile so expiration depends on
    profiles that have completed the entire process or have exceeded the
    ACCOUNT_ACTIVATION_DAYS -
    310 &lt;https://github.com/macropin/django-registration/pull/310&gt;_
  • Bugfix: Prevent resending an activation email if multiple
    RegistrationProfile objects exist for the given email address. -
    311 &lt;https://github.com/macropin/django-registration/pull/311&gt;_
  • Bugfix: Add logging to RegistrationProfile.delete_expired_users, use
    profile.activated instead of user.is_active. -
    308 &lt;https://github.com/macropin/django-registration/pull/308&gt;_
  • BACKWARDS-INCOMPATIBLE CHANGE: Change of return signature of
    RegistrationProfileManager.activate_user. A tuple containing the User
    instance and a boolean of whether or not said user was activated is now
    returned. -
    309 &lt;https://github.com/macropin/django-registration/pull/309&gt;_.
  • Bugfix: Updates pt_BR translation messages. -
    305 &lt;https://github.com/macropin/django-registration/pull/305&gt;_
  • Bugfix: Update all translation strings with django-admin makemessages --all. -
    304 &lt;https://github.com/macropin/django-registration/pull/304&gt;_
  • Feature: Configure from email address from Site object. -
    294 &lt;https://github.com/macropin/django-registration/pull/294&gt;_

1.8


  • Bugfix: Add outlook.com to the list of free email providers. -
    287 &lt;https://github.com/macropin/django-registration/pull/287&gt;_
  • Documentation: Add possible settings for activation emails. -
    283 &lt;https://github.com/macropin/django-registration/pull/282&gt;_
  • Feature: Added REGISTRATION_ADMINS setting to support different admins
    (than those in ADMINS) in charge of registration. Falls back to ADMINS in
    case this is not set. -
    279 &lt;https://github.com/macropin/django-registration/pull/279&gt;_
  • Documentation: Added documentation regarding admin approval registration. -
    279 &lt;https://github.com/macropin/django-registration/pull/279&gt;_
  • Redirect logged in users away from the registration page if authenticated. -
    262 &lt;https://github.com/macropin/django-registration/pull/262&gt;_
  • Document how to send password reset email with HTML content. -
    276 &lt;https://github.com/macropin/django-registration/pull/276&gt;_

1.7


  • Fix security issue of leaking password reset token through the Referer
    header. - 268 &lt;https://github.com/macropin/django-registration/pull/268&gt;_
  • Fix migration issue when using multiple databases - 264 &lt;https://github.com/macropin/django-registration/pull/264&gt;_
  • Improve German translation - 259 &lt;https://github.com/macropin/django-registration/pull/259&gt;_
  • Fix bug in templates if password reset is unsuccessful - 269 &lt;https://github.com/macropin/django-registration/pull/269&gt;_

1.6


  • Feature: Make search for email case insensitive when resending activation
    email.
    250 &lt;https://github.com/macropin/django-registration/pull/250&gt;_.
  • Feature: Add RegistrationFormUsernameLowercase to force all usernames to
    lowercase.
    251 &lt;https://github.com/macropin/django-registration/pull/251&gt;_.

1.5


  • BACKWARDS-INCOMPATIBLE CHANGE: Remove support for Django 1.7.
  • BACKWARDS-INCOMPATIBLE CHANGE: Change signature of
    RegistrationProfileManager.activate_user.
    site is now a required positional argument.
    244 &lt;https://github.com/macropin/django-registration/pull/244&gt;_.
  • Feature: Added workflow to resend activation email. See
    161 &lt;https://github.com/macropin/django-registration/pull/161&gt;_.
  • Enhancement: Separate logic between account creation and activation.
    See: 171 &lt;https://github.com/macropin/django-registration/issues/171&gt;_.
  • Bugfix: Add page title to activate.html
  • Feature: Added a 3-step registration flow requiring manual admin approval.
    See: 184 &lt;https://github.com/macropin/django-registration/pull/184&gt;_.
  • Enhancement: Using a more cryptographically secure method for generating
    activation keys.
    See: 213 &lt;https://github.com/macropin/django-registration/issues/213&gt;_.
  • Bugfix: Add redirection setting for simple backend after successful
    registration.
    See: 239 &lt;https://github.com/macropin/django-registration/pull/239&gt;_.
  • Bugfix: Use dict instead of RequestContext when sending activation email.

See: 194 &lt;https://github.com/macropin/django-registration/pull/194&gt;_.

1.4


  • BACKWARDS-INCOMPATIBLE CHANGE: Remove unnecessary _RequestPassingFormView.
    See 56 &lt;https://github.com/macropin/django-registration/pull/56&gt;_.
  • Compatibility: Added support for Django 1.10
  • Bugfix: Pass request object into resend_activation_mail so the email
    template can render the site URL with the correct schema (HTTP, HTTPS).
  • Bugfix: Ensure register method has consistent arguments.
    See 153 &lt;https://github.com/macropin/django-registration/pull/153&gt;_.
  • Enhancement: Add invoke tasks, requirements.txt file, and make wrapper to
    help developers get setup.
    See 154 &lt;https://github.com/macropin/django-registration/pull/154&gt;_.

1.3


  • Add support for Django 1.9. django-registration supports Django 1.7 and newer.
  • Feature: Added resend_activation_mail method to RegistrationManager.
  • Feature: Added support for additional registration forms;
    RegistrationFormTOSAndUniqueEmail and RegistrationFormTOSAndNoFreeEmail.
    See 113 &lt;https://github.com/macropin/django-registration/pull/113&gt;_.
  • Bugfix: Properly extend the base registration template.
  • Enhancement: Re-enable Python 3.3 support.
  • Enhancement: Distinguish between account activation failure and attempted
    reactivation. See 72 &lt;https://github.com/macropin/django-registration/pull/72&gt;_.
  • Bugfix: Install an unzipped package in order to support running migrations.
    See 104 &lt;https://github.com/macropin/django-registration/pull/104&gt;_.
  • Feature: Added Thai, Hungarian, and Russian localizations.
  • Feature: Added support for specifying template paths for activation email.

1.2


  • BACKWARDS-INCOMPATIBLE CHANGE: When overriding the
    registration/activation_email.txt template, you must also now override the
    registration/activation_email.html template or set the setting
    (REGISTRATION_EMAIL_HTML) to False.
  • BACKWARDS-INCOMPATIBLE CHANGE: An initial migration for Django > 1.7 has been
    provided. South users will need to configure a null migration with
    (SOUTH_MIGRATION_MODULES).
  • BACKWARDS-INCOMPATIBLE CHANGE: A base.html template is now assumed to
    exist.
  • Feature: Added support for disabling HTML emails using the setting option
    REGISTRATION_EMAIL_HTML.
  • Feature: Added settings' options that allows to exlude the default auth urls
    (INCLUDE_AUTH_URLS) and register url (INCLUDE_REGISTER_URL).
  • Feature: Added support to dynamically import any chosen registration form
    using the settings option REGISTRATION_FORM.
  • Enhancement: Make RegistrationForm a subclass of Django's
    UserCreationForm
  • Enhancement: Use registration form save method to create user instance,
    whenever form is a subclass of Django's ModelForm.

1.1


This represents the first release of django-registration-redux.
It is based off the defunct v1.0 django-registration abandoned by James Bennett.

  • Compatibility: Added support for Python 3.x.
  • Compatibility: Added support for Django 1.6, 1.7.
  • Feature: Added support for mime/multipart HTML / Text registration
    emails.
  • Feature: Added REGISTRATION_EMAIL_SUBJECT_PREFIX config.
  • Feature: Added support for REGISTRATION_AUTO_LOGIN config.
  • Feature: Added support for SEND_ACTIVATION_EMAIL config.
  • Bugfix: Signal "user_activated" was being sent twice.
  • Bugfix: Fixed broken tests.

The change log below is from the versions maintained
by James Bennett.

1.0


(Taken from release-notes.rst in this release)

  • The 1.0 release of django-registration represents a complete
    rewrite of the previous codebase. For information on upgrading,
    consult :ref:the upgrade guide &lt;upgrade&gt;.
  • The largest overall change is that in place of the monolithic backend
    classes and function-based views found in django-registration 0.8, in
    1.0 all views are class-based. A "backend" now consists of,
    typically, one or two subclasses of :ref:the built-in base views &lt;views&gt;.
  • Implementing these as class-based views allows for far simpler
    configuration and customization, without the overhead involved in
    supporting large numbers of optional keyword arguments to
    function-based views, or the need to provide a separate class-based
    infrastructure for implementing the logic of registration.
  • Notably, this implementation is also completely backwards-compatible
    for users of django-registration 0.8 who simply used the recommended
    default URLConf for one of the supplied backends; those URLConfs exist
    in the same locations, and have been rewritten to point to the
    appropriate class-based views with the appropriate options.

0.8


  • Backend-based rewrite. See docs/upgrade.rst for details.
  • Compatibility through Django 1.4.

0.7


  • Project hosting moved from Google Code to Bitbucket, and from a
    Subversion repository to Mercurial.
  • Added test suite.
  • Full Django 1.0 compatibility.
  • Registration and activation views now accept an extra_context
    argument, identical to the way that argument works in Django's
    generic views.
  • Added a custom management command for cleaning up expired
    registrations; you can now run manage.py cleanupregistration to
    handle this.
  • BACKWARDS-INCOMPATIBLE CHANGE: The "username" field in
    RegistrationForm is now a RegexField.
  • BACKWARDS-INCOMPATIBLE CHANGE: Removed the standalone script for
    deleting expired user registrations; use the new management command
    instead.

0.6


  • Packaged from revision 166 in Subversion.
  • Fixed a multiple-objects exception in
    RegistrationFormUniqueEmail when multiple users already have the
    same email address.
  • Changed the success_url of the register() view to use
    reverse URL resolution.
  • Added an extra_context argument to the register and
    activate views, mimicking its functionality in Django's generic
    views.
  • BACKWARDS-INCOMPATIBLE CHANGE: Switched the admin declaration to be
    compliant with the newforms-admin refactor; the admin declaration
    now lives in registration/admin.py.
  • BACKWARDS-INCOMPATIBLE CHANGE: Switched form imports from using
    django.newforms to using django.forms; the old style now
    raises a deprecation warning on Django trunk and on Django 1.0
    alpha.

0.5


  • Packaged from revision 155 in Subversion.
  • Added Serbian translation.
  • Added Italian translation.
  • Username/email uniqueness checks are now case-insensitive. This is
    potentially backwards-incompatible if you relied on them being
    case-sensitive, but I don't know of any reason why you'd be doing
    that.
  • Included forms now use lazy translations.
  • The register view can now handle files submitted for use in form
    processing.
  • Reactivation of a manually-deactivated account is now prevented by
    changing the activation key, on successful activation, to a dummy
    string which will fail on subsequent activation attempts.

Version 0.4p2, 10 Feburary 2008:

  • Added Brazilian Portuguese translation.
  • Added Japanese translation.
  • Added Hebrew translation.
  • Minor documentation fixes.

Version 0.4p1, 16 December 2007:

  • Packaged from revision 129 in Subversion.
  • Added Polish translation.

0.4


  • Packaged from revision 122 in Subversion.
  • Added Greek translation.
  • Added Russian translation.
  • Changed maxlength to max_length now that Django issues a
    deprecation warning for it.
  • BACKWARDS-INCOMPATIBLE CHANGE: Changed the password validation to be
    on clean() instead of clean_password2(). This means that
    errors from this must be accessed via non_field_errors().

Version 0.3p5, 6 October 2007:

  • Packaged from revision 112 in Subversion.
  • Added German translation.
  • Fixed a mismatch between the default RegistrationForm's maximum
    length on email addresses and the actual maximum length on Django's
    User model.
  • Fixed a situation where bad input for the password1 field on
    RegistrationForm could cause validation of password2 to fail
    with an exception.

Version 0.3p4, 4 October 2007:

  • Packaged from revision 101 in Subversion.
  • BACKWARDS-INCOMPATIBLE CHANGE: In response to larger numbers of
    complaints from people trying to use the example templates as-is,
    the example templates have been removed.

Version 0.3p2, 23 September 2007:

  • Packaged from revision 100 in Subversion.
  • Fixed activate view to actually take the template_name
    argument.

Version 0.3p1, 22 September 2007:

  • Packaged from revision 99 in Subversion.
  • Fixed a typo in docs/overview.txt.
  • Fixed a typo in bin/delete_expired_users.py.
  • Added French translation.

0.3


Packaged from revision 89 in Subversion; download at
http://django-registration.googlecode.com/files/registration-0.3.tar.gz

  • Changed register and activate views to accept
    template_name keyword argument for selecting a custom template.
  • Changed register view to accept form_class keyword
    argument specifying the form to use.
  • BACKWARDS-INCOMPATIBLE CHANGE: Changed
    RegistrationManager.create_inactive_user to use a template for
    the subject of the activation email.
  • BACKWARDS-INCOMPATIBLE CHANGE: Removed the tos field from
    RegistrationForm; if you were relying on it, switch to using
    RegistrationFormTermsOfService instead.
  • BACKWARDS-INCOMPATIBLE CHANGE: The activation email template now
    receives the current Site object as the context variable
    site, and the current_site variable, which only held the
    domain, is no longer available.
  • Added script bin/delete_expired_users.py with instructions on
    how to use it as a cron job to clean up expired/inactive accounts.
  • Marked strings for translation and added locale directory so
    that translations can be added.
  • Updated to deal with merge of Django's Unicode branch into trunk;
    now using Unicode-aware functions everywhere.

0.2


Packaged from revision 76 in Subversion; download at
http://django-registration.googlecode.com/files/registration-0.2.tar.gz

  • Added ability to specify a callback in
    RegistrationManager.create_inactive_user or in the register
    view to enable creation of site-specific user profile.
  • Separated out the logic of creating the profile into a new method on
    RegistrationManager: create_profile.
  • Added URLConf support for various useful views in
    django.contrib.auth.
  • BACKWARDS-INCOMPATIBLE CHANGE: removed the key_generated field
    from RegistrationProfile; activation key expiration is now
    calculated based on the date_joined field in the User model.
    Drop the key_generated column from your database when upgrading
    from 0.1.

0.1


Packaged from revision 56 in Subversion; download at
http://django-registration.googlecode.com/files/registration-0.1.tar.gz

  • First packaged version using distutils.
  • Added docs/ directory and overview.

Got merge conflicts? Close this PR and delete the branch. I'll create a new PR for you.

Happy merging! 🤖

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant