Re: [Django] #18756: Tutorial 3 Needs extra funky directive

[Django]

#18756: Tutorial 3 Needs extra funky directive
---+--
 Reporter:  anonymous  |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 charettes):

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


Comment:

 Hi, you are using django 1.4 while reading the documentation for the
 development version of django.

 As of django 1.5, `{% load url from future %}` won't be required anymore
 in this case, hence the omission in the development version documentation.

 By the way, you can switch documentation version in the bottom right of
 the screen (while browsing documentation).

 Thanks for reporting anyway.

-- 
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] #18757: Examine ways to get rid of DB backend convert_values()

[Django]

#18757: Examine ways to get rid of DB backend convert_values()
--+
 Reporter:  akaariai  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Database layer (models, ORM)  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 The convert_values() method is responsible for converting database values
 to Python values. The conversion is used at least for aggregates, GIS and
 Oracle's query compiler.

 The problem with current implementation is two-fold:
   1. The model fields have no way of specifying new converters. This is
 problematic for 3rd party fields. They would need to do some kind of a
 dynamic patch to the backend's convert_values() method if they need
 convert_values() support.
   2. The different backends have slightly differing implementation for the
 same cases.

 In #13844 it was suggested that Field.to_python() method could be reused.
 It seems it does mostly the correct thing, but it is meant for validation,
 not converting DB values to Python. So, going that route would need at
 least some more investigation.

 One possible solution is something like this: A field has convert_values()
 method. The field can (and likely will) call a backend specific converter
 method. So, a custom field could do the following:
   1. Add converter methods to backends it supports:
 {{{
 def psycopg2_converter(self, value):
 return value.lower()
 try:
 from django.db.backends.postgresql_psycopg2.operations import
 DatabaseOperations
 DatabaseOperations.convert_myfield_value = psycopg2_converter
 # Not sure if this exact syntax works.
 except ImportError:
 pass
 # Or, if there is need for just a generic converter:

 from django.db.backends import BaseDatabaseOperations
 BaseDatabaseOperations.convert_myfield_value = my_generic_converter
 }}}
   2. The convert_values method of the field itself would be:
 {{{
 def convert_values(self, connection, value):
 return connection.convert_myfield_value(value)
 }}}

 A little complicated, but it is general. I think it would be fast enough.

 Most fields could just do the conversion directly in
 field.convert_values() without messing with the !DatabaseOperations at
 all. Core fields would not need to do any dynamic installation, as we
 could of course just install the converter into the source code.

 The above proposal is just one way to achieve what is needed. I do think
 there is some need for improvement here, but I am not at all sure the
 suggestion in this post is the way forward.

-- 
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] #18756: Tutorial 3 Needs extra funky directive

[Django]

#18756: Tutorial 3 Needs extra funky directive
---+
 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
---+
 At the end of:
 https://docs.djangoproject.com/en/dev/intro/tutorial03/

 In the section:
 Removing hardcoded URLs in templates

 We are advised to remove a line from mysites_templates/polls/index.html:
 {{ poll.question }}

 and replace it with:
 {{ poll.question
 }}

 With the downloaded 1.4 tgz it will only work if this directive is
 included:
 {% load url from future %}

 This isn't mentioned.

-- 
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] 1930b8: Refix #13844 -- Made FloatField aggregates work on...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 1930b899bd69fb084856257598ab5ddd8ee4e016
  
https://github.com/django/django/commit/1930b899bd69fb084856257598ab5ddd8ee4e016
  Author: Anssi Kääriäinen 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/db/backends/__init__.py

  Log Message:
  ---
  Refix #13844 -- Made FloatField aggregates work on Python 2.6 + Postgres

Fixed a regression introduced in 59a655988ee95e4b4e4646cebea88b620d8fcdd2.



-- 
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] #18751: `BaseFormSet._should_delete_form` should use `form.cleaned_data`

[Django]

#18751: `BaseFormSet._should_delete_form` should use `form.cleaned_data`
-+-
 Reporter:  charettes|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Forms|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  formset  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by charettes):

 * stage:  Accepted => Ready for checkin


Comment:

 claudep, I'm marking the patch you've written for #10711 as RFC since it
 passes all tests (python 2.7.3rc1 sqlite3) and is the definitive way to
 clean up `_should_delete_form` with backward compatibility in mind. My
 patches we're incomplete since they introduced an obscure raises of
 `AttributeError` when attempting to `save` a not-yet-validated formset
 (which is a foolish thing to do anyway), see
 [https://code.djangoproject.com/attachment/ticket/18751/ticket-18751.2.diff
 ticket-18751.2.diff] testsuite changes.

-- 
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] #18755: admin site overlapping

[Django]

#18755: admin site overlapping
---+--
 Reporter:  senden9|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--

Comment (by dirigeant):

 Adding 'word-wrap' to '.aligned label' class to split long words may solve
 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.

[django/django] ac37c9: [py3] Encoded value before feeding it to hashlib.m...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ac37c9e495eb1003cc6d126ed5d686a29fb08596
  
https://github.com/django/django/commit/ac37c9e495eb1003cc6d126ed5d686a29fb08596
  Author: Claude Paroz 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/core/cache/backends/filebased.py
M django/utils/cache.py

  Log Message:
  ---
  [py3] Encoded value before feeding it to hashlib.md5


  Commit: 8a1f439d3aca3a021a43ba6c4235c3ac68908657
  
https://github.com/django/django/commit/8a1f439d3aca3a021a43ba6c4235c3ac68908657
  Author: Claude Paroz 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

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

  Log Message:
  ---
  [py3] Fix encoding issues in contrib.sessions


Compare: https://github.com/django/django/compare/99321e30cebb...8a1f439d3aca

-- 
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] #10790: Too many joins in a comparison for NULL.

[Django]

#10790: Too many joins in a comparison for NULL.
-+-
 Reporter:  mtredinnick  |Owner:
 Type:  Bug  |  mtredinnick
Component:  Database layer   |   Status:  new
  (models, ORM)  |  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 akaariai):

 Still some more digging into this. The problem with the trim_joins as
 stands is that the information of which direction we are traveling the
 join is lost. If we are traveling along a foreign key, it is trimmable, if
 into the other direction, it isn't usually trimmable.

 That information is available in setup_joins() and it should be added to
 the alias_map, or more likely it should be a parameter to qs.join(), and
 that would then add the info to the alias map. After that fixing
 trim_joins() to do the right thing should be easy.

 The patch provided in the previous comment is in my opinion a clear
 improvement and should be applied to master. It first needs a solution to
 that annoying join promotion problem in ORed 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 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] #18306: Deferred models should automatically issue update_fields when saving

[Django]

#18306: Deferred models should automatically issue update_fields when saving
-+-
 Reporter:  akaariai |Owner:  akaariai
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [99321e30cebbffeafc6ae19f4f92a0a665cbf19b]:
 {{{
 #!CommitTicketReference repository=""
 revision="99321e30cebbffeafc6ae19f4f92a0a665cbf19b"
 Fixed #18306 -- Made deferred models issue update_fields on save

 Deferred models now automatically update only the fields which are
 loaded from the db (with .only() or .defer()). In addition, any field
 set manually after the load is updated on save.
 }}}

-- 
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] 99321e: Fixed #18306 -- Made deferred models issue update_...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 99321e30cebbffeafc6ae19f4f92a0a665cbf19b
  
https://github.com/django/django/commit/99321e30cebbffeafc6ae19f4f92a0a665cbf19b
  Author: Andrei Antoukh 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/db/models/base.py
M docs/ref/models/instances.txt
M docs/ref/models/querysets.txt
M docs/releases/1.5.txt
M tests/modeltests/update_only_fields/models.py
M tests/modeltests/update_only_fields/tests.py
M tests/regressiontests/multiple_database/tests.py

  Log Message:
  ---
  Fixed #18306 -- Made deferred models issue update_fields on save

Deferred models now automatically update only the fields which are
loaded from the db (with .only() or .defer()). In addition, any field
set manually after the load is updated on save.



-- 
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
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [59a655988ee95e4b4e4646cebea88b620d8fcdd2]:
 {{{
 #!CommitTicketReference repository=""
 revision="59a655988ee95e4b4e4646cebea88b620d8fcdd2"
 Fixed #13844 -- Avoid converting unknown db values to float

 This patch removes an unconditional float(value) conversion from db
 backend default convert_values() method. This can cause problems when
 aggregating over character fields for example. In addition, Oracle
 and SQLite already return the bare value from their convert_values().

 In the long term the converting should be done by fields, and the
 fields should then call database backend specific converters when
 needed. The current setup is inflexible for 3rd party fields.

 Thanks to Merlijn van Deen for the original 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.

[django/django] 59a655: Fixed #13844 -- Avoid converting unknown db values...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 59a655988ee95e4b4e4646cebea88b620d8fcdd2
  
https://github.com/django/django/commit/59a655988ee95e4b4e4646cebea88b620d8fcdd2
  Author: Anssi Kääriäinen 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/db/backends/__init__.py
M tests/regressiontests/aggregation_regress/tests.py

  Log Message:
  ---
  Fixed #13844 -- Avoid converting unknown db values to float

This patch removes an unconditional float(value) conversion from db
backend default convert_values() method. This can cause problems when
aggregating over character fields for example. In addition, Oracle
and SQLite already return the bare value from their convert_values().

In the long term the converting should be done by fields, and the
fields should then call database backend specific converters when
needed. The current setup is inflexible for 3rd party fields.

Thanks to Merlijn van Deen for the original patch.



-- 
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] dce34d: [py3] Made __repr__ return str with Python 3

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: dce34dc9696734f7ca02d410ddac69d714a25f1e
  
https://github.com/django/django/commit/dce34dc9696734f7ca02d410ddac69d714a25f1e
  Author: Claude Paroz 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/contrib/databrowse/datastructures.py
M django/core/files/uploadedfile.py
M django/core/urlresolvers.py
M django/db/models/base.py
M django/template/base.py

  Log Message:
  ---
  [py3] Made __repr__ return str with Python 3


  Commit: 5513480fe1e616c236a7629072b4317e334b9b4b
  
https://github.com/django/django/commit/5513480fe1e616c236a7629072b4317e334b9b4b
  Author: Claude Paroz 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/db/backends/sqlite3/base.py

  Log Message:
  ---
  [py3] Always convert values from sqlite3 to unicode strings

Thanks Aymeric Augustin for the review.


Compare: https://github.com/django/django/compare/c1684e3dcb2a...5513480fe1e6

-- 
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] #18741: Small cleanup to split_exclude()

[Django]

#18741: Small cleanup to split_exclude()
-+-
 Reporter:  akaariai |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:  Ready for
 Severity:  Normal   |  checkin
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

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


Comment:

 In [c1684e3dcb2adf0fec8fd423cc73122330c268fe]:
 {{{
  #!CommitTicketReference repository=""
  revision="c1684e3dcb2adf0fec8fd423cc73122330c268fe"
  Fixed #18731 -- Cleaned up split_exclude's use of can_reuse

  The outer query's set of reusable joins (can_reuse) was passed to the
  inner query's add_filter call. This was incorrect.
 }}}

 Note that the ticket number is wrong in the commit message.

-- 
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] #18731: "makemessages" management command should handle import aliases

[Django]

#18731: "makemessages" management command should handle import aliases
-+-
 Reporter:  diabeteman   |Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  makemessages i18n|  Unreviewed
  gettext|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by akaariai):

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


Comment:

 Wrong ticket number in commit message -- reopening.

-- 
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] #18731: "makemessages" management command should handle import aliases

[Django]

#18731: "makemessages" management command should handle import aliases
-+-
 Reporter:  diabeteman   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.4
  commands)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:  makemessages i18n|  Unreviewed
  gettext|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Anssi Kääriäinen ):

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


Comment:

 In [c1684e3dcb2adf0fec8fd423cc73122330c268fe]:
 {{{
 #!CommitTicketReference repository=""
 revision="c1684e3dcb2adf0fec8fd423cc73122330c268fe"
 Fixed #18731 -- Cleaned up split_exclude's use of can_reuse

 The outer query's set of reusable joins (can_reuse) was passed to the
 inner query's add_filter call. This was incorrect.
 }}}

-- 
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] c1684e: Fixed #18731 -- Cleaned up split_exclude's use of ...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c1684e3dcb2adf0fec8fd423cc73122330c268fe
  
https://github.com/django/django/commit/c1684e3dcb2adf0fec8fd423cc73122330c268fe
  Author: Anssi Kääriäinen 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/db/models/sql/query.py

  Log Message:
  ---
  Fixed #18731 -- Cleaned up split_exclude's use of can_reuse

The outer query's set of reusable joins (can_reuse) was passed to the
inner query's add_filter call. This was incorrect.



-- 
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] #18755: admin site overlapping

[Django]

#18755: admin site overlapping
---+--
 Reporter:  senden9|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  1
---+--
Changes (by senden9):

 * needs_better_patch:   => 0
 * ui_ux:  0 => 1
 * 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] #18755: admin site overlapping

[Django]

#18755: admin site overlapping
---+
 Reporter:  senden9|  Owner:  nobody
 Type:  Bug| Status:  new
Component:  contrib.admin  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hi!
 I have a standard Django admin site. The description/label (a little bit
 longer) overlap the input widget.

-- 
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] 49bb72: [py3] Made exception examination py3-compatible.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 49bb72c403b24b58d8d8067dcd945f57878df9f0
  
https://github.com/django/django/commit/49bb72c403b24b58d8d8067dcd945f57878df9f0
  Author: Karen Tracey 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

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

  Log Message:
  ---
  [py3] Made exception examination py3-compatible.



-- 
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] 031896: [py3] Explained @python_2_unicode_compatible usage

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 031896c5101de83bca65e872fb4a91c15f55a42e
  
https://github.com/django/django/commit/031896c5101de83bca65e872fb4a91c15f55a42e
  Author: Aymeric Augustin 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M docs/topics/python3.txt

  Log Message:
  ---
  [py3] Explained @python_2_unicode_compatible usage



-- 
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] dbb63e: [py3] Avoided returning bytes in Model.__str__

[GitHub]

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

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

  Log Message:
  ---
  [py3] Avoided returning bytes in Model.__str__

on Python 3.


  Commit: 2bb2eecb6358ea4243ab7a6286048b86302f5128
  
https://github.com/django/django/commit/2bb2eecb6358ea4243ab7a6286048b86302f5128
  Author: Aymeric Augustin 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/contrib/auth/models.py
M django/contrib/databrowse/datastructures.py
M django/core/files/base.py
M django/template/base.py
M tests/modeltests/field_subclassing/fields.py
M tests/modeltests/serializers/models.py

  Log Message:
  ---
  [py3] Removed redundant __str__ methods.

These classes already have an identical __unicode__ method, which
will be used after an upcoming refactoring.


  Commit: e7e08fd48b3f88d4eb481f5b213b923fc1db3675
  
https://github.com/django/django/commit/e7e08fd48b3f88d4eb481f5b213b923fc1db3675
  Author: Aymeric Augustin 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/core/files/base.py
M django/db/models/options.py
M tests/modeltests/delete/models.py
M tests/regressiontests/comment_tests/models.py
M tests/regressiontests/datatypes/models.py
M tests/regressiontests/string_lookup/models.py

  Log Message:
  ---
  [py3] Replaced some __str__ methods by __unicode__

These methods actually return unicode.


  Commit: a0a0203a392f67832ba7a8a2f099e70d7db2d19e
  
https://github.com/django/django/commit/a0a0203a392f67832ba7a8a2f099e70d7db2d19e
  Author: Aymeric Augustin 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/utils/encoding.py
M docs/ref/utils.txt

  Log Message:
  ---
  [py3] Added python_2_unicode_compatible decorator.


  Commit: 79d62a71751140315227891bbe175630f9d3edc3
  
https://github.com/django/django/commit/79d62a71751140315227891bbe175630f9d3edc3
  Author: Aymeric Augustin 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
A django/bin/django-2to3.py
A django/utils/2to3_fixes/__init__.py
A django/utils/2to3_fixes/fix_unicode.py

  Log Message:
  ---
  [py3] Added fixer for python_2_unicode_compatible.

This doesn't deal with classes that define both __unicode__ and
__str__; the definition of __str__ should be removed first. It
doesn't guarantee that __str__ will return a str (rather than bytes)
under Python 3 either.


  Commit: d4a0b27838c815af87698920cc4db7d2afd6f05b
  
https://github.com/django/django/commit/d4a0b27838c815af87698920cc4db7d2afd6f05b
  Author: Aymeric Augustin 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M django/contrib/admin/models.py
M django/contrib/auth/models.py
M django/contrib/comments/models.py
M django/contrib/contenttypes/models.py
M django/contrib/contenttypes/tests.py
M django/contrib/databrowse/datastructures.py
M django/contrib/databrowse/tests.py
M django/contrib/flatpages/models.py
M django/contrib/gis/db/backends/base.py
M django/contrib/gis/db/backends/oracle/models.py
M django/contrib/gis/db/backends/postgis/models.py
M django/contrib/gis/db/backends/spatialite/models.py
M django/contrib/gis/maps/google/overlays.py
M django/contrib/gis/tests/distapp/models.py
M django/contrib/gis/tests/geo3d/models.py
M django/contrib/gis/tests/geoadmin/models.py
M django/contrib/gis/tests/geoapp/models.py
M django/contrib/gis/tests/geogapp/models.py
M django/contrib/gis/tests/relatedapp/models.py
M django/contrib/gis/utils/ogrinspect.py
M django/contrib/messages/storage/base.py
M django/contrib/redirects/models.py
M django/contrib/sites/models.py
M django/core/files/base.py
M django/core/files/uploadhandler.py
M django/db/models/options.py
M django/forms/forms.py
M django/forms/formsets.py
M django/forms/util.py
M django/forms/widgets.py
M django/template/base.py
M django/test/html.py
M tests/modeltests/aggregation/models.py
M tests/modeltests/basic/models.py
M tests/modeltests/choices/models.py
M tests/modeltests/custom_columns/models.py
M tests/modeltests/custom_managers/models.py
M tests/modeltests/custom_methods/models.py
M tests/modeltests/custom_pk/fields.py
M tests/modeltests/custom_pk/models.py
M tests/modeltests/defer/models.py
M tests/modeltests/delete/models.py
M tests/modeltests/distinct_on_fields/models.py
M tests/modeltests/expressions/models.py
M tests/modeltests/field_defaults/models.py
M tests/modeltests/field_subclassing/fields.py
M tests/modeltests/field_subclassing/models.py
M tests/modeltests/fixtures/models.py
M tests/mo

[django/django] 9e7b5b: Removed missplaced label in the docs.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 9e7b5ba50fd9c23876b0a17a03e6875a6899b7c6
  
https://github.com/django/django/commit/9e7b5ba50fd9c23876b0a17a03e6875a6899b7c6
  Author: Florian Apolloner 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M docs/internals/contributing/bugs-and-features.txt

  Log Message:
  ---
  Removed missplaced label in the docs.



-- 
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] 140179: Fix link to Gunicorn website in deployment howto.

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 140179c77046f45136821db2f902f2da64ec4bb6
  
https://github.com/django/django/commit/140179c77046f45136821db2f902f2da64ec4bb6
  Author: Martijn Vermaat 
  Date:   2012-08-12 (Sun, 12 Aug 2012)

  Changed paths:
M docs/howto/deployment/wsgi/gunicorn.txt

  Log Message:
  ---
  Fix link to Gunicorn website in deployment howto.



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