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

[Django]

#6362: Remove blank spaces with strip when validating the data
-+--
  Reporter:  marinho | Owner:  nobody   
Status:  new | Milestone:   
 Component:  Forms   |   Version:  SVN  
Resolution:  |  Keywords:  blank space strip
 Stage:  Design decision needed  | Has_patch:  1
Needs_docs:  0   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by fwenzel):

 * cc: fwen...@mozilla.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-upda...@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.

[Changeset] r13601 - in django/branches/releases/1.2.X: . docs/intro

[noreply]

Author: kmtracey
Date: 2010-08-17 21:44:58 -0500 (Tue, 17 Aug 2010)
New Revision: 13601

Modified:
   django/branches/releases/1.2.X/
   django/branches/releases/1.2.X/docs/intro/tutorial02.txt
Log:
[1.2.X] Fixed #14127: Adding a couple of missing backticks. Thanks kishkin.

r13600 from trunk.




Property changes on: django/branches/releases/1.2.X
___
Name: svnmerge-integrated
   - /django/trunk:1-13360,13434,13480,13574
   + /django/trunk:1-13360,13434,13480,13574,13600

Modified: django/branches/releases/1.2.X/docs/intro/tutorial02.txt
===
--- django/branches/releases/1.2.X/docs/intro/tutorial02.txt2010-08-18 
02:42:01 UTC (rev 13600)
+++ django/branches/releases/1.2.X/docs/intro/tutorial02.txt2010-08-18 
02:44:58 UTC (rev 13601)
@@ -426,7 +426,7 @@
 site's name as you see fit.
 
 This template file contains lots of text like ``{% block branding %}``
-and ``{{ title }}. The ``{%`` and ``{{`` tags are part of Django's
+and ``{{ title }}``. The ``{%`` and ``{{`` tags are part of Django's
 template language. When Django renders ``admin/base_site.html``, this
 template language will be evaluated to produce the final HTML page.
 Don't worry if you can't make any sense of the template right now --

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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.

[Changeset] r13600 - django/trunk/docs/intro

[noreply]

Author: kmtracey
Date: 2010-08-17 21:42:01 -0500 (Tue, 17 Aug 2010)
New Revision: 13600

Modified:
   django/trunk/docs/intro/tutorial02.txt
Log:
Fixed #14127: Adding a couple of missing backticks. Thanks kishkin.


Modified: django/trunk/docs/intro/tutorial02.txt
===
--- django/trunk/docs/intro/tutorial02.txt  2010-08-17 07:08:26 UTC (rev 
13599)
+++ django/trunk/docs/intro/tutorial02.txt  2010-08-18 02:42:01 UTC (rev 
13600)
@@ -426,7 +426,7 @@
 site's name as you see fit.
 
 This template file contains lots of text like ``{% block branding %}``
-and ``{{ title }}. The ``{%`` and ``{{`` tags are part of Django's
+and ``{{ title }}``. The ``{%`` and ``{{`` tags are part of Django's
 template language. When Django renders ``admin/base_site.html``, this
 template language will be evaluated to produce the final HTML page.
 Don't worry if you can't make any sense of the template right now --

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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] #14124: Cannot use a proxy model with unique_together

[Django]

#14124: Cannot use a proxy model with unique_together
+---
  Reporter:  mlhamel| Owner:  nobody
Status:  closed | Milestone:
 Component:  Uncategorized  |   Version:  1.2   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Old description:

> I've just used a proxy model in my own custom application and i've just
> found a small problem. Right now, to be able to create a Proxy model, i'm
> force to redefine a Meta options like that:
>
> class NewDiscount(Discount):
> class Meta:
> proxy = True
>
> The problem i have is that the original discount object defined the
> following Meta options:
>
> class Discount(models.Model):
> class Meta:
> verbose_name = _("Discount")
> verbose_name_plural = _("Discounts")
> unique_together = ('slug', 'amount')
>
> Since i've overwritten the Meta class I should copy the original Meta
> options inside my Proxy model like that:
>
> class NewDiscount(Discount):
> class Meta:
> proxy = True
> verbose_name = _("Discount")
> verbose_name_plural = _("Discounts")
> unique_together = ('slug', 'amount')
>
> But, when I'm doing that, Django throw me an error saying:
>
> "store.discount: "unique_together" refers to site. This is not in the
> same model as the unique_together statement."

New description:

 I've just used a proxy model in my own custom application and i've just
 found a small problem. Right now, to be able to create a Proxy model, i'm
 force to redefine a Meta options like that:
 {{{
 #!python
 class NewDiscount(Discount):
 class Meta:
 proxy = True
 }}}

 The problem i have is that the original discount object defined the
 following Meta options:

 {{{
 #!python
 class Discount(models.Model):
 class Meta:
 verbose_name = _("Discount")
 verbose_name_plural = _("Discounts")
 unique_together = ('slug', 'amount')
 }}}


 Since i've overwritten the Meta class I should copy the original Meta
 options inside my Proxy model like that:

 {{{
 #!python
 class NewDiscount(Discount):
 class Meta:
 proxy = True
 verbose_name = _("Discount")
 verbose_name_plural = _("Discounts")
 unique_together = ('slug', 'amount')
 }}}

 But, when I'm doing that, Django throw me an error saying:

 "store.discount: "unique_together" refers to site. This is not in the same
 model as the unique_together statement."

Comment:

 Fixed formatting. Please use WikiFormatting and use Preview before
 submitting.

 Why do you think you have to copy the Meta class wholesale? Given that
 `unique_together` affects the database table definitions, and proxy models
 are intended to simply change Python behavior while using the database
 table from the proxied model, it does not make sense to copy
 `unique_together` into the proxy model. So, what problem do you encounter
 if you do not attempt to set `unique_together` in the proxy model? That
 would be a problem to investigate and fix, if there is one. For now
 closing this as invalid since the described behavior appears correct to
 me.

-- 
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-upda...@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] #14127: Bad formatting in the text

[Django]

#14127: Bad formatting in the text
+---
  Reporter:  kishkin| Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.2   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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-upda...@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] #11726: FormWizard sanity check on step number performed before dynamic steps can be inserted

[Django]

#11726: FormWizard sanity check on step number performed before dynamic steps 
can
be inserted
---+
  Reporter:  Eric Friesen   | Owner:  
esper256  
Status:  assigned  | Milestone: 
   
 Component:  django.contrib.formtools  |   Version:  
SVN   
Resolution:|  Keywords:  
FormWizard
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  1 |   Needs_tests:  1  
   
Needs_better_patch:  0 |  
---+
Changes (by esper256):

  * needs_docs:  0 => 1
  * has_patch:  0 => 1
  * version:  1.1 => SVN
  * needs_tests:  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-upda...@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] #11726: FormWizard sanity check on step number performed before dynamic steps can be inserted

[Django]

#11726: FormWizard sanity check on step number performed before dynamic steps 
can
be inserted
---+
  Reporter:  Eric Friesen   | Owner:  
esper256  
Status:  assigned  | Milestone: 
   
 Component:  django.contrib.formtools  |   Version:  
1.1   
Resolution:|  Keywords:  
FormWizard
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by esper256):

  * status:  new => assigned

-- 
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-upda...@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] #11726: FormWizard sanity check on step number performed before dynamic steps can be inserted

[Django]

#11726: FormWizard sanity check on step number performed before dynamic steps 
can
be inserted
---+
  Reporter:  Eric Friesen   | Owner:  
esper256  
Status:  new   | Milestone: 
   
 Component:  django.contrib.formtools  |   Version:  
1.1   
Resolution:|  Keywords:  
FormWizard
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by esper256):

  * owner:  anonymous => esper256
  * status:  assigned => new

-- 
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-upda...@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] #11726: FormWizard sanity check on step number performed before dynamic steps can be inserted

[Django]

#11726: FormWizard sanity check on step number performed before dynamic steps 
can
be inserted
---+
  Reporter:  Eric Friesen   | Owner:  
anonymous 
Status:  assigned  | Milestone: 
   
 Component:  django.contrib.formtools  |   Version:  
1.1   
Resolution:|  Keywords:  
FormWizard
 Stage:  Accepted  | Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * owner:  nobody => anonymous
  * status:  new => assigned

-- 
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-upda...@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] #14128: oracle system tablespace privileges

[Django]

#14128: oracle system tablespace privileges
---+
 Reporter:  gleiwer|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords:  oracle |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hello there,

 When i execute python manage.py syncdb

 i get the next message.

 i'm using oracle database, and it has the privileges that are necessary
 like, create session, create table, create sequence, create procedure and
 create trigger. I don't know why is happening this. Thanks for you help.



 [django...@host test_one]$ python manage.py syncdb
 Creating table auth_permission
 Traceback (most recent call last):
   File "manage.py", line 11, in ?
 execute_manager(settings)
   File "/usr/lib/python2.4/site-
 packages/django/core/management/__init__.py", line 438, in execute_manager
 utility.execute()
   File "/usr/lib/python2.4/site-
 packages/django/core/management/__init__.py", line 379, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/usr/lib/python2.4/site-packages/django/core/management/base.py",
 line 191, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/usr/lib/python2.4/site-packages/django/core/management/base.py",
 line 218, in execute
 output = self.handle(*args, **options)
   File "/usr/lib/python2.4/site-packages/django/core/management/base.py",
 line 347, in handle
 return self.handle_noargs(**options)
   File "/usr/lib/python2.4/site-
 packages/django/core/management/commands/syncdb.py", line 95, in
 handle_noargs
 cursor.execute(statement)
   File "/usr/lib/python2.4/site-packages/django/db/backends/util.py", line
 15, in execute
 return self.cursor.execute(sql, params)
   File "/usr/lib/python2.4/site-
 packages/django/db/backends/oracle/base.py", line 507, in execute
 return self.cursor.execute(query, self._param_generator(params))
 django.db.utils.DatabaseError: ORA-01950: no privileges on tablespace
 'SYSTEM'

-- 
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-upda...@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] #14127: Bad formatting in the text

[Django]

#14127: Bad formatting in the text
---+
 Reporter:  kishkin|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hello!

 I've noticed a bit of a bad formatting here:
 http://docs.djangoproject.com/en/dev/intro/tutorial02/#intro-tutorial02

 You can just search for the string: "The ``{% and {{". Or you can go here
 - "Customize the admin look and feel" part - 7th (8th counting the
 example) paragraph - 2nd sentence.

 The "The ``{%" part of this sentence I think should be a bit different:
 "The" shouldn't be written in Curier New and there shouldn't be any '`'
 characters. Probably just a typo.

 Thank you for the great job on documentation and everything else!

 ---
 Michael

-- 
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-upda...@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] #6856: Better ModelForm examples

[Django]

#6856: Better ModelForm examples
+---
  Reporter:  ubernostrum| Owner:  ubernostrum
Status:  closed | Milestone: 
 Component:  Documentation  |   Version:  SVN
Resolution:  invalid|  Keywords: 
 Stage:  Accepted   | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by danielr):

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

Comment:

 The behaviour changed with model validation, and it is now correctly
 documented that attempting to save an invalid !ModelForm will raise a
 ValueError.

-- 
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-upda...@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] #5677: Debugging with mod_python (apache)

[Django]

#5677: Debugging with mod_python (apache)
--+-
  Reporter:  Manfred Wassmann   | 
Owner:  nickefford
Status:  new  | 
Milestone:
 Component:  Documentation|   
Version:  SVN   
Resolution:   |  
Keywords:  mod_python
 Stage:  Accepted | 
Has_patch:  1 
Needs_docs:  0|   
Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by danielr):

 Updated patch removing references to WSGI.

-- 
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-upda...@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] #3888: Allow {# comment #} tag to be multiline

[Django]

#3888: Allow {# comment #} tag to be multiline
--+-
  Reporter:  tonnzor  | Owner:  adrian
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 Cerin, if you want discussion, take it to the django-dev google group
 please.

-- 
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-upda...@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] #3888: Allow {# comment #} tag to be multiline

[Django]

#3888: Allow {# comment #} tag to be multiline
--+-
  Reporter:  tonnzor  | Owner:  adrian
Status:  closed   | Milestone:
 Component:  Template system  |   Version:  SVN   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by Cerin):

 I really wish the devs would re-consider their stance on this issue. No
 other templating language has such an unnecessarily verbose multi-line
 comment notation. Python allows multi-line comments with 6 characters
 (""), C with 4 (/**/), HTML with 7 ()). The fact that Django's
 is a whooping 29 characters ({% comment %}{% endcomment %}) seems quite
 unreasonable. If the logic for doing so is to maintain the logical
 consistency of the tag notation, then the tag notation is broken and
 should be fixed. Changing the single-line notation to support multiple
 lines would save a lot of unnecessary typing.

-- 
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-upda...@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] #14126: blocktrans count is parsing incorrectly

[Django]

#14126: blocktrans count is parsing incorrectly
---+
 Reporter:  mark0978   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Translations   | Version:  1.2   
 Keywords:  blocktrans plural  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Context looks like: {'docs_needed': 2, ...  (from the stack trace
 provided)

 {{{
 {% blocktrans count docs_needed as counter %}
 }}}
 Generates this error: Caught !KeyError while rendering: u'docs_needed'

 {{{
 {% blocktrans count docs_needed|default:2 as counter %}
 }}}
 Generates this error:  Caught !KeyError while rendering: u'docs_needed'

 {{{
 {% blocktrans count docs_needed|length as counter %}
 }}}
 Does not give a !KeyError, but produces the wrong result since the length
 of docs_needed is 1 since it is scalar?

 The template contains:
 {{{
 {% blocktrans count docs_needed|length as counter
 %}
 Waiting on the following
 document:
 {% plural %}
 Waiting on the following {{ counter }}
 documents:
 {% endblocktrans %}
 }}}

 and the output produced looks like:

 {{{
 Waiting on the following  documents:
 }}}

 The documentation @
 http://docs.djangoproject.com/en/dev/topics/i18n/internationalization
 /#blocktrans-template-tag makes it look like a scalar is needed after the
 word key word '''count''' because it uses '''list|length''' as an example,
 which appears to be a filter creating a scalar value.


 I'm using Django 1.2.1 (not a version you can pick below)

-- 
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-upda...@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] #3051: django.test.client.Client() does not set HttpResponse context and template properly

[Django]

#3051: django.test.client.Client() does not set HttpResponse context and 
template
properly
+---
  Reporter:  anonymous  | Owner:  adrian
Status:  reopened   | Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by danielr):

  * needs_better_patch:  1 => 0

Comment:

 Patch updated with more explanation and links.

-- 
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-upda...@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] #14125: 'Safe strings' are not force-escaped on development 500 page

[Django]

#14125: 'Safe strings' are not force-escaped on development 500 page
+---
  Reporter:  elijahr| Owner:  elijahr
Status:  assigned   | Milestone: 
 Component:  Uncategorized  |   Version:  SVN
Resolution: |  Keywords:  debug.py 500 escape
 Stage:  Unreviewed | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by elijahr):

  * owner:  nobody => elijahr
  * status:  new => assigned

-- 
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-upda...@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] #14125: 'Safe strings' are not force-escaped on development 500 page

[Django]

#14125: 'Safe strings' are not force-escaped on development 500 page
---+
   Reporter:  elijahr  |Owner:  nobody
 Status:  new  |Milestone:
  Component:  Uncategorized|  Version:  SVN   
   Keywords:  debug.py 500 escape  |Stage:  Unreviewed
  Has_patch:  1|   Needs_docs:  0 
Needs_tests:  0|   Needs_better_patch:  0 
---+
 In the 'Local vars' section of the debugging 500 error page, strings that
 have been 'marked safe' are not escaped before output, which has often
 resulted in HTML from my variables being inserted into the page.

 While using 'mark_safe' on a string variable indicates that the string
 should not be escaped further, I think an exception should be made for the
 debugging 500 page, based on my assumption that most developers would
 rather see a string's value than the resultant HTML elements.

 I have attached a patch that uses 'force_escape' in lieu of 'escape'.

-- 
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-upda...@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: 
 
 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: SafPlusPlus (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-upda...@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] #9084: File-based session does not store any data on Windows

[Django]

#9084: File-based session does not store any data on Windows
--+-
  Reporter:  mizutori | Owner: 
Status:  new  | Milestone: 
 Component:  django.contrib.sessions  |   Version:  1.2
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

  * version:  1.1 => 1.2

Comment:

 This still doesn't work in django 1.2

-- 
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-upda...@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] #14124: Cannot use a proxy model with unique_together

[Django]

#14124: Cannot use a proxy model with unique_together
---+
 Reporter:  mlhamel|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Uncategorized  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I've just used a proxy model in my own custom application and i've just
 found a small problem. Right now, to be able to create a Proxy model, i'm
 force to redefine a Meta options like that:

 class NewDiscount(Discount):
 class Meta:
 proxy = True

 The problem i have is that the original discount object defined the
 following Meta options:

 class Discount(models.Model):
 class Meta:
 verbose_name = _("Discount")
 verbose_name_plural = _("Discounts")
 unique_together = ('slug', 'amount')

 Since i've overwritten the Meta class I should copy the original Meta
 options inside my Proxy model like that:

 class NewDiscount(Discount):
 class Meta:
 proxy = True
 verbose_name = _("Discount")
 verbose_name_plural = _("Discounts")
 unique_together = ('slug', 'amount')

 But, when I'm doing that, Django throw me an error saying:

 "store.discount: "unique_together" refers to site. This is not in the same
 model as the unique_together statement."

-- 
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-upda...@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] #12241: Admin forgets URL used for prefilling forms when hitting Save and add another

[Django]

#12241: Admin forgets URL used for prefilling forms when hitting Save and add
another
---+
  Reporter:  velmont   | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Ready for checkin | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  1 |  
---+
Changes (by spinyol):

 * cc: spinyol (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-upda...@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] #14123: Trunk tests broken as of r13588 (1.2.x passes)

[Django]

#14123: Trunk tests broken as of r13588 (1.2.x passes)
+---
  Reporter:  PaulM  | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by lrekucki):

  * status:  closed => reopened
  * resolution:  invalid =>
  * stage:  Unreviewed => Accepted

Comment:

 This tests fail due to lack of Docutils. Citing django docs: "Each of
 these dependencies is optional. If you're missing any of them, the
 associated tests will be skipped.". I think it should be fixed.

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

[Changeset] r13599 - in django/branches/releases/1.2.X: . django/db/models tests/modeltests/model_forms tests/modeltests/validation

[noreply]

Author: russellm
Date: 2010-08-17 02:08:26 -0500 (Tue, 17 Aug 2010)
New Revision: 13599

Modified:
   django/branches/releases/1.2.X/AUTHORS
   django/branches/releases/1.2.X/django/db/models/base.py
   django/branches/releases/1.2.X/tests/modeltests/model_forms/tests.py
   django/branches/releases/1.2.X/tests/modeltests/validation/test_unique.py
Log:
[1.2.X] Fixed #14102 -- Ensure that fields that have been excluded from a form 
aren't included in the unique_for_* checks, either. Thanks to Travis Cline for 
the report and fix.

Backport of r13598 from trunk.

Modified: django/branches/releases/1.2.X/AUTHORS
===
--- django/branches/releases/1.2.X/AUTHORS  2010-08-17 07:07:28 UTC (rev 
13598)
+++ django/branches/releases/1.2.X/AUTHORS  2010-08-17 07:08:26 UTC (rev 
13599)
@@ -108,6 +108,7 @@
 Michal Chruszcz 
 Can Burak Çilingir 
 Ian Clelland 
+Travis Cline 
 Russell Cloran 
 co...@owlfish.com
 crankyco...@gmail.com

Modified: django/branches/releases/1.2.X/django/db/models/base.py
===
--- django/branches/releases/1.2.X/django/db/models/base.py 2010-08-17 
07:07:28 UTC (rev 13598)
+++ django/branches/releases/1.2.X/django/db/models/base.py 2010-08-17 
07:08:26 UTC (rev 13599)
@@ -1,6 +1,5 @@
 import types
 import sys
-import os
 from itertools import izip
 import django.db.models.manager # Imported to register signal handler.
 from django.core.exceptions import ObjectDoesNotExist, 
MultipleObjectsReturned, FieldError, ValidationError, NON_FIELD_ERRORS
@@ -16,7 +15,7 @@
 from django.utils.translation import ugettext_lazy as _
 import django.utils.copycompat as copy
 from django.utils.functional import curry, update_wrapper
-from django.utils.encoding import smart_str, force_unicode, smart_unicode
+from django.utils.encoding import smart_str, force_unicode
 from django.utils.text import get_text_list, capfirst
 from django.conf import settings
 
@@ -744,11 +743,11 @@
 continue
 if f.unique:
 unique_checks.append((model_class, (name,)))
-if f.unique_for_date:
+if f.unique_for_date and f.unique_for_date not in exclude:
 date_checks.append((model_class, 'date', name, 
f.unique_for_date))
-if f.unique_for_year:
+if f.unique_for_year and f.unique_for_year not in exclude:
 date_checks.append((model_class, 'year', name, 
f.unique_for_year))
-if f.unique_for_month:
+if f.unique_for_month and f.unique_for_month not in exclude:
 date_checks.append((model_class, 'month', name, 
f.unique_for_month))
 return unique_checks, date_checks
 

Modified: django/branches/releases/1.2.X/tests/modeltests/model_forms/tests.py
===
--- django/branches/releases/1.2.X/tests/modeltests/model_forms/tests.py
2010-08-17 07:07:28 UTC (rev 13598)
+++ django/branches/releases/1.2.X/tests/modeltests/model_forms/tests.py
2010-08-17 07:08:26 UTC (rev 13599)
@@ -156,6 +156,10 @@
 form = PostForm({'subtitle': "Finally", "title": "Django 1.0 is 
released",
 "slug": "Django 1.0", 'posted': '2008-09-03'}, instance=p)
 self.assertTrue(form.is_valid())
+form = PostForm({'title': "Django 1.0 is released"})
+self.assertFalse(form.is_valid())
+self.assertEqual(len(form.errors), 1)
+self.assertEqual(form.errors['posted'], [u'This field is required.'])
 
 def test_inherited_unique_for_date(self):
 p = Post.objects.create(title="Django 1.0 is released",

Modified: 
django/branches/releases/1.2.X/tests/modeltests/validation/test_unique.py
===
--- django/branches/releases/1.2.X/tests/modeltests/validation/test_unique.py   
2010-08-17 07:07:28 UTC (rev 13598)
+++ django/branches/releases/1.2.X/tests/modeltests/validation/test_unique.py   
2010-08-17 07:08:26 UTC (rev 13599)
@@ -40,6 +40,15 @@
 ), m._get_unique_checks()
 )
 
+def test_unique_for_date_exclusion(self):
+m = UniqueForDateModel()
+self.assertEqual((
+[(UniqueForDateModel, ('id',))],
+[(UniqueForDateModel, 'year', 'count', 'end_date'),
+ (UniqueForDateModel, 'month', 'order', 'end_date')]
+), m._get_unique_checks(exclude='start_date')
+)
+
 class PerformUniqueChecksTest(unittest.TestCase):
 def setUp(self):
 # Set debug to True to gain access to connection.queries.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to 
django-updat

[Changeset] r13598 - in django/trunk: . django/db/models tests/modeltests/model_forms tests/modeltests/validation

[noreply]

Author: russellm
Date: 2010-08-17 02:07:28 -0500 (Tue, 17 Aug 2010)
New Revision: 13598

Modified:
   django/trunk/AUTHORS
   django/trunk/django/db/models/base.py
   django/trunk/tests/modeltests/model_forms/tests.py
   django/trunk/tests/modeltests/validation/test_unique.py
Log:
Fixed #14102 -- Ensure that fields that have been excluded from a form aren't 
included in the unique_for_* checks, either. Thanks to Travis Cline for the 
report and fix.

Modified: django/trunk/AUTHORS
===
--- django/trunk/AUTHORS2010-08-16 16:29:17 UTC (rev 13597)
+++ django/trunk/AUTHORS2010-08-17 07:07:28 UTC (rev 13598)
@@ -108,6 +108,7 @@
 Michal Chruszcz 
 Can Burak Çilingir 
 Ian Clelland 
+Travis Cline 
 Russell Cloran 
 co...@owlfish.com
 crankyco...@gmail.com

Modified: django/trunk/django/db/models/base.py
===
--- django/trunk/django/db/models/base.py   2010-08-16 16:29:17 UTC (rev 
13597)
+++ django/trunk/django/db/models/base.py   2010-08-17 07:07:28 UTC (rev 
13598)
@@ -1,6 +1,5 @@
 import types
 import sys
-import os
 from itertools import izip
 import django.db.models.manager # Imported to register signal handler.
 from django.core.exceptions import ObjectDoesNotExist, 
MultipleObjectsReturned, FieldError, ValidationError, NON_FIELD_ERRORS
@@ -16,7 +15,7 @@
 from django.utils.translation import ugettext_lazy as _
 import django.utils.copycompat as copy
 from django.utils.functional import curry, update_wrapper
-from django.utils.encoding import smart_str, force_unicode, smart_unicode
+from django.utils.encoding import smart_str, force_unicode
 from django.utils.text import get_text_list, capfirst
 from django.conf import settings
 
@@ -744,11 +743,11 @@
 continue
 if f.unique:
 unique_checks.append((model_class, (name,)))
-if f.unique_for_date:
+if f.unique_for_date and f.unique_for_date not in exclude:
 date_checks.append((model_class, 'date', name, 
f.unique_for_date))
-if f.unique_for_year:
+if f.unique_for_year and f.unique_for_year not in exclude:
 date_checks.append((model_class, 'year', name, 
f.unique_for_year))
-if f.unique_for_month:
+if f.unique_for_month and f.unique_for_month not in exclude:
 date_checks.append((model_class, 'month', name, 
f.unique_for_month))
 return unique_checks, date_checks
 

Modified: django/trunk/tests/modeltests/model_forms/tests.py
===
--- django/trunk/tests/modeltests/model_forms/tests.py  2010-08-16 16:29:17 UTC 
(rev 13597)
+++ django/trunk/tests/modeltests/model_forms/tests.py  2010-08-17 07:07:28 UTC 
(rev 13598)
@@ -156,6 +156,10 @@
 form = PostForm({'subtitle': "Finally", "title": "Django 1.0 is 
released",
 "slug": "Django 1.0", 'posted': '2008-09-03'}, instance=p)
 self.assertTrue(form.is_valid())
+form = PostForm({'title': "Django 1.0 is released"})
+self.assertFalse(form.is_valid())
+self.assertEqual(len(form.errors), 1)
+self.assertEqual(form.errors['posted'], [u'This field is required.'])
 
 def test_inherited_unique_for_date(self):
 p = Post.objects.create(title="Django 1.0 is released",

Modified: django/trunk/tests/modeltests/validation/test_unique.py
===
--- django/trunk/tests/modeltests/validation/test_unique.py 2010-08-16 
16:29:17 UTC (rev 13597)
+++ django/trunk/tests/modeltests/validation/test_unique.py 2010-08-17 
07:07:28 UTC (rev 13598)
@@ -40,6 +40,15 @@
 ), m._get_unique_checks()
 )
 
+def test_unique_for_date_exclusion(self):
+m = UniqueForDateModel()
+self.assertEqual((
+[(UniqueForDateModel, ('id',))],
+[(UniqueForDateModel, 'year', 'count', 'end_date'),
+ (UniqueForDateModel, 'month', 'order', 'end_date')]
+), m._get_unique_checks(exclude='start_date')
+)
+
 class PerformUniqueChecksTest(unittest.TestCase):
 def setUp(self):
 # Set debug to True to gain access to connection.queries.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-upda...@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.