Re: [Django] #18484: csrfmiddlewaretoken enclosed in redundant invisible div

[Django]

#18484: csrfmiddlewaretoken enclosed in redundant invisible div
---+
 Reporter:  hedleyroos@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  reopened
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  csrf   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by hedleyroos@…):

 I vote for removing the div completely.

-- 
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] #18853: get_template_names() does not consider the queryset-only case

[Django]

#18853: get_template_names() does not consider the queryset-only case
-+-
 Reporter:  msopacua |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  CBV  | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  1|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by bhuztez):

 #16502 is a similar problem. I guess patch there may also fix this
 problem.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #18855: persist a socket across reloads of the dev server

[Django]

#18855: persist a socket across reloads of the dev server
---+
 Reporter:  dlamotte   |Owner:  dlamotte
 Type:  New feature|   Status:  assigned
Component:  HTTP handling  |  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 bhuztez):

 I think this is duplicate of #16049

-- 
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] #18484: csrfmiddlewaretoken enclosed in redundant invisible div

[Django]

#18484: csrfmiddlewaretoken enclosed in redundant invisible div
---+
 Reporter:  hedleyroos@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  reopened
Component:  Uncategorized  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords:  csrf   | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by simonb):

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


Comment:

 By removing style="display:none" the layout of every form that uses
 csrf_token has been changed. The div becomes significant to the
 layout/flow of the form and moves everything that follows below it - divs
 are blocks. This is a backwards incompatible change. Could we, at least,
 give the surrounding div an id or class so we can address it in CSS to fix
 the layout of all of our forms?

 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] #18881: tag "trans" not working with "context"

[Django]

#18881: tag "trans" not working with "context"
+--
 Reporter:  lanyjie |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Template system |  Version:  1.4
 Severity:  Normal  |   Resolution:
 Keywords:  trans context i18n  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--

Comment (by lanyjie):

 I would love to try write a unit test if someone can give me an example
 for the i18n module. For now, I can specify how to reproduce this problem:

 1. in a django project, write a real simple template file named
 "testempt.html" with two lines like this:
 {{{
 {%trans "budget" context "finance"%}

 "{%trans 'budget' context 'finance'%}"
 }}}
 2. now issue this command:
 {{{
 python manage.py makemessages -l en
 }}}
 3. then open the message file django.po and you will get this:
 {{{
 #: testempt.html:1
 msgctxt "finance"
 msgid "budget"
 msgstr ""

 #: testempt.html:3
 msgid "budget"
 msgstr ""
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #2304: [patch] DISABLE_TRANSACTION_MANAGEMENT is not working as described in Doc's

[Django]

#2304: [patch] DISABLE_TRANSACTION_MANAGEMENT is not working as described in 
Doc's
-+-
 Reporter:  scott.benninghoff@…  |Owner:
 Type:  Bug  |  tjshewmake
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:
 Severity:  Normal   |   Resolution:
 Keywords:  Unit of work,| Triage Stage:  Accepted
  commit, rollback, transactions |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by jdunck):

 This flag has never worked the way it's been documented, while
 TRANSACTIONS_MANAGED does - probably there is deployed code depending upon
 TRANSACTIONS_MANAGED, though it is undocumented.

 I don't see the point of deprecating TRANSACTIONS_MANAGED while keeping
 the documented but useless DISABLE_TRANSACTION_MANAGEMENT.

 I'd prefer to document TRANSACTIONS_MANAGED and remove
 DISABLE_TRANSACTION_MANAGEMENT from docs; it's not even a backwards-
 compatibility issue because people can still happily set the useless (but
 newly undocumented) flag.

-- 
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] #18952: template syntax to access individual elements of a list

[Django]

#18952: template syntax to access individual elements of a list
-+-
 Reporter:  mail@…   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:
 Keywords:  template syntax  |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timo):

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


Comment:

 Thanks for the suggestion, but I don't think this is the best place for
 that bit of info since .0, .1 aren't filters.  List lookup is described
 here: https://docs.djangoproject.com/en/dev/topics/templates/

-- 
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] #18933: docstring for cycle templatetag method differs from documentation

[Django]

#18933: docstring for cycle templatetag method differs from documentation
-+-
 Reporter:  martey   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  cycle templatetag|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"87c06fa4f4b908b940bea7cde95251d4daf78f3c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="87c06fa4f4b908b940bea7cde95251d4daf78f3c"
 Merge pull request #364 from martey/ticket_18933

 Fixed #18933 - Fixes code example for cycle in docstring.
 }}}

-- 
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] #18933: docstring for cycle templatetag method differs from documentation

[Django]

#18933: docstring for cycle templatetag method differs from documentation
-+-
 Reporter:  martey   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  cycle templatetag|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Martey Dodoo ):

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


Comment:

 In [changeset:"3fb2662edcdfb03ebb4b2ab60ffe309104809246"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3fb2662edcdfb03ebb4b2ab60ffe309104809246"
 Fixes #18933. Fixes code example in docstring.

 Makes code example of silent keyword docstring in cycle templatetag
 method the same as in the documentation.
 }}}

-- 
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] 3fb266: Fixes #18933. Fixes code example in docstring.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 3fb2662edcdfb03ebb4b2ab60ffe309104809246
  
https://github.com/django/django/commit/3fb2662edcdfb03ebb4b2ab60ffe309104809246
  Author: Martey Dodoo 
  Date:   2012-09-08 (Sat, 08 Sep 2012)

  Changed paths:
M django/template/defaulttags.py

  Log Message:
  ---
  Fixes #18933. Fixes code example in docstring.

Makes code example of silent keyword docstring in cycle templatetag
method the same as in the documentation.


  Commit: 87c06fa4f4b908b940bea7cde95251d4daf78f3c
  
https://github.com/django/django/commit/87c06fa4f4b908b940bea7cde95251d4daf78f3c
  Author: Tim Graham 
  Date:   2012-09-13 (Thu, 13 Sep 2012)

  Changed paths:
M django/template/defaulttags.py

  Log Message:
  ---
  Merge pull request #364 from martey/ticket_18933

Fixed #18933 - Fixes code example for cycle in docstring.


Compare: https://github.com/django/django/compare/690170a8b9bb...87c06fa4f4b9

-- 
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] #4796: force_unicode error

[Django]

#4796: force_unicode error
-+-
 Reporter:  fpierfed@…   |Owner:
 Type:  Uncategorized|   Status:  closed
Component:  Core (Other) |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  fcgi unicode | Triage Stage:  Accepted
  __proxy__ databrowse   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by joseph8th@…):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 I had the same problem but found that I was returning the object in my
 __unicode__ instead of returning unicode(self.object) in the model. Fixed
 it right up.

-- 
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] 690170: Removed unused quoting/encoding in gis db backend

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 690170a8b9bbcea1ae51e4020aea49987fefdbd2
  
https://github.com/django/django/commit/690170a8b9bbcea1ae51e4020aea49987fefdbd2
  Author: Claude Paroz 
  Date:   2012-09-13 (Thu, 13 Sep 2012)

  Changed paths:
M django/contrib/gis/db/backends/base.py
M django/contrib/gis/db/backends/util.py

  Log Message:
  ---
  Removed unused quoting/encoding in gis db backend



-- 
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] #18518: wsgi.py does not overwrite DJANGO_SETTINGS_MODULE in apache prefork

[Django]

#18518: wsgi.py does not overwrite DJANGO_SETTINGS_MODULE in apache prefork
-+-
 Reporter:  schaefer@…   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 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 benjaoming):

 I've suggested a commented out example of how things should look with
 WSGI. Would that work together with a comment in the documentation?

-- 
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] #18518: wsgi.py does not overwrite DJANGO_SETTINGS_MODULE in apache prefork

[Django]

#18518: wsgi.py does not overwrite DJANGO_SETTINGS_MODULE in apache prefork
-+-
 Reporter:  schaefer@…   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Uncategorized|  Version:  1.4
 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 aaugustin):

 FWIW I agree with Carl's last comment. I would be extremely surprised if
 DJANGO_SETTINGS_MODULE was arbitrarily overridden.

-- 
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] #18953: python is a snake to me; that said, django settings creating a problem

[Django]

#18953: python is a snake to me; that said, django settings creating a problem
---+--
 Reporter:  beckybernat@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  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 claudep):

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


Comment:

 Hi,

 There is nothing you can do to change anything from your computer. Only
 the site developer can change this variable, which wouldn't change much
 for you, you would simply get another style of 404 page (the page you are
 looking for does not exist on the site). You can try to communicate with
 the target site developer to resolve 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] #18932: Buildin template tags seem to break i18n

[Django]

#18932: Buildin template tags seem to break i18n
-+-
 Reporter:  houmie   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:   |  Version:
  Internationalization   |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:  i18n |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by claudep):

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


Comment:

 Happy end :-)

-- 
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] #18954: Initial sql data documentation

[Django]

#18954: Initial sql data documentation
---+
 Reporter:  jli|  Owner:  nobody
 Type:  New feature| Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Ok on this page:
 https://docs.djangoproject.com/en/dev/howto/initial-data/#providing-
 initial-sql-data

 I think it would be nice to add that if for some reason you're using
 models as a directory with __init__.py that import every sub modules in
 there, you need to actually move the sql folder inside your models folder.

 So to be clear:
 usual setups is :
 my_app/
  sql/
   mymodel.sql
  models.py --> myModel

 the setup that needs documentation:
 my_app/
  models/
   mymodelgroup.py --> myModel
   anothermodelgroup.py --> anotherModel
   sql/
mymodel.sql

 There is no info anywhere about this, I don't know if it's a feature or a
 bug by the way.
 But it make sense I think to move the sql script inside the models folder
 it it's actually a folder.

 Cheers!

-- 
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] #18953: python is a snake to me; that said, django settings creating a problem

[Django]

#18953: python is a snake to me; that said, django settings creating a problem
---+
 Reporter:  beckybernat@…  |  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 dont use python nor have I ever heard of django until I got an error
 message (on all my browsers) that I can't open a window due to my django
 setting reading true instead of false. Django comes up empty when I search
 my computer.  When I searched the web for how to fix it I ended at your
 site, and your instructions on what to do make no sense to me.  Can you
 please tell me what this means, and how can fix this problem:  You're
 seeing this error because you have DEBUG = True in your Django settings
 file. Change that to False, and Django will display a standard 404 page.
 Just tell me where on my computer I can find this and change it, without
 all the python info.
 thank you

-- 
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] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgis 2.0  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by fcurella):

 Thanks @claudep, I missed that. Just ignore patch v10.

-- 
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] #16455: Postgis 2.0 Compatibility

[Django]

#16455: Postgis 2.0 Compatibility
-+
 Reporter:  ckarrie  |Owner:  jbronn
 Type:  New feature  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  postgis 2.0  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by claudep):

 The test failures have been fixed through ticket #18795, they were not
 directly related to Postgis 2. This part can now be removed from the
 patch.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #18795: Failing GeoDjango tests

[Django]

#18795: Failing GeoDjango tests
+
 Reporter:  julien  |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  GIS |  Version:  1.4
 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 Claude Paroz ):

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


Comment:

 In [changeset:"7e5ebcce5365a172d802c76b57771c321430317f"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7e5ebcce5365a172d802c76b57771c321430317f"
 Fixed #18795 -- Fixed failing GeoDjango tests

 Proj.4 and SRS strings may slightly vary depending on the installed
 libraries. Made some tests pass again with recent Proj.4/GDAL lib
 versions.
 }}}

-- 
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] 7e5ebc: Fixed #18795 -- Fixed failing GeoDjango tests

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7e5ebcce5365a172d802c76b57771c321430317f
  
https://github.com/django/django/commit/7e5ebcce5365a172d802c76b57771c321430317f
  Author: Claude Paroz 
  Date:   2012-09-13 (Thu, 13 Sep 2012)

  Changed paths:
M django/contrib/gis/gdal/tests/test_ds.py
M django/contrib/gis/gdal/tests/test_geom.py
M django/contrib/gis/geos/tests/test_geos.py
M django/contrib/gis/tests/test_spatialrefsys.py

  Log Message:
  ---
  Fixed #18795 -- Fixed failing GeoDjango tests

Proj.4 and SRS strings may slightly vary depending on the installed
libraries. Made some tests pass again with recent Proj.4/GDAL lib
versions.



-- 
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] #18951: Datetime microseconds cutoff first zero in Django templates

[Django]

#18951: Datetime microseconds cutoff first zero in Django templates
-+-
 Reporter:  olofom@… |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  datetime | Triage Stage:  Accepted
  microseconds   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * owner:  nobody => aaugustin


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

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

[Django] #18952: template syntax to access individual elements of a list

[Django]

#18952: template syntax to access individual elements of a list
--+-
 Reporter:  mail@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  template syntax
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+-
 Maybe this is too trivial but I think that in addition to "first" and
 "last" it could be mentioned at
 https://docs.djangoproject.com/en/1.4/ref/templates/builtins/
 that {{ value.0 }}, {{ value.1 }}, {{
 value.2 }}, etc. can be used to access individual elements of a list.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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] #10405: quoted class names in foreign key definition causes 'str' object has no attribute '_default_manager'

[Django]

#10405: quoted class names in foreign key definition causes 'str' object has no
attribute '_default_manager'
-+-
 Reporter:  danbrwn  |Owner:  mitsuhiko
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
  foreign,key,quoted,dceu2011|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by seocam):

 * cc: seocam@… (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] #10405: quoted class names in foreign key definition causes 'str' object has no attribute '_default_manager'

[Django]

#10405: quoted class names in foreign key definition causes 'str' object has no
attribute '_default_manager'
-+-
 Reporter:  danbrwn  |Owner:  mitsuhiko
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
  foreign,key,quoted,dceu2011|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by seocam):

 Still happening to me too.
 I'm using Django 1.3.3 and the steps to reproduce are the same mentioned
 in comment 8.

-- 
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] #18932: Buildin template tags seem to break i18n

[Django]

#18932: Buildin template tags seem to break i18n
-+-
 Reporter:  houmie   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  i18n |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by houmie):

 Sorry for late reply. Don't worry I don't think you are slow, more likely
 I am not explaining well enough. :)

 For your convenience I have attached a screenshot of my demo to discuss it
 here. [[Image(http://i.imgur.com/l3aAl.png)]]

 In the example if I use `item.conversation_datetime` I would get the
 British dateformat coming from my overriden `formats.py`: `30 August 2012,
 21:33`

 However the moment I extract only the date and time with |date & |time
 accordingly I would loose the localization. As you can see from the
 screenshot the date has the American date format.

 Now that we agree upon the problem, lets investigate your suggested
 solutions:

   1) and 2) are hardcoded and won't be good in my case as I need the user
 to be able to change the language at any time.

   3) You want the format depending on the language; use a predefined
 format (|date:"DATE_FORMAT")

 Yes, this is the solution. I didn't know this is possible.  This way you
 extract the "DATE_FORMAT" from `formats.py` same for time:
 `|time:"TIME_FORMAT".` This was exactly what I was looking for.   I am so
 sorry I couldn't see this bit in the documentation.

 Your help was highly appreciated to solve 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 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] #18951: Datetime microseconds cutoff first zero in Django templates

[Django]

#18951: Datetime microseconds cutoff first zero in Django templates
-+-
 Reporter:  olofom@… |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  datetime | Triage Stage:  Accepted
  microseconds   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by kmtracey):

 * needs_better_patch:   => 0
 * stage:  Unreviewed => Accepted
 * 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.

Re: [Django] #18131: insufficient info about ContentTypeManager

[Django]

#18131: insufficient info about ContentTypeManager
---+
 Reporter:  sir_sigurd |Owner:  nobody
 Type:  Bug|   Status:  reopened
Component:  Documentation  |  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:  0  |UI/UX:  0
---+

Old description:

> get_for_model is not listed among ContentTypeManager methods.
>
> The only mention of caching is in description of clear_cache method, but
> documentation should say that get_* methods are cached and using them is
> preferred way to get ContentType.

New description:

 `get_for_id` is not listed among ContentTypeManager methods.

 The only mention of caching is in description of clear_cache method, but
 documentation should say that get_* methods are cached and using them is
 preferred way to get ContentType.

--

Comment (by kmtracey):

 Corrected name of undocumented method in original description.

-- 
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] #18951: Datetime microseconds cutoff first zero in Django templates

[Django]

#18951: Datetime microseconds cutoff first zero in Django templates
-+---
 Reporter:  olofom@… |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.4
 Severity:  Normal   |   Keywords:  datetime microseconds
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+---
 So I had a datetime object that I wanted to display on a web page and then
 post back through a hidden field. This didn't work (unless I use the 'c'
 flag with the date filter to get the ISO format, then it works fine).
 [[BR]]



 {{{
 >>> datetime.datetime(2013, 9, 12, 9, 24, 16, 14070)
 datetime.datetime(2013, 9, 12, 9, 24, 16, 14070)
 >>> str(datetime.datetime(2013, 9, 12, 9, 24, 16, 14070))
 '2013-09-12 09:24:16.014070'
 }}}

 [[BR]]


 BUT {{ timestamp|date:'Y-m-d H:i:s.u' }} prints:
 2013-09-12 09:24:16.14070
 without the first zero. Then when trying to convert this back to a
 datetime object I get:
 [[BR]]



 {{{
 >>> datetime.datetime.strptime('2013-09-12 09:24:16.14070', "%Y-%m-%d
 %H:%M:%S.%f")
 datetime.datetime(2013, 9, 12, 9, 24, 16, 140700)
 >>> str(datetime.datetime.strptime('2013-09-12 09:24:16.14070', "%Y-%m-%d
 %H:%M:%S.%f"))
 '2013-09-12 09:24:16.140700'
 }}}

 So in the end I ended up with the microseconds: 140700 instead of 014070,
 but the real bug is that the 'u' flag of date prints 14070 instead of
 014070.

-- 
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] #16774: Backtracking URL resolver

[Django]

#16774: Backtracking URL resolver
---+
 Reporter:  nbstrite   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  HTTP handling  |  Version:  1.3
 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 meric):

 I have continued to work on the patch here:
 https://github.com/meric/django/compare/ticket_16774

-- 
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] #9523: Restart runserver after translation MO files change

[Django]

#9523: Restart runserver after translation MO files change
-+-
 Reporter:  wim@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  1.0
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * cc: charette.s@… (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] #9523: Restart runserver after translation MO files change

[Django]

#9523: Restart runserver after translation MO files change
-+-
 Reporter:  wim@…|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  1.0
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  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 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] #16357: Navigation buttons in Docs footer would be helpful

[Django]

#16357: Navigation buttons in Docs footer would be helpful
--+
 Reporter:  ncoghlan@…|Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.3
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  1
--+
Changes (by julien):

 * owner:  julien =>


-- 
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] #17208: Dogfood class-based views in contrib.admin

[Django]

#17208: Dogfood class-based views in contrib.admin
-+-
 Reporter:  melinath |Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.admin|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  class-based views|  Needs documentation:  1
  admin  |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by julien):

 * owner:  julien =>


-- 
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] #18530: Inconsistent error handling on admin filter url's

[Django]

#18530: Inconsistent error handling on admin filter url's
-+
 Reporter:  david@…  |Owner:  julien
 Type:  Bug  |   Status:  new
Component:  contrib.admin|  Version:  1.4
 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 julien):

 * owner:  nobody => julien
 * status:  reopened => new


Comment:

 I'll try and get that committed soon.

-- 
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.