Re: [Django] #3594: Translation problem in javascript

[Django]

#3594: Translation problem in javascript
---+
  Reporter:  karsu | Owner:  msaelices
Status:  reopened  | Milestone:   
 Component:  Internationalization  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Changes (by arkx):

  * needs_better_patch:  1 => 0

Comment:

 I've attempted to create a patch that fixes the issue without causing
 breakage in cases where people want the fallback language to be other than
 English.

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

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

[Django]

#494: Collapse in admin interface for inline related objects
---+
  Reporter:  jcsto...@nilling.nl   | Owner:  aptiko 
 
Status:  reopened  | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  edit_inline, 
nfa-someday
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Comment (by anonymous):

 {{{
 I didn't use django for a while, but from what I remember.
 For a tablular view of related objects you can collapse that
 view, but not when it is stacked. That was it about. If it is
 working for stacked objects now its okay.
 }}}

 How can I do that? (aka, is there a work around for doing this w/o
 patching code?)

-- 
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] #373: Add support for multiple-column primary keys

[Django]

#373: Add support for multiple-column primary keys
---+
  Reporter:  jacob | Owner:  dcramer 
Status:  assigned  | Milestone:  
 Component:  Database layer (models, ORM)  |   Version:  
Resolution:|  Keywords:  database
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by Stef Walter ):

 * cc: s...@memberwebs.com (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] #11869: makemessages command hangs when there're many errors in the .po file

[Django]

#11869: makemessages command hangs when there're many errors in the .po file
---+
  Reporter:  jmv   | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  Internationalization  |   Version:  1.1

Resolution:|  Keywords:  gettext, msgmerge, 
popen3, i18n
 Stage:  Unreviewed| Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Changes (by soulburner):

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

Comment:

 ran into the same issue (repeatable, just had a file with a lot of
 error(warning because i had a lot of strings with unnamed arguments)),
 from python sub-process docs
 "
 Warning

 This will deadlock if the child process generates enough output to a
 stdout or stderr pipe such that it blocks waiting for the OS pipe buffer
 to accept more data. Use communicate() to avoid that.
 "
 so my fix was this

 from subprocess import Popen, PIPE
 p = Popen(cmd, shell=True,stdin=PIPE, stdout=PIPE,
 stderr=PIPE)
 (msgs, errors) = p.communicate()

-- 
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] #11465: Broken representation of nonexisting objects for raw_id_fields

[Django]

#11465: Broken representation of nonexisting objects for raw_id_fields
---+
  Reporter:  sa...@wp.pl   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by Alex):

 Could have been.  If so my mistake.

-- 
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] #11985: not generating all fields

[Django]

#11985: not generating all fields
+---
  Reporter:  maciejplonski  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution:  worksforme |  Keywords:  orm   
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 Cutting and pasting exactly what you have posted into a new app's
 models.py file, adding an import for datetime, and running manage.py sql
 on the new app, produces SQL that includes the is_mod and is_active
 fields:

 {{{
 k...@lbox:~/software/web/playground$ python manage.py sql 
 BEGIN;
 CREATE TABLE "_user" (
 "id" integer NOT NULL PRIMARY KEY,
 "username" varchar(30) NOT NULL UNIQUE,
 "first_name" varchar(30) NOT NULL,
 "last_name" varchar(30) NOT NULL,
 "email" varchar(75) NOT NULL,
 "public_email" bool NOT NULL,
 "password" varchar(128) NOT NULL,
 "is_active" bool NOT NULL,
 "is_mod" bool NOT NULL,
 "last_login" datetime NOT NULL,
 "date_joined" datetime NOT NULL
 )
 ;
 COMMIT;
 }}}

 Really, Django SQL generation for tables is not fundamentally broken.
 Whatever is going on is something weird in your setup.  The right place to
 figure out what that is is django-users or the IRC channel.

 I will also note you posted the model definitions for 'user' and 'group'
 but the SQL generated for 'fuser' and 'fgroup'.  You really need to post
 (in one of those other places, not here) exactly what you are using, not
 something kind of like it.  Figuring out what is wrong with something kind
 of different from what you are actually using is going to be very hard.

-- 
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] #11985: not generating all fields

[Django]

#11985: not generating all fields
+---
  Reporter:  maciejplonski  | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Uncategorized  |   Version:  1.1   
Resolution: |  Keywords:  orm   
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by maciejplonski):

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

Comment:

 no, I deleted database and did syncdb again - there is still no 'is_mod'
 and 'is_active' field in database

-- 
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] #11957: runserver must be restarted after error in admin.py

[Django]

#11957: runserver must be restarted after error in admin.py
+---
  Reporter:  carljm | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  django-admin.py runserver  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 I don't have time to look into it now, but I agree it's worth looking into
 so I suppose it might as well be open.  If someone can explain the
 rationale for rejecting the proposed approach in #8245 that would be
 helpful.  Without understanding that I'm reluctant to simply proceed with
 adopting something that was previously rejected.

-- 
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] #11465: Broken representation of nonexisting objects for raw_id_fields

[Django]

#11465: Broken representation of nonexisting objects for raw_id_fields
---+
  Reporter:  sa...@wp.pl   | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 Replying to [comment:2 Alex]:
 > Duplicate of another ticket that reports this exact same thing (and
 who's number I can't recall).

 Might be #8746 you were thinking of but that has been "fixed" without
 actually fixing this case.  I can't find any open tickets reporting this,
 so it seems valid for this to be open.

-- 
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] #11991: Inconsistent MEDIA_URL values

[Django]

#11991: Inconsistent MEDIA_URL values
+---
 Reporter:  anonymous   |   Owner:  nobody
   Status:  new |   Milestone:  1.2   
Component:  Core framework  | Version:  SVN   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 The documentation states the following:
 {{{
 URL that handles the media served from MEDIA_ROOT. Example:
 "http://media.lawrence.com;

 Note that this should have a trailing slash if it has a path component.

 Good: "http://www.example.com/static/; Bad:
 "http://www.example.com/static;
 }}}

 Why does a path component need to have a trailing slash but a domain
 doesn't?

 We should pick one of these forms, as changing the value affects other
 areas (like the FileField.url attribute).
 I, personally, think the slash-less form makes templates look better:
 {{{
 ...

 Versus:
 ...
 }}}

-- 
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] #11990: TECHNICAL_404_TEMPLATE doesn't see URLConfs directly on request objects

[Django]

#11990: TECHNICAL_404_TEMPLATE doesn't see URLConfs directly on request objects
---+
 Reporter:  mattbennett|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Core framework | Version:  SVN   
 Keywords:  404, urlconf, debug, template  |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 The default debug 404 template in django/views/debug.py assumes that the
 urlconf searched was the root urlconf. Since [4237] the urlconf can be set
 by middleware, so this is not necessarily the case.

 The attached patch puts the module name of the urlconf being used into the
 template context, and modifies the template accordingly.

-- 
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] #11989: Allow @register.inclusion_tag to take a template as well as a template name

[Django]

#11989: Allow @register.inclusion_tag to take a template as well as a template 
name
---+
   Reporter:  jdunck   |Owner:  nobody
 Status:  new  |Milestone:
  Component:  Template system  |  Version:  1.1   
   Keywords:   |Stage:  Unreviewed
  Has_patch:  0|   Needs_docs:  1 
Needs_tests:  1|   Needs_better_patch:  1 
---+
 Sometimes, I want the convenience of an inclusion_tag without specifying
 an external template.  I can't use simple_tag because I need context
 access.

 @inclusion_tag allows either a template name or an iterable of template
 names.

 The attach patch allows a template to be given directly, as well.

 I noticed @inclusion_tag doesn't seem to be currently tested, and this
 patch doesn't include tests.  Where should @inclusion_tag tests live?

-- 
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] #5833: Custom FilterSpecs

[Django]

#5833: Custom FilterSpecs
---+
  Reporter:  Honza_Kral| Owner:  jkocherhans
 
Status:  assigned  | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  nfa-someday 
list_filter filterspec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  1 |   Needs_tests:  1  
 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: seanl (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] #3400: [patch] Support for lookup separator with list_filter admin option

[Django]

#3400: [patch] Support for lookup separator with list_filter admin option
---+
  Reporter:  n...@intv.com.au  | Owner:  jakub_vysoky   
 
Status:  new   | Milestone:  1.2
 
 Component:  django.contrib.admin  |   Version:  newforms-admin 
 
Resolution:|  Keywords:  edc nfa-someday 
list_filter FilterSpec nfa-changelist ep2008
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  1  
 
Needs_better_patch:  1 |  
---+
Changes (by andybak):

 * cc: a...@andybak.net (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] #11988: Wrong translated result count text on admin search form block when LANGUAGE_CODE = 'zh-CN'

[Django]

#11988: Wrong translated result count text on admin search form block when
LANGUAGE_CODE = 'zh-CN'
---+
  Reporter:  twinsant  | Owner:  nobody 
Status:  new   | Milestone: 
 Component:  Translations  |   Version:  1.1
Resolution:|  Keywords:  search_form
 Stage:  Unreviewed| Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by twinsant):

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

Comment:

 forgot the bug code block:
 django/contrib/admin/templates/admin/search_form.html

 {% if show_result_count %}
 {% blocktrans count cl.result_count as
 counter %}1 result{% plural %}{{ counter }} results{% endblocktrans %} ({% blocktrans with
 cl.full_result_count as full_result_count %}{{ full_result_count }}
 total{% endblocktrans %})
 {% endif %}

-- 
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] #11988: Wrong translated result count text on admin search form block when LANGUAGE_CODE = 'zh-CN'

[Django]

#11988: Wrong translated result count text on admin search form block when
LANGUAGE_CODE = 'zh-CN'
--+-
 Reporter:  twinsant  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Translations  | Version:  1.1   
 Keywords:  search_form   |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 1 result/{{ coutner }} results always will be "1 个结果", which means 1
 result in Chinese.

 We have two solution for this bug, just see attached files.

-- 
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] #11987: destroy_test_db can destroy the production database in some situations

[Django]

#11987: destroy_test_db can destroy the production database in some situations
---+
 Reporter:  eronen |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I have some tests which need to be run against the production database, so
 these test cases temporarily change settings.DATABASE_NAME. If those get
 interrupted (by e.g. Control-C) in the wrong place, settings.DATABASE_NAME
 might be left pointing to the production database.

 Ticket #10868 describes another situation (involving threads) where
 destroy_test_db could end up destroying the wrong database.

 There might be other reasons why this could happen. I would suggest
 rewriting this line in a bit safer way to avoid this ituation. Perhaps
 something like this:

 {{{
 OLD:
 test_database_name = settings.DATABASE_NAME
 NEW:
 if settings.TEST_DATABASE_NAME:
 test_database_name = settings.TEST_DATABASE_NAME
 elif settings.DATABASE_NAME.startswith(TEST_DATABASE_PREFIX):
 test_database_name = settings.DATABASE_NAME
 else:
 test_database_name = TEST_DATABASE_PREFIX + settings.DATABASE_NAME
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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
-~--~~~~--~~--~--~---