Re: status of 1.8 release blockers

2015-01-15 Thread Tim Graham
I think master is stabilizing and the number of unsolved regressions should be ~0 by tomorrow. I'd like to release the alpha around 2100 UTC tomorrow +/- ~4 hours depending on how things go with the remaining issues. Let me know if there is anything you think needs to be in the alpha that wouldn

Django template coverage experiment

2015-01-15 Thread Ned Batchelder
Hi, I've added support to coverage.py for plugins to support non-Python files, and I've written a plugin to measure Django templates. I'm looking for a collaborator to decide how to complete the work. I'm asking on the dev list because ideally, the plugin would be part of Django itself, alt

Re: permissions and groups data migration

2015-01-15 Thread Luis-José Torres
Hi, This worked for me: from django.apps.registry import apps as apps_alt from django.contrib.auth.management import create_permissions for app_config in apps_alt.get_app_configs(): create_permissions(app_config) On Tuesday, December 30, 2014 at 11:01:11 PM UTC-6, Adam Venturella wrote:

Re: Can't login after upgrading to 1.7.3, and workaround

2015-01-15 Thread Horacio G. de Oro
On Thursday, January 15, 2015 at 6:03:40 AM UTC-3, Nic West wrote: > > Authenticated returns a user instance assumably with the correct hash why > not do some thing like: > > authenticated_user.count = 0 > authenticated_user.save() Yes, I implemented that fix last night, but I really like the

Re: Can't login after upgrading to 1.7.3, and workaround

2015-01-15 Thread Nic West
Authenticated returns a user instance assumably with the correct hash why not do some thing like: authenticated_user.count = 0 authenticated_user.save() -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To

Re: Can't login after upgrading to 1.7.3, and workaround

2015-01-15 Thread James Bennett
On Thu, Jan 15, 2015 at 12:05 AM, Horacio G. de Oro wrote: > If you see the new hash in the database, I think that, maybe the admin, is > saving the user instance with the new hash. And doing that, ie: save()'ing > the user returned by authenticate() solved the issue for me too (but I > don't wan