Re: [Django] #11154: Inconsistency with permissions for proxy models

[Django]

#11154: Inconsistency with permissions for proxy models
--+
 Reporter:  etianen   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  SVN
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by the_drow):

 * cc: omer.drow@… (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] #17181: Allow for specifying multiple locales and domains for makemessages and compilemessages commands

[Django]

#17181: Allow for specifying multiple locales and domains for makemessages and
compilemessages commands
-+-
 Reporter:  aminland |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:   |  Version:  1.3
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  i18n makemessages|  Needs documentation:  0
  compilemessages|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by julien):

 * type:  Uncategorized => New feature
 * stage:  Unreviewed => Accepted


Comment:

 That sounds good to me. I'm just wondering if we should allow "-d django
 -d djangojs -l de -l fr" or "-d django,djangojs -l de,fr" or both. Note
 that the "extensions" option of `makemessages` allows both.

-- 
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] #17181: Allow for specifying multiple locales and domains for makemessages and compilemessages commands

[Django]

#17181: Allow for specifying multiple locales and domains for makemessages and
compilemessages commands
-+-
 Reporter:  aminland |Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:   |  Version:  1.3
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  i18n makemessages|  Unreviewed
  compilemessages|  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by aminland):

 * cc: aminland@… (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #17181: Allow for specifying multiple locales and domains for makemessages and compilemessages commands

[Django]

#17181: Allow for specifying multiple locales and domains for makemessages and
compilemessages commands
-+-
 Reporter:  aminland |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:   |Version:  1.3
  Internationalization   |   Keywords:  i18n makemessages
 Severity:  Normal   |  compilemessages
 Triage Stage:  Unreviewed   |  Has patch:  1
Easy pickings:  1|  UI/UX:  0
-+-
 It is pretty annoying to have to run the commands separately for each
 language/domain combo without having to do all of them. Lets say only
 german, spanish, french, and italian have been changed. Your current
 choices are to run makemessages 8 times (4 each for django and djangojs
 domains), or to run it for all languages (which in the case of a large
 project like django itself, will take much much longer).

 This patch allows you to specify multiple languages and/or domains when
 doing translation.

 The old way:
 {{{
 django-admin.py makemessages -d django -l de
 django-admin.py makemessages -d django -l fr
 django-admin.py makemessages -d django -l es
 django-admin.py makemessages -d django -l it
 django-admin.py makemessages -d djangojs -l de
 django-admin.py makemessages -d djangojs -l fr
 django-admin.py makemessages -d djangojs -l es
 django-admin.py makemessages -d djangojs -l it
 django-admin.py compilemessages -l de
 django-admin.py compilemessages -l fr
 django-admin.py compilemessages -l es
 django-admin.py compilemessages -l it
 }}}
 With this patch:
 {{{
 django-admin.py makemessages -d django -d djangojs -l de -l fr -l es -l it
 django-admin.py compilemessages -l de -l fr -l es -l it
 }}}


 Backwards compatibility is maintained, and the existing defaults remain.

-- 
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] #14586: Make interpolate JS function not require the named parameter.

[Django]

#14586: Make interpolate JS function not require the named parameter.
-+-
 Reporter:  aminland |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.2
Component:   |   Resolution:
  Internationalization   | Triage Stage:  Design
 Severity:  Normal   |  decision needed
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anonymous):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 Looking at the two lines changed makes it pretty clear that backwards
 compatibility remains intact. The only thing it does is allow for the
 option to be omitted.

-- 
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] #17180: Documentation should mention that {% load i18n %} is needed in every template

[Django]

#17180: Documentation should mention that {% load i18n %} is needed in every
template
--+
 Reporter:  stefan.freyr@…|  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.3
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  1 |  UI/UX:  0
--+
 The documentation for i18n doesn't explicitly state that the {% load i18n
 %} statement needs to be put into every template file, even the ones that
 extend from a template that has already loaded the i18n template tags.

 At https://docs.djangoproject.com/en/1.3/topics/i18n/internationalization/

 The paragraph:

 "Translations in Django templates uses two template tags and a slightly
 different syntax than in Python code. To give your template access to
 these tags, put {% load i18n %} toward the top of your template."

 Might be extended as:

 "Translations in Django templates uses two template tags and a slightly
 different syntax than in Python code. To give your template access to
 these tags, put {% load i18n %} toward the top of your template. Note that
 this needs to be stated in all templates that use translations, even the
 ones which extend from templates that have already loaded the i18n tags."

-- 
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] #17179: yesno arg is optional

[Django]

#17179: yesno arg is optional
---+
 Reporter:  CarlFK |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 "Given a string mapping values for true, false and (optionally) None,
 returns one of those strings according to the value:"
 https://docs.djangoproject.com/en/dev/ref/templates/builtins/#yesno

 Looking at the code, I see the string is optional.

 if arg is None:
 arg = ugettext('yes,no,maybe')

 
http://code.djangoproject.com/svn/django/trunk/django/template/defaultfilters.py

-- 
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] #10964: Admin for group doesn't allow to easily add users to the group

[Django]

#10964: Admin for group doesn't allow to easily add users to the group
-+-
 Reporter:  gruszczy |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  SVN
 Severity:  Normal   |   Resolution:
 Keywords:  admin, groups| Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  1|  Needs documentation:  1
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  1
-+-
Changes (by koenb):

 * needs_better_patch:  0 => 1
 * easy:   => 0
 * needs_docs:  0 => 1


Comment:

 Added a patch that allows adding a descriptor of a reverse m2m (like
 'user_set') to the fields list for a form.

 An extra is that you can also add the same into the fields and
 filter_horizontal attributes of a modeladmin.

 As an example this is used into the GroupAdmin to allow easy user
 selection for a group.

 No tests or documentation yet, since I am not completely happy with the
 implementation yet.

 I think an implementation for reverse foreign keys would also be usefull.

 Feedback welcome.

-- 
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] #17177: Building django documentation with Sphinx 1.1

[Django]

#17177: Building django documentation with Sphinx 1.1
---+--
 Reporter:  gavenkoa   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.3
 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:  0
---+--
Changes (by gavenkoa):

 * cc: gavenkoa (added)
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #17177: Building django documentation with Sphinx 1.1

[Django]

#17177: Building django documentation with Sphinx 1.1
---+
 Reporter:  gavenkoa   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.3
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 I install **python-sphinx** from Cygwin:
 {{{
   $ cygcheck.exe -c python-sphinx
 Cygwin Package Information
 Package  VersionStatus
 python-sphinx1.1-1  OK
 }}}
 Get Django from official mirror:
 {{{
   $ hg clone https://bitbucket.org/django/django
   $ hg up -r releases/1.3.1
 }}}
 and try build **html** docs:
 {{{
   $ cd docs
   $ make html
 }}}
 I get error:
 {{{
 sphinx-build -b djangohtml -d _build/doctrees   . _build/html
 Running Sphinx v1.1
 loading pickled environment... done
 building [djangohtml]: targets for 205 source files that are out of date
 updating environment: [config changed] 205 added, 0 changed, 0 removed
 reading sources... [100%] topics/testing
 looking for now-outdated files... none found
 pickling environment... done
 checking consistency... done
 preparing documents... done
 writing output... [  5%] howto/apache-auth
 Exception occurred:
   File "/usr/lib/python2.6/site-packages/sphinx/writers/html.py", line
 522, in visit_row
 self._table_row_index += 1
 AttributeError: DjangoHTMLTranslator instance has no attribute
 '_table_row_index'
 }}}
 I go to **docs/_ext/djangodocs.py** class **DjangoHTMLTranslator** and
 just add **_table_row_index** field. Next build stoped at:
 {{{
   $ make html
 sphinx-build -b djangohtml -d _build/doctrees   . _build/html
 Running Sphinx v1.1
 loading pickled environment... done
 building [djangohtml]: targets for 205 source files that are out of date
 updating environment: 0 added, 0 changed, 0 removed
 looking for now-outdated files... none found
 preparing documents... done
 writing output... [  7%] howto/custom-management-commands
 Exception occurred:
   File "/usr/lib/python2.6/site-packages/sphinx/writers/html.py", line
 125, in visit_desc_parameter
 self.body.append(self.param_separator)
 AttributeError: DjangoHTMLTranslator instance has no attribute
 'param_separator'
 }}}
 So I add **param_separator** to **DjangoHTMLTranslator**. So I get:
 {{{
 class DjangoHTMLTranslator(SmartyPantsHTMLTranslator):
 """
 Django-specific reST to HTML tweaks.
 """

 _table_row_index = 0
 param_separator = ', '

 
 }}}
 After this I succesfully build Djando docs!

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

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

Re: [Django] #17073: focus uwsgi docs to only Django integration

[Django]

#17073: focus uwsgi docs to only Django integration
--+
 Reporter:  ptone |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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 |UI/UX:  0
--+
Changes (by anonymous):

 * needs_better_patch:  1 => 0


Comment:

 updated to trunk, fixed the typo in the external link

-- 
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] #16986: Model.clean cannot report errors on individual fields

[Django]

#16986: Model.clean cannot report errors on individual fields
-+-
 Reporter:  davidfstr|Owner:  davidfstr
 Type:  New feature  |   Status:  new
Component:  Forms|  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|UI/UX:  0
-+-

Comment (by kmtracey):

 Adding this makes sense to me...however I'm a little curious if there was
 a good reason for this not being done by r12402.

-- 
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] #17176: Problem when retrieving objects with AND over multiple OR statements

[Django]

#17176: Problem when retrieving objects with AND over multiple OR statements
-+-
 Reporter:  hanson2010   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by hanson2010):

 Thanks for your quick input. Then what is the related package? Any advice
 is appreciated!

-- 
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] #2879: Add live test server support to test framework

[Django]

#2879: Add live test server support to test framework
-+-
 Reporter:  Mikeal Rogers|Owner:  devin
   |   Status:  new
 Type:  New feature  |  Version:
Component:  Testing framework|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by julien):

 The latest patch brings two major improvements: 1) static media are now
 handled properly, allowing Selenium tests to be run from a project via
 `manage.py test` (the previous patch only allowed them to work in the
 Django test suite); and 2) I think I've solved the threading issues by
 borrowing a bit of code from `SocketServer.BaseServer` in Python 2.6.

 I'm now reasonably happy with the implementation and will move on to
 writing more documentation. At this stage I'd really appreciate getting
 some feedback from testers so we can identify and address any edge cases.
 Thank you!

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

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

Re: [Django] #11077: Django's built-in tests fail when using url reverse tags in default registration templates

[Django]

#11077: Django's built-in tests fail when using url reverse tags in default
registration templates
-+-
 Reporter:  srosro   |Owner:  nobody
 Type:  Bug  |   Status:  reopened
Component:  Testing framework|  Version:
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Design
Has patch:  1|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  1
 |UI/UX:  0
-+-

Comment (by anonymous):

 +1, this occurred for us when we tried to over ride the default 500 error
 template. 500.html which in turn inherited from a base template that
 contained a % url.

-- 
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] #17176: Problem when retrieving objects with AND over multiple OR statements

[Django]

#17176: Problem when retrieving objects with AND over multiple OR statements
-+-
 Reporter:  hanson2010   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.3
  (models, ORM)  |   Resolution:
 Severity:  Normal   |  worksforme
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 It isn't a problem with Django:

 {{{
 >>> AutoName.objects.all()
 [, ]
 >>> AutoName.objects.filter(Q(name=u'A') | Q(name=u'B'), Q(name=u'C') |
 Q(name=u'D'))
 []
 >>> AutoName.objects.filter(Q(name=u'A') | Q(name=u'B'))
 []
 >>> AutoName.objects.filter(Q(name=u'C') | Q(name=u'D'))
 []
 }}}

 (example with the models from https://bitbucket.org/aaugustin/django-tz-
 demo)

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