Re: [Django] #19451: Scripting error on Django tutorial

[Django]

#19451: Scripting error on Django tutorial
-+-
 Reporter:  Ganiserb |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  tutorial |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ganiserb):

 You are right! I opened step 1 from a link in the Google search results
 and it was different than getting there manually from the Django docs page
 and selecting "dev" version for the 1st step.

 Thanks and sorry for the confusion.

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

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

Re: [Django] #17716: include(arg, namespace=None, app_name=None) replace app_name with namespace

[Django]

#17716: include(arg, namespace=None, app_name=None) replace app_name with 
namespace
-+-
 Reporter:  blackip@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (URLs)  |  Version:
 Severity:  Normal   |  1.4-alpha-1
 Keywords:  include reverse url  |   Resolution:
Has patch:  0| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by k.znamenskiy@…):

 I'm new in django and begin learning info about urls, app_name and
 namspace

 It's realized so intricately:
 when include
 {{{
 url(r'^anypages1/', include('anypages.urls', app_name='anypages'
 namespace='anypages1'))
 url(r'^anypages2/', include('anypages.urls', app_name='anypages'
 namespace='anypages2'))
 }}}

 when reverse
 {{{
 reverse('anypages:url_name', args=[myarg], current_app='anypages1')
 reverse('anypages:url_name', args=[myarg], current_app='anypages2')
 }}}

 now app_name used in viewname as namespace and namespace pass as
 curreny_app parameter
 so so intricately!

 may be at least rename parameter current_app to current_namespace? Or any
 another actions for more consistency...

 Sorry for my english:)

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

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

Re: [Django] #19425: Inline Admin does not allow extra to be a property

[Django]

#19425: Inline Admin does not allow extra to be a property
-+-
 Reporter:  dave@…   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  inline dynamic   | Triage Stage:
  extras |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by charettes):

 The pull request is looking quite good.

 This would also need documentation and a 1.6 release note but before going
 forward with this I think we should wait for this feature to be accepted
 by a core developer.

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

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

Re: [Django] #19344: Tutorial should tell Windows users to run 'python django-admin.py'

[Django]

#19344: Tutorial should tell Windows users to run 'python django-admin.py'
-+-
 Reporter:  Hourann Bosci|Owner:  nobody
     |   Status:  new
 Type:  Uncategorized|  Version:  1.4
Component:  Documentation|   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 daBosq):

 Sorry, I'd forgotten about this bug! But it sounds like we're agreed on
 having a little note for Windows users? Or maybe that section of the docs
 could have some sort of table for the different platforms showing "here
 are the different ways of invoking django-admin.py", rather than a string
 of OS-specific notes. (The only other fix I can think of is of getting
 virtualenv to do something crazy like change Windows file associations on
 the fly ...?!)

 For now, I've changed my pull request (
 https://github.com/django/django/pull/547) back to add my original note,
 with no other changes to the docs.

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

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

Re: [Django] #14286: Support for BigAutoField

[Django]

#14286: Support for BigAutoField
-+-
 Reporter:  hongrich |Owner:  mmcnickle
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  1|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by ejucovy):

 * cc: ethan.jucovy@… (added)


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

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

Re: [Django] #19431: Prepopulate modeladmin forms datetime fields using querystrings

[Django]

#19431: Prepopulate modeladmin forms datetime fields using querystrings
---+
 Reporter:  aleray |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 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 apollo13):

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


Comment:

 Makes sense to me since we have explicit support for M2M field too, so why
 not DatetimeFields. Using dateutil is not an option though since we don't
 want a hard dependency 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19433: Allow declaration form_list and condition_dict in WizzardView subclass, not as params to as_view

[Django]

#19433: Allow declaration form_list and condition_dict in WizzardView subclass, 
not
as params to as_view
-+-
 Reporter:  migajek  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  contrib.formtools|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  cbv wizzard  |  Needs documentation:  0
  wizzardview|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by apollo13):

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


Comment:

 Can you write a pull request for 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #19344: Tutorial should tell Windows users to run 'python django-admin.py'

[Django]

#19344: Tutorial should tell Windows users to run 'python django-admin.py'
-+-
 Reporter:  Hourann Bosci|Owner:  nobody
     |   Status:  new
 Type:  Uncategorized|  Version:  1.4
Component:  Documentation|   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 ramiro):

 Replying to [comment:6 timo]:
 > Do you think it's still best to recommend all users to use that?  Seems
 a little sad to tell unix users to have to figure out the full path to
 django-admin.py when plain old django-admin.py should work just fine since
 it gets installed to PATH, I think?

 Hmm no, I was thinking about a Windows-specific note. I know we having one
 in the first tutorial it isn´t ideal but OTHOH we already have a note for
 OS X and another for Linux distribution-specific details.

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

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

Re: [Django] #13844: Errors when using character fields for aggregation

[Django]

#13844: Errors when using character fields for aggregation
-+-
 Reporter:  zegrep@… |Owner:  wogan
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by apollo13):

 #19448 is a duplicate.

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

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

Re: [Django] #19448: BaseDatabaseFeatures convert_values

[Django]

#19448: BaseDatabaseFeatures convert_values
-+-
 Reporter:  anton.nagornyi@… |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Core (Other) |   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  convert_values   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by apollo13):

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


Comment:

 This is a duplicate of the already fixed ticket #13844 (will be in 1.5)

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

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

Re: [Django] #19344: Tutorial should tell Windows users to run 'python django-admin.py'

[Django]

#19344: Tutorial should tell Windows users to run 'python django-admin.py'
-+-
 Reporter:  Hourann Bosci|Owner:  nobody
     |   Status:  new
 Type:  Uncategorized|  Version:  1.4
Component:  Documentation|   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 aaugustin):

 #19452 was a colorful duplicate.

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

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

Re: [Django] #19452: your documentation is a poor introduction to a seemingly brilliant idea

[Django]

#19452: your documentation is a poor introduction to a seemingly brilliant idea
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:  duplicate
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by aaugustin):

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


Comment:

 The problem described here is essentially the same as #19344.

 We've tried various permutations of this in the past and none works for
 everyone :(

 To be fair, this is more a problem with the state of Python (and Python
 packaging) on Windows than with Django 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12502: Diagram doesn't match text in Middleware documentation

[Django]

#12502: Diagram doesn't match text in Middleware documentation
-+-
 Reporter:  petrilli |Owner:  Aymeric
 Type:  Bug  |  Augustin 
Component:  Documentation|   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-

Comment (by shai):

 Oh, Ok, then. I stand corrected. Thanks for finally taking care of 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Django] #19452: your documentation is a poor introduction to a seemingly brilliant idea

[Django]

#19452: your documentation is a poor introduction to a seemingly brilliant idea
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 i'm working on windows vista.
 i've installed activestate python 2.7, eclipse and pydev.
 i installed django with AS python package manager PYPM.

 your documentation is very easy to read - i really like the style of
 writing - but your 'hello world' project is awful!
 you tell people to put a command in the python shell that has about a
 50/50 chance of working - if the number of people inquiring on sites like
 stackoverflow about how to get django-admin.py working is anything to go
 by - and if it doesn't work, you suggest altering the os registry or
 'symlinking'!?? It is the FIRST THING PEOPLE DO!!!
 why not just give us a command that we can use? I've altered my registry
 with RegEdit, adding a key to the command or module in question and it
 still doesn't work. Why not just explain a temporary workround? I want to
 get a database/website cranked up and i'm wading through information about
 windows misinterpreting hashbang headers!

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

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

Re: [Django] #19451: Scripting error on Django tutorial

[Django]

#19451: Scripting error on Django tutorial
-+-
 Reporter:  Ganiserb |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  tutorial |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 You're probably mixing versions of the tutorial. This part changed between
 Django 1.4 and 1.5.

 There's a version switcher at the bottom right of each page of the
 tutorial. Make sure you're always reading the version that matches the
 version of Django you're using.

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

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

Re: [Django] #19449: Add user id to sessions table

[Django]

#19449: Add user id to sessions table
-+-
 Reporter:  Nate Dudenhoeffer|Owner:  nobody
    |   Status:  closed
 Type:  New feature  |  Version:  1.4
Component:  contrib.sessions |   Resolution:  wontfix
 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 aaugustin):

 I agree that this method isn't practical.

 Django's session API doesn't provide a way to invalidate sessions, because
 it isn't possible in the general case. For instance, you can't invalidate
 a session stored in a cookie!

 If Django's built-in session backends don't match your requirements —
 like, being able to invalidate a session at will — you can write your own
 session backend. Subclassing the database session backend, extracting the
 user id from the session (when it's available, ie. the user is logged in),
 and storing it alongside the session data should be easy.

 However this won't be possible for other session backends, and as such, it
 isn't a good match for inclusion in core.

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

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

Re: [Django] #12502: Diagram doesn't match text in Middleware documentation

[Django]

#12502: Diagram doesn't match text in Middleware documentation
-+-
 Reporter:  petrilli |Owner:  Aymeric
 Type:  Bug  |  Augustin 
Component:  Documentation|   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-

Comment (by aaugustin):

 Replying to [comment:18 shai]:
 > I agree that the second version is better, but I still think it doesn't
 achieve the goals you set for it in comment:16.

 Sorry, I committed before seeing your comment. I wanted to get it done
 tonight rather than let it linger for another three years :)

 > Question: is it -- as implied by the suggested diagrams -- that an
 exception middleware can return a template response to be processed by the
 template-response middleware?

 Yes, this is possible (look at `django.core.handlers.base`).

 There are four possibilities for the response phase:
 - exception => template_response => response
 - exception => response
 - template_response => response
 - response

 The dashes on the diagram mean that exception and  template_response are
 optional, so these four possibilities are represented.

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

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

Re: [Django] #12502: Diagram doesn't match text in Middleware documentation

[Django]

#12502: Diagram doesn't match text in Middleware documentation
-+-
 Reporter:  petrilli |Owner:  Aymeric
 Type:  Bug  |  Augustin 
Component:  Documentation|   Status:  closed
 Severity:  Normal   |  Version:  master
 Keywords:   |   Resolution:  fixed
Has patch:  1| Triage Stage:  Accepted
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

 * owner:   => Aymeric Augustin 
 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"ae8e97384bbacaf4094b5f98c83b8599478b3fac"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ae8e97384bbacaf4094b5f98c83b8599478b3fac"
 Fixed #12502 -- Improved middleware diagram.
 }}}

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

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

[django/django] ae8e97: Fixed #12502 -- Improved middleware diagram.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ae8e97384bbacaf4094b5f98c83b8599478b3fac
  
https://github.com/django/django/commit/ae8e97384bbacaf4094b5f98c83b8599478b3fac
  Author: Aymeric Augustin 
  Date:   2012-12-09 (Sun, 09 Dec 2012)

  Changed paths:
A docs/topics/http/_images/middleware.graffle
R docs/topics/http/_images/middleware.png
A docs/topics/http/_images/middleware.svg
M docs/topics/http/middleware.txt

  Log Message:
  ---
  Fixed #12502 -- Improved middleware diagram.


  Commit: be9f2919e0e52faa7f7177c795d20646eff89874
  
https://github.com/django/django/commit/be9f2919e0e52faa7f7177c795d20646eff89874
  Author: Aymeric Augustin 
  Date:   2012-12-09 (Sun, 09 Dec 2012)

  Changed paths:
M django/core/handlers/base.py
M docs/topics/http/middleware.txt

  Log Message:
  ---
  Edited the middleware doc for completeness, clarity, and consistency.


Compare: https://github.com/django/django/compare/49519328b498...be9f2919e0e5

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

Re: [Django] #19451: Scripting error on Django tutorial

[Django]

#19451: Scripting error on Django tutorial
-+-
 Reporter:  Ganiserb |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  tutorial |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by anonymous):

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


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

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

[Django] #19451: Scripting error on Django tutorial

[Django]

#19451: Scripting error on Django tutorial
--+--
 Reporter:  Ganiserb  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  tutorial
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+--
 I think there is a mistake in the step 3 of the tutorial.

 I the part that reads:
 
 Use the template system

 Back to the detail() view for our poll application. Given the context
 variable poll, here's what the polls/detail.html template might look like:


 {{{
 {{ poll.question }}
 
 {% for choice in poll.choice_set.all %}
 {{ choice.choice_text }}
 {% endfor %}
 
 }}}
 

 I think the part that reads "{{ choice.choice_text }}" should be
 "{{ choice.choice }}"; since the ''change'' is not mentioned
 before and the attribute "choice" itself contains the "choice text".

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

Re: [Django] #12502: Diagram doesn't match text in Middleware documentation

[Django]

#12502: Diagram doesn't match text in Middleware documentation
---+
 Reporter:  petrilli   |Owner:
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 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
---+

Comment (by shai):

 I agree that the second version is better, but I still think it doesn't
 achieve the goals you set for it in comment:16. In particular, it doesn't
 clarify the relationship between the three middleware functions on the way
 out.

 Here's a quick ascii-art sketch of what I think the diagram should look
 like. Every block should be expanded to "middleware1, middleware2,
 middleware3" in the correct order as in my previous suggestion.

 Question: is it -- as implied by the suggested diagrams -- that an
 exception middleware can return a template response to be processed by the
 template-response middleware? The below represents my guess that this is
 not the case.

 {{{
 #   |
 #   V
 #  [ process_request ]
 #   |
 #   V
 #  [  process_view   ]
 #   |
 #   V
 #  [USER VIEW ]
 #  /| \
 # [process_exception]   |   [process_template_response]
 #  \V /
 #  [ process_response ]
 #   |
 #   V
 }}}
 (Of course, the arrows to process_exception and process_template_response
 should be formed and colored to mark their optionality etc).

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

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

Re: [Django] #12502: Diagram doesn't match text in Middleware documentation

[Django]

#12502: Diagram doesn't match text in Middleware documentation
---+
 Reporter:  petrilli   |Owner:
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 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
---+

Comment (by aaugustin):

 After getting some feedback on IRC, I'm going to commit the second
 version.

 I'll include the OmniGraffle source file in the commit, even though it's
 in a proprietary format, because we often waste time looking for sources.

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

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

Re: [Django] #12502: Diagram doesn't match text in Middleware documentation

[Django]

#12502: Diagram doesn't match text in Middleware documentation
---+
 Reporter:  petrilli   |Owner:
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 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
---+

Comment (by aaugustin):

 We have to strike a balance between completeness and clarity. This graph
 is displayed at the beginning of the introduction to middleware and should
 be understandable at first sight. For this reason, I wouldn't attempt to
 show that each middleware can short-circuit the rest of the chain by
 returning a response in `process_request/view/exception`. It's clearly
 explained in the text and rather intuitive.

 However, there's another aspect that I'd like to represent:
 `process_template_response` and `process_response` are applied after
 `process_exception`. The current docs describe `process_exception` at the
 end — they start with the common case; that can be confusing. They repeat
 that "Response middleware is always called on every response" but the
 concrete result is difficult to understand (at least for me) without a
 visual representation.

 I'm attaching (yet another) SVG file that implements these ideas and tries
 not to be too ugly.

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

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

[Django] #19450: Python 2.1.4.

[Django]

#19450: Python 2.1.4.
--+
 Reporter:  freespirit4601@…  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  Python
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 adware

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

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

Re: [Django] #19449: Add user id to sessions table

[Django]

#19449: Add user id to sessions table
-+-
 Reporter:  Nate Dudenhoeffer|Owner:  nobody
    |   Status:  closed
 Type:  New feature  |  Version:  1.4
Component:  contrib.sessions |   Resolution:  wontfix
 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 Nate Dudenhoeffer ):

 Thanks for the comments aaugustin,and the suggestion of a pluggable
 backend.  I absolutely agree with you that the correct answer in that post
 is rated second.  However, the method described doesn't seem practical on
 even a moderate traffic site with any regularity.

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

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

Re: [Django] #13654: QuerySet .dates() method should support "hour" and "minute"

[Django]

#13654: QuerySet .dates() method should support "hour" and "minute"
-+-
 Reporter:  UloPe|Owner:  aaugustin
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.2
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 A prerequisite is making `.dates()` work on datetime fields when `USE_TZ`
 is enabled ie. #17260.

 If we start down this path, we should support "seconds" too.

 The name of the function should be changed to reflect its new
 capabilities.

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

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

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

[Django]

#19392: Old-style url names (with dashes) throw confusing template traceback
-+-
 Reporter:  dloewenherz  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Template system  |  1.5-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Aymeric Augustin ):

 In [changeset:"49519328b4988bf89c11d50191cdee8e9bec3aaa"]:
 {{{
 #!CommitTicketReference repository=""
 revision="49519328b4988bf89c11d50191cdee8e9bec3aaa"
 Fixed #19392 -- Improved error for old-style url tags with dashes.

 Thanks dloewenherz 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

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

[Django]

#19392: Old-style url names (with dashes) throw confusing template traceback
-+-
 Reporter:  dloewenherz  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:
Component:  Template system  |  1.5-beta-1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Aymeric Augustin ):

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


Comment:

 In [changeset:"d6bad2e9ea77ce48ee5755a7b44682d892bfa3d4"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d6bad2e9ea77ce48ee5755a7b44682d892bfa3d4"
 [1.5.x] Fixed #19392 -- Improved error for old-style url tags with dashes.

 Thanks dloewenherz for the report.

 Backport of 4951932 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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[django/django] 495193: Fixed #19392 -- Improved error for old-style url t...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 49519328b4988bf89c11d50191cdee8e9bec3aaa
  
https://github.com/django/django/commit/49519328b4988bf89c11d50191cdee8e9bec3aaa
  Author: Aymeric Augustin 
  Date:   2012-12-09 (Sun, 09 Dec 2012)

  Changed paths:
M django/template/defaulttags.py
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  Fixed #19392 -- Improved error for old-style url tags with dashes.

Thanks dloewenherz for the report.



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

[django/django] d6bad2: [1.5.x] Fixed #19392 -- Improved error for old-sty...

[GitHub]

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: d6bad2e9ea77ce48ee5755a7b44682d892bfa3d4
  
https://github.com/django/django/commit/d6bad2e9ea77ce48ee5755a7b44682d892bfa3d4
  Author: Aymeric Augustin 
  Date:   2012-12-09 (Sun, 09 Dec 2012)

  Changed paths:
M django/template/defaulttags.py
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  [1.5.x] Fixed #19392 -- Improved error for old-style url tags with dashes.

Thanks dloewenherz for the report.

Backport of 4951932 from master.



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

Re: [Django] #19449: Add user id to sessions table

[Django]

#19449: Add user id to sessions table
-+-
 Reporter:  Nate Dudenhoeffer|Owner:  nobody
    |   Status:  closed
 Type:  New feature  |  Version:  1.4
Component:  contrib.sessions |   Resolution:  wontfix
 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 aaugustin):

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


Comment:

 Unsurprisingly, the accepted answer at SO in wrong is many ways, while the
 correct answer written by a Django core developer lingers in second
 position.

 If you want to store the user id alongside the session key in a database
 table, use the extensibility mechanism provided by Django for such cases:
 pluggable sessions backends.

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

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

[Django] #19449: Add user id to sessions table

[Django]

#19449: Add user id to sessions table
-+
 Reporter:  Nate Dudenhoeffer   |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  contrib.sessions |Version:  1.4
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 Add user id column to the session model to allow developers to easily
 retrieve old session data for a user, and to allow administrators to
 easily end a session for a particular user.

 This is was discussed on Stack Overflow here:
 [http://stackoverflow.com/q/235950/480303]

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

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

Re: [Django] #6903: Go back to old change_list view after hitting save

[Django]

#6903: Go back to old change_list view after hitting save
---+
 Reporter:  jarrow |Owner:
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  1
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  1
---+

Comment (by revolunet):

 Hi :)

 So here's my session based patch :
 https://github.com/revolunet/django/compare/bug-6903-2

 Its much more simpler than the querystring based approach :

  - records the current changelist querystring in an
 `admin_[APP]_[MODEL]_filters` session variable
  - if any, redirect with that querystring on add/change/delete object

 I added some standard unittests

 comments ?

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

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

Re: [Django] #19326: Add a first method to the QuerySet

[Django]

#19326: Add a first method to the QuerySet
-+-
 Reporter:  Wim Feijen   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  first|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by bleskes):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good to me.

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

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

[Django] #19448: BaseDatabaseFeatures convert_values

[Django]

#19448: BaseDatabaseFeatures convert_values
--+
 Reporter:  anton.nagornyi@…  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Core (Other)  |Version:  1.4
 Severity:  Normal|   Keywords:  convert_values
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 In django.db.backends there is convert_values function. I have declared
 custom field which corresponds to Postgresql interval type. By default
 convert_values assumes that unknown type is float. Is it possible to
 change this behaviour? Like that (look at return):


 {{{

 def convert_values(self, value, field):
 """Coerce the value returned by the database backend into a
 consistent type that
 is compatible with the field type.
 """
 internal_type = field.get_internal_type()
 if internal_type == 'DecimalField':
 return value
 elif internal_type and internal_type.endswith('IntegerField') or
 internal_type == 'AutoField':
 return int(value)
 elif internal_type in ('DateField', 'DateTimeField', 'TimeField'):
 return value
 # No field, or the field isn't known to be a decimal or integer
 # Default to a float
 #return float(value)
 #Not to a float. Just leave as is
 return value
 }}}

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

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

Re: [Django] #16187: Refactor lookup system

[Django]

#16187: Refactor lookup system
-+-
 Reporter:  UloPe|Owner:  UloPe
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:   |  Patch needs improvement:  1
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by sfllaw):

 * cc: sfllaw@… (added)


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

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

Re: [Django] #19384: Managers can no longer be used on abstract models

[Django]

#19384: Managers can no longer be used on abstract models
-+-
 Reporter:  mhsparks |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Release blocker  | Triage Stage:  Design
 Keywords:   |  decision needed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 I agree with ptone.

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

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