[Django] #18475: Sorts of interesting

[Django]

#18475: Sorts of interesting
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 There are actually distinctive MMA [http://www.burberryhub.org/ burberry
 handbags] supporters and athletes many of these days which of you aspire
 to be really serious UFC contenders.

-- 
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] #18474: Bags from new york st.

[Django]

#18474: Bags from new york st.
---+
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 If the los angeles accountant generally offer people with your specifics
 in a painless to be aware of data format, [http://www.burberryhub.org/
 burberry outlet] store online you will probably be before towards the
 winner.

-- 
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] #18473: Contradictory advice on middleware order

[Django]

#18473: Contradictory advice on middleware order
-+-
 Reporter:  david@…  |  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |Version:  1.4
Component:  Documentation|   Keywords:  middleware order
 Severity:  Normal   |  GZipMiddleware
 Triage Stage:  Unreviewed   |  UpdateCacheMiddleware
Easy pickings:  0|  Has patch:  0
 |  UI/UX:  0
-+-
 From
 
https://docs.djangoproject.com/en/dev/ref/middleware/#django.middleware.gzip.GZipMiddleware
   It is suggested to place this first in the middleware list, so that the
 compression
   of the response content is the last thing that happens.

 From https://docs.djangoproject.com/en/dev/topics/cache/#order-of-
 middleware-classes
   you need to make sure that !UpdateCacheMiddleware appears before any
 other middleware
   that might add something to the Vary header. The following middleware
 modules do so:

 !SessionMiddleware adds Cookie \\
 GZipMiddleware adds Accept-Encoding


 I suspect
 
https://docs.djangoproject.com/en/dev/ref/middleware/#django.middleware.gzip.GZipMiddleware
 might need to be changed. With GZipMiddleware first, not only will it
 alter the "Vary" header handling, but presumably it will be recompressing
 the uncompressed cached content on each request, and it would be better to
 cache the compressed content instead.

-- 
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] #18471: Add a localization field option in Model Fields.

[Django]

#18471: Add a localization field option in Model Fields.
-+-
 Reporter:  serge_spaolonzi  |Owner:
 Type:  New feature  |  serge_spaolonzi
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 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 serge_spaolonzi):

 This is the link to my fork in Github:
 https://github.com/cobalys/django/tree/ticket_18471

 The modified file is: django/django/db/models/fields/__init__.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] #18471: Add a localization field option in Model Fields. (was: Add a new field option for localization in Model Fields.)

[Django]

#18471: Add a localization field option in Model Fields.
-+-
 Reporter:  serge_spaolonzi  |Owner:
 Type:  New feature  |  serge_spaolonzi
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  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] #18472: `set_language` view documentation improvements

[Django]

#18472: `set_language` view documentation improvements
--+
 Reporter:  DrMeers   |  Owner:  DrMeers
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.4
 Severity:  Normal|   Keywords:  i18n, set_language
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 * I've seen people get confused by including the `set_language` URL within
 their `i18n_patterns` and wondering why it doesn't work (the form `POST`
 turns into a redirected `GET` request which fails); we should probably add
 a warning to ensure that this URL is locale-independent
 * Why do we have a hardcoded URL as the form `action`? This should be
 reversed instead, and possibly have a name added to the URL.

 Happy to tackle/commit this, just wanted to make sure I wasn't missing
 anything.

-- 
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] #18471: Add a new field option for localization in Model Fields.

[Django]

#18471: Add a new field option for localization in Model Fields.
-+-
 Reporter:  serge_spaolonzi  |Owner:
 Type:  New feature  |  serge_spaolonzi
Component:  Database layer   |   Status:  assigned
  (models, ORM)  |  Version:  1.4
 Severity:  Normal   |   Resolution:
 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 serge_spaolonzi):

 * owner:  nobody => serge_spaolonzi
 * needs_docs:   => 0
 * status:  new => assigned
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 This is the link to my fork in Github:
 https://github.com/cobalys/django/tree/ticket_18471

 The modified file is: django/django/db/models/fields/__init__.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.

[Django] #18471: Add a new field option for localization in Model Fields.

[Django]

#18471: Add a new field option for localization in Model Fields.
--+
 Reporter:  serge_spaolonzi   |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Add a new field option for localization in Model Fields in order to
 simplify the process of localization.
 It happens that activating the localization of a field in the Admin site
 from a model is a complex task now.
 Instead it can be done easily using only a parameter in the Model
 declaration, in order to archive this I had to modify three lines in the
 file django.db.models.fields.__init__.py


 '''Example:'''
 Expected result localization of a decimal field in a model according to
 the THOUSAND_SEPARATOR setting.

 '''Currently it is done this way'''
 {{{
 import django

 class LocalizedModelForm(django.forms.ModelForm):
 def __new__(cls, *args, **kwargs):
 new_class = super(LocalizedModelForm, cls).__new__(cls, *args,
 **kwargs)
 for field in new_class.base_fields.values():
 if isinstance(field, django.forms.DecimalField):
 field.localize = True
 field.widget.is_localized = True
 return new_class

 class FooForm(LocalizedModelForm):
 class Meta:
 model = Foo

 django.admin.site.register(Foo, form=FooForm)
 }}}


 '''After improvement it can be done easily'''
 {{{
 class Foo(models.Model)
 price = models.DecimalField(verbose_name='Price', max_digits=20,
 decimal_places=2, localize=True)
 }}}


 I have the patched code in my Github fork, I will update this ticket with
 the link to my github 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] #18470: Widget argument description in Form fields documentation

[Django]

#18470: Widget argument description in Form fields documentation
---+--
 Reporter:  jnschaeffer@…  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.4
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by jakul):

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


Comment:

 Can you show some example code which shows the error? The form field
 should accept either an instance or a class

-- 
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] #2594: Template system should handle whitespace better

[Django]

#2594: Template system should handle whitespace better
-+-
 Reporter:  Gary Wilson  |Owner:  jshedd
  |   Status:  new
 Type:  Bug  |  Version:  master
Component:  Template system  |   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|
-+-
Changes (by ldiqual@…):

 * cc: ldiqual@… (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.

[Django] #18470: Widget argument description in Form fields documentation

[Django]

#18470: Widget argument description in Form fields documentation
---+
 Reporter:  jnschaeffer@…  |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Documentation  |Version:  1.4
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  1  |  UI/UX:  0
---+
 In the description of the widget field in form fields, the specified type
 for the parameter is "a Widget class". However, passing the class in
 throws an error--instead, it seems that the user must pass in an instance
 of the Widget class. Fixing this problem doesn't take much time, but it
 does take a bit of guesswork and reading between the lines of the
 documentation rather than simply going by what it says.

-- 
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] #18469: Django 1.4 + Apache 2.2.22 + WSGI 3.3 + Apache VirtualDocumentRoot

[Django]

#18469: Django 1.4 + Apache 2.2.22 + WSGI 3.3 + Apache VirtualDocumentRoot
-+
 Reporter:  paulkudla|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  HTTP handling|Version:  1.4
 Severity:  Release blocker  |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 In general i have upgraded from django 1.3 to 1.4

 apache Config has :

 # include the server name in the filenames used to satisfy requests
 VirtualDocumentRoot /usr/home/www/%0/
 VirtualScriptAlias "/usr/home/www/%0/cgi-bin"

 to allow mapping to virtual web sites.

 On django 1.3 i had a html file to redirect into the wsgi file to get to
 the admin login

 {{{
 # cat index.html
 
 
 http://admin.scom.ca/scom_billing/django.wsgi/admin/";>
 
 

 # cat django.wsgi
 import os
 import sys

 sys.path.append('/usr/home/www/admin.scom.ca/')

 os.environ['DJANGO_SETTINGS_MODULE'] = 'scom_billing.settings'

 import django.core.handlers.wsgi

 application = django.core.handlers.wsgi.WSGIHandler()

 }}}

 the above worked fine.

 when migrating to django 1.4 the wsgi wrapper (and i have tried several)
 is now '''mixing''' projects

 ie when in the browser and i bring up 2 different projects at the same
 time i can move around in them and then it will try to call the wrong
 project name and because that project is not authorized by the browser
 thus the project session crashes.

 this was NOT an issue under 1.3

 However when upgrading to 1.4 the password hashes etc were upgraded thus i
 was forced to stay at 1.4 and run the 2 projects under the manage.py
 runserver command in the background.

 This is obviously a security issue but I had not choice since wsgi keeps
 mixing the projects

 also note the wsgi.py file that comes with the release version crashes as
 '''unable to load settings'''

 {{{
 import os

 os.environ.setdefault("DJANGO_SETTINGS_MODULE", "testsite.settings")

 from django.core.wsgi import get_wsgi_application
 application = get_wsgi_application()
 }}}

 Error Returned :

 {{{
 Jun 13 13:15:31 django root: 10.1.0.2 - - [13/Jun/2012:13:15:31 -0400]
 "GET /testsite/wsgi.py/admin HTTP/1.1" 404 220
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2] mod_wsgi
 (pid=1209): Exception occurred processing WSGI script
 '/usr/home/www/testsite.scom.ca/testsite/wsgi.py'.
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2] Traceback
 (most recent call last):
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2]   File
 "/usr/local/lib/python2.7/site-packages/django/core/handlers/wsgi.py",
 line 219, in __call__
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2]
 self.load_middleware()
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2]   File
 "/usr/local/lib/python2.7/site-packages/django/core/handlers/base.py",
 line 39, in load_middleware
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2] for
 middleware_path in settings.MIDDLEWARE_CLASSES:
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2]   File
 "/usr/local/lib/python2.7/site-packages/django/utils/functional.py", line
 184, in inner
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2]
 self._setup()
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2]   File
 "/usr/local/lib/python2.7/site-packages/django/conf/__init__.py", line 42,
 in _setup
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2]
 self._wrapped = Settings(settings_module)
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2]   File
 "/usr/local/lib/python2.7/site-packages/django/conf/__init__.py", line 95,
 in __init__
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2] raise
 ImportError("Could not import settings '%s' (Is it on sys.path?): %s" %
 (self.SETTINGS_MODULE, e))
 Jun 13 13:16:13 django httpd[1209]: [error] [client 10.1.0.2] ImportError:
 Could not import settings 'testsite.settings' (Is it on sys.path?): No
 module named testsite.settings
 Jun 13 13:16:13 django root: 10.1.0.2 - - [13/Jun/2012:13:16:12 -0400]
 "GET /testsite/wsgi.py/admin HTTP/1.1" 500 535

 }}}

 Although if you add the path that is what is causing the mixing effect
 between the projects.

-- 
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] #18026: can't update extra_data in process_step of form wizard

[Django]

#18026: can't update extra_data in process_step of form wizard
-+-
 Reporter:  creecode |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.formtools|  Version:  1.4
 Severity:  Normal   |   Resolution:
 Keywords:  form wizard  | Triage Stage:  Accepted
  extra_data process_step can't  |  Needs documentation:  0
  update |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-

Comment (by steph):

 Could you add a test for this issue? I think a setdefault instead of the
 anonymous dict before returning the extra data key would help. Maybe you
 could add a patch for this too - would be really cool!

-- 
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] #11398: pre_syncdb signal to signal before creating tables for models

[Django]

#11398: pre_syncdb signal to signal before creating tables for models
-+-
 Reporter:  yrashk@… |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Other) |  Version:
 Severity:  Normal   |  1.1-beta-1
 Keywords:   |   Resolution:
Has patch:  1| Triage Stage:  Design
  Needs tests:  0|  decision needed
Easy pickings:  0|  Needs documentation:  0
 |  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by v.z.afzal@…):

 Will this be integrated into the next Major release?

-- 
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] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  oracle postgresql|  decision needed
  mysql schemas  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by carneiro.be@…):

 * cc: carneiro.be@… (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] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  ikelly   |Owner:  akaariai
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  oracle postgresql|  decision needed
  mysql schemas  |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by carneiro.be@…):

 @akaariai, I have interest in testing your patch with my code. I have a
 SaaS application and would like each tenant to have a particular schema.
 To set the schema based on the logged in user, all I have to do is to
 dynamically set the db.schema setting? Thanks in advance.

-- 
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] #18461: UnicodeDecodeError in sql logger

[Django]

#18461: UnicodeDecodeError in sql logger
--+
 Reporter:  zw0rk |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 akaariai):

 For future reference: the problem with the test was that it used
 .filter(name='й'). This caused problems on MySQL when TEST_CHARSET =
 'UTF8' is not in use. I didn't have that, and didn't spot that this is
 required (documented
 [https://docs.djangoproject.com/en/dev/internals/contributing/writing-code
 /unit-tests/#using-another-settings-module| here]). So, the original test
 was correct. I don't see a need to change the test back, as the removed
 .filter() doesn't make the test incorrect either. Of course, I am not
 objecting changing the test back if that is wanted...

-- 
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/django] a2022d: Removed escaping test of query content

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a2022dae7ff70b00ab61e2ca2da0980a7747824b
  
https://github.com/django/django/commit/a2022dae7ff70b00ab61e2ca2da0980a7747824b
  Author: Claude Paroz 
  Date:   2012-06-13 (Wed, 13 Jun 2012)

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

  Log Message:
  ---
  Removed escaping test of query content

As the content of last_executed_query() is not under Django's control
for most backends, it is useless to test too specific aspects of it.



-- 
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] #18461: UnicodeDecodeError in sql logger

[Django]

#18461: UnicodeDecodeError in sql logger
--+
 Reporter:  zw0rk |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Anssi Kääriäinen ):

 In [86c20e39eb9ea0bbd25889403d16d857748aff9b]:
 {{{
 #!CommitTicketReference repository=""
 revision="86c20e39eb9ea0bbd25889403d16d857748aff9b"
 Fixed connection.queries encoding handling on Oracle

 In addition, removed a possibly problematic .filter() call from
 backends.test_query_encoding test. It is possible the .filter could
 cause collation problems on MySQL, and as it wasn't absolutely needed
 for the test it seemed better to get rid of the call.

 Refs #18461.
 }}}

-- 
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/django] 86c20e: Fixed connection.queries encoding handling on Orac...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 86c20e39eb9ea0bbd25889403d16d857748aff9b
  
https://github.com/django/django/commit/86c20e39eb9ea0bbd25889403d16d857748aff9b
  Author: Anssi Kääriäinen 
  Date:   2012-06-13 (Wed, 13 Jun 2012)

  Changed paths:
M django/db/backends/oracle/base.py
M tests/regressiontests/backends/tests.py

  Log Message:
  ---
  Fixed connection.queries encoding handling on Oracle

In addition, removed a possibly problematic .filter() call from
backends.test_query_encoding test. It is possible the .filter could
cause collation problems on MySQL, and as it wasn't absolutely needed
for the test it seemed better to get rid of the call.

Refs #18461.



-- 
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] #18465: Date and Timestamp formats for Oracle Backend incorrect with Oracle RAC 11g R2

[Django]

#18465: Date and Timestamp formats for Oracle Backend incorrect with Oracle RAC 
11g
R2
-+-
 Reporter:  josh.smeaton@…   |Owner:  akaariai
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle backend NLS   |  Needs documentation:  0
  Date Format|  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by akaariai):

 * owner:  nobody => akaariai


Comment:

 I agree that we should fix this both in 1.4 and trunk. I will try to find
 time to get this committed.

 FWIW the test actually tests a bit too much IMHO - it is enough to just
 test that the query works - there is no need to test that the query
 doesn't work under different connection settings. No need to change that
 test though, it is useful for testing the test :)

-- 
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] #12915: formfield_callback is lost in an inherited ModelForm

[Django]

#12915: formfield_callback is lost in an inherited ModelForm
-+
 Reporter:  semenov  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.1
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by jezdez):

 * needs_docs:  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] #5493: make-messages.py not parses JS *.html templates for domain djangojs

[Django]

#5493: make-messages.py not parses JS *.html templates for domain djangojs
-+-
 Reporter:  msaelices|Owner:  nobody
 Type:  New feature  |   Status:  reopened
Component:   |  Version:  1.4
  Internationalization   |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  javascript tools |  Unreviewed
  feature_request|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by tonnzor):

 * has_patch:  1 => 0
 * type:  Bug => New feature


Comment:

 It was a good start, but we need something more sophisticated as
 `xgettext` breaks in some cases on EJS files..

 We need a way to provide a way to use custom pre-processors for
 `makemessages` for each of extensions.

 In this case I would be able to simply attach needed parser to my file
 extension (e.g. `.ejs`) and do any needed logic there.

 Something like this:
 {{{#!python
 # in settings.py
 GETTEXT_PROCESSORS = {
 '.ejs': 'mysite.gettext_processors.ejs'
 }

 # in django/core/management/commands/makemessages.py
 processor = django.conf.settings.GETTEXT_PROCESSORS.get(file_ext,
 default_processor)
 src_data = processor(src_data)
 }}}

 It seems to be quite straightforward change that would break nothing but
 add a way to customize it.

 Any better ideas how to allow using custom processors are 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.

[Django] #18468: Define COMMENT in table / colomns

[Django]

#18468: Define COMMENT in table / colomns
--+
 Reporter:  mrechte   |  Owner:  nobody
 Type:  Uncategorized | Status:  new
Component:  Database layer (models, ORM)  |Version:  1.4
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hello,

 That would be nice if it was possible to include comment on table /
 columns at creation time with the syncdb manage.py option.

 There could be a new Model Meta option like:
comment = 'This table is for storing blabla"
 And a new Field option like:
comment = 'This field is for ...'

 Thanks a lot

-- 
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] #18461: UnicodeDecodeError in sql logger

[Django]

#18461: UnicodeDecodeError in sql logger
--+
 Reporter:  zw0rk |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 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 Claude Paroz ):

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


Comment:

 In [e9ef9776d186a3379cdbf47a73b14e89b74d0926]:
 {{{
 #!CommitTicketReference repository=""
 revision="e9ef9776d186a3379cdbf47a73b14e89b74d0926"
 Fixed #18461 -- Ensured that last_executed_query returns Unicode

 Thanks Anssi Kääriäinen for the review.
 }}}

-- 
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/django] e9ef97: Fixed #18461 -- Ensured that last_executed_query r...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e9ef9776d186a3379cdbf47a73b14e89b74d0926
  
https://github.com/django/django/commit/e9ef9776d186a3379cdbf47a73b14e89b74d0926
  Author: Claude Paroz 
  Date:   2012-06-13 (Wed, 13 Jun 2012)

  Changed paths:
M django/db/backends/mysql/base.py
M django/db/backends/postgresql_psycopg2/operations.py
M tests/regressiontests/backends/tests.py

  Log Message:
  ---
  Fixed #18461 -- Ensured that last_executed_query returns Unicode

Thanks Anssi Kääriäinen for the review.



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