date:20110520

Re: [Django] #16025: distinct does not apply to aggregated querysets

2011-05-20 Thread Django

#16025: distinct does not apply to aggregated querysets
+-
   Reporter:  micolous  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  ORM aggregation
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
+-
Changes (by ramiro):

 * component:  Database layer (models, ORM) => ORM aggregation
 * stage:  Unreviewed => Accepted


Comment:

 Does your Food model have any `Meta.ordering` model option or does the
 queryset have a `order_by()` call somewhere?

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

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

Re: [Django] #15796: Contributing docs need to be updated to include new triage stages and ticket states

2011-05-20 Thread Django

#15796: Contributing docs need to be updated to include new triage stages and
ticket states
-+-
   Reporter:  russellm   |  Owner:  julien
   Type:  Bug| Status:  new
  Milestone: |  Component:  Documentation
Version:  1.2|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by julien):

 Thanks Jannis, well spotted! Let me just quickly fix that as well as a
 couple of small things that were suggested on the dev-list. Will post a
 new patch shortly.

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

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

Re: [Django] #14180: Creating redundant indexes on foreign keys for MySQL/InnoDB tables

2011-05-20 Thread Django

#14180: Creating redundant indexes on foreign keys  for MySQL/InnoDB tables
-+-
   Reporter:  zimnyx |  Owner:
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.2|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage: |  Has patch:  0
  Someday/Maybe  |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

 * component:  ORM aggregation => Database layer (models, ORM)
 * easy:   => 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15130: Model.validate_unique method doesn't take in account multi-db

2011-05-20 Thread Django

#15130: Model.validate_unique method doesn't take in account multi-db
-+-
   Reporter:  t2y|  Owner:
   Type:  Bug| Status:  reopened
  Milestone:  1.3|  Component:  Database layer
Version:  1.2|  (models, ORM)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:  multi-db
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  1  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by ramiro):

 * component:  ORM aggregation => Database layer (models, ORM)
 * easy:   => 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #5025: Add a "truncate" template filter

2011-05-20 Thread Django

#5025: Add a "truncate" template filter
---+-
   Reporter:  SmileyChris  |  Owner:  nobody
   Type:  New feature  | Status:  reopened
  Milestone:   |  Component:  Template system
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
---+-
Changes (by SmileyChris):

 * easy:   => 0


Comment:

 The length of the truncated string in floguy's previous patch wasn't
 taking into account the length of the string when it had combining
 characters with no precomposed form.

 I'm pretty happy with the patch I uploaded - I wonder though that if
 instead of having `ugettext_lazy('...')` we should use:
 `ugettext_lazy('%(truncated_text)s...')`

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

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

Re: [Django] #16057: uWSGI documentation

2011-05-20 Thread Django

#16057: uWSGI documentation
---+---
   Reporter:  jpic |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Documentation
Version:  1.3  |   Severity:  Normal
 Resolution:   |   Keywords:  uwsgi
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
---+---
Changes (by russellm):

 * has_patch:  0 => 1
 * type:  Uncategorized => New feature
 * stage:  Design decision needed => Accepted


Comment:

 I don't think there's a design decision needed here - the broad concept of
 adding uWSGI docs has been discussed on Django-dev already. We just need
 someone to review the proposed text.

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

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

Re: [Django] #16028: Consolidate default template filters' tests

2011-05-20 Thread Django

#16028: Consolidate default template filters' tests
-+-
   Reporter:  julien |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  Testing framework
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

 * stage:  Unreviewed => Accepted


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

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

Re: [Django] #16057: uWSGI documentation

2011-05-20 Thread Django

#16057: uWSGI documentation
-+-
   Reporter:  jpic   |  Owner:  nobody
   Type: | Status:  new
  Uncategorized  |  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:  uwsgi
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

 * needs_docs:   => 0
 * has_patch:  1 => 0
 * stage:  Unreviewed => Design decision needed
 * needs_tests:   => 0
 * needs_better_patch:   => 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16060: Model entry does not get verified and no error raised

2011-05-20 Thread Django

#16060: Model entry does not get verified and no error raised
-+-
   Reporter:  m.vovcu@…  |  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Database layer
Version:  1.3|  (models, ORM)
 Resolution:  invalid|   Severity:  Normal
   Triage Stage: |   Keywords:
  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-
Changes (by mattmcc):

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


Comment:

 Model validation does not happen automatically when you're manipulating a
 model object directly.  See
 http://docs.djangoproject.com/en/1.3/ref/models/instances/#validating-
 objects

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

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

Re: [Django] #16061: Broken Pipe in FireFox

2011-05-20 Thread Django

#16061: Broken Pipe in FireFox
-+-
   Reporter: |  Owner:  rowend
  rowend07@… | Status:  closed
   Type:  Bug|  Component:  HTTP handling
  Milestone:  2.0|   Severity:  Normal
Version:  1.3|   Keywords:  broke pipe in
 Resolution:  duplicate  |  firefox
   Triage Stage: |  Has patch:  1
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

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


Comment:

 Duplicate of #14239

 Note I quickly found #14239 and other previous reports of the same issue
 like #8094 and # by using the right upper corner search box of this
 Trac instance with "broken pipe firefox" search terms and restricting the
 results to tickets. I'd to suggest to the same the next time you want to
 report an issue because chances are somebody already experienced it.

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

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

Re: [Django] #16062: Broken Pipe in FireFox

2011-05-20 Thread Django

#16062: Broken Pipe in FireFox
-+-
   Reporter: |  Owner:  rowend
  rowend07@… | Status:  closed
   Type:  Bug|  Component:  HTTP handling
  Milestone:  2.0|   Severity:  Normal
Version:  1.3|   Keywords:  broke pipe in
 Resolution:  duplicate  |  firefox
   Triage Stage: |  Has patch:  1
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

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


Comment:

 duplicate of #16061

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

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

[Django] #16062: Broken Pipe in FireFox

2011-05-20 Thread Django

#16062: Broken Pipe in FireFox
---+---
 Reporter:  rowend07@… |  Owner:  rowend
 Type:  Bug| Status:  new
Milestone:  2.0|  Component:  HTTP handling
  Version:  1.3|   Severity:  Normal
 Keywords:  broke pipe in firefox  |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
---+---
 Hi my name is Ramiro Tinoco Duarte also you can callme by my nickname.
 I am a new porgrammer in django.
 And my English is not good.
 But I try to explain the error.

 Enviroment
 SO - Ubuntu 10.10
 web-browser firefox 3.6.17
 django version 1.3

 error

 Traceback (most recent call last):
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 284, in run
 self.finish_response()
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 324, in finish_response
 self.write(data)
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 403, in write
 self.send_headers()
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 467, in send_headers
 self.send_preamble()
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 385, in send_preamble
 'Date: %s\r\n' % http_date()
   File "/usr/lib/python2.6/socket.py", line 318, in write
 self.flush()
   File "/usr/lib/python2.6/socket.py", line 297, in flush
 self._sock.sendall(buffer(data, write_offset, buffer_size))
 error: [Errno 32] Broken pipe
 
 Exception happened during processing of request from ('127.0.0.1', 35205)
 Traceback (most recent call last):
   File "/usr/lib/python2.6/SocketServer.py", line 283, in
 _handle_request_noblock
 self.process_request(request, client_address)
   File "/usr/lib/python2.6/SocketServer.py", line 309, in process_request
 self.finish_request(request, client_address)
   File "/usr/lib/python2.6/SocketServer.py", line 322, in finish_request
 self.RequestHandlerClass(request, client_address, self)
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 570, in __init__
 BaseHTTPRequestHandler.__init__(self, *args, **kwargs)
   File "/usr/lib/python2.6/SocketServer.py", line 618, in __init__
 self.finish()
   File "/usr/lib/python2.6/SocketServer.py", line 661, in finish
 self.wfile.flush()
   File "/usr/lib/python2.6/socket.py", line 297, in flush
 self._sock.sendall(buffer(data, write_offset, buffer_size))
 error: [Errno 32] Broken pipe
 

 why causes this error in firefox
 put the next html code in a template

 some
 text

 and when you click the button-link the error occurs
 a great broken pipe line

 I apologize for my bads english skills

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

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

[Django] #16061: Broken Pipe in FireFox

2011-05-20 Thread Django

#16061: Broken Pipe in FireFox
---+---
 Reporter:  rowend07@… |  Owner:  rowend
 Type:  Bug| Status:  new
Milestone:  2.0|  Component:  HTTP handling
  Version:  1.3|   Severity:  Normal
 Keywords:  broke pipe in firefox  |   Triage Stage:  Unreviewed
Has patch:  1  |  Easy pickings:  1
---+---
 Hi my name is Ramiro Tinoco Duarte also you can callme by my nickname.
 I am a new porgrammer in django.
 And my English is not good.
 But I try to explain the error.

 Enviroment
 SO - Ubuntu 10.10
 web-browser firefox 3.6.17
 django version 1.3

 error

 Traceback (most recent call last):
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 284, in run
 self.finish_response()
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 324, in finish_response
 self.write(data)
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 403, in write
 self.send_headers()
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 467, in send_headers
 self.send_preamble()
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 385, in send_preamble
 'Date: %s\r\n' % http_date()
   File "/usr/lib/python2.6/socket.py", line 318, in write
 self.flush()
   File "/usr/lib/python2.6/socket.py", line 297, in flush
 self._sock.sendall(buffer(data, write_offset, buffer_size))
 error: [Errno 32] Broken pipe
 
 Exception happened during processing of request from ('127.0.0.1', 35205)
 Traceback (most recent call last):
   File "/usr/lib/python2.6/SocketServer.py", line 283, in
 _handle_request_noblock
 self.process_request(request, client_address)
   File "/usr/lib/python2.6/SocketServer.py", line 309, in process_request
 self.finish_request(request, client_address)
   File "/usr/lib/python2.6/SocketServer.py", line 322, in finish_request
 self.RequestHandlerClass(request, client_address, self)
   File "/usr/local/lib/python2.6/dist-
 packages/django/core/servers/basehttp.py", line 570, in __init__
 BaseHTTPRequestHandler.__init__(self, *args, **kwargs)
   File "/usr/lib/python2.6/SocketServer.py", line 618, in __init__
 self.finish()
   File "/usr/lib/python2.6/SocketServer.py", line 661, in finish
 self.wfile.flush()
   File "/usr/lib/python2.6/socket.py", line 297, in flush
 self._sock.sendall(buffer(data, write_offset, buffer_size))
 error: [Errno 32] Broken pipe
 

 why causes this error in firefox
 put the next html code in a template

 some
 text

 and when you click the button-link the error occurs
 a great broken pipe line

 I apologize for my bads english skills

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

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

Re: [Django] #13612: manage.py imports settings.py even when --settings is used

2011-05-20 Thread Django

#13612: manage.py imports settings.py even when --settings is used
-+-
   Reporter:  tonnzor|  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Management
Version:  SVN|  commands)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  1  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by ramiro):

 * needs_better_patch:  0 => 1


Comment:

 Replying to [comment:6 graham_king]:
 > A disadvantage is that if no settings.py is present in the current
 directory, and the settings file used throws an !ImportError, the actual
 error is obscured by the warning message. However that message asks you to
 try django-admin.py, which does correctly display the error.
 Another nit about the proposed patch is the one shown by the test in line
 870 of the admin_script tests and the change you had to make to the
 expected `manage.py` output: If no `settings.py` file is present in the
 directory and the user doesn't specify one (either with the `--setting`
 option or by the DJANGO_SETTINGS_MODULE envvar) then the error shown is
 (e.g. in the test case) `Unknown command: 'noargs_command'`. No hint is
 given to the user about the fact that she is trying to run `manage.py`
 without a settings file at all it the reason of the failure.

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

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

Re: [Django] #11240: Compilemessages fails if a % character is at certain places in the .po file

2011-05-20 Thread Django

#11240: Compilemessages fails if a % character is at certain places in the .po 
file
-+-
   Reporter:  tback  |  Owner:  garcia_marc
   Type:  Bug| Status:  closed
  Milestone: |  Component:
Version:  1.3|  Internationalization
 Resolution:  needsinfo  |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  0
Patch needs improvement:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by ramiro):

 * component:  Translations => Internationalization


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

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

Re: [Django] #11240: Compilemessages fails if a % character is at certain places in the .po file

2011-05-20 Thread Django

#11240: Compilemessages fails if a % character is at certain places in the .po 
file
-+--
   Reporter:  tback  |  Owner:  garcia_marc
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Translations
Version:  1.3|   Severity:  Normal
 Resolution:  needsinfo  |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+--
Changes (by ramiro):

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


Comment:

 Replying to [comment:2 ramiro]:
 > Yes, for the translatable literals extraction process templates are
 (internally) converted to python code and then fed as such to the gettext
 tools.
 >
 > This means that Python string formatting specifiers rules should be
 followed when using the i18n template tags with string literals containing
 extrapolated variables or special meaning chars like `%`. In this case it
 means you literal would need to be `{% trans "findme 10%% " %}`

 I've verified this is behaving correctly with trunk as of now and with
 1.3. Ignore that advice I gave back then. I suspect r11459 fixed this in
 django so it works transparently for the app developer without the need to
 use `%%` with the `trans` i18n template tag.

 To test thing I created a template like this:

 {{{
 {% load i18n %}
 {% trans "a literal with a percent symbol at the end %" %}
 {% trans "a literal with a percent symbol at the end 10%" %}
 {% trans "a literal with a percent % symbol in the middle" %}
 {% trans "a literal with a percent 20% symbol in the middle" %}
 }}}

 `makemessages -l de` created a `.po` file like this from it (note I've
 already added dummy translations):

 {{{
 #: t11240/templates/a.html:2
 msgid "a literal with a percent symbol at the end %"
 msgstr "translation to German of a literal with a percent symbol at the
 end %"

 #: t11240/templates/a.html:3
 msgid "a literal with a percent symbol at the end 10%"
 msgstr ""
 "translation to German of a literal with a percent symbol at the end 10%"

 #: t11240/templates/a.html:4
 #, python-format
 msgid "a literal with a percent % symbol in the middle"
 msgstr ""
 "translation to German of a literal with a percent % symbol in the middle"

 #: t11240/templates/a.html:5
 #, python-format
 msgid "a literal with a percent 20% symbol in the middle"
 msgstr ""
 "translation to German a literal with a percent 20% symbol in the middle"
 }}}

 and `compilemessages` creates a corresponding `.mo` file without problems.

 Setting `LANGUAGE="de"` and using the template in a view correctly shows:

 {{{
 translation to German of a literal with a percent symbol at the end %
 translation to German of a literal with a percent symbol at the end 10%
 translation to German of a literal with a percent % symbol in the middle
 translation to German a literal with a percent 20% symbol in the middle
 }}}

 I'm closing this ticket and setting the reason ''needsinfo''. If you
 reopen it please provide exact details of what you are seeing.

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

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

[Django] #16060: Model entry does not get verified and no error raised

2011-05-20 Thread Django

#16060: Model entry does not get verified and no error raised
---+--
 Reporter:  m.vovcu@…  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  Database layer (models, ORM)
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
---+--
 Model:

 class DestMail(models.Model):
 user = models.ForeignKey(User)[[BR]]

 mail = models.EmailField()[[BR]]

 class Meta:
 unique_together = (("user", "mail"),)
 def __unicode__(self):
 return self.mail

 First of all, even on the command line you can enter anything in the mail-
 field. No verification.

 While used this code:[[BR]]

 ## user defined, mail defined[[BR]]

 m, created = DestMail.objects.get_or_create(user=user,mail=mail)

 Object got created even if it existed. Neither "unique_together" does
 help.

 I have to check anytime something is entered if it's not blank, because
 even blank entries got entered. Although there is no "blank=True"
 directive.

 Didn't seem to have that problem with previous Django release. That's all
 I noticed so far.

 marius

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

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

Re: [Django] #13829: EMAIL_CHARSET setting

2011-05-20 Thread Django

#13829: EMAIL_CHARSET setting
---+-
   Reporter:  IanLewis |  Owner:  nobody
   Type:  New feature  | Status:  closed
  Milestone:   |  Component:  Core (Mail)
Version:  1.2  |   Severity:  Normal
 Resolution:  wontfix  |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  1|Needs tests:  0
Patch needs improvement:  1|  Easy pickings:  0
---+-
Changes (by graham_king):

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


Comment:

 Is an email specific encoding still needed, different from
 DEFAULT_CHARSET? And is it a common enough case to warrant it's own
 setting?

 I think it's rare enough that we can use !EmailMessage (which does support
 setting the encoding) directly in those cases. Given that there's been no
 activity in 6 months, and the patch would need updating anyway, I'm going
 to close. Please re-open as needed.

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

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

Re: [Django] #6362: Remove blank spaces with strip when validating the data

2011-05-20 Thread Django

#6362: Remove blank spaces with strip when validating the data
-+-
   Reporter:  marinho|  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  Forms
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  blank space strip
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by ramiro):

 * easy:  1 => 0


Comment:

 Replying to [comment:39 boxed]:

 ''Easy picking'' is a recently added nullable boolean-like flag for
 tickets in our Trac instance that is reset to false with the first update
 to the ticket after it got added. That is the reason it changes even when
 you hadn't deactivated it explicitly. There is no need to set it back to
 on.

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

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

Re: [Django] #16058: Values_list with distinct return duplicate values

2011-05-20 Thread Django

#16058: Values_list with distinct return duplicate values
-+-
   Reporter: |  Owner:  nobody
  jonasnockert   | Status:  closed
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.3|   Severity:  Normal
 Resolution:  invalid|   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by ramiro):

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


Comment:

 I suspect is is because the (default, implicit) ordering Article model
 queries have and/or the `unique_together` condition. You are seeing
 duplicate results because '.ditinct()` is acting on all the columns
 included in the low level SQL query.

 Take a look at:

  * The note in the
 
[http://docs.djangoproject.com/en/1.3/ref/models/querysets/#django.db.models.query.QuerySet.distinct
 distinct()] method and
  * the suggestion in the last paragraph of the
 
[http://docs.djangoproject.com/en/1.3/ref/models/querysets/#django.db.models.query.QuerySet.values
 values()] method (using `.unique().values_list(...)` if possible)

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

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

Re: [Django] #13635: URLconfs should accept classes as views

2011-05-20 Thread Django

#13635: URLconfs should accept classes as views
-+-
   Reporter:  bfirsh |  Owner:  bfirsh
   Type:  New| Status:  closed
  feature|  Component:  Core (Other)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  urlconf
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by russellm):

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


Comment:

 Agreed - this was resolved with the introduction of generic views.

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

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

Re: [Django] #13635: URLconfs should accept classes as views

2011-05-20 Thread Django

#13635: URLconfs should accept classes as views
-+-
   Reporter:  bfirsh |  Owner:  bfirsh
   Type:  New| Status:  new
  feature|  Component:  Core (Other)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  urlconf
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by graham_king):

 * easy:   => 0


Comment:

 Is this still necessary, given that we can do it this way:
 http://docs.djangoproject.com/en/dev/ref/class-based-views/#generic-views

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

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

Re: [Django] #13612: manage.py imports settings.py even when --settings is used

2011-05-20 Thread Django

#13612: manage.py imports settings.py even when --settings is used
-+-
   Reporter:  tonnzor|  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Core (Management
Version:  SVN|  commands)
 Resolution: |   Severity:  Normal
   Triage Stage:  Accepted   |   Keywords:
Needs documentation:  0  |  Has patch:  1
Patch needs improvement:  0  |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by graham_king):

 * needs_better_patch:  1 => 0
 * easy:   => 0
 * milestone:  1.3 => 1.4


Comment:

 If settings.py is not found, instead of issuing a warning message asking
 the user to run django-admin, couldn't we just do it for them? Only issue
 the error if that doesn't work.

 The attached patch tries {{{management.execute_from_command_line()}}}
 before it issues the warning message.

 That seems to make manage.py work for the three cases:
  - settings.py in current directory
  - settings on command line as --settings (and settings.py in current
 directory is optional)
  - settings in env variable DJANGO_SETTINGS_MODULE (and settings.py in
 current directory is optional)

 A disadvantage is that if no settings.py is present in the current
 directory, and the settings file used throws an !ImportError, the actual
 error is obscured by the warning message. However that message asks you to
 try django-admin.py, which does correctly display the error.

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

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

Re: [Django] #6362: Remove blank spaces with strip when validating the data

2011-05-20 Thread Django

#6362: Remove blank spaces with strip when validating the data
-+-
   Reporter:  marinho|  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  Forms
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  blank space strip
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by boxed):

 * easy:  0 => 1


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

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

Re: [Django] #6362: Remove blank spaces with strip when validating the data

2011-05-20 Thread Django

#6362: Remove blank spaces with strip when validating the data
-+-
   Reporter:  marinho|  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  Forms
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  blank space strip
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by boxed):

 * easy:   => 0


Comment:

 Spaces in various fields in the database screw up sorting too, which gets
 reported as bugs because the spaces are of course not even shown by HTML.

 It's also very hard to fix after the fact. Cron jobs that run strips on
 all character fields on all your models? No thanks :P

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

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

Re: [Django] #16059: FilteredSelectMultiple "remove" button appears disabled

2011-05-20 Thread Django

#16059: FilteredSelectMultiple "remove" button appears disabled
-+-
   Reporter:  boxed  |  Owner:  nobody
   Type: | Status:  new
  Cleanup/optimization   |  Component:  User Experience
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * needs_tests:   => 0
 * easy:  1 => 0
 * stage:  Unreviewed => Design decision needed


Comment:

 I agree that this is not ideal. Also, the fact that "Select your choice(s)
 and click" appears on the right hand side isn't particularly great either.
 I definitely think there's room for improvement -- needs some more design
 discussion.

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

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

[Django] #16059: FilteredSelectMultiple "remove" button appears disabled

2011-05-20 Thread Django

#16059: FilteredSelectMultiple "remove" button appears disabled
--+-
 Reporter:  boxed |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Milestone:|  Component:  User Experience
  Version:  1.3   |   Severity:  Normal
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  1
--+-
 The color choice for the remove buttons for FilteredSelectMultiple is
 unfortunate. Multiple times when looking at someone doing a demo of a site
 that used this control I see them hesitate before clicking the button,
 even though they have used it multiple times before. The reason is that
 the gray color when viewed in opposition to the blue looks like it's
 disabled.

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

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

Re: [Django] #10696: manage.py throws away exception information

2011-05-20 Thread Django

#10696: manage.py throws away exception information
-+-
   Reporter:  Leo|  Owner:  nobody
   Type:  Bug| Status:  closed
  Milestone: |  Component:  Core (Other)
Version:  SVN|   Severity:  Normal
 Resolution:  duplicate  |   Keywords:
   Triage Stage:  Design |  Has patch:  0
  decision needed|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by graham_king):

 * status:  new => closed
 * resolution:   => duplicate
 * easy:   => 0


Comment:

 Looks like a duplicate of #14130. Please re-open if I'm mistaken.

 Either way, the problem is gone. I've tried every which way I can think to
 cause an error in settings.py (import errors, regular errors, file
 permission errors deep within the logging module, etc) and it always gets
 reported correctly to the console.

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

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

Re: [Django] #15880: manage.py: difficult to run in background (and crashes when input isn't a terminal)

2011-05-20 Thread Django

#15880: manage.py: difficult to run in background (and crashes when input isn't 
a
terminal)
-+-
   Reporter: |  Owner:  nobody
  dstndstn@… | Status:  new
   Type:  Bug|  Component:  Core (Management
  Milestone: |  commands)
Version:  1.3|   Severity:  Release blocker
 Resolution: |   Keywords:  regression
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-

Comment (by kmtracey):

 Replying to [comment:11 brillgen]:
 > I can confirm that the brutal hack described above works for me as
 well...not sure of its bigger implications

 But is that "brutal hack" described above even necessary with current
 trunk, 1.3.X, or 1.2.X code levels? The fix put in (r15911, r15912,
 r16029) should avoid the need for that hack since it avoids calling
 termios if stdin is not a tty. So far as I can see there's no need for the
 brutal hack since that problem was already fixed in current code
 levels...if that is not the case someone please spell out what exactly you
 are doing to still see a problem current code levels.

 To my mind this ticket is open to deal with the stalling issue, which was
 not addressed by the already-in-place fix. Nobody has commented on that
 patch -- are you saying that you don't see the stalling in whatever setup
 you are using (which is...?)?

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

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

Re: [Django] #15880: manage.py: difficult to run in background (and crashes when input isn't a terminal)

2011-05-20 Thread Django

#15880: manage.py: difficult to run in background (and crashes when input isn't 
a
terminal)
-+-
   Reporter: |  Owner:  nobody
  dstndstn@… | Status:  new
   Type:  Bug|  Component:  Core (Management
  Milestone: |  commands)
Version:  1.3|   Severity:  Release blocker
 Resolution: |   Keywords:  regression
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-

Comment (by brillgen):

 I can confirm that the brutal hack described above works for me as
 well...not sure of its bigger implications

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

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

Re: [Django] #15796: Contributing docs need to be updated to include new triage stages and ticket states

2011-05-20 Thread Django

#15796: Contributing docs need to be updated to include new triage stages and
ticket states
-+-
   Reporter:  russellm   |  Owner:  julien
   Type:  Bug| Status:  new
  Milestone: |  Component:  Documentation
Version:  1.2|   Severity:  Release blocker
 Resolution: |   Keywords:
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by jezdez):

 * stage:  Accepted => Ready for checkin


Comment:

 Content wise it's great stuff, marking it as RFC.

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

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

Re: [Django] #15796: Contributing docs need to be updated to include new triage stages and ticket states

2011-05-20 Thread Django

#15796: Contributing docs need to be updated to include new triage stages and
ticket states
+-
   Reporter:  russellm  |  Owner:  julien
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Documentation
Version:  1.2   |   Severity:  Release blocker
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
+-

Comment (by jezdez):

 It's not correct anymore to point to Jacob to add a blog to the community
 section since the community-redux refactor landed. You can simply add your
 feed yourself.

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

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

Re: [Django] #5805: Specify multicolumn indexes.

2011-05-20 Thread Django

#5805: Specify multicolumn indexes.
-+-
   Reporter:  Stavros|  Owner:  nobody
  Korokithakis    | Status:  reopened
   Type:  New|  Component:  Database layer
  feature|  (models, ORM)
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  index multicolumn
 Resolution: |  indexes database
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-
Changes (by mpessas):

 * cc: mpessas (added)


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

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

Re: [Django] #16021: Minor documentation fixes for Generic Class Views

2011-05-20 Thread Django

#16021: Minor documentation fixes for Generic Class Views
-+-
   Reporter:  Bradley|  Owner:  nobody
  Ayers | Status:  new
   Type:  Bug|  Component:  Documentation
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Ready for  |Needs tests:  0
  checkin|  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * stage:  Accepted => Ready for checkin


Comment:

 Thanks a lot. The patch looks good. I've just capitalized the word "Model"
 ;-)

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

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

Re: [Django] #15796: Contributing docs need to be updated to include new triage stages and ticket states

2011-05-20 Thread Django

#15796: Contributing docs need to be updated to include new triage stages and
ticket states
+-
   Reporter:  russellm  |  Owner:  julien
   Type:  Bug   | Status:  new
  Milestone:|  Component:  Documentation
Version:  1.2   |   Severity:  Release blocker
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
+-
Changes (by julien):

 * has_patch:  0 => 1


Comment:

 This was a big patch so I took it to the dev-list for feedback:
 http://groups.google.com/group/django-
 developers/browse_thread/thread/15441f05a72063fd

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

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

Re: [Django] #494: Collapse in admin interface for inline related objects

2011-05-20 Thread Django

#494: Collapse in admin interface for inline related objects
-+-
   Reporter: |  Owner:  aptiko
  jcstover@… | Status:  reopened
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone: |   Keywords:  edit_inline, nfa-
Version:  SVN|  someday
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  1
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
-+-
Changes (by CarstenF):

 * cc: carsten.fuchs@… (added)
 * easy:   => 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #8281: Django running ounder PyISAPIe on IIS doesn't detect HTTPS

2011-05-20 Thread Django

#8281: Django running ounder PyISAPIe on IIS doesn't detect HTTPS
---+
   Reporter:  KayEss   |  Owner:  nobody
   Type:  New feature  | Status:  closed
  Milestone:   |  Component:  HTTP handling
Version:  1.0-alpha|   Severity:  Normal
 Resolution:  wontfix  |   Keywords:  PyISAPIe HTTPS
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  1|  Easy pickings:  0
---+
Changes (by lukeplant):

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


Comment:

 I can't see any reason why this needs to be in Django, rather than in your
 PyASPIe handler (which I have no access to - it's not part of Django and I
 can't find it). Look at `WSGIRequest` in django/core/handlers/wsgi.py for
 an example.

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

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

Re: [Django] #8281: Django running ounder PyISAPIe on IIS doesn't detect HTTPS

2011-05-20 Thread Django

#8281: Django running ounder PyISAPIe on IIS doesn't detect HTTPS
---+
   Reporter:  KayEss   |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  HTTP handling
Version:  1.0-alpha|   Severity:  Normal
 Resolution:   |   Keywords:  PyISAPIe HTTPS
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  1|  Easy pickings:  0
---+
Changes (by ayaz@…):

 * easy:   => 0


Comment:

 Hello everyone:

 I'd like to give this a gentle push.

 If I may ask, is there any chance this could make it into trunk? This
 ticket was opened three years ago. I recently deployed multiple Django web
 applications on IIS7 using PyISAPIe and got bitten by this bug.

 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #13721: pass extra content-type values to file upload handlers

2011-05-20 Thread Django

#13721: pass extra content-type values to file upload handlers
-+-
   Reporter: |  Owner:  nobody
  wkornewald | Status:  new
   Type:  New|  Component:  File
  feature|  uploads/storage
  Milestone:  1.4|   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-
Changes (by wkornewald):

 * needs_better_patch:  1 => 0
 * version:  1.2 => SVN
 * milestone:  1.3 => 1.4


Comment:

 I've updated 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #16051: Misleading information in Writing your first Django app, part 3

2011-05-20 Thread Django

#16051: Misleading information in Writing your first Django app, part 3
-+-
   Reporter: |  Owner:  ShawnMilo
  felix.morency@…| Status:  new
   Type: |  Component:  Documentation
  Cleanup/optimization   |   Severity:  Normal
  Milestone:  1.4|   Keywords:
Version:  SVN|  Has patch:  1
 Resolution: |Needs tests:  0
   Triage Stage:  Ready for  |  Easy pickings:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by graham_king):

 * component:  Djangoproject.com Web site => Documentation
 * version:  1.3 => SVN
 * easy:  1 => 0
 * milestone:   => 1.4
 * type:  New feature => Cleanup/optimization
 * stage:  Accepted => Ready for checkin


Comment:

 I agree that this makes things clearer. The text either refers to the
 URLconf ''polls.urls'' - as in {{{(r'^polls/', include('polls.urls'))}}} -
 or it refers to the file ''polls/urls.py''. In this case it is the file
 being referred to.

 The patch applies cleanly to the latest trunk in SVN.

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

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

[Django] #16058: Values_list with distinct return duplicate values

2011-05-20 Thread Django

#16058: Values_list with distinct return duplicate values
--+--
 Reporter:  jonasnockert  |  Owner:  nobody
 Type:  Bug   | Status:  new
Milestone:|  Component:  Database layer (models, ORM)
  Version:  1.3   |   Severity:  Normal
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
--+--
 I'm using Django 1.3 with the following model (and as far as I can tell
 the generated sqlite3 schema looks okay as well):
 {{{
 class Article(Model):
 product_number = PositiveIntegerField(_("Product number"),
 db_index=True)
 product_variant = PositiveIntegerField(_("Variant"), db_index=True)
 ...
 class Meta:
 unique_together = (('product_number', 'product_variant'),)
 ordering = ['-date_added']

 }}}

 I'm making the following query which returns duplicate results:
 {{{
 >>>
 Article.objects.filter(product_number=99668).values_list('product_number',
 flat=True).distinct()
 [99668, 99668]
 }}}

 It looks like a bug from here but I'm also a bit sceptical since other
 people seem to be using this query construct successfully.

 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 this group at 
http://groups.google.com/group/django-updates?hl=en.

41 matches

Mail list logo