date:20140429

Re: [Django] #22544: Error happened when I use LiveServerTestCase to test static file

2014-04-29 Thread Django

#22544: Error happened when I use LiveServerTestCase to test static file
---+--
 Reporter:  lifeng |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by lifeng):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Sorry, I forgot my environment, it's python3.3, django1.7.2.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ee4e0eec75567d51f30faac0c54e2656%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22544: Error happened when I use LiveServerTestCase to test static file

2014-04-29 Thread Django

#22544: Error happened when I use LiveServerTestCase to test static file
---+
 Reporter:  lifeng |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Testing framework  |Version:  1.7-beta-2
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 I know I should use StaticLiveServerCase to test static file, and when I
 use it, everything is OK. But when I use LiveServerTestCase to test static
 file, some error occurred. Bellow is the error message:


 {{{

 TypeError: unsupported operand type(s) for +=: 'NoneType' and 'str'
 .Traceback (most recent call last):
   File "/usr/lib/python3.3/wsgiref/handlers.py", line 137, in run
 self.result = application(self.environ, self.start_response)
   File "/home/lf/.virtualenvs/django1.7/lib/python3.3/site-
 packages/django/test/testcases.py", line 1011, in __call__
 return super(FSFilesHandler, self).__call__(environ, start_response)
   File "/home/lf/.virtualenvs/django1.7/lib/python3.3/site-
 packages/django/core/handlers/wsgi.py", line 187, in __call__
 response = self.get_response(request)
   File "/home/lf/.virtualenvs/django1.7/lib/python3.3/site-
 packages/django/test/testcases.py", line 994, in get_response
 return self.serve(request)
   File "/home/lf/.virtualenvs/django1.7/lib/python3.3/site-
 packages/django/test/testcases.py", line 1006, in serve
 return serve(request, final_rel_path,
 document_root=self.get_base_dir())
   File "/home/lf/.virtualenvs/django1.7/lib/python3.3/site-
 packages/django/views/static.py", line 50, in serve
 fullpath = os.path.join(document_root, newpath)
   File "/home/lf/.virtualenvs/django1.7/lib/python3.3/posixpath.py", line
 83, in join
 path += b

 }}}

 The document_root is None, Is there anything wrong in
 
[https://github.com/django/django/blob/stable/1.7.x/django/test/testcases.py#L993]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/049.869b4f814f775a7194c2ed96b9d96237%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21461: Add pre_update and post_update signals

2014-04-29 Thread Django

#21461: Add pre_update and post_update signals
-+-
 Reporter:  loic84   |Owner:  loic84
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by bendavis78):

 I would love to have an update signal for the purpose of cache
 invalidation. Currently I use save/delete signals to detect when something
 has changed to update an expensive calculation. While `pk_set` idea solves
 some problems, it's not ideal for large result sets and has unpredictable
 consequences.

 For example, let's say I don't care about the primary keys of objects that
 were updated, but rather the objects related to those that were updated. I
 could run a much less expensive query by doing, for example,
 `queryset.distinct().values_list('related_id')`.

 Personally I feel it's better to allow the user be explicit in what is
 passed around. I would propose that `pre_update` accept the queryset, and
 users have the option to return a dict of extra data that will be
 available to `post_update` receivers. For example:

 {{{
 #!python
 @receiver(pre_update, sender=MyModel)
 def on_pre_update(sender, update_fields, queryset, **kwargs):
 return {
 'related_pks': queryset.distinct().values_list('relatedmodel_id')
 }

 @receiver(post_update, sender=MyModel)
 def on_post_update(sender, update_feilds, extra_data, **kwargs):
 related_pks = extra_data.get('related_pks', [])
 for obj in RelatedModel.objects.filter(pk__in=related_pks):
 obj.do_something()
 }}}

 The implementation if `QuerySet.update()` would look like this:

 {{{
 #!python
 def update(self, **kwargs):
   """
   Updates all elements in the current QuerySet, setting all the given
   fields to the appropriate values.
   """
   assert self.query.can_filter(), \
   "Cannot update a query once a slice has been taken."
   meta = self.model._meta
   self._for_write = True
   query = self.query.clone(sql.UpdateQuery)
   query.add_update_values(kwargs)
   extra_data = {}
   if not meta.auto_created:
   responses = signals.pre_update.send(
   sender=self.model, update_fields=kwargs, queryset=self,
   using=self.db)
   for rcvr, response in responses:
   extra_data.update(response)
   with transaction.atomic(using=self.db, savepoint=False):
   rows = query.get_compiler(self.db).execute_sql(CURSOR)
   self._result_cache = None
   if not meta.auto_created:
   signals.post_update.send(
   sender=self.model, update_fields=kwargs,
   extra_data=extra_data, using=self.db)
   return rows
 }}}

 It's a bit cleaner and addresses any performance concerns, as well as the
 issue with updated pks. Regarding comment:10, I think there use cases for
 both `pre_update` and `post_update`, either together or alone.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.349ea9f5b669f8c550f2cec0a2264892%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22502: Datetime fields break empty form validation on first attempt (but not second)

2014-04-29 Thread Django

#22502: Datetime fields break empty form validation on first attempt (but not
second)
--+-
 Reporter:  melinath  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Someday/Maybe
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+-

Comment (by melinath):

 ... or maybe we should have consistent handling of milliseconds. This
 problem would be resolved if we were either using datetime form fields
 that displayed millisecond data or if we didn't include millisecond data
 in default values.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.0db668c125f5893e61396ecf72256238%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22411: Migrations attempt to create content types without first running contenttypes sync/migrations

2014-04-29 Thread Django

#22411: Migrations attempt to create content types without first running
contenttypes sync/migrations
+--
 Reporter:  melinath|Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-beta-1
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by melinath):

 One option would be to always have a dependency on contenttypes in initial
 migrations:

 {{{
 dependencies = [
 ('contenttypes', '__first__'),
 ]
 }}}

 Untested, but I think it would work.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.85a318e224b9e936654b1c05e41da3d2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-04-29 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by melinath):

 Workaround for contenttypes (as described in #22518) is to make your
 dependencies look like this:

 {{{
 dependencies = [
 ('contenttypes', '__first__'),
 ('myapp', '0001_initial'),
 ]
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.a6cbfb30277c719f2f4db0be443c1481%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22420: Postgresql connections not being dropped between tests?

2014-04-29 Thread Django

Comment (by anonymous):

Replying to [comment:6 timo]:
> Any chance you could provide a minimal test project that reproduces the
issue?
>
> Also you said, "A successful test run or a test run that produces error
results will not produce the issue." but the example in the description
doesn't appear to have any failures?

Good points. I just tried again with a forced failure and an error. Now of
course it appears to be reproducing in all 3 cases. (Fail, Error, Pass).
Bah. I will try to get a GitHub project together and post back here.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.ef5c92eb4cb7bdc9b4c3090ae6851f21%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22534: Checks fail on non-swappable ForeignKeys when the related model is swapped out

2014-04-29 Thread Django

Comment (by bendavis78):

For reference, the swappable keyword was originally proposed here:
https://groups.google.com/forum/#!msg/django-
developers/arSS604xc6U/24j1vKtlESoJ

Although, it was not implemented as proposed. Russel suggested that the
`swappable` keyword default to `None`, as we can safely assume that when
the "to" model is not a string, it should point to the original. If `to`
is a string that points to a swappable model, we would assume that it
should point to the swapped model. Any other case would be an edge case,
and can be controlled explicitly by setting the keyword to either `True`
or `False`.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.8afe74510dcc1fca347fa1fc98463aea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21638: Infinite migrations when using AUTH_USER_MODEL

2014-04-29 Thread Django

#21638: Infinite migrations when using AUTH_USER_MODEL
-+-
 Reporter:  patrick@…|Owner:  Andrew
 Type:  Bug  |  Godwin 
Component:  Migrations   |   Status:  new
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by timo):

 I cannot reproduce with the provided information due to `ValueError:
 Lookup failed for model referenced by field polls.User.groups: auth.Group`
 when running `makemigrations` a second time, which I believe is #22485. I
 will leave this ticket open so we can check this after that is fixed.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/088.04efa2de43820c5896186996829747c1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22051: Running `makemigrations` twice in a row fails

2014-04-29 Thread Django

#22051: Running `makemigrations` twice in a row fails
-+
 Reporter:  bmispelon|Owner:  andrewgodwin
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by drackett@…):

 thanks l.a.evil.genius, the user fix did it for me.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.efe1a4ebf0cd09e596f6718e2080e14d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9602: Add admin.site._registry manipulation methods

2014-04-29 Thread Django

#9602: Add admin.site._registry manipulation methods
-+-
 Reporter:  robhudson|Owner:  anonymous
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  register modeladmin  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * needs_docs:  1 => 0
 * has_patch:  1 => 0
 * version:  1.0 => master
 * easy:  1 => 0
 * needs_tests:  1 => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.6b4b1216f352b586dcd07c4905418572%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22420: Postgresql connections not being dropped between tests?

2014-04-29 Thread Django

#22420: Postgresql connections not being dropped between tests?
---+--
 Reporter:  bacongobbler   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timo):

 Any chance you could provide a minimal test project that reproduces the
 issue?

 Also you said, "A successful test run or a test run that produces error
 results will not produce the issue." but the example in the description
 doesn't appear to have any failures?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.1294070e5adb66bc7dc4bb04e6b8a975%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22427: _session_cache of SessionBase affected by database session engine save

2014-04-29 Thread Django

#22427: _session_cache of SessionBase affected by database session engine save
-+-
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.sessions |  Version:  1.6
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  session dict | Triage Stage:
  disappear middleware save  |  Unreviewed
  database   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * status:  new => closed
 * resolution:   => needsinfo


Comment:

 I am going to close this as needsinfo for now as I am not sure we'll be
 able to reproduce this given the details so far. If you can provide a
 minimal project that reproduces the issue that would be helpful.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f1b9c2e5532ee163d66d36adeba5268b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22396: Admin AllValuesFieldListFilter not respecting ModelAdmin.get_queryset

2014-04-29 Thread Django

#22396: Admin AllValuesFieldListFilter not respecting ModelAdmin.get_queryset
---+--
 Reporter:  serialx.net@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

 * status:  new => closed
 * resolution:   => needsinfo


Comment:

 The proposed patch breaks some `admin_view` tests. Please reopen if you
 can provide more details and a patch that doesn't break tests. Thanks!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/079.4b05aacb7525821f4bcb24edfbe94107%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22527: FK proxy model not properly deferred in syncdb

2014-04-29 Thread Django

#22527: FK proxy model not properly deferred in syncdb
-+-
 Reporter:  leftmoose|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  proxy model, |  Needs documentation:  0
  constraints|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * cc: timo (added)
 * needs_better_patch:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.73b5c2c8f9049bccf30a1d8dbe018bde%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22534: Checks fail on non-swappable ForeignKeys when the related model is swapped out

2014-04-29 Thread Django

#22534: Checks fail on non-swappable ForeignKeys when the related model is 
swapped
out
-+--
 Reporter:  bendavis78   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7-beta-2
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--
Changes (by timo):

 * needs_better_patch:   => 0
 * version:  master => 1.7-beta-2
 * stage:  Unreviewed => Accepted
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Haven't completely verified this, but I don't see any tests for
 `swappable=False` in c9de1b4a55713ad1557f8c40621226253038f665.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.3fdaf2d2505f62dbcfd66dbf6c883b38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22520: CircularDependencyError when there's a foreign key to a model with PermissionsMixin

2014-04-29 Thread Django

#22520: CircularDependencyError when there's a foreign key to a model with
PermissionsMixin
---+--
 Reporter:  Naddiseo   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Migrations |  Version:  1.7-beta-2
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timo):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 It seems like it's probably a duplicate of #22325.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.ba2f810d746fab99db7ad892c84a5e1a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22542: Migrations introduce circular dependency on custom user model

2014-04-29 Thread Django

#22542: Migrations introduce circular dependency on custom user model
+--
 Reporter:  hoha@…  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.7-beta-2
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by timo):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Duplicate of #22325

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.4a2345260f573d9084c0dc34182f9a51%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22543: Add pre_update and post_update signal for querysets

2014-04-29 Thread Django

#22543: Add pre_update and post_update signal for querysets
-+-
 Reporter:  bendavis78   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  queryset update  |  Unreviewed
  signals|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * resolution:  duplicate => wontfix


Comment:

 Seems this is similar to #17824 which was won't fixed. Needs discussion on
 the django-developers mailing list in order to be accepted.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.ec893b66d3dba2ca5a99fc5731e3db16%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22543: Add pre_update and post_update signal for querysets

2014-04-29 Thread Django

#22543: Add pre_update and post_update signal for querysets
-+-
 Reporter:  bendavis78   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  queryset update  |  Unreviewed
  signals|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by loic84):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 Hi @bendavis78, this feature is discussed at #21461.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.4df2f55f2a035cc36696c0105ebed9d6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22543: Add pre_update and post_update signal for querysets

2014-04-29 Thread Django

#22543: Add pre_update and post_update signal for querysets
--+
 Reporter:  bendavis78|  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:  queryset
 Triage Stage:  Unreviewed|  update signals
Easy pickings:  0 |  Has patch:  0
  |  UI/UX:  0
--+
 One use case for this would be cache coherence. For example, let's say
 we're caching an expensive operation based on a model pk, and we want to
 invalidate that cache when a row is changed in any way. Currently we can
 only do this with save/delete signals. Consider the following example for
 calculating points awarded to an account:

 {{{
 #!python
 def get_points_earned(account):
 key = 'acct-{0}-points'.format(account.id)
 if not cache.get(key):
 point_awards = PointAward.objects.filter(account=account)
 points = point_awards.aggregate(total=Sum('points'))['total']
 cache.set(key, points)
 return cache.get(key)

 # Invalidate points earned if a PointAward is added/changed/deleted
 @receiver([post_save, post_delete, post_update], sender=PointAward)
 def on_point_award_changed(sender, **kwargs):
 instance = kwargs.get('instance')
 if instance:
 key = 'acct-{0}-points'.format(instance.id)
 cache.delete(key)
 }}}

 With this coherence strategy, a call to `PointAward.objects.update()` will
 cause the cache to become incoherent, and will cause errors in the
 calculation.

  This can easily be addressed by providing a signal allowing a developer
 to decide how best to update the cache when `update()` is called:

 {{{
 #!python
 # django/db/models/signals.py

 pre_update = ModelSignal(providing_args=["queryset", "values", "using"],
 use_caching=True)
 post_update = ModelSignal(providing_args=["queryset", "values", "using"],
 use_caching=True)
 }}}

 We can now update our receiver to also respond to updates as well as
 changes and deletions:

 {{{
 #!python

 @receiver([post_save, post_delete], sender=PointAward)
 def on_point_award_changed(sender, **kwargs):
 point_award = kwargs.get('instance')
 if instance and instance.pk:
 # this is a save/delete, invalidate the related account's points
 account_id = point_award.account_id
 key = 'acct-{0}-points'.format(instance.id)
 cache.delete(key)

 elif kwargs.get('queryset'):
 # this is an update, invalidate all matching accounts
 qs = kwargs['queryset']
 for acct_id in qs.objects.distinct().values_list('account_id',
 flat=True)
 key = 'acct-{0}-points'.format(acct_id)
 cache.delete(key)
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.f75b440195931432e2c1d8b773d94c17%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-04-29 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by chockey):

 * cc: chockey (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.6701af2d1aa0028d4a18341c9fb79aa4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22542: Migrations introduce circular dependency on custom user model

2014-04-29 Thread Django

#22542: Migrations introduce circular dependency on custom user model
+
 Reporter:  hoha@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7-beta-2
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 It appears that a custom user model which inherits from another model
 which has foreign keys to the user model, will fail when the migration is
 run, due to a circular dependency. This code works just fine under Django
 1.6 syncdb or South for that matter. The code fails both when the base
 class is abstract and if not (making it abstract produces an extra
 migration file though).

 Attached is a model file with a custom user model implemented (and set as
 the AUTH_MODEL in settings).

 When makemigrations is run, three migrations are created. Upon appliance
 it fails with the following traceback:
 {{{
 Traceback (most recent call last):
   File "./manage.py", line 10, in 
 execute_from_command_line(sys.argv)
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 427, in
 execute_from_command_line
 utility.execute()
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/core/management/__init__.py", line 419, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/core/management/base.py", line 288, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/core/management/base.py", line 337, in execute
 output = self.handle(*args, **options)
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/core/management/commands/migrate.py", line 103, in handle
 plan = executor.migration_plan(targets)
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/db/migrations/executor.py", line 36, in migration_plan
 backwards_plan = self.loader.graph.backwards_plan(target)[:-1]
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/db/migrations/graph.py", line 64, in backwards_plan
 return self.dfs(node, lambda x: self.dependents.get(x, set()))
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/db/migrations/graph.py", line 119, in dfs
 return _dfs(start, get_children, [])
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/db/migrations/graph.py", line 111, in _dfs
 results = _dfs(n, get_children, path) + results
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/db/migrations/graph.py", line 111, in _dfs
 results = _dfs(n, get_children, path) + results
   File "/Users/henrik/dj17b3/venv/lib/python3.4/site-
 packages/django/db/migrations/graph.py", line 103, in _dfs
 raise CircularDependencyError(path[path.index(start):] + [start])
 django.db.migrations.graph.CircularDependencyError: [('accounts',
 '0001_initial'), ('accounts', '0001_initial')]
 }}}

 Tested in Django 1.7b3 (not available to choose in the version list).
 Personally I'd consider this a release blocker; the functionality worked
 as expected in Django 1.6. I will let you guys decide on the severity
 though, obviously.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/060.ff7479683d7172f09d292ae7b44b65b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22510: Form fields cannot have names that are present as attributes on the form

2014-04-29 Thread Django

Comment (by anonymous):

Replying to [comment:9 mjtamlyn]:
> I am strongly in favour of loic's option number 1 - change no code and
document the problems with naming fields after things which would be on
the form anyway. In the spirit of the fix for #8620 (making forms behave
more like "normal" python objects), this makes sense anyway.

This is, in no way similar to how normal python objects behave. In
particular, normal Python objects do not silently discard attributes you
put on the class definition. Also, normal objects, as you mention, do not
magic attributes into `__getitem__()` stuff.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.8b90ab4845fedadcfef637adf3c456e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-04-29 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mesemus):

 * cc: miroslav.simek@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.66c5b271c18bc17b57f0239739b49bfc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22510: Form fields cannot have names that are present as attributes on the form

2014-04-29 Thread Django

* component: Forms => Documentation

Comment:

I am strongly in favour of loic's option number 1 - change no code and
document the problems with naming fields after things which would be on
the form anyway. In the spirit of the fix for #8620 (making forms behave
more like "normal" python objects), this makes sense anyway.

As a side note, it would be much more incompatible (but imo better) to not
remove the field definitions from the form object at all - i.e.
`MyForm().foo == MyForm['foo']`. This may have serious implications for
the use of forms in DTL though. However, it would potentially give us the
option of using the metaclass simply to define fields after the class is
resolved normally by python. This is likely a step too far.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.fce9162b44ff2cc925d1b19d385fb593%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22431: TestCase swallows IntegrityError when creating object with invalid foreign key

2014-04-29 Thread Django

* component: Database layer (models, ORM) => Documentation
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted

Comment:

I would guess switching to immediate constraint checking would have a
performance penalty. It doesn't seem worth it for the majority of cases so
I'd be in favor of simply documenting this. If you want to try to work up
a patch otherwise, we can of course take a look.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.999c83a6263bb31fba2b793043abdb24%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22491: TestCase + select_for_update()

2014-04-29 Thread Django

#22491: TestCase + select_for_update()
-+-
 Reporter:  andreas_pelme|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 Accepting at least the documentation route if it's not feasible.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.f377977e98ecf670f6e1782a6d525521%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22416: Migrate can't create ManyToManyField for Model wigrated in the same run

2014-04-29 Thread Django

#22416: Migrate can't create ManyToManyField for Model wigrated in the same run
-+-
 Reporter:  roughdesignapps@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:
Component:  Migrations   |  1.7-alpha-2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * stage:  Unreviewed => Accepted


Comment:

 This might be a duplicate of some other ticket, but it's difficult to say.
 A minimal project (or ideally a test for Django's test suite) would be
 really helpful.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/083.fa8f9f99eb58397c397cf347c7d14e0f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-04-29 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by mjrohr330@…):

 * cc: mjrohr330@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.8f52991f9dbb5f8156bcc1d52bc5d998%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22438: Slow INNER JOIN in MySQL can be fixed in Django ORM, but should it?

2014-04-29 Thread Django

#22438: Slow INNER JOIN in MySQL can be fixed in Django ORM, but should it?
-+-
 Reporter:  frol |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  mysql, orm, slow |  Unreviewed
  query, join|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 I'm not sure, but I found http://stackoverflow.com/a/516720 which
 indicates this change may not be a good idea. Could you reopen the ticket
 if you have information suggesting otherwise? If you still think the
 change is a good one, it would probably be a good topic to bring up on the
 django-developers mailing list.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.22802a89942408f1cfecc2a8a5116e10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22540: .save() called in multiple "creation" queryset functions

2014-04-29 Thread Django

#22540: .save() called in multiple "creation" queryset functions
-+-
 Reporter:  craig.labenz@…   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  creation |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * easy:  1 => 0
 * stage:  Unreviewed => Accepted


Comment:

 Looking at the code briefly I think it might be possible.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/080.6acc5a3563e94fb88195e99e0a1ddc08%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22480: "django-admin.py dumpdata" - unable to serialize

2014-04-29 Thread Django

#22480: "django-admin.py dumpdata" - unable to serialize
---+--
 Reporter:  yn |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timo):

 I have been unable to reproduce this error, but could you try `python
 manage.py ...`?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/060.023cdf3ff176c1de229840c28009551c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12500: Support for MySQL Connector/Python

2014-04-29 Thread Django

#12500: Support for MySQL Connector/Python
-+-
 Reporter:  geertjanvdk  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.1
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  backend mysql|  Someday/Maybe
  myconnpy   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by timo):

 #22370 details a failing test with the connector (unclear to me if the
 problem is ours or theirs).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.ff969df41de78251ce5e2d5171a42e8e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22370: Mysql TimeZone problems

2014-04-29 Thread Django

#22370: Mysql TimeZone problems
-+-
 Reporter:  info@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  Mysql Timezone SQL   |  Unreviewed
  generation |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anonymous):

 * status:  new => closed
 * resolution:   => duplicate


Comment:

 I can reproduce the test failure of
 `datetimes.tests.DateTimesTests.test_21432` on Django 1.6 with
 Connector/Python 1.1.6. Not sure if the bug is in our code or the
 connector, but in any case, I'm going to mark this as a duplicate of
 #12500.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.8db4ebe9d18006ec9f14ef094a384a95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22523: Clarify pytz requirement for time zone support

2014-04-29 Thread Django

#22523: Clarify pytz requirement for time zone support
-+-
 Reporter:  z|Owner:  timo
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  unique_for_date, |  Needs documentation:  0
  UnicodeDecodeError |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by aaugustin):

 Yes, but other parts of Django may depend or not on pytz depending on your
 database backend. For instance PostgreSQL on Linux almost works without
 pytz.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/059.8207f9eb656476e2a96ee457b29f5fdc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-04-29 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by andrewsg):

 * cc: andrewsg (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.cfde1967a169e3f29123a0d1a595f9df%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22541: Missing space character in Dutch translation

2014-04-29 Thread Django

#22541: Missing space character in Dutch translation
--+--
 Reporter:  pdewacht  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Translations  |  Version:  1.6
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--

Comment (by charettes):

 You'll need to create an account and send a request to join the Dutch
 translator team. From there you should be able to suggest a correction.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.4ea076164a4e40831e8874b41cb11245%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22541: Missing space character in Dutch translation

2014-04-29 Thread Django

#22541: Missing space character in Dutch translation
--+--
 Reporter:  pdewacht  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Translations  |  Version:  1.6
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--

Comment (by pdewacht):

 I've been to that site before, but I can't figure out how to submit
 anything there.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.090da680b52d18c434ff252d1cdc1c93%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22541: Missing space character in Dutch translation

2014-04-29 Thread Django

#22541: Missing space character in Dutch translation
--+--
 Reporter:  pdewacht  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Translations  |  Version:  1.6
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by charettes):

 * status:  new => closed
 * needs_docs:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 Hi pdewacht, you'll need to
 
[https://docs.djangoproject.com/en/dev/internals/contributing/localizing/#translations
 submit your change through Transifex instead]. Here's the
 [https://www.transifex.com/projects/p/django/language/nl/ Dutch project
 page].

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.d61c85cfa319404272102320ced4329d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19272: gettext_lazy returns "unexpected type"

2014-04-29 Thread Django

#19272: gettext_lazy returns "unexpected type"
-+-
 Reporter:  tyrion   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Translations |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by charettes):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Please don't re-open a ticket that has been closed and fixed (the reported
 issue here is about `gettext_lazy`).

 Open a new ticket that refers to this one for the `pgettext_lazy` issue by
 making sure to use formatting (wrap your code between `{{{` and `}}}`).

 You can go ahead and mark the ticket as an accepted bug from the beginning
 since I managed to reproduce with you provided test case.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.6b1e4316cce853512bf7f8a045464d83%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22046: unhelpful queryset handling for model formsets with data

2014-04-29 Thread Django

#22046: unhelpful queryset handling for model formsets with data
+
 Reporter:  Jim Bailey  |Owner:
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by hershbergien):

 * owner:  hershbergien =>
 * status:  assigned => new


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.31a7e92ecc79d6a786dd5edc71d397a0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22539: Model.full_clean() mutates exclude argument

2014-04-29 Thread Django

#22539: Model.full_clean() mutates exclude argument
-+-
 Reporter:  maggotfish@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by charettes):

 Yes please, go ahead and make sure to include tests and link the PR to
 this Trac issue.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.8394541c8e48c24e902f9843137ade62%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22447: Migrations have bases=(NewBase, ) for models with custom metaclass

2014-04-29 Thread Django

#22447: Migrations have bases=(NewBase,) for models with custom metaclass
-+-
 Reporter:  cdestigter   |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Simon Charette ):

 In [changeset:"cda5745df0e9301c65e13f552ee19a4bf0490997"]:
 {{{
 #!CommitTicketReference repository=""
 revision="cda5745df0e9301c65e13f552ee19a4bf0490997"
 [1.7.x] Fixed #22447 -- Make sure custom model bases can be migrated.

 Thanks to cdestigter for the report.

 Backport of 390f888745 from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.edbd2c887d2ed8e9f1fc2e4812762fb2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] f02f20: [1.7.x] Use the new implementation of `six.with_me...

2014-04-29 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: f02f20a7395fe6681cfcae1c52d4bab68f6aa0d5
  
https://github.com/django/django/commit/f02f20a7395fe6681cfcae1c52d4bab68f6aa0d5
  Author: Simon Charette 
  Date:   2014-04-29 (Tue, 29 Apr 2014)

  Changed paths:
M django/db/models/base.py
M django/utils/six.py

  Log Message:
  ---
  [1.7.x] Use the new implementation of `six.with_metaclass`.

No more `NewBase` horrors.

Thanks to bendavis78 for his work on merging this into six.

Backport of a2340ac6d6 from master


  Commit: cda5745df0e9301c65e13f552ee19a4bf0490997
  
https://github.com/django/django/commit/cda5745df0e9301c65e13f552ee19a4bf0490997
  Author: Simon Charette 
  Date:   2014-04-29 (Tue, 29 Apr 2014)

  Changed paths:
M tests/migrations/models.py
M tests/migrations/test_state.py

  Log Message:
  ---
  [1.7.x] Fixed #22447 -- Make sure custom model bases can be migrated.

Thanks to cdestigter for the report.

Backport of 390f888745 from master


Compare: https://github.com/django/django/compare/62bbfba3aa96...cda5745df0e9

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/535fbd7f98b08_4ccdc89d441004e3%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22046: unhelpful queryset handling for model formsets with data

2014-04-29 Thread Django

#22046: unhelpful queryset handling for model formsets with data
+
 Reporter:  Jim Bailey  |Owner:  hershbergien
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+

Comment (by hershbergien):

 Jim,

 This is my mistake. The data section for my test should have been:

 {{{
 data = {
 'form-TOTAL_FORMS': 2,
 'form-INITIAL_FORMS': 2,
 'form-MAX_NUM_FORMS': 2,
 'form-0-id': '3',
 'form-0-name': 'e',  # this should have been e, not c
 'form-1-id': '4',
 'form-1-name': 'g',
 }
 }}}

 I will update and check again.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.624009f33a5bbe2a506c0b52a0446370%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22523: Clarify pytz requirement for time zone support

2014-04-29 Thread Django

Comment (by z):

Thanks! By the way, I got to the bottom of this. Django's ''timezone.py''
uses standard ''time'' module in python (when pytz is unavailable), and in
particular it uses '''"time.tzname"'''. And in windows using
'''time.tzname''' is unreliable, because it acquires time zone names from
the registry and apparently

{{{
Microsoft stores the the name of the time zone as displayed in the dialog
box where you change time zones ...
that value will be translated into the language of the installed Windows.
}}}

So this stuff "\xcc\xee\xf1\xea\xee\xe2\xf1\xea\xee\xe5
\xe2\xf0\xe5\xec\xff (\xe7\xe8\xec\xe0) \" is the name of the time zone,
the value of '''time.tzname'''.

So in fact it doesn't depend on the database backend.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/059.604af3ecd41c4a30516214189ed085b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22447: Migrations have bases=(NewBase, ) for models with custom metaclass

2014-04-29 Thread Django

#22447: Migrations have bases=(NewBase,) for models with custom metaclass
-+-
 Reporter:  cdestigter   |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Migrations   |  Version:
 Severity:  Release blocker  |  1.7-beta-1
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Simon Charette ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"390f888745803a2f6c75c5a22402daf1221f8e29"]:
 {{{
 #!CommitTicketReference repository=""
 revision="390f888745803a2f6c75c5a22402daf1221f8e29"
 Fixed #22447 -- Make sure custom model bases can be migrated.

 Thanks to cdestigter for the report.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.cdb352f98d148da95010da77b237a837%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] a2340a: Use the new implementation of `six.with_metaclass`...

2014-04-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a2340ac6d6b7e31c7e97e8fdaf3e1d73e43b24ba
  
https://github.com/django/django/commit/a2340ac6d6b7e31c7e97e8fdaf3e1d73e43b24ba
  Author: Simon Charette 
  Date:   2014-04-29 (Tue, 29 Apr 2014)

  Changed paths:
M django/db/models/base.py
M django/utils/six.py

  Log Message:
  ---
  Use the new implementation of `six.with_metaclass`.

No more `NewBase` horrors.

Thanks to bendavis78 for his work on merging this into six.


  Commit: 390f888745803a2f6c75c5a22402daf1221f8e29
  
https://github.com/django/django/commit/390f888745803a2f6c75c5a22402daf1221f8e29
  Author: Simon Charette 
  Date:   2014-04-29 (Tue, 29 Apr 2014)

  Changed paths:
M tests/migrations/models.py
M tests/migrations/test_state.py

  Log Message:
  ---
  Fixed #22447 -- Make sure custom model bases can be migrated.

Thanks to cdestigter for the report.


Compare: https://github.com/django/django/compare/2df7238512ec...390f88874580

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/535facad3886b_4b8fabbd3c411e3%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[Django] #22541: Missing space character in Dutch translation

2014-04-29 Thread Django

#22541: Missing space character in Dutch translation
--+
 Reporter:  pdewacht  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Translations  |Version:  1.6
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 In the Dutch translation (django/conf/locale/nl/LC_MESSAGES/django.po),
 this translated message has a missing space character after the comma.

 {{{
 #. Translators: This string is used as a separator between list elements
 #: utils/text.py:256
 msgid ", "
 msgstr ","
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/051.aca83e5478d40d76132086b1e1622b8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22540: .save() called in multiple "creation" queryset functions

2014-04-29 Thread Django

#22540: .save() called in multiple "creation" queryset functions
--+--
 Reporter:  craig.labenz@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:  creation
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+--
 Both `create()` and `_create_object_from_params()` (which is obviously
 called by `get_or_create()`), have raw calls to `save()`. It would be nice
 if one of those two low level creation functions used the other so
 additional logic pinned to `create()` by custom managers would also be
 available to `get_or_create()`.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6bfcb924ae588e59b4f49a0e0c28aee1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22485: makemigrations fails with dependencies to unmigrated apps

2014-04-29 Thread Django

#22485: makemigrations fails with dependencies to unmigrated apps
-+-
 Reporter:  apollo13 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations,  | Triage Stage:  Accepted
  unmigrated, makemigrations |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by hjwp):

 * cc: hjwp2@… (added)


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.cf3f20603cb7db30c0131a77a93fdc4a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22016: Automatically reload i18n files on change, when DEBUG is True

2014-04-29 Thread Django

#22016: Automatically reload i18n files on change, when DEBUG is True
--+
 Reporter:  vegitron  |Owner:  vegitron
 Type:  New feature   |   Status:  new
Component:  Internationalization  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timo):

 * version:   => master
 * stage:  Unreviewed => Accepted


Comment:

 I'm not very familiar with translations, but this seems like a reasonable
 request.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.897b8af4535f7bcc2ccd9073d60c9d9b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22503: Inconsistent behavior when a QuerySet is sliced

2014-04-29 Thread Django

#22503: Inconsistent behavior when a QuerySet is sliced
-+-
 Reporter:  ajaest   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  QuerySet, filter,|  Needs documentation:  0
  slice  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * stage:  Unreviewed => Accepted


Comment:

 If we don't do this, let's document why not.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.b2b01f0e3bb6aa9fc6e427a950f13ad2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22330: Model.reduce() includes cached lookups

2014-04-29 Thread Django

#22330: Model.__reduce__() includes cached lookups
-+-
 Reporter:  patrys   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Database layer (models, ORM)
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I am not sure of the expected behavior. If we don't make a change here, we
 should at least document like we've done for
 [https://docs.djangoproject.com/en/dev/ref/models/querysets/#pickling-
 querysets QuerySet pickling].

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.89fdc4c1088e4971a7152e5ddcebfb95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22382: ManyRelatedManager's get_prefetch_queryset doesn't validate the prefetch types

2014-04-29 Thread Django

#22382: ManyRelatedManager's get_prefetch_queryset doesn't validate the prefetch
types
-+-
 Reporter:  Keryn Knight |Owner:  nobody
   |   Status:  new
 Type:  Bug  |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/095.5c5486cc6488cd84c2b2c73c401c7fb8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22514: Postgres index generator does not expect db_type to be None

2014-04-29 Thread Django

#22514: Postgres index generator does not expect db_type to be None
-+-
 Reporter:  vzima|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.93f8359647f25e7dc1525449679e5341%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22508: select_related on a foreign related object fails to load fields on original object

2014-04-29 Thread Django

#22508: select_related on a foreign related object fails to load fields on 
original
object
-+-
 Reporter:  boxm |Owner:  aaugustin
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timo):

 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.c64fa5c85f4c079eba3759e3d220fc3b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21743: formset prefix attribute and formset empty form "prefix" don't refer to the same thing

2014-04-29 Thread Django

#21743: formset prefix attribute and formset empty form "__prefix__" don't 
refer to
the same thing
-+-
 Reporter:  bjb@…|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.6
Component:  Forms|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  formset prefix   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => wontfix
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 The inconsistency is too bad, but I don't think we can make the change
 without breaking backwards compatibility. If I'm missing something, feel
 free to reopen.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/072.1708ad2f8f61101d0a1d9deadf88c7c0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22046: unhelpful queryset handling for model formsets with data

2014-04-29 Thread Django

#22046: unhelpful queryset handling for model formsets with data
+
 Reporter:  Jim Bailey  |Owner:  hershbergien
 Type:  Bug |   Status:  assigned
Component:  Forms   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by timo):

 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.2cd0c819c808088580b7f7a6a8bcbf9e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22295: admin/base.html only shows #user-tools when user is staff

2014-04-29 Thread Django

#22295: admin/base.html only shows #user-tools when user is staff
-+-
 Reporter:  wouter@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  user-tools admin |  Needs documentation:  0
  base template  |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timo):

 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.d3574856e00f141516b983cf887a9df0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22537: Misleading documentation on choices for a model field

2014-04-29 Thread Django

#22537: Misleading documentation on choices for a model field
---+
 Reporter:  carbonXT   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.6
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+
Changes (by timo):

 * needs_docs:   => 0
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.f9841b9867237c4e9a6894ada3b9aa3f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22539: Model.full_clean() mutates exclude argument

2014-04-29 Thread Django

#22539: Model.full_clean() mutates exclude argument
-+-
 Reporter:  maggotfish@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by anonymous):

 I have patch ready, shall I send a pull request under a new branch
 ticket_22539?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.0b4ae004cc1b036eaeaa0417e8180ce2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22539: Model.full_clean() mutates exclude argument

2014-04-29 Thread Django

#22539: Model.full_clean() mutates exclude argument
-+-
 Reporter:  maggotfish@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by timo):

 * needs_better_patch:   => 0
 * has_patch:  1 => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/078.73c7f7de56dc43c1a97514fc9fb310c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 62bbfb: [1.7.x] Removed bogus, ineffective 'U' flag from c...

2014-04-29 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 62bbfba3aa96011a374f935d2c2176e5c2c90b85
  
https://github.com/django/django/commit/62bbfba3aa96011a374f935d2c2176e5c2c90b85
  Author: Ramiro Morales 
  Date:   2014-04-29 (Tue, 29 Apr 2014)

  Changed paths:
M django/core/management/sql.py

  Log Message:
  ---
  [1.7.x] Removed bogus, ineffective 'U' flag from codecs.open() call.

2df7238512 from master.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/535f84d54dc70_49b3b89d40821db%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 2df723: Removed bogus, ineffective 'U' flag from codecs.op...

2014-04-29 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2df7238512ecb9c19922a288592f4edfac1df43f
  
https://github.com/django/django/commit/2df7238512ecb9c19922a288592f4edfac1df43f
  Author: Ramiro Morales 
  Date:   2014-04-29 (Tue, 29 Apr 2014)

  Changed paths:
M django/core/management/sql.py

  Log Message:
  ---
  Removed bogus, ineffective 'U' flag from codecs.open() call.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/535f83cf2abb2_482da47d38497fa%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22510: Form fields cannot have names that are present as attributes on the form

2014-04-29 Thread Django

* needs_better_patch: 1 => 0
* needs_docs: 1 => 0

Comment:

I've renamed `shadow_fields` to `ignore_fields` on the premise that
"overloading" (which forms support) is also a form of shadowing, whereas
this feature is only about opting out from previously declared fields.

@apollo13 commented on the PR "Shadow_fields should at least be on meta to
not clutter the form namespace any more". The issue is that normal `Form`
don't support `Meta`, and I'm not convinced we should start introducing
it. We already have a bunch of fields related attributes, namely `fields`,
`base_fields`, `declared_fields`, IMO `ignore_fields` fits nicely.

I like this implementation better because there is now an obvious parallel
between the handling of `declared_fields` and `ignore_fields`, it also
does away with fiddling with `__dict__`.

To move this ticket forward we need to make a design decision, but if this
solution is retained the patch on the PR is ready for review.

--
Ticket URL:
Django
The Web framework for perfectionists with deadlines.

--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/071.b9fa6d783f746fd9a3467d38841161c8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19272: gettext_lazy returns "unexpected type"

2014-04-29 Thread Django

#19272: gettext_lazy returns "unexpected type"
-+-
 Reporter:  tyrion   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Translations |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by ygbo):

 * status:  closed => new
 * resolution:  fixed =>


Comment:

 The issue still occurs with pgettext_lazy:

 In [1]: from django.utils.translation import pgettext_lazy

 In [2]: s = pgettext_lazy("a context", "foo bar")  # using bytestring

 In [3]: s.upper()
 /usr/lib/python2.7/dist-packages/django/db/backends/sqlite3/base.py:53:
 RuntimeWarning: SQLite received a naive datetime (2014-04-29
 12:18:28.940685) while time zone support is active.
   RuntimeWarning)

 ---
 TypeError Traceback (most recent call
 last)
 /usr/lib/python2.7/dist-packages/django/core/management/commands/shell.pyc
 in ()
 > 1 s.upper()

 /usr/lib/python2.7/dist-packages/django/utils/functional.pyc in
 __wrapper__(self, *args, **kw)
 121 if t in self.__dispatch:
 122 return self.__dispatch[t][funcname](res,
 *args, **kw)
 --> 123 raise TypeError("Lazy object returned unexpected
 type.")
 124
 125 if klass not in cls.__dispatch:

 TypeError: Lazy object returned unexpected type.

 In [4]: s = pgettext_lazy("a context", u"foo bar")  # using unicode string

 In [5]: s.upper()
 Out[5]: u'FOO BAR'

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.e9ef637843a79e7617ec769454953300%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22539: Model.full_clean() mutates exclude argument

2014-04-29 Thread Django

#22539: Model.full_clean() mutates exclude argument
--+
 Reporter:  maggotfish@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 If model.full_clean() gets a list argument for `exclude`, and after
 running clean_fields() errors are raised, it appends the names of those
 fields to the `exclude` argument, mutating it and causing a really bad
 side effect which is not expected by the user.

 Instead, the list should be copied if it is not None.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.74b4782d9b36985fc1c9bc275cfdd727%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22533: Allow overriding `label_suffix` on a per-field basis

2014-04-29 Thread Django

#22533: Allow overriding `label_suffix` on a per-field basis
-+
 Reporter:  julen|Owner:  julen
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by julen):

 * has_patch:  0 => 1


Comment:

 PR available for review at:
 https://github.com/django/django/pull/2616

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.ac073e3b905024af77f705224c0b745f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22538: Support for HTML5 Date and Time input fields

2014-04-29 Thread Django

#22538: Support for HTML5 Date and Time input fields
---+--
 Reporter:  me@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Forms  |  Version:  1.6
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by anonymous):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => duplicate
 * needs_tests:   => 0
 * needs_docs:   => 0


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/073.b031157f4b5fe2d23eec6739714d874f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #22538: Support for HTML5 Date and Time input fields

2014-04-29 Thread Django

#22538: Support for HTML5 Date and Time input fields
---+
 Reporter:  me@…   |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Forms  |Version:  1.6
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 By default, the input_type of fields of type DateInput, DateTimeInput,
 TimeInput in the file django/forms/widgets.py is "text". This is because
 these fields inherit from TextField class which has input_type = "text".

 If we change the input_type in each of the classes to their HTML5
 specified equivalent, forms will be better.



 {{{
 ...
 class DateInput(TextInput):
  input_type = "date"
 ...

 ...
 class DateTimeInput(TextInput):
  input_type = "datetime"
 ...

 ...
 class TimeInput(TextInput):
  input_type = "time"
 ...
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/058.01a84f57f231dcb01377490f8ba7e313%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22421: Loading fixtures with one-to-one inheritance on abstract model and M2M fails since 1.7 Beta (was: Loading fixtures with one-to-one inheritance on proxy model and M2M with natural

2014-04-29 Thread Django

#22421: Loading fixtures with one-to-one inheritance on abstract model and M2M
fails since 1.7 Beta
--+
 Reporter:  stanislas.guerra@…|Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Serialization)  |  Version:  master
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+

Comment (by stanislas.guerra@…):

 Edit:

 This is not a proxy model but an abstract one.
 And it does not looks like it is related to the natural keys since the
 regression test fails without them.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/084.db4f5d4ff373153088a46aae25458bb8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #16025: distinct does not apply to aggregated querysets

2014-04-29 Thread Django

#16025: distinct does not apply to aggregated querysets
-+-
 Reporter:  micolous |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by vsajip):

 * version:  1.3 => 1.6


Comment:

 Still there in 1.6 :-(

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.9184bb707af79c99da1f8ffdf8d7e0d4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

74 matches

Mail list logo