Re: [Django] #19736: ViewDoesNotExist exception in views.py

[Django]

#19736: ViewDoesNotExist exception in views.py
---+--
 Reporter:  rpq@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.4
 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 rpq@…):

 * cc: rpq@… (added)


Comment:

 Replying to [comment:1 claudep]:
 > I know this sort of error reporting has been much improved in Django
 1.5, please test with a recent Django and reopen if you can still
 reproduce.



 Thanks, I could confirm for you that this particular error reporting issue
 is fixed in 1.5.  You could update the ticket to reflect that if you want.

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

Re: [Django] #19044: Allow get_success_url to access self. object in DeletionMixin

[Django]

#19044: Allow get_success_url to access self. object in DeletionMixin
-+-
 Reporter:  anonymous|Owner:  charettes
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Generic views|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by charettes):

 Added a new patch based on nxvl and slurms work with a release note.

 Tests were rewritten because they were not failing without the
 `DeletionMixin.delete` fix since `self.object.slug` is still accessible
 after deletion. It's not the case with `self.object.id`.

 Also fixed some badly indented code while I was there.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19744: File-based session don't work with login_required decorators.

[Django]

#19744: File-based session don't work with login_required decorators.
---+
 Reporter:  NJ |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I am new to the Django Framework and still studying. And currently, I'm
 working on the session handling. At first I thought it has a conflict with
 the login feature but when I removed the login_required decorators, and it
 worked and there was a result in the request.session

 Is it because of the decorator or I'm just missing something

 Thanks for the help..

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

Re: [Django] #19044: Allow get_success_url to access self. object in DeletionMixin

[Django]

#19044: Allow get_success_url to access self. object in DeletionMixin
-+-
 Reporter:  anonymous|Owner:  charettes
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Generic views|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by charettes):

 * owner:  nxvl => charettes


Old description:

> Let's say I have object with parent set and once object is deleted,
> browser should be redirected to parent page.
> Expected way to work is:
> url(r'^object/(?P\d+)/delete/$', DeleteView.as_view(model=Object,
> success_url='/parent/%(parent_id)d/'), name='object_delete'),
>

> This can be achieved by evaluating success_url first and then deleting
> object:
> class DeletionMixin(object):
> """
> A mixin providing the ability to delete objects
> """
> success_url = None
>
> def delete(self, request, *args, **kwargs):
> self.object = self.get_object()
> success_url = self.get_success_url()
> self.object.delete()
> return HttpResponseRedirect(success_url)
>
> # Add support for browsers which only accept GET and POST for now.
> def post(self, *args, **kwargs):
> return self.delete(*args, **kwargs)
>
> def get_success_url(self):
> if self.success_url:
> return self.success_url % self.object.__dict__
> else:
> raise ImproperlyConfigured(
> "No URL to redirect to. Provide a success_url.")

New description:

 Let's say I have object with parent set and once object is deleted,
 browser should be redirected to parent page.

 Expected way to work is:
 {{{
 #!python
 url(r'^object/(?P\d+)/delete/$', DeleteView.as_view(model=Object,
 success_url='/parent/%(parent_id)d/'), name='object_delete')
 }}}

 This can be achieved by evaluating success_url first and then deleting
 object:
 {{{
 #!python
 class DeletionMixin(object):
 """
 A mixin providing the ability to delete objects
 """
 success_url = None

 def delete(self, request, *args, **kwargs):
 self.object = self.get_object()
 success_url = self.get_success_url()
 self.object.delete()
 return HttpResponseRedirect(success_url)

 # Add support for browsers which only accept GET and POST for now.
 def post(self, *args, **kwargs):
 return self.delete(*args, **kwargs)

 def get_success_url(self):
 if self.success_url:
 return self.success_url % self.object.__dict__
 else:
 raise ImproperlyConfigured(
 "No URL to redirect to. Provide a success_url.")
 }}}

--

Comment:

 Assigning to myself since I'm planning to commit this.

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

Re: [Django] #19686: Support HTML5 number input type

[Django]

#19686: Support HTML5 number input type
-+
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by charettes):

 All tests pass on Python 2.7.3 SQLite3.

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

Re: [Django] #18174: Model inheritance pointers doesn't refer to parent to refer to grandparents

[Django]

#18174: Model inheritance pointers doesn't refer to parent to refer to 
grandparents
-+-
 Reporter:  phowe|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.4
  (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 carljm):

 Replying to [comment:8 pnhowe]:
 > Any word if this patch will be considered and Merged?

 The next step here is for someone other than the patch author to review
 the patch and try it out. If they think the code looks ok, and can verify
 that it solves the problem and all tests pass, they can mark it Ready For
 Checkin and that will help bring it to the attention of a core developer
 for commit. Feel free to recruit someone to do that if you want to move
 things along!

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

Re: [Django] #18174: Model inheritance pointers doesn't refer to parent to refer to grandparents

[Django]

#18174: Model inheritance pointers doesn't refer to parent to refer to 
grandparents
-+-
 Reporter:  phowe|Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Database layer   |  Version:  1.4
  (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 pnhowe):

 Any word if this patch will be considered and Merged?

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

Re: [Django] #19686: Support HTML5 number input type

[Django]

#19686: Support HTML5 number input type
-+
 Reporter:  claudep  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Forms|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by charettes):

 * needs_better_patch:  1 => 0


Comment:

 Attached a version of claudep's patch with additionnal tests and a fix
 for`DecimalField`'s input `"maxlength"`.

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

Re: [Django] #19689: Deprecate `Options.module_name` in favor of `model_name`

[Django]

#19689: Deprecate `Options.module_name` in favor of `model_name`
-+-
 Reporter:  charettes|Owner:  charettes
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by charettes):

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


Comment:

 Added a patch with release note and deprecation timeline entry. I'd
 appreciate if someone could take a look at my wording.

 All tests pass on Python 2.7.3 SQLite3.

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

Re: [Django] #19689: Deprecate `Options.module_name` in favor of `model_name` (was: Use `Options.module_name` instead of `object_name.lower()`)

[Django]

#19689: Deprecate `Options.module_name` in favor of `model_name`
-+-
 Reporter:  charettes|Owner:  charettes
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  1|
Easy pickings:  0|
-+-
Changes (by charettes):

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


Comment:

 Added a patch that raises a warning when accessing `module_name` and
 returns the newly introduced `model_name`.

 Also made some cleanup in `django/contrib/auth/context_processors.py`
 since it was manipulating `app_label`s using a variable/parameter named
 `module_name`.

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

Re: [Django] #6262: Cache templates

[Django]

#6262: Cache templates
-+-
   Reporter:  SmileyChris|Owner:  mmalone
   Type: |   Status:  closed
  Component:  Template system|  Version:  master
   Severity: |   Resolution:  fixed
   Keywords: | Triage Stage:  Design
  Has patch:  1  |  decision needed
Needs tests:  0  |  Needs documentation:  0
 |  Patch needs improvement:  0
-+-

Comment (by Ramiro Morales ):

 In [changeset:"826d9de00e74a53d7cc65fcb2aaa5ccdf33674ab"]:
 {{{
 #!CommitTicketReference repository=""
 revision="826d9de00e74a53d7cc65fcb2aaa5ccdf33674ab"
 Fixed #19729 -- Removed leftover refactoring helper variables.

 Thanks chrismedrela for the report.

 Refs #6262, 44b9076 and 4d94c0c.
 }}}

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

Re: [Django] #19729: Leftover `_loader` variable in template loader modules

[Django]

#19729: Leftover `_loader` variable in template loader modules
-+-
 Reporter:  aaugustin|Owner:
 Type:   |  chrismedrela
  Cleanup/optimization   |   Status:  closed
Component:  Template system  |  Version:  master
 Severity:  Normal   |   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
-+-
Changes (by Ramiro Morales ):

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


Comment:

 In [changeset:"826d9de00e74a53d7cc65fcb2aaa5ccdf33674ab"]:
 {{{
 #!CommitTicketReference repository=""
 revision="826d9de00e74a53d7cc65fcb2aaa5ccdf33674ab"
 Fixed #19729 -- Removed leftover refactoring helper variables.

 Thanks chrismedrela for the report.

 Refs #6262, 44b9076 and 4d94c0c.
 }}}

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

[django/django] 826d9d: Fixed #19729 -- Removed leftover refactoring helpe...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 826d9de00e74a53d7cc65fcb2aaa5ccdf33674ab
  
https://github.com/django/django/commit/826d9de00e74a53d7cc65fcb2aaa5ccdf33674ab
  Author: Ramiro Morales 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M django/template/loaders/app_directories.py
M django/template/loaders/eggs.py
M django/template/loaders/filesystem.py

  Log Message:
  ---
  Fixed #19729 -- Removed leftover refactoring helper variables.

Thanks chrismedrela for the report.

Refs #6262, 44b9076 and 4d94c0c.



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

Re: [Django] #19731: previous values of ManyToManyField in model's save method

[Django]

#19731: previous values of ManyToManyField in model's save method
-+-
 Reporter:  s4mmael@…|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
  manytomanyfield,save,previous  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by russellm):

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


Comment:

 You've been caught by a leaky abstraction. M2M relationships aren't saved
 as part of the save() method.

 In the admin, the main object is saved, and then the m2m relation is
 saved; so, by serializing the list of tags in the save method, you're
 printing the value of the tags before the new values have been saved.

 If you want to install "post m2m save" behavior, you'd need to override
 the update view on the admin itself.

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

Re: [Django] #17379: Don't force output of the 'shell' management command to en-us

[Django]

#17379: Don't force output of the 'shell' management command to en-us
-+-
 Reporter:  chrischambers|Owner:  ramiro
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  master
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  management, shell,   |  Needs documentation:  1
  i18n, l10n, en-us, translation,|  Patch needs improvement:  1
  documentation  |UI/UX:  0
Has patch:  1|
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by ramiro):

 #19737 proposes deprecating the shell command. If accepted, that would
 turn this ticket irrelevant.

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

[Django] #19743: Document limitations of django.contrib.auth

[Django]

#19743: Document limitations of django.contrib.auth
+
   Reporter:  aaugustin |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Documentation |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 django.contrib.auth aims to be very generic and doesn't provide some
 features commonly found in web authentication systems:

 - password strength checking: requirements depend very much on the
 context.
 - throttling of login attempts: possible with a custom auth backend, for
 example https://github.com/brutasse/django-ratelimit-backend (I haven't
 audited that code)
 - external auth providers: possible with a custom auth backend, there are
 several third-party apps providing this feature.

 The documentation should point out that these features aren't implemented
 to raise awareness.

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

Re: [Django] #13320: loaddata and syncdb should use the python logging

[Django]

#13320: loaddata and syncdb should use the python logging
---+--
 Reporter:  chtito |Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Uncategorized  |  Version:
 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 anonymous):

 * status:  closed => new
 * severity:   => Normal
 * type:   => Uncategorized
 * version:  1.1 =>
 * easy:   => 0
 * ui_ux:   => 0
 * resolution:  duplicate =>


Comment:

 Sorry to bother, but since #12012 is closed and syncdb still uses
 self.stdout.write, I believe this ticket should be re-opened.

 If using stdout.write was intentional decision, please write a short
 clarification (so those who wonder won't re-ask and re-open this) and
 close this 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 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19529: Searching documentation for "class based views" gives ten times the same result

[Django]

#19529: Searching documentation for "class based views" gives ten times the same
result
-+-
 Reporter:  wim@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  documentation,   | Triage Stage:  Accepted
  search |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by aaugustin):

 As discussed on IRC, xapian is used in production, whoosh in development.

 Versions are pinned in the requirements file.

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

Re: [Django] #19734: missing values in DATETIME_INPUT_FORMATS docs

[Django]

#19734: missing values in DATETIME_INPUT_FORMATS docs
-+-
 Reporter:  minddust |Owner:  charettes
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 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 Simon Charette ):

 In [changeset:"5c70299a712434c8f1b2156230634913c6a0c813"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5c70299a712434c8f1b2156230634913c6a0c813"
 Fixed #19734 -- Missing values in `DATETIME_INPUT_FORMATS` doc.

 Also changed formating of `DATE_INPUT_FORMATS` and
 `TIME_INPUT_FORMATS` for readability.

 Thanks minddust for the report!
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19734: missing values in DATETIME_INPUT_FORMATS docs

[Django]

#19734: missing values in DATETIME_INPUT_FORMATS docs
-+-
 Reporter:  minddust |Owner:  charettes
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 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 Simon Charette ):

 In [changeset:"f58aae9311ade7a59ca97ec1e5dee7c08ab86f28"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f58aae9311ade7a59ca97ec1e5dee7c08ab86f28"
 [1.5.x] Fixed #19734 -- Missing values in `DATETIME_INPUT_FORMATS` doc.

 Also changed formating of `DATE_INPUT_FORMATS` and
 `TIME_INPUT_FORMATS` for readability.

 Thanks minddust for the report!

 Backport of 5c70299a71 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19737: Deprecate and then remove "shell" management command

[Django]

#19737: Deprecate and then remove "shell" management command
-+-
 Reporter:  carljm   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by jezdez):

 <3

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

Re: [Django] #19734: missing values in DATETIME_INPUT_FORMATS docs

[Django]

#19734: missing values in DATETIME_INPUT_FORMATS docs
-+-
 Reporter:  minddust |Owner:  charettes
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 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 charettes):

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


Comment:

 Fixed on [https://github.com/django/django/commit/5c70299a71 master] and
 on
 
[https://github.com/django/django/commit/f58aae9311ade7a59ca97ec1e5dee7c08ab86f28
 1.5.x]

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

[django/django] f58aae: [1.5.x] Fixed #19734 -- Missing values in `DATETIM...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: f58aae9311ade7a59ca97ec1e5dee7c08ab86f28
  
https://github.com/django/django/commit/f58aae9311ade7a59ca97ec1e5dee7c08ab86f28
  Author: Simon Charette 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  [1.5.x] Fixed #19734 -- Missing values in `DATETIME_INPUT_FORMATS` doc.

Also changed formating of `DATE_INPUT_FORMATS` and
`TIME_INPUT_FORMATS` for readability.

Thanks minddust for the report!

Backport of 5c70299a71 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19742: Missing blog post appears at the top of community feed

[Django]

#19742: Missing blog post appears at the top of community feed
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component: |   Keywords:
  Djangoproject.com Web site |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 [originally reported by IlianIliev at
 https://github.com/django/djangoproject.com/issues/34]

 For a few weeks the "Goodbye iOS, hello Android" post is staying at the
 top of the community feed. I wondered about no one posting for such a long
 time when I realized that this is this post just constantly changes its
 date to keep on the top.

 Probable this have something in common with the fact that the post page
 returns 404.

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

[django/django] 5c7029: Fixed #19734 -- Missing values in `DATETIME_INPUT_...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5c70299a712434c8f1b2156230634913c6a0c813
  
https://github.com/django/django/commit/5c70299a712434c8f1b2156230634913c6a0c813
  Author: Simon Charette 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M docs/ref/settings.txt

  Log Message:
  ---
  Fixed #19734 -- Missing values in `DATETIME_INPUT_FORMATS` doc.

Also changed formating of `DATE_INPUT_FORMATS` and
`TIME_INPUT_FORMATS` for readability.

Thanks minddust for the report!



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

[django/django] 7a90c6: [1.5.x] Updated translations (bn/es/eu/lb/mn)

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: 7a90c6adccb57eb27b363c9cffc759243e17ed1f
  
https://github.com/django/django/commit/7a90c6adccb57eb27b363c9cffc759243e17ed1f
  Author: Claude Paroz 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M django/conf/locale/bn/LC_MESSAGES/django.mo
M django/conf/locale/bn/LC_MESSAGES/django.po
M django/conf/locale/es/LC_MESSAGES/django.mo
M django/conf/locale/es/LC_MESSAGES/django.po
M django/conf/locale/lb/LC_MESSAGES/django.mo
M django/conf/locale/lb/LC_MESSAGES/django.po
M django/contrib/admin/locale/eu/LC_MESSAGES/django.mo
M django/contrib/admin/locale/eu/LC_MESSAGES/django.po
M django/contrib/admin/locale/mn/LC_MESSAGES/django.mo
M django/contrib/admin/locale/mn/LC_MESSAGES/django.po

  Log Message:
  ---
  [1.5.x] Updated translations (bn/es/eu/lb/mn)



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

[Django] #19741: Procedure in README.txt for setting up djangoproject locally doesn't work

[Django]

#19741: Procedure in README.txt for setting up djangoproject locally doesn't 
work
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  master
  Djangoproject.com Web site |   Keywords:
   Severity:  Normal |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 [originally reported by eswenson1 at
 https://github.com/django/djangoproject.com/issues/28]

 '''eswenson1'''

 The current procedures described in README.txt for setting up the
 djangoproject locally don't work. This appears to be because they assume
 that you already have a trac database setup properly with the correct
 schema. When the ./manage.py migrate step is executed, it fails due to
 missing relations from the trac model. In particular, the migration fails
 with the following error:

 Running migrations for trac:

 {{{
 > Migrating forwards to 0001_initial.
 > trac:0001_initial ERROR: relation "attachment" does not exist STATEMENT:
 CREATE VIEW "attachment_django_view" AS SELECT "type" || '.' || "id" ||
 '.' || "filename" AS "django_id", * FROM attachment;
 }}}

 Perhaps you could provide a truncated database dump from the live trac
 instance so that this can be used to create a dummy trac database.

 I decided to try to simply install Trac (0.12) and specify a database
 connection string that pointed to the code.djangoproject database. Once I
 did that, I was able to run the "./manage.py migrate" with no errors. The
 server started up fine after that.

 ''dlo'''

 Pull request: https://github.com/django/djangoproject.com/pull/46

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

[Django] #19740: Make sure only posts not marked as defunct show up in feed

[Django]

#19740: Make sure only posts not marked as defunct show up in feed
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  master
  Djangoproject.com Web site |   Keywords:
   Severity:  Normal |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 [originally reported by jezdez at
 https://github.com/django/djangoproject.com/issues/27]

 '''jezdez'''

 A bunch of feeds from David Larlet's blog showed up in the feed even
 though the feed object was marked as defunct.

 http://jzdz.me/F5Mr

 '''aaugustin'''

 defunct is used only in
 `django_website.aggregator.templatetags.aggregator`, and that module is
 dead code -- the `{% get_feed_list %}` tag doesn't appear to be used
 anywhere.

 Jacob says the proper fix is to add a try/catch around the call to
 unsubscribe:
 
https://github.com/django/djangoproject.com/blob/master/django_website/aggregator/models.py#L37

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

[Django] #19739: Implement accessibility for the visually impaired

[Django]

#19739: Implement accessibility for the visually impaired
-+-
   Reporter:  aaugustin  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  master
  Component: |   Keywords:
  Djangoproject.com Web site |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 [originally reported by pydanny at
 https://github.com/django/djangoproject.com/issues/28]

 '''pydanny'''

 Using a screen reader on djangoproject.com is not a pleasant experience.
 Please see the following:

 - http://www.w3.org/WAI/
 - http://www.section508.gov

 '''jacobian'''

 (This came up during Jessica's DjangoCon Europe keynote; it's something we
 didn't want to forget during the redesign. Danny will help.)

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

Re: [Django] #19734: missing values in DATETIME_INPUT_FORMATS docs

[Django]

#19734: missing values in DATETIME_INPUT_FORMATS docs
-+-
 Reporter:  minddust |Owner:  charettes
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   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 charettes):

 * status:  new => assigned
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * owner:  nobody => charettes
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19738: "manage.py shell" on a fresh project raises RuntimeWarning about naive datetime, if IPython is installed

[Django]

#19738: "manage.py shell" on a fresh project raises RuntimeWarning about naive
datetime, if IPython is installed
-+-
 Reporter:  carljm   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by charettes):

 * stage:  Unreviewed => Accepted


Comment:

 I've also been experiencing this issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19736: ViewDoesNotExist exception in views.py

[Django]

#19736: ViewDoesNotExist exception in views.py
---+--
 Reporter:  rpq@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  HTTP handling  |  Version:  1.4
 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:

 I know this sort of error reporting has been much improved in Django 1.5,
 please test with a recent Django and reopen if you can still reproduce.

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

Re: [Django] #19735: Sometimes string interpolation is needed in templates

[Django]

#19735: Sometimes string interpolation is needed in templates
-+-
 Reporter:  aalexgabi|Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  filter,  | Triage Stage:  Design
  interpolation  |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by carljm):

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


Comment:

 I don't think this is nearly a common enough need to warrant adding a new
 built-in filter to Django. There's a reason Django lets you write your own
 filters and tags when you need them, and this one is easy enough to write
 for those who want 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 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19735: Sometimes string interpolation is needed in templates

[Django]

#19735: Sometimes string interpolation is needed in templates
-+-
 Reporter:  aalexgabi|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  filter,  | Triage Stage:  Design
  interpolation  |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-

Comment (by anonymous):

 (Reading the Stack Overflow question) I don't understand what's the
 relationship with translation.

 If you need to interpolate and translate you can simply use the blocktrans
 tag in the i18n template library.

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

Re: [Django] #19237: The use of > in single or double quoted attributes in strip_tags

[Django]

#19237: The use of > in single or double quoted attributes in strip_tags
-+---
 Reporter:  chris.khoo@… |Owner:  khoomeister
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  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:  0|UI/UX:  0
-+---

Comment (by Pablo Recio ):

 I'm not a regex guru, but it seems good for me. Although, I feel that this
 stuff should be either reverted or adding a really big batch of tests for
 releasing this into 1.5. Just my humble thought.

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

Re: [Django] #19738: "manage.py shell" on a fresh project raises RuntimeWarning about naive datetime, if IPython is installed

[Django]

#19738: "manage.py shell" on a fresh project raises RuntimeWarning about naive
datetime, if IPython is installed
-+-
 Reporter:  carljm   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by carljm):

 * type:  Uncategorized => Bug
 * component:  Uncategorized => Database layer (models, ORM)


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

[Django] #19738: "manage.py shell" on a fresh project raises RuntimeWarning about naive datetime, if IPython is installed

[Django]

#19738: "manage.py shell" on a fresh project raises RuntimeWarning about naive
datetime, if IPython is installed
-+
   Reporter:  carljm |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  1.4
   Severity:  Normal |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+
 IPython uses SQLite internally to store shell session history. At the
 beginning and end of every shell session, it issues a SQLite query to
 get/save the history. For some reason this query includes a (timezone-
 naive) datetime.

 Django's SQLite DB backend registers a global datetime adapter function
 which issues a warning in case it receives a naive datetime when timezone
 support is activated.

 In combination, this means that on a fresh `startproject` if you fire up
 `manage.py shell` without making a single change to settings, if IPython
 is installed you'll get "RuntimeWarning: SQLite received a naive datetime
 (2013-02-04 17:14:13.070091) while time zone support is active." on shell
 startup and exit. That's an ugly experience for a newcomer to Django - it
 _looks_ to them as if Django is shipping a broken setup by default.

 Probably this is Django's fault for registering a potentially-noisy
 process-global SQLite adapter, and we should consider whether to just
 remove that warning in the adapter. The model layer will already warn
 about naive datetimes, so this warning is only needed for raw SQL.

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

Re: [Django] #19737: Deprecate and then remove "shell" management command

[Django]

#19737: Deprecate and then remove "shell" management command
-+-
 Reporter:  carljm   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by Alex):

 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19737: Deprecate and then remove "shell" management command

[Django]

#19737: Deprecate and then remove "shell" management command
-+-
 Reporter:  carljm   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Core (Management |   Resolution:
  commands)  | Triage Stage:
 Severity:  Normal   |  Unreviewed
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Description changed by carljm:

Old description:

> The only benefit of the "shell" management command is that it saves you
> from having to set the DJANGO_SETTINGS_MODULE env var, and instead
> automatically use the one set in ``manage.py``. This is a pretty minor
> benefit; it's not hard to use your favorite technique (alias, script,
> whatever) to reduce the number of characters you need to type to run
> ``DJANGO_SETTINGS_MODULE=someproj.settings python``, with the added
> advantage that you can easily use any python REPL you like without having
> to patch "shell" to explicitly support it.
>
> The downside of having "shell" in Django is that it's a non-trivial
> maintenance burden to decide which REPLs to support, add support for
> them, and then update/fix that support through the years. We've already
> seen a steady stream of tickets related to various edge-cases in IPython
> startup, not to mention the major API changes in recent IPython versions.
> There's no reason for Django to have to be maintaining code related to
> IPython.

New description:

 The only benefit of the "shell" management command is that it saves you
 from having to set the DJANGO_SETTINGS_MODULE env var, and instead
 automatically use the one set in `manage.py`. This is a pretty minor
 benefit; it's not hard to use your favorite technique (alias, script,
 whatever) to reduce the number of characters you need to type to run
 `DJANGO_SETTINGS_MODULE=someproj.settings python`, with the added
 advantage that you can easily use any python REPL you like without having
 to patch "shell" to explicitly support it.

 The downside of having "shell" in Django is that it's a non-trivial
 maintenance burden to decide which REPLs to support, add support for them,
 and then update/fix that support through the years. We've already seen a
 steady stream of tickets related to various edge-cases in IPython startup,
 not to mention the major API changes in recent IPython versions. There's
 no reason for Django to have to be maintaining code related to IPython.

--

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

[Django] #19737: Deprecate and then remove "shell" management command

[Django]

#19737: Deprecate and then remove "shell" management command
-+-
   Reporter:  carljm |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |Version:  1.4
  Component:  Core   |   Keywords:
  (Management commands)  |  Has patch:  0
   Severity:  Normal |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
 The only benefit of the "shell" management command is that it saves you
 from having to set the DJANGO_SETTINGS_MODULE env var, and instead
 automatically use the one set in ``manage.py``. This is a pretty minor
 benefit; it's not hard to use your favorite technique (alias, script,
 whatever) to reduce the number of characters you need to type to run
 ``DJANGO_SETTINGS_MODULE=someproj.settings python``, with the added
 advantage that you can easily use any python REPL you like without having
 to patch "shell" to explicitly support it.

 The downside of having "shell" in Django is that it's a non-trivial
 maintenance burden to decide which REPLs to support, add support for them,
 and then update/fix that support through the years. We've already seen a
 steady stream of tickets related to various edge-cases in IPython startup,
 not to mention the major API changes in recent IPython versions. There's
 no reason for Django to have to be maintaining code related to IPython.

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

[Django] #19736: ViewDoesNotExist exception in views.py

[Django]

#19736: ViewDoesNotExist exception in views.py
---+
 Reporter:  rpq@…  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  HTTP handling  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 ViewDoesNotExist exception is being raised even though my view function is
 correctly placed in the django view (views.py file). Upon further
 inspection I discovered there was an AttributeError being raised in one of
 my imported modules (a forms.py call to a missing model form's model).
 More testing revealed that raising an AttributeError anywhere in the
 django view *or* in any imported module before the view function that is
 executed generates a ViewDoesNotExist exception.

 Here's my traceback...

 {{{
 Traceback:
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/core/handlers/base.py" in get_response
   89. response = middleware_method(request)
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/middleware/common.py" in process_request
   67. if (not urlresolvers.is_valid_path(request.path_info,
 urlconf) and
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/core/urlresolvers.py" in is_valid_path
   531. resolve(path, urlconf)
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/core/urlresolvers.py" in resolve
   420. return get_resolver(urlconf).resolve(path)
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/core/urlresolvers.py" in resolve
   300. sub_match = pattern.resolve(new_path)
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/core/urlresolvers.py" in resolve
   300. sub_match = pattern.resolve(new_path)
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/core/urlresolvers.py" in resolve
   209. return ResolverMatch(self.callback, args, kwargs,
 self.name)
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/core/urlresolvers.py" in callback
   216. self._callback = get_callable(self._callback_str)
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/utils/functional.py" in wrapper
   27. result = func(*args)
 File "/home/ray/.python-ves/superkids/lib/python2.7/site-
 packages/django/core/urlresolvers.py" in get_callable
   101. (lookup_view, mod_name))
 }}}

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

Re: [Django] #19662: Explain correct `authenticate` usage with custom user model.

[Django]

#19662: Explain correct `authenticate` usage with custom user model.
-+--
 Reporter:  tomchristie  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.5-beta-1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+--

Comment (by shaneallgeier@…):

 I believe that `authenticate()` should be left as is (only expecting
 `username`). Otherwise, all DRY/pluggable authentication backends would
 have to first check the `USERNAME_FIELD` from the user model every time
 someone tries to authenticate. It would also require pluggable backends to
 check the Django version to figure out if it even needs to check for a
 possible `USERNAME_FIELD`. I know it won't be a difference in speed or
 anything, but it would still be annoying to write.

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

Re: [Django] #19735: Sometimes string interpolation is needed in templates

[Django]

#19735: Sometimes string interpolation is needed in templates
-+-
 Reporter:  aalexgabi|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Template system  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  filter,  | Triage Stage:  Design
  interpolation  |  decision needed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mjtamlyn):

 * needs_better_patch:   => 1
 * version:  1.4 =>
 * stage:  Unreviewed => Design decision needed
 * needs_tests:   => 1
 * needs_docs:   => 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19237: The use of > in single or double quoted attributes in strip_tags

[Django]

#19237: The use of > in single or double quoted attributes in strip_tags
-+---
 Reporter:  chris.khoo@… |Owner:  khoomeister
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  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:  0|UI/UX:  0
-+---
Changes (by claudep):

 * needs_better_patch:  1 => 0


Comment:

 I may have found it. Regex gurus needed :-)

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

Re: [Django] #19237: The use of > in single or double quoted attributes in strip_tags

[Django]

#19237: The use of > in single or double quoted attributes in strip_tags
-+---
 Reporter:  chris.khoo@… |Owner:  khoomeister
 Type:  Bug  |   Status:  new
Component:  Core (Other) |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+---
Changes (by claudep):

 * needs_better_patch:  0 => 1
 * severity:  Normal => Release blocker
 * easy:  1 => 0
 * stage:  Ready for checkin => Accepted


Comment:

 Yes, either we quickly find the flaw in the new regex or we should revert
 the commit.

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

[Django] #19735: Sometimes string interpolation is needed in templates

[Django]

#19735: Sometimes string interpolation is needed in templates
-+---
 Reporter:  aalexgabi|  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  Template system  |Version:  1.4
 Severity:  Normal   |   Keywords:  filter, interpolation
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  0
-+---
 Sometimes string interpolation is needed in templates. I.e.
 http://stackoverflow.com/questions/14626680/how-to-interpolate-already-
 translated-string-in-django-templates

 I made a pull request here https://github.com/django/django/pull/699

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

Re: [Django] #18986: Improve error message for broken CSS in CachedStaticFilesStorage

[Django]

#18986: Improve error message for broken CSS in CachedStaticFilesStorage
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  1.4
Component:  contrib.staticfiles  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by zyegfryed):

 I've updated the patch according to your concern : delegating error
 handling to the management command.
 Let me know whether you've thought of some other improvements.

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

[django/django] 40260b: Fixed error message test assertions under Python 3...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 40260bc30b11bfe0134107bf9dc82a0cd1dcd800
  
https://github.com/django/django/commit/40260bc30b11bfe0134107bf9dc82a0cd1dcd800
  Author: Claude Paroz 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M tests/regressiontests/file_storage/tests.py

  Log Message:
  ---
  Fixed error message test assertions under Python 3.3

Thanks Florian Apolloner for testing.



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

[Django] #19734: missing values in DATETIME_INPUT_FORMATS docs

[Django]

#19734: missing values in DATETIME_INPUT_FORMATS docs
--+
 Reporter:  minddust  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 here [https://docs.djangoproject.com/en/dev/ref/settings/#datetime-input-
 formats 1] are some values missing.

 current code:

 {{{#!python
 DATETIME_INPUT_FORMATS = (
 '%Y-%m-%d %H:%M:%S', # '2006-10-25 14:30:59'
 '%Y-%m-%d %H:%M:%S.%f',  # '2006-10-25 14:30:59.000200'
 '%Y-%m-%d %H:%M',# '2006-10-25 14:30'
 '%Y-%m-%d',  # '2006-10-25'
 '%m/%d/%Y %H:%M:%S', # '10/25/2006 14:30:59'
 '%m/%d/%Y %H:%M:%S.%f',  # '10/25/2006 14:30:59.000200'
 '%m/%d/%Y %H:%M',# '10/25/2006 14:30'
 '%m/%d/%Y',  # '10/25/2006'
 '%m/%d/%y %H:%M:%S', # '10/25/06 14:30:59'
 '%m/%d/%y %H:%M:%S.%f',  # '10/25/06 14:30:59.000200'
 '%m/%d/%y %H:%M',# '10/25/06 14:30'
 '%m/%d/%y',  # '10/25/06'
 )
 }}}

 current doc:

 {{{#!python
 DATETIME_INPUT_FORMATS = (
 '%Y-%m-%d %H:%M:%S',
 '%Y-%m-%d %H:%M',
 '%Y-%m-%d',
 '%m/%d/%Y %H:%M:%S',
 '%m/%d/%Y %H:%M',
 '%m/%d/%Y',
 '%m/%d/%y %H:%M:%S',
 '%m/%d/%y %H:%M',
 '%m/%d/%y'
 )
 }}}

 1: [https://docs.djangoproject.com/en/dev/ref/settings/#datetime-input-
 formats]

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

[django/django] 7c5b24: Fixed #17061 -- Factored out importing object from...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7c5b244826be636429791a8ca76b2adc678e82e7
  
https://github.com/django/django/commit/7c5b244826be636429791a8ca76b2adc678e82e7
  Author: Claude Paroz 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M django/conf/__init__.py
M django/contrib/admin/tests.py
M django/contrib/auth/__init__.py
M django/contrib/auth/hashers.py
M django/contrib/formtools/tests/wizard/loadstorage.py
M django/contrib/formtools/wizard/storage/__init__.py
M django/contrib/formtools/wizard/storage/exceptions.py
M django/contrib/messages/storage/__init__.py
M django/contrib/staticfiles/finders.py
M django/core/cache/__init__.py
M django/core/cache/backends/base.py
M django/core/files/storage.py
M django/core/files/uploadhandler.py
M django/core/handlers/base.py
M django/core/mail/__init__.py
M django/core/servers/basehttp.py
M django/core/signing.py
M django/db/utils.py
M django/template/context.py
M django/template/loader.py
M django/utils/module_loading.py
M django/views/debug.py
M tests/regressiontests/file_storage/tests.py
M tests/regressiontests/utils/module_loading.py
M tests/regressiontests/utils/tests.py
M tests/regressiontests/wsgi/tests.py

  Log Message:
  ---
  Fixed #17061 -- Factored out importing object from a dotted path

Thanks Carl Meyer for the report.



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

Re: [Django] #17061: Factor out "get a module-level object from a dotted path" function

[Django]

#17061: Factor out "get a module-level object from a dotted path" function
--+
 Reporter:  carljm|Owner:  claudep
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   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 Claude Paroz ):

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


Comment:

 In [changeset:"7c5b244826be636429791a8ca76b2adc678e82e7"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7c5b244826be636429791a8ca76b2adc678e82e7"
 Fixed #17061 -- Factored out importing object from a dotted path

 Thanks Carl Meyer for the report.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #14760: Admin inlines with file/image field fails to save_as

[Django]

#14760: Admin inlines with file/image field fails to save_as
-+-
 Reporter:  paulos   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by bmihelac):

 This pull request addresses assigning initial values for FileFields and
 its subclasses:

 https://github.com/django/django/pull/697

 What do you think?

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

[Django] #19733: Deprecate exclude in ModelForm

[Django]

#19733: Deprecate exclude in ModelForm
--+
 Reporter:  aaugustin |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Forms |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 See https://groups.google.com/d/topic/django-
 developers/io74RDWgiLw/discussion

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

Re: [Django] #19732: unable to use database view in test cases

[Django]

#19732: unable to use database view in test cases
---+--
 Reporter:  anonymous  |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 timo):

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


Comment:

 https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels

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

[django/django] 3f1c7b: Simplified default project template.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3f1c7b70537330435e2ec2fca9550f7b7fa4372e
  
https://github.com/django/django/commit/3f1c7b70537330435e2ec2fca9550f7b7fa4372e
  Author: Aymeric Augustin 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
A django/conf/app_template/admin.py
M django/conf/app_template/tests.py
M django/conf/app_template/views.py
M django/conf/project_template/project_name/settings.py
M django/conf/project_template/project_name/urls.py
M django/conf/project_template/project_name/wsgi.py
M django/core/management/templates.py
M django/views/debug.py
M docs/howto/deployment/wsgi/index.txt
M docs/howto/error-reporting.txt
M docs/intro/_images/admin02.png
M docs/intro/_images/admin02t.png
M docs/intro/_images/admin03.png
M docs/intro/_images/admin03t.png
M docs/intro/reusable-apps.txt
M docs/intro/tutorial01.txt
M docs/intro/tutorial02.txt
M docs/intro/tutorial05.txt
M docs/ref/clickjacking.txt
M docs/ref/contrib/admin/index.txt
M docs/ref/contrib/gis/tutorial.txt
M docs/ref/contrib/sites.txt
M docs/ref/django-admin.txt
M docs/ref/settings.txt
M docs/releases/1.6.txt
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  Simplified default project template.

Squashed commit of:

commit 508ec9144b35c50794708225b496bde1eb5e60aa
Author: Aymeric Augustin 
Date:   Tue Jan 29 22:50:55 2013 +0100

Tweaked default settings file.

* Explained why BASE_DIR exists.
* Added a link to the database configuration options, and put it in its
  own section.
* Moved sensitive settings that must be changed for production at the
  top.

commit 6515fd2f1aa73a86dc8dbd2ccf512ddb6b140d57
Author: Aymeric Augustin 
Date:   Tue Jan 29 14:35:21 2013 +0100

Documented the simplified app & project templates in the changelog.

commit 2c5b576c2ea91d84273a019b3d0b3b8b4da72f23
Author: Aymeric Augustin 
Date:   Tue Jan 29 13:59:27 2013 +0100

Minor fixes in tutorials 5 and 6.

commit 55a51531be8104f21b3cca3f6bf70b0a7139a041
Author: Aymeric Augustin 
Date:   Tue Jan 29 13:51:11 2013 +0100

Updated tutorial 2 for the new project template.

commit 29ddae87bdaecff12dd31b16b000c01efbde9e20
Author: Aymeric Augustin 
Date:   Tue Jan 29 11:58:54 2013 +0100

Updated tutorial 1 for the new project template.

commit 0ecb9f6e2514cfd26a678a280d471433375101a3
Author: Aymeric Augustin 
Date:   Tue Jan 29 11:29:13 2013 +0100

Adjusted the default URLconf detection to account for the admin.

It's now enabled by default.

commit 5fb4da0d3d09dac28dd94e3fde92b9d4335c0565
Author: Aymeric Augustin 
Date:   Tue Jan 29 10:36:55 2013 +0100

Added security warnings for the most sensitive settings.

commit 718d84bd8ac4a42fb4b28ec93965de32680f091e
Author: Aymeric Augustin 
Date:   Mon Jan 28 23:24:06 2013 +0100

Used an absolute path for the SQLite database.

This ensures the settings file works regardless of which directory
django-admin.py / manage.py is invoked from.

BASE_DIR got a +1 from a BDFL and another core dev. It doesn't involve
the concept of a "Django project"; it's just a convenient way to express
relative paths within the source code repository for non-Python files.

Thanks Jacob Kaplan-Moss for the suggestion.

commit 1b559b4bcda622e10909b68fe5cab90db6727dd9
Author: Aymeric Augustin 
Date:   Mon Jan 28 23:22:40 2013 +0100

Removed STATIC_ROOT from the default settings template.

It isn't necessary in development, and it confuses beginners to no end.

Thanks Carl Meyer for the suggestion.

commit a55f141a500bb7c9a1bc259bbe1954c13b199671
Author: Aymeric Augustin 
Date:   Mon Jan 28 23:21:43 2013 +0100

Removed MEDIA_ROOT/URL from default settings template.

Many sites will never deal with user-uploaded files, and MEDIA_ROOT is
complicated to explain.

Thanks Carl Meyer for the suggestion.

commit 44bf2f2441420fd9429ee9fe1f7207f92dd87e70
Author: Aymeric Augustin 
Date:   Mon Jan 28 22:22:09 2013 +0100

Removed logging config.

This configuration is applied regardless of the value of LOGGING;
duplicating it in LOGGING is confusing.

commit eac747e848eaed65fd5f6f254f0a7559d856f88f
Author: Aymeric Augustin 
Date:   Mon Jan 28 22:05:31 2013 +0100

Enabled the locale middleware by default.

USE_I18N is True by default, and doesn't work well without
LocaleMiddleware.

commit d806c62b2d00826dc2688c84b092627b8d571cab
Author: Aymeric Augustin 
Date:   Mon Jan 28 22:03:16 2013 +0100

Enabled clickjacking protection by default.

commit 99152c30e6a15003f0b6737dc78e87adf462aacb
Author: Aymeric Augustin 
Date:   Mon Jan 28 22:01:48 2013 +0100

Reorganized settings in logical sections, and trimmed comments.

commit d37ffdfcb24b7e0ec7cc113d07190f65fb12fb8a
Author: Aymeric Augustin 
Date:   Mon Jan 28 16:54:11 2013 +0100

Avoided misleading TEMPLATE_DE

[Django] #19732: unable to use database view in test cases

[Django]

#19732: unable to use database view in test cases
---+
 Reporter:  anonymous  |  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
---+
 unable to use database view in test cases. other hand i am able to use
 those database view in front end function . but when i try to get data
 from view in it return null in test case. Please give me suggestion for
 use database views in test cases

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

[django/django] 21ea58: Enhanced docs and docctrings added in 869c9ba.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 21ea58b8ccf95798271157876d59d46dcc745b0d
  
https://github.com/django/django/commit/21ea58b8ccf95798271157876d59d46dcc745b0d
  Author: Ramiro Morales 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M django/core/management/base.py
M docs/howto/custom-management-commands.txt
M docs/releases/1.6.txt

  Log Message:
  ---
  Enhanced docs and docctrings added in 869c9ba.

Thanks Claude 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.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19731: previous values of ManyToManyField in model's save method

[Django]

#19731: previous values of ManyToManyField in model's save method
-+-
 Reporter:  s4mmael@…|  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Database layer   |Version:  1.4
  (models, ORM)  |   Keywords:
 Severity:  Normal   |  manytomanyfield,save,previous
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Hello,

 I'm terribly sorry for bothering you, but I believe this behavior may be
 incorrect. I've already asked at django-users mailing list and I've had no
 answer.

 How to reproduce it:



 {{{
 class Tag(models.Model):
 name = models.CharField(max_length=50, unique=True, db_index=True)
 parent = ForeignKey('self', null=True, blank=True,
 related_name='children')

 class Album(models.Model):
 name = models.CharField(max_length=64, blank=True)
 tags = models.ManyToManyField(Tag, blank=True)
 def tags_(self):
 return ', '.join([t.name for t in self.tags.all()])
 def save(self, *args, **kwargs):
 super(Album, self).save(*args, **kwargs)
 f = open('/tmp/test.txt', 'wt')
 f.write('%s\n%s\n' % (self.name, self.tags_()))
 f.close
 }}}
 Now let's go to django admin and create two tags: tag1, tag2. After that
 let's create an album 'Album_1' with tag 'tag1' and save the album. In the
 file /tmp/test.txt we see:

 
 Album_1

 


 Let's add tag2 to the album, change it's name to Album_2 and save. The
 file will be:

 
 Album_2
 tag1
 

 Let's remove both tags and save:

 
 Album_2
 tag1, tag2
 

 Let's save it again:

 
 Album_2

 

 So, while everything looks good in Django admin, we get old values of
 album.tags_() method in Album.save(), even if we call super(Album,
 self).save(*args, * *kwargs) before.

 I've also tried to use signals like this:


 {{{
 @receiver(post_save, sender=Album)
 def album_save_handler(sender, instance, **kwargs):
 f = open('/tmp/test.txt', 'wt')
 f.write('%s\n%s\n' % (instance.name, instance.tags_()))
 f.close

 }}}

 And even like this:


 {{{
 @receiver(post_save, sender=Album)
 def album_save_handler(sender, instance, **kwargs):
 t = Album.objects.get(pk = instance.id).tags_()
 f = open('/tmp/test.txt', 'wt')
 f.write('%s\n%s\n' % (instance.name, t))
 f.close

 }}}

 Still no luck, results are the same: previous tags instead of the current
 ones.

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

Re: [Django] #19730: Action triggered by django.core.management.base.BaseCommand.can_import_settings is a side effect of i18n locale handling

[Django]

#19730: Action triggered by
django.core.management.base.BaseCommand.can_import_settings is a side
effect of i18n locale handling
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by ramiro):

 Replying to [comment:2 claudep]:
 > Thanks Ramiro for taking this forward. However I'm not sure about the
 comment: ''because many of them create database content that is locale-
 sensitive (like permissions)''.
 >
 > So apart from `syncdb`, which are the commands who alter the database
 with potentially localized content?

 I will reword that paragraph beacuse I can only think of 'test'. 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19237: The use of > in single or double quoted attributes in strip_tags

[Django]

#19237: The use of > in single or double quoted attributes in strip_tags
-+-
 Reporter:  chris.khoo@… |Owner:
 Type:  Bug  |  khoomeister
Component:  Core (Other) |   Status:  new
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Ready for
  Needs tests:  0|  checkin
Easy pickings:  1|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Pablo Recio ):

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


Comment:

 I just ran out a really basic case where this fails:

 {{{
 >>> from django.utils.html import strip_tags
 >>> strip_tags('foohttp://example.com";>bar')
 u'bar'
 }}}

 But the result should be 'foobar'. I think this should be fixed for the
 1.5 release, should I mark it as blocker?

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

Re: [Django] #19724: manage.py app commands enumeration fails silently when MEDIA_URL doesn't end with a slash

[Django]

#19724: manage.py app commands enumeration fails silently when MEDIA_URL doesn't
end with a slash
-+-
 Reporter:  peter.davis8@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.5-beta-1
 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 claudep):

 * needs_better_patch:  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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19724: manage.py app commands enumeration fails silently when MEDIA_URL doesn't end with a slash

[Django]

#19724: manage.py app commands enumeration fails silently when MEDIA_URL doesn't
end with a slash
-+-
 Reporter:  peter.davis8@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:
  commands)  |  1.5-beta-1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 The patch was not good.
 For example, when running `django-admin.py startproject`, accessing
 `settings.INSTALLED_APPS` will always raise `ImproperlyConfigured` and
 this is the regular behaviour (no errors should be shown).

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

Re: [Django] #19724: manage.py app commands enumeration fails silently when MEDIA_URL doesn't end with a slash

[Django]

#19724: manage.py app commands enumeration fails silently when MEDIA_URL doesn't
end with a slash
-+-
 Reporter:  peter.davis8@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:
  commands)  |  1.5-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"2edef932ff4ffc766c7abe18bde2cc77babd8fef"]:
 {{{
 #!CommitTicketReference repository=""
 revision="2edef932ff4ffc766c7abe18bde2cc77babd8fef"
 Revert "Fixed #19724 -- Output error when settings are improperly
 configured"

 This reverts commit 40ca99097f34b2180b2afe6d0056cade4c732618.
 Outputting error is not always suitable, for example this shouldn't
 happen for the 'startproject' command.
 }}}

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

[django/django] 2edef9: Revert "Fixed #19724 -- Output error when settings...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2edef932ff4ffc766c7abe18bde2cc77babd8fef
  
https://github.com/django/django/commit/2edef932ff4ffc766c7abe18bde2cc77babd8fef
  Author: Claude Paroz 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

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

  Log Message:
  ---
  Revert "Fixed #19724 -- Output error when settings are improperly configured"

This reverts commit 40ca99097f34b2180b2afe6d0056cade4c732618.
Outputting error is not always suitable, for example this shouldn't
happen for the 'startproject' command.



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

Re: [Django] #19724: manage.py app commands enumeration fails silently when MEDIA_URL doesn't end with a slash

[Django]

#19724: manage.py app commands enumeration fails silently when MEDIA_URL doesn't
end with a slash
-+-
 Reporter:  peter.davis8@…   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:
  commands)  |  1.5-beta-1
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"40ca99097f34b2180b2afe6d0056cade4c732618"]:
 {{{
 #!CommitTicketReference repository=""
 revision="40ca99097f34b2180b2afe6d0056cade4c732618"
 Fixed #19724 -- Output error when settings are improperly configured

 ...during retrieval of available management commands.
 Thanks Peter Davis for the report and Julien Phalip for the review.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 40ca99: Fixed #19724 -- Output error when settings are imp...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 40ca99097f34b2180b2afe6d0056cade4c732618
  
https://github.com/django/django/commit/40ca99097f34b2180b2afe6d0056cade4c732618
  Author: Claude Paroz 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

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

  Log Message:
  ---
  Fixed #19724 -- Output error when settings are improperly configured

...during retrieval of available management commands.
Thanks Peter Davis for the report and Julien Phalip for the review.



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

Re: [Django] #19725: `createsuperuser` command fails with custom User model

[Django]

#19725: `createsuperuser` command fails with custom User model
-+--
 Reporter:  michisu  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  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:  1|UI/UX:  0
-+--

Comment (by Claude Paroz ):

 In [changeset:"f5232597ea31bf274b02983f32ba89be4f7bf02b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="f5232597ea31bf274b02983f32ba89be4f7bf02b"
 [1.5.x] Fixed #19725 -- Made createsuperuser handle non-ascii prompts

 Thanks Michisu for the report.
 Backport of 55c585f1c 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.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] f52325: [1.5.x] Fixed #19725 -- Made createsuperuser handl...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: f5232597ea31bf274b02983f32ba89be4f7bf02b
  
https://github.com/django/django/commit/f5232597ea31bf274b02983f32ba89be4f7bf02b
  Author: Claude Paroz 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M django/contrib/auth/management/commands/createsuperuser.py
M django/contrib/auth/tests/basic.py

  Log Message:
  ---
  [1.5.x] Fixed #19725 -- Made createsuperuser handle non-ascii prompts

Thanks Michisu for the report.
Backport of 55c585f1c 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19725: `createsuperuser` command fails with custom User model

[Django]

#19725: `createsuperuser` command fails with custom User model
-+--
 Reporter:  michisu  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  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:  1|UI/UX:  0
-+--
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"55c585f1c7a9c91308193f0648caf36203174564"]:
 {{{
 #!CommitTicketReference repository=""
 revision="55c585f1c7a9c91308193f0648caf36203174564"
 Fixed #19725 -- Made createsuperuser handle non-ascii prompts

 Thanks Michisu for the report.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 55c585: Fixed #19725 -- Made createsuperuser handle non-as...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 55c585f1c7a9c91308193f0648caf36203174564
  
https://github.com/django/django/commit/55c585f1c7a9c91308193f0648caf36203174564
  Author: Claude Paroz 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M django/contrib/auth/management/commands/createsuperuser.py
M django/contrib/auth/tests/basic.py

  Log Message:
  ---
  Fixed #19725 -- Made createsuperuser handle non-ascii prompts

Thanks Michisu for the report.



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

Re: [Django] #19385: Add support for multiple-column join

[Django]

#19385: Add support for multiple-column join
-+-
 Reporter:  cseibert |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  join |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by akaariai):

 Sorry for not replying sooner, I've been busy lately...

 I just took a quick look at the second approach and I think I like it. It
 seems the ForeignObject could have more uses than just ForeignKey, so it
 is a good addition. I will try to take a closer look soon. In any case,
 this looks to be on good track for inclusion in 1.6.

 If you have interest in reviewing / working on other ORM tickets that
 would be a good way to make sure I will have time to review this 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 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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19653: `Manager.get_empty_query_set` should call `get_query_set`

[Django]

#19653: `Manager.get_empty_query_set` should call `get_query_set`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  ORM aggregation  |   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
-+-
Changes (by Simon Charette ):

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


Comment:

 In [changeset:"fb606e10ac07af6014cae838c21bf30cf50e8b40"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fb606e10ac07af6014cae838c21bf30cf50e8b40"
 Fixed #19653 -- Removed `Manager.get_empty_query_set`.
 }}}

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

[django/django] fb606e: Fixed #19653 -- Removed `Manager.get_empty_query_s...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fb606e10ac07af6014cae838c21bf30cf50e8b40
  
https://github.com/django/django/commit/fb606e10ac07af6014cae838c21bf30cf50e8b40
  Author: Simon Charette 
  Date:   2013-02-04 (Mon, 04 Feb 2013)

  Changed paths:
M django/db/models/manager.py

  Log Message:
  ---
  Fixed #19653 -- Removed `Manager.get_empty_query_set`.



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

Re: [Django] #19653: `Manager.get_empty_query_set` should call `get_query_set`

[Django]

#19653: `Manager.get_empty_query_set` should call `get_query_set`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  ORM aggregation  |   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
-+-

Comment (by charettes):

 Looks like `get_empty_query_set` was introduced at the
 
[https://github.com/django/django/commit/13280259a8f3ce8c462dc4b484efc922d60666de
 same time] as `EmptyQuerySet`.

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

Re: [Django] #19730: Action triggered by django.core.management.base.BaseCommand.can_import_settings is a side effect of i18n locale handling

[Django]

#19730: Action triggered by
django.core.management.base.BaseCommand.can_import_settings is a side
effect of i18n locale handling
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 Thanks Ramiro for taking this forward. However I'm not sure about the
 comment: ''because many of them create database content that is locale-
 sensitive (like permissions)''.

 So apart from `syncdb`, which are the commands who alter the database with
 potentially localized content?

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

Re: [Django] #19730: Action triggered by django.core.management.base.BaseCommand.can_import_settings is a side effect of i18n locale handling

[Django]

#19730: Action triggered by
django.core.management.base.BaseCommand.can_import_settings is a side
effect of i18n locale handling
-+-
 Reporter:  ramiro   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  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
 * resolution:   => fixed
 * type:  Uncategorized => New feature


Comment:

 Fixed in [869c9ba30615cb24fb5786787a2db8655f2f0d2b]:

 Fixed #19730 -- Don't validate importability of settings by using i18n in
 management commands.

 They are handled independently now and the latter can be influenced by
 the new BaseCommand.leave_locale_alone internal option.

 Thanks chrischambers for the report, Claude, lpiatek, neaf and gabooo for
 their work on a patch, originally on refs. #17379.

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

Re: [Django] #14760: Admin inlines with file/image field fails to save_as

[Django]

#14760: Admin inlines with file/image field fails to save_as
-+-
 Reporter:  paulos   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  contrib.admin|  Version:  1.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by bmihelac):

 * cc: bmihelac@… (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.
For more options, visit https://groups.google.com/groups/opt_out.