date:20140228

Re: [Django] #22172: Allow skipping outer parenthesis when defining index_together

2014-02-28 Thread Django

#22172: Allow skipping outer parenthesis when defining index_together
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  New feature  |   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 anubhav9042):

 I too found this thing to be true, single tuple doesn't works.

 Although a  thing to note:
 unique_together works as a single tuple and list both:
 {{{
 class Test(models.Model):
 t1 = models.CharField(max_length=255, blank=True)
 t2 = models.CharField(max_length=255, blank=True, null=True)
 t3 = models.CharField(max_length=255, blank=True, null=True)

 class Meta:
 unique_together = ['t1','t2','t3']
 }}}

-- 
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.08b17648fecf871ce10ac2f9674fd6da%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22173: hungry weight loss

2014-02-28 Thread Django

#22173: hungry weight loss
---+--
 Reporter:  dollkristy |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:  invalid
 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 Siecje):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => invalid
 * 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/068.534adf311d276764f7b210833740c1bb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22173: hungry weight loss

2014-02-28 Thread Django

#22173: hungry weight loss
---+
 Reporter:  dollkristy |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I'm checking my email oh and he has his eyes right now they have fail but
 now Wednesday with everything right and perspective he even my water turn
 off that for info event after over see after that I'm a sure that have
 hockey coffee I do you have a protein shake my hand would make breakfast
 I'll probably http://cleanseultimotruth.com/";>Cleanse Ultimo
  be and something from a lot sometimes I have director of it is just the
 way it yak say e every 3-4 hours not that and do that I eat with ever I
 felt hungry okay nor has he eat profit at nine o'clock if you hungry 8
 o'clock I always tried to eat my dinner to the hours before I go to bed
 some time and I'll I just happen like that but most of the time does house
 Friday not to have a late night snack have your meal some work here so 18
 all that you have to work all day.
 http://cleanseultimotruth.com/

-- 
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.18db065e766d4a115a32858a103ac4ae%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21908: Misleading documentation in ModelAdmin.get_inline_instances

2014-02-28 Thread Django

#21908: Misleading documentation in ModelAdmin.get_inline_instances
--+
 Reporter:  matt@…|Owner:  avendael
 Type:  Cleanup/optimization  |   Status:  assigned
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):

 * has_patch:  0 => 1


-- 
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/076.d581bb7a4ddf68ce036eb504561ecd02%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 1f5f01: Fixed spelling mistakes in docs.

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1f5f015c32550c1424dd7804e8ee4717bcc5b9b7
  
https://github.com/django/django/commit/1f5f015c32550c1424dd7804e8ee4717bcc5b9b7
  Author: Tim Graham 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M docs/internals/committers.txt
M docs/internals/contributing/localizing.txt
M docs/intro/tutorial01.txt
M docs/ref/applications.txt
M docs/ref/contrib/gis/geoip.txt
M docs/ref/contrib/sites.txt
M docs/ref/databases.txt
M docs/ref/django-admin.txt
M docs/ref/migration-operations.txt
M docs/ref/models/instances.txt
M docs/ref/models/querysets.txt
M docs/ref/settings.txt
M docs/ref/utils.txt
M docs/releases/0.95.txt
M docs/releases/1.3-alpha-1.txt
M docs/releases/1.7.txt
M docs/topics/class-based-views/mixins.txt
M docs/topics/forms/formsets.txt
M docs/topics/migrations.txt
M docs/topics/testing/advanced.txt

  Log Message:
  ---
  Fixed spelling mistakes in docs.


-- 
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/5311401f863e9_236903d3c632db%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21643: QuerySets that use F() + timedelta() crash when compiling their query more than once

2014-02-28 Thread Django

#21643: QuerySets that use F() + timedelta() crash when compiling their query 
more
than once
-+-
 Reporter:  despawn@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"5cda1d27027ea74d8a1b53e43bef697cd4426e9a"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5cda1d27027ea74d8a1b53e43bef697cd4426e9a"
 [1.6.x] Fixed #21643 -- repeated execution of qs with F() + timedelta

 Thanks Tim Graham for review and Tai Lee for the additional test to prove
 this was a regression in 1.6.

 Backport of 7f2485b4d1 and 8137215973 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/075.dc6e3579b0759cc853ec54e59c0805d7%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 5cda1d: [1.6.x] Fixed #21643 -- repeated execution of qs w...

2014-02-28 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 5cda1d27027ea74d8a1b53e43bef697cd4426e9a
  
https://github.com/django/django/commit/5cda1d27027ea74d8a1b53e43bef697cd4426e9a
  Author: Alexey Voronov 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M django/db/models/sql/expressions.py
M docs/releases/1.6.3.txt
M tests/expressions_regress/tests.py

  Log Message:
  ---
  [1.6.x] Fixed #21643 -- repeated execution of qs with F() + timedelta

Thanks Tim Graham for review and Tai Lee for the additional test to prove
this was a regression in 1.6.

Backport of 7f2485b4d1 and 8137215973 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/53113cc1350ad_54ba8bd44692ad%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 813721: Added release note and regression test for refs #2...

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8137215973c8cf97f58f244021b1a4e75923ade8
  
https://github.com/django/django/commit/8137215973c8cf97f58f244021b1a4e75923ade8
  Author: Tim Graham 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M docs/releases/1.6.3.txt
M tests/expressions_regress/tests.py

  Log Message:
  ---
  Added release note and regression test for refs #21643.

This will be backported to stable/1.6.x along with the original fix.


-- 
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/53113b5de8cf3_913c89d441183a9%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21643: QuerySets that use F() + timedelta() crash when compiling their query more than once

2014-02-28 Thread Django

#21643: QuerySets that use F() + timedelta() crash when compiling their query 
more
than once
-+-
 Reporter:  despawn@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"8137215973c8cf97f58f244021b1a4e75923ade8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="8137215973c8cf97f58f244021b1a4e75923ade8"
 Added release note and regression test for refs #21643.

 This will be backported to stable/1.6.x along with the original fix.
 }}}

-- 
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.223097bff1936401665eccf4b538105c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22168: Sqlite3 backend fails during _remake_table with column named "order"

2014-02-28 Thread Django

#22168: Sqlite3 backend fails during _remake_table with column named "order"
-+-
 Reporter:  netwamp@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


-- 
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.10926b33c53e10642f135e05ed45ae80%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22137: Widgets class should drop the is_hidden bool property

2014-02-28 Thread Django

#22137: Widgets class should drop the is_hidden bool property
-+-
 Reporter:  django@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

 * stage:  Accepted => Ready for checkin


-- 
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.3c5625a4b8813164abd1c471ff3065a0%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7c0102: Removed some ReST links to undocumented functions.

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7c0102379a1a1b386f4f4908d4a05b01df5f29f0
  
https://github.com/django/django/commit/7c0102379a1a1b386f4f4908d4a05b01df5f29f0
  Author: Tim Graham 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M docs/releases/1.7.txt

  Log Message:
  ---
  Removed some ReST links to undocumented functions.


-- 
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/5311153d219be_28191225d34107997%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22171: sanitize_separators throws away too many thousand separators

2014-02-28 Thread Django

#22171: sanitize_separators throws away too many thousand separators
---+--
 Reporter:  vanschelven|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.4
 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 wim@…):

 Hi Klaas,

 I tried to reproduce the error and failed (Django 1.4.10 and Django
 1.4.3). Although I recall having encountered such a weird situation
 before. Maybe my os was set to Dutch then?

 Good idea to raise an error when invalid input has been entered.

-- 
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.321f8bb3f212a4ac35ca54e23ee1c062%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22172: Allow skipping outer parenthesis when defining index_together

2014-02-28 Thread Django

#22172: Allow skipping outer parenthesis when defining index_together
-+-
 Reporter:  EmilStenstrom|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 wim@…):

 * stage:  Unreviewed => Accepted


Comment:

 Additionally, for some reason unique_together is defined as a tuple of
 tuples, and index_together as a list of lists, which seems odd to me as
 well.

-- 
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.c0206410976aa24c8a8e5fa0ec53f463%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22172: Allow skipping outer parenthesis when defining index_together

2014-02-28 Thread Django

#22172: Allow skipping outer parenthesis when defining index_together
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  New feature  |   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 anonymous):

 * type:  Bug => New feature


-- 
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.61ca91d8edc93574571410154cd2914f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8809: Better error message when can't import url callback

2014-02-28 Thread Django

#8809: Better error message when can't import url callback
---+
 Reporter:  TP |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Core (URLs)|  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  error message  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by anubhav9042):

 In django.core.urlresolvers.py:
 {{{
 if not callable(lookup_view):
 mod_name, func_name = get_mod_func(lookup_view)
 if func_name == '':
 return lookup_view

 try:
 mod = import_module(mod_name)
 except ImportError:
 parentmod, submod = get_mod_func(mod_name)
 if (not can_fail and submod != '' and
 not module_has_submodule(import_module(parentmod),
 submod)):
 raise ViewDoesNotExist(
 "Could not import %s. Parent module %s does not
 exist." %
 (lookup_view, mod_name))
 if not can_fail:
 raise
 else:
 try:
 lookup_view = getattr(mod, func_name)
 if not callable(lookup_view):
 raise ViewDoesNotExist(
 "Could not import %s.%s. View is not callable." %
 (mod_name, func_name))
 except AttributeError:
 if not can_fail:
 raise ViewDoesNotExist(
 "Could not import %s. View does not exist in
 module %s." %
 (lookup_view, mod_name))
 return lookup_view
 }}}

 This explains why I have closed this as 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/060.6a4376e464e51ff9eea1968e52e6abbb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #8809: Better error message when can't import url callback

2014-02-28 Thread Django

#8809: Better error message when can't import url callback
---+
 Reporter:  TP |Owner:  nobody
 Type:  New feature|   Status:  closed
Component:  Core (URLs)|  Version:  master
 Severity:  Normal |   Resolution:  fixed
 Keywords:  error message  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by anubhav9042):

 * status:  new => closed
 * resolution:   => 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/060.5b6c10e5cf765692d0ffc8fd306073ee%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21948: Docs on extending admin templates should mention TEMPLATE_LOADERS

2014-02-28 Thread Django

#21948: Docs on extending admin templates should mention TEMPLATE_LOADERS
--+
 Reporter:  django@…  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.6
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"ea869b514846cdd4803e3a87b08686113c14f7f2"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ea869b514846cdd4803e3a87b08686113c14f7f2"
 Fixed #21948 -- Noted TEMPLATE_LOADERS requirement when overriding admin
 templates.

 Thanks django at patjack.co.uk for the suggestion.
 }}}

-- 
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.145d50239fdf51e64102fa0c949ddd81%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] ea869b: Fixed #21948 -- Noted TEMPLATE_LOADERS requirement...

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ea869b514846cdd4803e3a87b08686113c14f7f2
  
https://github.com/django/django/commit/ea869b514846cdd4803e3a87b08686113c14f7f2
  Author: Alex de Landgraaf 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M docs/ref/contrib/admin/index.txt

  Log Message:
  ---
  Fixed #21948 -- Noted TEMPLATE_LOADERS requirement when overriding admin 
templates.

Thanks django at patjack.co.uk for the suggestion.


-- 
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/53110248dbe42_2abc77bd3491125%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22058: Add `Http405` exception class and `handler405` view (simillar to 404, 403 and 500)

2014-02-28 Thread Django

#22058: Add `Http405` exception class and `handler405` view (simillar to 404, 
403
and 500)
-+---
 Reporter:  debanshuk|Owner:  anubhav9042
 Type:  New feature  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 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
-+---
Changes (by anubhav9042):

 * status:  new => assigned
 * owner:  nobody => anubhav9042
 * cc: anubhav9042@… (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/067.fe98f6164f789e43ccba301321a51dd3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22058: Add `Http405` exception class and `handler405` view (simillar to 404, 403 and 500)

2014-02-28 Thread Django

#22058: Add `Http405` exception class and `handler405` view (simillar to 404, 
403
and 500)
-+--
 Reporter:  debanshuk|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (URLs)  |  Version:  master
 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 anubhav9042):

 I am interested in this especially I want this to incorporate in GSoC
 proposal.
 As suggested we can just have two views which can be matched with regex
 4XX and 5XX, and accordingly lot of code will be reduced.
 Also as this ticket suggests, we can add some more cases including 405
 like 401, etc

 Any suggestions??

-- 
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.6e5739a088ce52ab22cc520a9ebf1230%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22171: sanitize_separators throws away too many thousand separators

2014-02-28 Thread Django

#22171: sanitize_separators throws away too many thousand separators
---+--
 Reporter:  vanschelven|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.4
 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 claudep):

 Strange, I cannot reproduce your shell example. However, I can see that
 `12.210.10` is cleaned to `12.210.10`, so no cleaning happens in that
 case. That last issue could be fixed by:
 {{{
  if decimal_separator in value:
 -value, decimals = value.split(decimal_separator, 1)
 +value, decimals = value.rsplit(decimal_separator, 1)
  parts.append(decimals)
 }}}
 Can you check once more?

-- 
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.4a031a932c3a353e6b6431b55e033b48%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22161: Sending an email with no recipients fails silently

2014-02-28 Thread Django

#22161: Sending an email with no recipients fails silently
-+
 Reporter:  ian@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 Erik has a point in his comment:3. We should first ponder arguments for or
 against raising an exception when sending email with no recipients.

-- 
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.630dbaa8bfebbf869fc26d39032fe451%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22125: Unnecessary creation of index for ManyToManyField

2014-02-28 Thread Django

#22125: Unnecessary creation of index for ManyToManyField
-+-
 Reporter:  tbhtan3@…|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.6
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by ceaess):

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


Comment:

 Is there some of the code missing? I'm not seeing a unique index created
 in the SQL code you have here, just a unique constraint on food_id and
 restaurant_id.

-- 
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.73707ab0272875c473e4a598c6ad7aca%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22172: Allow skipping outer parenthesis when defining index_together (was: Allow skipping outer parentesis when defining index_together)

2014-02-28 Thread Django

#22172: Allow skipping outer parenthesis when defining index_together
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  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/071.e9359c0b7c1c6bcf934f24fc100a2b3a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] cbd04c: Fix keyword agument names in RunPython to be posit...

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: cbd04c7c498689382ce56a7b7b31eca5ba98b590
  
https://github.com/django/django/commit/cbd04c7c498689382ce56a7b7b31eca5ba98b590
  Author: Andrew Godwin 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M django/db/migrations/operations/special.py

  Log Message:
  ---
  Fix keyword agument names in RunPython to be positional


-- 
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/5310c5f56d1c4_44a10bbd4061396%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22163: select_for_update should take nowait directly

2014-02-28 Thread Django

#22163: select_for_update should take nowait directly
-+-
 Reporter:  kenny.macdermid@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by ceaess):

 * cc: ceaess (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/083.d3730d6ea324e135893dd49542bb5492%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22163: select_for_update should take nowait directly

2014-02-28 Thread Django

#22163: select_for_update should take nowait directly
-+-
 Reporter:  kenny.macdermid@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by ceaess):

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


Comment:

 I think the fix for this is pretty simple. Could modify query.py method
 `select_for_update(self, **kwargs)` to `select_for_update(self,
 nowait=False)`. This yields the reasonable error `TypeError:
 select_for_update() got an unexpected keyword argument 'id'` when passing
 in (id=1).

 This will prevent the misunderstanding that filtering can happen within
 the method.

 {{{
 def select_for_update(self, nowait=False):
 """
 Returns a new QuerySet instance that will select objects with a
 FOR UPDATE lock.
 """
 obj = self._clone()
 obj._for_write = True
 obj.query.select_for_update = True
 obj.query.select_for_update_nowait = nowait
 return obj
 }}}

-- 
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.265d8e5c46b183d15f19cdd9b6c3b7cc%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7f2505: Fixed doc typos.

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7f2505ad9e27962ecbd61d2ce26ad691727404a4
  
https://github.com/django/django/commit/7f2505ad9e27962ecbd61d2ce26ad691727404a4
  Author: Tim Graham 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M docs/internals/contributing/triaging-tickets.txt
M docs/internals/security.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/gis/geoquerysets.txt
M docs/ref/contrib/gis/install/postgis.txt
M docs/ref/contrib/staticfiles.txt
M docs/ref/databases.txt
M docs/ref/django-admin.txt
M docs/ref/forms/fields.txt
M docs/ref/migration-operations.txt
M docs/ref/models/custom-lookups.txt
M docs/ref/models/fields.txt
M docs/ref/templates/api.txt
M docs/releases/1.2.txt
M docs/releases/1.4-alpha-1.txt
M docs/releases/1.4-beta-1.txt
M docs/releases/1.4.txt
M docs/releases/1.7.txt
M docs/topics/auth/passwords.txt
M docs/topics/cache.txt
M docs/topics/class-based-views/generic-display.txt
M docs/topics/class-based-views/mixins.txt
M docs/topics/db/queries.txt
M docs/topics/forms/modelforms.txt
M docs/topics/migrations.txt
M docs/topics/performance.txt
M docs/topics/testing/tools.txt

  Log Message:
  ---
  Fixed doc typos.


-- 
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/5310bcde39df2_1f58138dd3465273%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22172: Allow skipping outer parentesis when defining index_together (was: Use the same convenience)

2014-02-28 Thread Django

#22172: Allow skipping outer parentesis when defining index_together
-+-
 Reporter:  EmilStenstrom|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by EmilStenstrom):

 * needs_better_patch:   => 0
 * 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/071.7303e8994e800e3826c99fe86c5f16cb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22172: Use the same convenience

2014-02-28 Thread Django

#22172: Use the same convenience
--+
 Reporter:  EmilStenstrom |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 {{{
 "For convenience, unique_together can be a single tuple when dealing with
 a single set of fields"
 }}}

 https://docs.djangoproject.com/en/dev/ref/models/options/#unique-together

 This convenience feature is missing from
 [https://docs.djangoproject.com/en/dev/ref/models/options/#index-together
 index_together]. This code...

 {{{
 class Subscription(models.Model):
 ...
 class Meta:
 unique_together = ("dialog_content_type", "dialog_object_id")
 index_together = ("dialog_content_type", "dialog_object_id")
 }}}

 ... crashes with this error message:

 {{{
 notifications.subscription: "index_together" refers to d, a field that
 doesn't exist.
 notifications.subscription: "index_together" refers to i, a field that
 doesn't exist.
 notifications.subscription: "index_together" refers to a, a field that
 doesn't exist.
 notifications.subscription: "index_together" refers to l, a field that
 doesn't exist.
 notifications.subscription: "index_together" refers to o, a field that
 doesn't exist.
 notifications.subscription: "index_together" refers to g, a field that
 doesn't exist.
 }}}

 I think it would be nice if the two similar settings worked the same.

-- 
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/056.9688234b89ebe37c4afa7b2650812a8d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22171: sanitize_separators throws away too many thousand separators

2014-02-28 Thread Django

#22171: sanitize_separators throws away too many thousand separators
---+--
 Reporter:  vanschelven|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:  1.4
 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
---+--
Changes (by vanschelven):

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


Comment:

 ... I cannot edit ...

 Finishing the sentence above:

 This solution also happens to cover all scenarios where cents are
 involved, which happens to be an important subclass of dealing with
 Decimals (Money!)

-- 
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.5a5d7d330f711285d23e2d8663006f4c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22171: sanitize_separators throws away too many thousand separators

2014-02-28 Thread Django

#22171: sanitize_separators throws away too many thousand separators
---+
 Reporter:  vanschelven|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Users in countries that use symbols other than the period (e.g. comma) as
 a decimal separator, may still occasionally use the period as a decimal
 separator. (Because they've come to expect that computers want input with
 a period). If the period coincides with the THOUSANDS_SEPARATOR, and
 USE_THOUSANDS_SEPARATOR is turned on, this results in the decimal
 separator basically being thrown out, but still with a validated result.

 Example shell output (THOUSANDS_SEPARATOR == '.'; USE_THOUSANDS_SEPARATOR
 = True)):


 {{{
 >>> from django.utils.translation import activate
 >>> activate('nl-nl')
 >>>
 >>> class F(forms.Form):
 ...   f = forms.DecimalField(max_digits=15, decimal_places=2)
 ...
 >>> f = F({'f': '10.10'})
 >>> print f.is_valid()
 True
 >>> print f.cleaned_data['f']
 1010

 }}}

 Why does this happen? django/utils/formats.py has a function
 sanitize_separators, that basically tosses all thousands separators ''even
 if they do not actually separate thousands''

 My solution would be to only toss thousands separators which have at least
 3 digits on their right hand side.

 Admittedly this is not a full solution: the value 100.000 is still
 ambiguous if we assume that users may mean either "thousands separator" or
 "decimal separator" with the period. But at least it does not silently
 convert 10.00 (which doesn't mean 1000 to anyone) into 1000. This solution
 also happens to cover all scenarios where cents are involved, which

 A better solution would not validate "10.00" at all (since it does not
 contain either a decimal separator nor a thousands separator separating
 thousands). However, the current interface of sanitize_operators does not
 allow for it: it attempts to sanitize towards a string w/ period, and does
 not allow us to complain if the input is a string w/ period, but we
 wouldn't want to allow that as a valid input.

 The/a solution for Django 1.4 is attached. I imagine it may be a bit more
 hairy in the up-to-date version, as this supports full unicode for the
 input, and I'm not entirely sure on the interaction of regex & unicode.

 I've reproduced this in 1.4, but can see in the repo that as of today the
 code still experiences this problem.

-- 
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/054.8863bb2f0e89d641c6cd8573eb16f97d%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14549: Disambiguation of target/source fields for intermediary models when using ManyToManyField

2014-02-28 Thread Django

#14549: Disambiguation of target/source fields for intermediary models when 
using
ManyToManyField
-+-
 Reporter:  Kronuz   |Owner:  dfunckt
 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|
-+-
Changes (by dfunckt):

 * status:  new => assigned
 * owner:  nobody => dfunckt


-- 
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.4c0b59d3d2192a0e1257019e430dc7e3%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14549: Disambiguation of target/source fields for intermediary models when using ManyToManyField

2014-02-28 Thread Django

#14549: Disambiguation of target/source fields for intermediary models when 
using
ManyToManyField
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:  New feature  |   Status:  new
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 dfunckt):

 For this patch to go forward, is it possible that a core dev can confirm
 or discuss the API?

 I personally agree with loic84 regarding the API which I believe is short,
 simple and explicit. However, I'm all for re-implementing the patch if the
 suggested API is not accepted and there are other suggestions.

-- 
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.50378cc6f7eb3ad17f5416fe0c474a04%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #10939: Allow for dynamic registration of inlines into an admin model

2014-02-28 Thread Django

#10939: Allow for dynamic registration of inlines into an admin model
---+--
 Reporter:  zbyte64|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.admin  |  Version:  1.4-rc-2
 Severity:  Normal |   Resolution:  invalid
 Keywords:  inlines| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by mhcfaihD):

 * version:  1.0 => 1.4-rc-2
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0
 * ui_ux:   => 0


Comment:

 http://www.andresramirezgaviria.com/file/#3il45>buy provigil
 provigil generic discount - provigil interactions

-- 
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.4ceafd6af0a2c56673f622949066dc46%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 55fb16: Fixed #22028 -- Documented that database signals a...

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 55fb1625443bc70398248b6e681f3bc032c8
  
https://github.com/django/django/commit/55fb1625443bc70398248b6e681f3bc032c8
  Author: Tim Graham 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M docs/ref/applications.txt
M docs/ref/signals.txt

  Log Message:
  ---
  Fixed #22028 -- Documented that database signals aren't emitted for apps that 
laack a models module.

Thanks un33k for the suggestion and donjpacheco for the draft patch.


-- 
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/53109c9da04f5_7d2c13cbd3c29611%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22161: Sending an email with no recipients fails silently

2014-02-28 Thread Django

#22161: Sending an email with no recipients fails silently
-+
 Reporter:  ian@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by ian@…):

 I'm happy to add some documentation for this, but I'm not sure where is
 appropriate.

-- 
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.f9fb27ab5f7a16a524a778af0885ac21%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22028: documentation: apps without models.py can register for db related signals

2014-02-28 Thread Django

#22028: documentation: apps without models.py can register for db related 
signals
-+-
 Reporter:  un33k|Owner:
 Type:   |  donjpacheco
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  apps without models  | Triage Stage:  Accepted
  database signals   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"55fb1625443bc70398248b6e681f3bc032c8"]:
 {{{
 #!CommitTicketReference repository=""
 revision="55fb1625443bc70398248b6e681f3bc032c8"
 Fixed #22028 -- Documented that database signals aren't emitted for apps
 that laack a models module.

 Thanks un33k for the suggestion and donjpacheco for the draft patch.
 }}}

-- 
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.da682bbdccbcc92a7796943240952633%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22170: Add initial migrations for contrib apps

2014-02-28 Thread Django

#22170: Add initial migrations for contrib apps
---+
   Reporter:  timo |  Owner:
   Type:  New feature  | Status:  new
  Component:  Migrations   |Version:  master
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 There was some discussion among the core devs about the possibility of
 adding migrations for contrib apps in 1.7. I think the consensus was that
 it would be safer to release 1.7 without any schema changes, but to
 include the initial migrations for contrib apps to get people thinking
 about 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/047.c01618f8610d94450d76986ecfe0082f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #18959: Error message for table names > 50 characters is very poor.

2014-02-28 Thread Django

#18959: Error message for table names > 50 characters is very poor.
-+-
 Reporter:  slacy|Owner:
 Type:   |  anubhav9042
  Cleanup/optimization   |   Status:  closed
Component:  contrib.auth |  Version:  master
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  permission   | 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):

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


Comment:

 I tried to reproduce this, but I think it's actually a duplicate of
 #18866. The `auth_permission.name` column is limited to 50 characters, but
 it's based on the `verbose_name` which is now validated for length < 39 so
 the permission name won't be too long.

-- 
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.29275c9b5988cc8b19ef8a37d3326e26%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22161: Sending an email with no recipients fails silently

2014-02-28 Thread Django

#22161: Sending an email with no recipients fails silently
-+
 Reporter:  ian@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Mail)  |  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by claudep):

 * needs_docs:  0 => 1
 * stage:  Ready for checkin => 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/072.55c7273032d76e1a89fe05c88d625f49%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 2f25cd: Fixed #22129 -- Added steps for creating superuser...

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2f25cdc18a3c15dd9feb9daa522f41aac39e232b
  
https://github.com/django/django/commit/2f25cdc18a3c15dd9feb9daa522f41aac39e232b
  Author: Greg Chapple 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M docs/intro/tutorial01.txt

  Log Message:
  ---
  Fixed #22129 -- Added steps for creating superusers to tutorial.


-- 
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/53108b772a11b_7e31cb1d44524a2%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22129: super user creation prompts after executing migrate, not in tutorial

2014-02-28 Thread Django

#22129: super user creation prompts after executing migrate, not in tutorial
--+
 Reporter:  kirby_agudelo |Owner:  gchp
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:  documentation | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"2f25cdc18a3c15dd9feb9daa522f41aac39e232b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2f25cdc18a3c15dd9feb9daa522f41aac39e232b"
 Fixed #22129 -- Added steps for creating superusers to tutorial.
 }}}

-- 
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.ade6ddd216e1c38c882e08d7fd259ddb%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19280: Detect broken {% url %} syntax

2014-02-28 Thread Django

#19280: Detect broken {% url %} syntax
-+-
 Reporter:  akaariai |Owner:  tome
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Template system  |  1.5-alpha-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"72b080c2c8a5ab7930b13688b2865ebc5b636687"]:
 {{{
 #!CommitTicketReference repository=""
 revision="72b080c2c8a5ab7930b13688b2865ebc5b636687"
 Removed Django 1.5 upgrade hints for {% url %} tag.

 Refs #19280 and Refs #19392.
 }}}

-- 
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.49e47ef3d35a472465a841248f2c4307%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 72b080: Removed Django 1.5 upgrade hints for {% url %} tag...

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 72b080c2c8a5ab7930b13688b2865ebc5b636687
  
https://github.com/django/django/commit/72b080c2c8a5ab7930b13688b2865ebc5b636687
  Author: Tim Graham 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M django/template/defaulttags.py
M tests/template_tests/tests.py

  Log Message:
  ---
  Removed Django 1.5 upgrade hints for {% url %} tag.

Refs #19280 and Refs #19392.


-- 
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/531080aec6d99_2664cabd40104439%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19392: Old-style url names (with dashes) throw confusing template traceback

2014-02-28 Thread Django

#19392: Old-style url names (with dashes) throw confusing template traceback
-+-
 Reporter:  dloewenherz  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Template system  |  1.5-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 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 Tim Graham ):

 In [changeset:"72b080c2c8a5ab7930b13688b2865ebc5b636687"]:
 {{{
 #!CommitTicketReference repository=""
 revision="72b080c2c8a5ab7930b13688b2865ebc5b636687"
 Removed Django 1.5 upgrade hints for {% url %} tag.

 Refs #19280 and Refs #19392.
 }}}

-- 
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.5ffe1f094d6d4af5456d69e7b1f1a019%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22168: Sqlite3 backend fails during _remake_table with column named "order"

2014-02-28 Thread Django

#22168: Sqlite3 backend fails during _remake_table with column named "order"
-+
 Reporter:  netwamp@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   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 bmispelon):

 * needs_tests:  1 => 0


Comment:

 Tentative pull request (with tests) here:
 https://github.com/django/django/pull/2378

 Reviews welcome.

-- 
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.47c71fb6d1a723f507ff0a7058d67e43%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] c23b37: Fixed #21962 -- Added escape_html flag to ErrorDic...

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c23b3717be71e4b2e5a32f156ef0a7b4703d012d
  
https://github.com/django/django/commit/c23b3717be71e4b2e5a32f156ef0a7b4703d012d
  Author: vvojvoda 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M django/forms/utils.py
M docs/ref/forms/api.txt
M tests/forms_tests/tests/test_forms.py

  Log Message:
  ---
  Fixed #21962 -- Added escape_html flag to ErrorDict.as_json()


-- 
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/53107dea139ba_9d365bd3c5389b%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21962: Add a flag to ErrorDict.as_json() to escape html

2014-02-28 Thread Django

#21962: Add a flag to ErrorDict.as_json() to escape html
--+
 Reporter:  timo  |Owner:  vedran
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Forms |  Version:  master
 Severity:  Release blocker   |   Resolution:  fixed
 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 Tim Graham ):

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


Comment:

 In [changeset:"c23b3717be71e4b2e5a32f156ef0a7b4703d012d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="c23b3717be71e4b2e5a32f156ef0a7b4703d012d"
 Fixed #21962 -- Added escape_html flag to ErrorDict.as_json()
 }}}

-- 
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.8ec3c74b7582e886899ca32b39e85153%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20825: Make cookies use the HTTPOnly flag by default

2014-02-28 Thread Django

#20825: Make cookies use the HTTPOnly flag by default
---+
 Reporter:  julien |Owner:  julien
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  1.5
 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 erikr):

 The current default for SESSION_COOKIE_HTTPONLY in current master is True.
 So, this concerns only the CSRF cookie, and custom cookies set though
 set_cookie() on a response. Are you referring to one of these
 specifically, or both?

-- 
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.0dbf72160f1c739a7b14996d890a0f14%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #20292: Django 1.5.1: ORA-01843: not a valid month

2014-02-28 Thread Django

Comment (by jtiai):

Accidentally we do use use custom DateTime field for Oracle and we had
never problems with that.

Now looking closely our magical field it actually passes __real__ datetime
objects for cx_Oracle (cx_Oracle knowns how to do conversions internally).

My suggestion is to change Oracle backend hooks for ''value_to_db_date'',
''value_to_db_time'' and ''value_to_db_datetime'' to return real
datetime/date/time objects for Oracle.

See http://www.oracle.com/technetwork/articles/dsl/prez-python-
timesanddates-093014.html for more information about conversions.

--
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.3e273a90fe1ebab334e24b575de0ec35%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22169: weight loss 18

2014-02-28 Thread Django

#22169: weight loss 18
---+---
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:  true cleanse complete
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 Tuesday video the 2d at great sleighs yesterday so if today yet the first
 video of the week being Tuesday and Thursday first video of the week is
 the video I talk about my actual weight loss up to this point now I'm
 crazy crazy crazy story to tell you for tomorrow's video and so I didn't
 get a chance to weigh myself Monday 7 actually getting when I seventy two
 instill date 10 so I D 10 when I wake myself up I released 16 pounds all
 overcast I mean yes step on the scale and you look at the number and then
 you go back and make sure that the
  actual number is it supposed[http://truecleansecompleteadvice.com/ true
 cleanse complete] a it 16 pounds I'm very excited I haven't had that on
 mount watt released at the very beginning ever yeah I ever some really
 excited about that however I was reluctant to put that number up I'm real
 I mean really elected because after last week's video I got the on lot
 messages from people Karla I know you say that we should expect point five
 pounds if you're female 25pounds %ah lot on scale or pound loss if your
 man this is
 http://truecleansecompleteadvice.com/

-- 
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/052.f24eace2de7cad4ee6f12ca1a0ec2441%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22168: Sqlite3 backend fails during _remake_table with column named "order"

2014-02-28 Thread Django

#22168: Sqlite3 backend fails during _remake_table with column named "order"
-+
 Reporter:  netwamp@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+
Changes (by claudep):

 * component:  Database layer (models, ORM) => Migrations


-- 
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.90fdef25640ebc689a0ee0bf4fc4084b%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22161: Sending an email with no recipients fails silently

2014-02-28 Thread Django

* cc: eromijn@… (added)

Comment:

But that's technically not an error condition. send() does exactly what
you asked it to do: send a mail to all recipients you specified. Why
should this throw an exception?

Also, people may have become dependent on the behaviour that send() can be
called even though recipients is empty. Therefore, if we do change this, I
think it warrants at least a mention in the release notes, as a backwards
incompatible change, although it will probably not hit too many users. I
checked briefly, but it seems the current behaviour is not explicitly
documented.

--
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.540e8c4b32ce96e66425970589cc2e69%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22168: Sqlite3 backend fails during _remake_table with column named "order"

2014-02-28 Thread Django

* needs_tests: 0 => 1
* stage: Unreviewed => Accepted

Comment:

Hi,

I can reproduce the issue by doing the following:

1) Create a model with a field called `order`.
2) Run `makemigrations`. This creates a first migration file.
3) Add another field to the model created in 1)
4) Run `makemigrations` again. This creates a second migration file.
5) Attempt to run `migrate`. This fails with the reported error.

Your proposed fix looks sensible and it works for the reported issue but a
full patch should have some tests too.

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/075.09e96769218f8a16ef297a603b0b01bd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #22168: Sqlite3 backend fails during _remake_table with column named "order"

2014-02-28 Thread Django

#22168: Sqlite3 backend fails during _remake_table with column named "order"
-+-
 Reporter:  netwamp@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by fallen_flint):

 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * 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/075.1f662ebe4565d35a59ed013690bc122c%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22168: Sqlite3 backend fails during _remake_table with column named "order"

2014-02-28 Thread Django

#22168: Sqlite3 backend fails during _remake_table with column named "order"
--+
 Reporter:  netwamp@… |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Release blocker   |   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 It seems that column names should be quoted, cause if I try migrate my
 app, migration fails on following sql request:
 {{{#!sql
 INSERT INTO "services_group__new" (description, order, id, slug, title)
 SELECT description, order, id, slug, title FROM "services_group"
 }}}

 If I try it in db shell, it fails too, as expected.
 Message is "Error: near "order": syntax error"

 Adding quotes around column names in
 django.db.backends.sqlite3.schema.DatabaseSchemaEditor._remake_table fixes
 the problem for me:
 {{{#!diff
 diff --git a/django/db/backends/sqlite3/schema.py
 b/django/db/backends/sqlite3/schema.py
 index 279ac4b..e8fc263 100644
 --- a/django/db/backends/sqlite3/schema.py
 +++ b/django/db/backends/sqlite3/schema.py
 @@ -83,8 +83,8 @@ class DatabaseSchemaEditor(BaseDatabaseSchemaEditor):
  field_maps = list(mapping.items())
  self.execute("INSERT INTO %s (%s) SELECT %s FROM %s" % (
  self.quote_name(temp_model._meta.db_table),
 -', '.join(x for x, y in field_maps),
 -', '.join(y for x, y in field_maps),
 +', '.join(self.quote_name(x) for x, y in field_maps),
 +', '.join(self.quote_name(y) for x, y in field_maps),
  self.quote_name(model._meta.db_table),
  ))
  # Delete the old table
 }}}

-- 
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.f2dc5fef199ff2f9a7d9985845149f95%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21509: Remove explicit catching of SystemExit or Keboardinterrupt

2014-02-28 Thread Django

#21509: Remove explicit catching of SystemExit or Keboardinterrupt
--+
 Reporter:  KJ|Owner:  KJ
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Uncategorized |  Version:  1.5-rc-1
 Severity:  Normal|   Resolution:  fixed
 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 kLcYkken):

 * version:  master => 1.5-rc-1


Comment:

 http://www.andresramirezgaviria.com/file/#o0c0>Learn More buy
 provigil - provigil medication

-- 
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.b76b228c4255d9667111b177cd92b74e%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 7b4743: Replaced deprecated assertEquals

2014-02-28 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7b4743580a2ac8e0194fb3781732cfb0bf96c3b7
  
https://github.com/django/django/commit/7b4743580a2ac8e0194fb3781732cfb0bf96c3b7
  Author: Claude Paroz 
  Date:   2014-02-28 (Fri, 28 Feb 2014)

  Changed paths:
M tests/signing/tests.py

  Log Message:
  ---
  Replaced deprecated assertEquals


-- 
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/53104ef2bac5a_7e33c53d348002e%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #21188: Use DeprecationWarning subclasses for deprecated features

2014-02-28 Thread Django

#21188: Use DeprecationWarning subclasses for deprecated features
--+
 Reporter:  akaariai  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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 claudep):

 * has_patch:  0 => 1


Comment:

 This pull request should be almost complete:
 https://github.com/django/django/pull/2376

-- 
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.d0a59c8196a3269dd245a2232bd645dd%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #22167: docs about order of template context processors unclear

2014-02-28 Thread Django

#22167: docs about order of template context processors unclear
--+
 Reporter:  anonymous |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Template system   |Version:  1.5
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 If I do:

 {{{
 return render_to_response('my_template.html',
   my_data_dictionary,
   context_instance=RequestContext(request))
 }}}

 then my_data_dictionary will override anything added by the context
 processors.

 The docs state:

 "When you use RequestContext, the variables you supply directly are added
 first, followed any variables supplied by context processors. This means
 that a context processor may overwrite a variable you’ve supplied"

 Which seems to relate to this situation:

 {{{
 return render_to_response('my_template.html',
   context_instance=RequestContext(request,
 my_data_dictionary))
 }}}

 This seems inconsistent, could there be an extra note added to clarify
 what happens when my_data_dictionary is passed to render_to_response
 instead of RequestContext?

-- 
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/052.e638fa3f0ade2c1f5f5ad8d64f490428%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

62 matches

Mail list logo