Re: [Django] #17159: Paginator.Page() should throw an exception for invalid [next|previous]_page_number()

[Django]

#17159: Paginator.Page() should throw an exception for invalid
[next|previous]_page_number()
+--
 Reporter:  mehta.apurva@…  |Owner:  mehta.apurva@…
 Type:  New feature |   Status:  reopened
Component:  Core (Other)|  Version:  1.3
 Severity:  Normal  |   Resolution:
 Keywords:  paginator core  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by julien):

 * needs_docs:  0 => 1
 * needs_tests:  0 => 1


Comment:

 Thank you. This would now need some tests and documentation
 (https://docs.djangoproject.com/en/dev/topics/pagination/).

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17176: Problem when retrieving objects with AND over multiple OR statements

[Django]

#17176: Problem when retrieving objects with AND over multiple OR statements
--+
 Reporter:  hanson2010|  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 I'm using Django 1.3 on MongoDB, and met a weird situation.

 Project.objects.filter(
 Q(owner=u'A') | Q(owner=u'B'),
 Q(owner=u'C') | Q(owner=u'D'),
 )

 The above returned queryset is same to
 Project.objects.filter(Q(owner=u'C') | Q(owner=u'D')), but not '''None''',
 as expected. It seems that the first half lookup function was omitted.

 Does someone know that it's problem with Django or third-party mongodb-
 engine libraries? Thanks in ad!

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17159: Paginator.Page() should throw an exception for invalid [next|previous]_page_number()

[Django]

#17159: Paginator.Page() should throw an exception for invalid
[next|previous]_page_number()
+--
 Reporter:  mehta.apurva@…  |Owner:  mehta.apurva@…
 Type:  New feature |   Status:  reopened
Component:  Core (Other)|  Version:  1.3
 Severity:  Normal  |   Resolution:
 Keywords:  paginator core  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by aaugustin):

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


Comment:

 Please don't mark tickets as fixed until the fix is actually committed to
 the code base.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17161: Call super in BaseForm.__init__

[Django]

#17161: Call super in BaseForm.__init__
--+--
 Reporter:  reames@…  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.3
 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 davidfstr):

 * needs_better_patch:   => 0
 * component:  Uncategorized => Forms
 * needs_tests:   => 0
 * needs_docs:   => 0


Comment:

 I believe if you reorder the superclasses, adding the call to super() is
 not necessary. For example:

 {{{
 class MyForm(FormMixin, forms.Form):
   field1 = forms.CharField()
 }}}

 I would normally add a mixin in this order anyway since I normally have
 the mixin override the superclass instead of inserting a mixin to be
 called by the superclass.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17159: Paginator.Page() should throw an exception for invalid [next|previous]_page_number()

[Django]

#17159: Paginator.Page() should throw an exception for invalid
[next|previous]_page_number()
+--
 Reporter:  mehta.apurva@…  |Owner:  mehta.apurva@…
 Type:  New feature |   Status:  closed
Component:  Core (Other)|  Version:  1.3
 Severity:  Normal  |   Resolution:  fixed
 Keywords:  paginator core  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  1   |UI/UX:  0
+--
Changes (by amehta):

 * status:  new => closed
 * has_patch:  0 => 1
 * resolution:   => fixed


Comment:

 Updated the functions to call Page.paginator.validate_number()

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16822: HTTPRequest::raw_post_data broken for tests

[Django]

#16822: HTTPRequest::raw_post_data broken for tests
---+--
 Reporter:  Whitney|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Testing framework  |  Version:
 Severity:  Normal |   Resolution:
 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 davidfstr):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16986: Model.clean cannot report errors on individual fields

[Django]

#16986: Model.clean cannot report errors on individual fields
-+-
 Reporter:  davidfstr|Owner:  davidfstr
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  SVN
 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 davidfstr):

 * needs_better_patch:  1 => 0


Comment:

 Clearing the "Patch needs improvement" flag, based on guidance from
 [https://docs.djangoproject.com/en/dev/internals/contributing/triaging-
 tickets/].

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16986: Model.clean cannot report errors on individual fields

[Django]

#16986: Model.clean cannot report errors on individual fields
-+-
 Reporter:  davidfstr|Owner:  davidfstr
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by davidfstr):

 * owner:  nobody => davidfstr


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17155: ModelForm.clean() return value not applied to instance when used in a modelformset

[Django]

#17155: ModelForm.clean() return value not applied to instance when used in a
modelformset
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  SVN
 Severity:  Normal |   Resolution:  worksforme
 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 anonymous):

 My sincere apologies for the time wasted. It helps to not put the field
 you're altering into the form's {{{exclude}}}.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10870: Aggregates with joins ignore extra filters provided by setup_joins

[Django]

#10870: Aggregates with joins ignore extra filters provided by setup_joins
-+-
 Reporter:  fas  |Owner:  fas
 Type:  Bug  |   Status:  new
Component:  ORM aggregation  |  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  orm, aggregation,| Triage Stage:  Accepted
  join, contenttypes, filter |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by alanjds):

 * cc: alanjds (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17155: ModelForm.clean() return value not applied to instance when used in a modelformset

[Django]

#17155: ModelForm.clean() return value not applied to instance when used in a
modelformset
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Forms  |  Version:  SVN
 Severity:  Normal |   Resolution:  worksforme
 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 claudep):

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


Comment:

 Attached is a test that is currently passing. If you can make a test that
 fails, then please reopen the ticket.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  SVN
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle postgresql|  Needs documentation:  0
  mysql schemas  |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-
Changes (by carbonXT):

 * cc: mike@… (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #17175: Pronunciation

[Django]

#17175: Pronunciation
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 JANG-O isn't the same as the correct pronunciation for Django. It omits
 the voiced /g/ in the middle of the word. It's really JANG-GO. The
 provided audio clip makes this clear, but the preceding text, e.g. FANG-O,
 is misleading.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17170: django.forms.fields.CharField.widget_attrs wrong return

[Django]

#17170: django.forms.fields.CharField.widget_attrs wrong return
+
 Reporter:  tsabi   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Forms   |  Version:  1.3
 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 julien):

 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17145: Documentation lacking import paths

[Django]

#17145: Documentation lacking import paths
---+--
 Reporter:  drozzy@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.3
 Severity:  Normal |   Resolution:
 Keywords:  imports| Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by aaugustin):

 > where does one import !TemplateResponseMixin from?

 The reference page (your link) begins with a link to the topic page, where
 you can see that class-based generic views live in `django.views.generic`.

 

 > This has always been a problem throughout the Django docs.

 I agree that import paths must be included in the docs. But I don't find
 it realistic to keep a ticket that basically says "read all the docs and
 add missing import paths" — especially when that ticket doesn't come with
 a patch, so I'm reluctant to accept this.

 

 > Is there a way to consistently document this?

 The usual approach is to include import statement in code snippets.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17073: focus uwsgi docs to only Django integration

[Django]

#17073: focus uwsgi docs to only Django integration
--+
 Reporter:  ptone |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by aaugustin):

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


Comment:

 Patch applies cleanly with `curl -k
 https://github.com/django/django/pull/69.diff | patch -p1`.

 However, there's a warning when building the docs:

 {{{
 docs/howto/deployment/wsgi/uwsgi.txt:39: (ERROR/3) Unknown target name:
 "configuration documentation".
 }}}

 Otherwise the patch looks sane.

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17174: The docs should mention, that MySql doesn't support microseconds

[Django]

#17174: The docs should mention, that MySql doesn't support microseconds
---+
 Reporter:  jammon |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Documentation  |  Version:  1.3
 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 aaugustin):

 * owner:  aaugustin => nobody
 * status:  assigned => new
 * 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #10870: Aggregates with joins ignore extra filters provided by setup_joins

[Django]

#10870: Aggregates with joins ignore extra filters provided by setup_joins
-+-
 Reporter:  fas  |Owner:  fas
 Type:  Bug  |   Status:  new
Component:  ORM aggregation  |  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  orm, aggregation,| Triage Stage:  Accepted
  join, contenttypes, filter |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ris):

 * cc: ris (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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #11118: BaseCommand doesn't restore translation

[Django]

#8: BaseCommand doesn't restore translation
-+-
 Reporter:  rvdrijst |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  SVN
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  basecommand execute  |  checkin
  syncdb translation testing |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ramiro):

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


Comment:

 In [17077]:
 {{{
 #!CommitTicketReference repository="" revision="17077"
 Fixed #8 -- Made management command BaseCommand restore locale after
 execution.

 Thanks rvdrijst for the report and initial patch and Claude Paroz for
 enhancing it.
 }}}

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r17077 - in django/trunk: django/core/management tests/modeltests/user_commands

[noreply]

Author: ramiro
Date: 2011-11-07 03:28:31 -0800 (Mon, 07 Nov 2011)
New Revision: 17077

Modified:
   django/trunk/django/core/management/base.py
   django/trunk/tests/modeltests/user_commands/tests.py
Log:
Fixed #8 -- Made management command BaseCommand restore locale after 
execution.

Thanks rvdrijst for the report and initial patch and Claude Paroz for enhancing 
it.

Modified: django/trunk/django/core/management/base.py
===
--- django/trunk/django/core/management/base.py 2011-11-07 07:41:24 UTC (rev 
17076)
+++ django/trunk/django/core/management/base.py 2011-11-07 11:28:31 UTC (rev 
17077)
@@ -203,9 +203,11 @@
 # like permissions, and those shouldn't contain any translations.
 # But only do this if we can assume we have a working settings file,
 # because django.utils.translation requires settings.
+saved_lang = None
 if self.can_import_settings:
 try:
 from django.utils import translation
+saved_lang = translation.get_language()
 translation.activate('en-us')
 except ImportError, e:
 # If settings should be available, but aren't,
@@ -232,6 +234,8 @@
 except CommandError, e:
 self.stderr.write(smart_str(self.style.ERROR('Error: %s\n' % e)))
 sys.exit(1)
+if saved_lang is not None:
+translation.activate(saved_lang)
 
 def validate(self, app=None, display_num_errors=False):
 """

Modified: django/trunk/tests/modeltests/user_commands/tests.py
===
--- django/trunk/tests/modeltests/user_commands/tests.py2011-11-07 
07:41:24 UTC (rev 17076)
+++ django/trunk/tests/modeltests/user_commands/tests.py2011-11-07 
11:28:31 UTC (rev 17077)
@@ -3,6 +3,7 @@
 from django.core import management
 from django.core.management.base import CommandError
 from django.test import TestCase
+from django.utils import translation
 
 
 class CommandTests(TestCase):
@@ -18,5 +19,11 @@
 self.assertEqual(out.getvalue(),
 "I don't feel like dancing Jive.")
 
+def test_language_preserved(self):
+out = StringIO()
+with translation.override('fr'):
+management.call_command('dance', stdout=out)
+self.assertEqual(translation.get_language(), 'fr')
+
 def test_explode(self):
-self.assertRaises(CommandError, management.call_command, ('explode',))
\ No newline at end of file
+self.assertRaises(CommandError, management.call_command, ('explode',))

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17174: The docs should mention, that MySql doesn't support microseconds

[Django]

#17174: The docs should mention, that MySql doesn't support microseconds
---+--
 Reporter:  jammon |Owner:  aaugustin
 Type:  New feature|   Status:  assigned
Component:  Documentation  |  Version:  1.3
 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 aaugustin):

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


-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #17147: DecimalField causes inline formsets to disappear

[Django]

#17147: DecimalField causes inline formsets to disappear
---+--
 Reporter:  leith.john@…   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Forms  |  Version:  1.2
 Severity:  Normal |   Resolution:
 Keywords:  admin formset  | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by julien):

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


Comment:

 Raising a `ValidationError` is actually the way to return an error message
 to the user.

 Note that `models.fields.DecimalField.to_python()` catches a different
 error (`decimal.InvalidOperation`). Maybe the form field should also catch
 `decimal.InvalidOperation` instead of `DecimalException`.

 Could you please provide a minimal test case reproducing the problem
 you're facing?

-- 
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.