Bug#806182: Will fix python-django-registration RCs shortly (Was: Re: Request to join DPMT && python-django-registration)
Hi James, On Mi, 2016-01-06 at 07:13 -0600, James Bennett wrote: > Stephan Sürken wrote: > > Let's see if I got this right: > > > > django-registration is actually no longer discontinued, and now lives at > > > > https://github.com/ubernostrum/django-registration > > > > The (incompatible) *-redux fork lives at > > > > https://github.com/macropin/django-registration > > Yes. django-registration upstream has been revived and the latest > release of it (on PyPI as django-registration 2.0.3) is compatible with > Django 1.7 and 1.8, on any Python version supported by those versions of great! This does really simplify matters; so I will start integrating 2.0.3 first (and see, then, where it goes in respect to django 1.9). The *-redux fork should imho be packaged separately as alternative by any interested third party ;). Thx, S
Bug#806182: Will fix python-django-registration RCs shortly (Was: Re: Request to join DPMT && python-django-registration)
Hi list, interested parties, On Mi, 2015-11-11 at 16:39 +0100, Stephan Sürken wrote: > I would like to join the DPM Team. I am a DD, my user name on alioth is > "absurd" (and yes, I read the policy document and I am aware of the git > move ;). seems I am still not in the official members list https://alioth.debian.org/projects/python-modules/ but maybe I am just not getting something ;). So anyway, this is to avoid maybe ongoing duplicate work. If no one objects, I will... > As first urgent quest I would like to fix the RC django 1.8 (I already > did some work on that package for some time before it was moved to the > DPMT). ...update the package shortly (i.e., within this week). This will focus on minimal changes to make it work with django 1.8+. > As for p-d-r in general: Has there been any discussion here already > if/how to package 'p-d-r-redux' (which seems to be a (still maintained) > fork)? As we now have #806182, I am hoping for some discussion/advice there how to exactly handle this in the future (I have not looked into *-redux at all yet). So the 1st question for me is whether it's really a drop-in replacement, or if we might, at this point, create a new package *-redux (maybe with the option to fix #567739, too). Thx for any advice on this! S signature.asc Description: This is a digitally signed message part
Bug#806182: Will fix python-django-registration RCs shortly (Was: Re: Request to join DPMT && python-django-registration)
Stephan Sürken wrote: > Let's see if I got this right: > > django-registration is actually no longer discontinued, and now lives at > > https://github.com/ubernostrum/django-registration > > The (incompatible) *-redux fork lives at > > https://github.com/macropin/django-registration Yes. django-registration upstream has been revived and the latest release of it (on PyPI as django-registration 2.0.3) is compatible with Django 1.7 and 1.8, on any Python version supported by those versions of Django. It also has a feature or two added. Probably within a week there will also be django-registration 2.1, compatible with Django 1.8 and 1.9 and some more new stuff in it. There is an upgrade guide in django-registration's documentation for coming from older versions of django-registration (0.8 or 1.0): https://django-registration.readthedocs.org/en/2.0.3/upgrade.html My advice, personally, would be to target the current master branch of django-registration (which will become the 2.1 release very soon). There's a bugfix related to Django making the email field optional, and a workaround for a performance bug in the 1.9 release of Django, both of which are probably worth having (and the one new feature coming in django-registration 2.1 -- checking usernames against a list of reserved names -- can be turned off if needed for compatibility).
Bug#806182: Will fix python-django-registration RCs shortly (Was: Re: Request to join DPMT && python-django-registration)
Hi James, On Mi, 2016-01-06 at 06:23 -0600, James Bennett wrote: (...) > > So the 1st question for me is whether it's really a drop-in replacement, > > or if we might, at this point, create a new package *-redux (maybe with > > the option to fix #567739, too). > > -redux is not a drop-in replacement. However, upstream > django-registration is 1.8 compatible as of the current release on PyPI, > and is about to gain a 1.9-compatible release as well. So please make > sure to check on what's happening in upstream before you duplicate the > work already done there: > > https://github.com/ubernostrum/django-registration ahh, thanks James, I guess now I understand your previous comment ;). Let's see if I got this right: django-registration is actually no longer discontinued, and now lives at https://github.com/ubernostrum/django-registration The (incompatible) *-redux fork lives at https://github.com/macropin/django-registration Thx! S signature.asc Description: This is a digitally signed message part
Bug#806182: Will fix python-django-registration RCs shortly (Was: Re: Request to join DPMT && python-django-registration)
Stephan Sürken wrote: >> As for p-d-r in general: Has there been any discussion here already >> if/how to package 'p-d-r-redux' (which seems to be a (still maintained) >> fork)? > > As we now have #806182, I am hoping for some discussion/advice there how > to exactly handle this in the future (I have not looked into *-redux at > all yet). > > So the 1st question for me is whether it's really a drop-in replacement, > or if we might, at this point, create a new package *-redux (maybe with > the option to fix #567739, too). -redux is not a drop-in replacement. However, upstream django-registration is 1.8 compatible as of the current release on PyPI, and is about to gain a 1.9-compatible release as well. So please make sure to check on what's happening in upstream before you duplicate the work already done there: https://github.com/ubernostrum/django-registration
