Re: [Django] #10809: mod_wsgi authentication handler

[Django]

#10809: mod_wsgi authentication handler
-+--
  Reporter:  baumer1122  | Owner:  davidfischer
Status:  assigned| Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  mod_wsgi
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by davidfischer):

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

Comment:

 I added a patch with supporting documentation and I removed the
 authorization functions from the old patch.

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

Re: [Django] #12000: Code display box renders wrong on Safari

[Django]

#12000: Code display box renders wrong on Safari
+---
  Reporter:  anonymous  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution:  worksforme |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ubernostrum):

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

Comment:

 I can't reproduce this.

-- 
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] #12000: Code display box renders wrong on Safari

[Django]

#12000: Code display box renders wrong on Safari
---+
 Reporter:  anonymous  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When I view http://docs.djangoproject.com/en/dev/intro/tutorial03/#intro-
 tutorial03, one of the code display boxes renders in a way that's
 unreadable.  I'm attaching a screen-shot.  I'm using Safari Version 4.0.3
 (5531.9) on Mac OSX 10.5.7.  If I reduce the font size with Command-minus,
 it renders correctly.  Oddly enough, if I increase the size back to the
 original with Command-plus, it still renders correctly.  I don't know if
 this is a problem with your CSS or with Safari, but I figured you'd want
 to know about it.

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

Re: [Django] #10809: mod_wsgi authentication handler

[Django]

#10809: mod_wsgi authentication handler
-+--
  Reporter:  baumer1122  | Owner:  davidfischer
Status:  assigned| Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  mod_wsgi
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Comment (by grahamd):

 Presuming there is a corresponding Django application running in same
 process/sub interpreter, a better way is have all the following in single
 WSGI script file:

 {{{
 import sys
 sys.path.append(...)

 import os
 os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings'

 import django.contrib.auth.handlers.modwsgi

 def check_password(environ, user, password):
 return django.contrib.auth.handlers.modwsgi.check_password(environ,
 user, password)

 import django.core.handlers.wsgi

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

 That is, no need to actually have multiple script files. Apache
 configuration would then be:

 {{{
 AuthType Basic
 AuthName "Top Secret"
 AuthBasicProvider wsgi
 Require valid-user

 WSGIProcessGroup %{GLOBAL}
 WSGIApplicationGroup django

 WSGIAuthUserScript /usr/local/django/mysite/apache/django.wsgi
 WSGIScriptAlias / /usr/local/django/mysite/apache/django.wsgi
 }}}

 The WSGIProcessGroup/WSGIApplicationGroup are to ensure both are executed
 in same sub interpreter as by default authentication handler will execute
 in %{GLOBAL} application group where as Django will be in group named
 based on virtual host ServerName and application mount point.

-- 
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] #10809: mod_wsgi authentication handler

[Django]

#10809: mod_wsgi authentication handler
-+--
  Reporter:  baumer1122  | Owner:  davidfischer
Status:  assigned| Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  mod_wsgi
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Changes (by davidfischer):

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

Comment:

 It sounds like you've thought this through. Still, I think that a mod_wsgi
 auth handler is a good idea. Considering your suggestions, I think an auth
 script should look something like this:
 {{{
 import sys
 sys.path.append(...)

 import os
 os.environ['DJANGO_SETTINGS_MODULE'] = 'mysite.settings'

 import django.contrib.auth.handlers.modwsgi

 def check_password(environ, user, password):
 return django.contrib.auth.handlers.modwsgi.check_password(environ,
 user, password)
 }}}

 In this way, there will always be an external auth script but at least
 users won't be repeating themselves as much.

 I like this solution a lot better than making sure that the system path is
 set properly and that the `DJANGO_SETTINGS_MODULE` environment variable is
 set in the OS level before starting Apache. That solution would also have
 problems with multiple Django projects authenticating against multiple
 auth databases running on the same Apache instance.

 I'll start working on a patch.

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

Re: [Django] #10360: allow customized forbidden message when using exceptions

[Django]

#10360: allow customized forbidden message when using exceptions
-+--
  Reporter:  tallfred| Owner:  ericholscher
Status:  assigned| Milestone:  1.2 
 Component:  Core framework  |   Version:  1.0 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  1   
Needs_better_patch:  0   |  
-+--
Comment (by Leo):

 Actually, even better behavior would be to redirect to a 403.html page
 just like the 500 and 404 handlers that currently exist. Some more
 discussion in #5515.

-- 
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] #10809: mod_wsgi authentication handler

[Django]

#10809: mod_wsgi authentication handler
-+--
  Reporter:  baumer1122  | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  mod_wsgi
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Changes (by grahamd):

 * cc: grahamd (removed)
 * cc: graham.dumple...@gmail.com (added)

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

Re: [Django] #10809: mod_wsgi authentication handler

[Django]

#10809: mod_wsgi authentication handler
-+--
  Reporter:  baumer1122  | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  mod_wsgi
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Changes (by grahamd):

 * cc: grahamd (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] #10809: mod_wsgi authentication handler

[Django]

#10809: mod_wsgi authentication handler
-+--
  Reporter:  baumer1122  | Owner:  nobody  
Status:  new | Milestone:  
 Component:  Authentication  |   Version:  SVN 
Resolution:  |  Keywords:  mod_wsgi
 Stage:  Design decision needed  | Has_patch:  1   
Needs_docs:  1   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Comment (by grahamd):

 I wouldn't be copying how mod_python/Django works as it is technically
 broken, or at least is a very bad way of doing things because of the
 problems it can cause.

 The interaction with mod_python for both authentication handler and
 content handler, ie., main Django application, relies on stuffing all
 mod_python request variables into os.environ on every request. Doing this
 is bad for a number of reasons.

 The first is that it causes pollution of the set of process environment
 variables. This is because every time you set something in os.environ, it
 also under the covers calls C level putenv(). Because mod_python and
 mod_wsgi can have multiple sub interpreters with separate applications
 running in them, any change made will affect the process environment
 variables used by other applications running in same process.

 The second is that if the first application to get a request has
 additional variables set beyond what is set for other applications in
 other sub interpreters, when that second application gets a request,
 os.environ will be created as a copy of process environment variables at
 that time, so variables set in configuration for the first effectively
 leak into the os.environ dictionary of the second application. If the
 point of the configuration was not to affect something needing process
 environment variables, but just in Python context via os.environ, you have
 then potentially affected the way that the second application works.

 The third is that it is in the main pointless setting os.environ on every
 request because for variables like DJANGO_SETTINGS_MODULE only the first
 value seen is ever used as it is only read when django first initialises
 itself.

 For some additional detail about process environment variable leakage
 between Python sub interpreters read:

 
http://code.google.com/p/modwsgi/wiki/ApplicationIssues#Application_Environment_Variables

 Overall, the use of a globally scoped variable set in os.environ for
 driving Django configuration, and all the subsequent caching of
 configuration in global data, is suboptimal design. It is therefore
 arguable that this really comes down to being a Django problem and not a
 mod_wsgi limitation.

 I would also suggest that having the authentication handler be dependent
 on loading and initialising the full Django stack is also sub optimal.
 This is because authentication hooks in mod_wsgi can only run in the
 embedded mode processes. If the main Django site instance is running
 daemon mode you therefore potentially have a full second set of copies of
 Django loaded just to handle authentication. What should be aimed at is a
 way for the authentication handler only loading the absolute minimum of
 what is required from Django instance to do what it needs, otherwise you
 just risk bloating out your Apache if main application actually running in
 daemon mode. Maybe it does do, that, but since it requires settings file,
 presuming it is doing all initialisation.

 That all said, the other reason that SetEnv variables aren't propagated
 into authentication handler is that the authentication handler can only be
 setup from main Apache configuration file. Thus only by the administrator.
 This is done specifically so that the administrator can fully control how
 authentication is handled, given than any issues with it are going to be a
 security issue. If you allow SetEnv variables to control what
 configuration the authentication handler sees, then if a normal user if
 given FileInfo override rights for .htaccess file, then they could
 override the configuration sent into the authentication handler and so
 override the configuration the administrator set up. This would allow a
 normal user to circumvent the authentication mechanism and so open up
 security holes.

 A solution to this is to have a separate set of directives for setting
 WSGI environment variables. Do this though and you end up with silly mess
 with mod_python where you have choice of SetEnv and PythonOption. Because
 in mod_python PythonOption can also be set in .htaccess, it also is
 subject to the same security hole where a normal user could override a
 variable being passed into an authentication handler and circumvent the
 security.

 One solution is for the separate direct

Re: [Django] #11698: Add Django Debug Toolbar to contrib

[Django]

#11698: Add Django Debug Toolbar to contrib
---+
  Reporter:  russellm  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Contrib apps  |   Version:  1.1   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by idangazit):

 * cc: idangazit (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] #11863: Add a method to the orm to create Model instances from raw sql queries

[Django]

#11863: Add a method to the orm to create Model instances from raw sql queries
---+
  Reporter:  seanoc| Owner:  seanoc
Status:  assigned  | Milestone:  1.2   
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: i...@dav-muz.net (added)

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

[Django] #11999: Support for Google Maps encoded geometries

[Django]

#11999: Support for Google Maps encoded geometries
---+
 Reporter:  rcoup  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  GIS| Version:
 Keywords:  gmaps  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 When displaying polygons and polylines with GMaps, performance can be
 massively improved by using encoded geometries. It would be great for
 GeoDjango to support this:
  * a module to encode geometries and return a dictionary, so people can
 JSON-encode and send to the client, embed in templates, etc.
  * use encoded geometries in !GoogleGeoAdmin

 Resources:
  * http://code.google.com/apis/maps/documentation/polylinealgorithm.html
 -- official docs
  * http://facstaff.unca.edu/mcmcclur/GoogleMaps/EncodePolyline/ --
 detailed discussion, examples, links to implementations in various
 languages
  * http://wyattbaldwin.com/2007/04/19/google-maps-encoded-polylines/ --
 Python implementation. GPLv3 licensed, and code isn't tidy.

-- 
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] #7270: selected_related() can not follow reverse relations of OneToOne.

[Django]

#7270: selected_related() can not follow reverse relations of OneToOne.
---+
  Reporter:  towjz...@hotmail.com  | Owner:  
mtredinnick
Status:  new   | Milestone:  1.2

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  
select_related onetoone reverse
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

 * cc: vinil...@gmail.com (added)

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

Re: [Django] #10706: Incorrect error from manage.py sql when app fails to load

[Django]

#10706: Incorrect error from manage.py sql when app fails to load
--+-
  Reporter:  Glenn| Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  1|  
--+-
Changes (by xiongchiamiov):

 * cc: xiong.chiam...@gmail.com (added)

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

Re: [Django] #17: Metasystem optimization: Share select_related in memory

[Django]

#17: Metasystem optimization: Share select_related in memory
---+
  Reporter:  adrian| Owner:  PhiR   

Status:  assigned  | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  feature 
caching
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  1 |   Needs_tests:  0  

Needs_better_patch:  1 |  
---+
Changes (by alexkoshelev):

 * cc: alexkoshelev (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] #5025: Add a "truncate" template filter

[Django]

#5025: Add a "truncate" template filter
-+--
  Reporter:  SmileyChris | Owner:  nobody
Status:  reopened| Milestone:
 Component:  Template system |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Guilherme Gondim ):

 * cc: seme...@taurinus.org (added)

Comment:

 I made a similar and simple filter, but your patch is better to Django.

 For reference: http://www.djangosnippets.org/snippets/1715/.

-- 
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] #11998: IntegerField not validated for overflow

[Django]

#11998: IntegerField not validated for overflow
+---
  Reporter:  francis.girald...@revolutionlinux.com  | Owner:  
nobody
Status:  new| Milestone:  
1.2   
 Component:  Uncategorized  |   Version:  
1.1   
Resolution: |  Keywords:

 Stage:  Unreviewed | Has_patch:  0 

Needs_docs:  0  |   Needs_tests:  0 

Needs_better_patch:  0  |  
+---
Old description:

> Let be this small model :
>
> class IntegerOverflowTest(models.Model):
> someint = models.IntegerField()
>
> For mysql, maximum values for signed integer is 2147483647 [1]
>
> In admin interface, defining a value more than the maximum raises this
> exception :
>
> Warning : Out of range value for column 'someint' at row 1
>
> I would have expected that the form to be validated and prompt the error
> gracefully.
>
> [1] http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html

New description:

 Let be this small model :
 {{{
 class IntegerOverflowTest(models.Model):
 someint = models.IntegerField()
 }}}
 For mysql, maximum values for signed integer is 2147483647 [1]

 In admin interface, defining a value more than the maximum raises this
 exception :
 {{{
 Warning : Out of range value for column 'someint' at row 1
 }}}
 I would have expected that the form to be validated and prompt the error
 gracefully.

 [1] http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html

Comment (by Alex):

 Please use preview.

-- 
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] #11998: IntegerField not validated for overflow

[Django]

#11998: IntegerField not validated for overflow
+---
  Reporter:  francis.girald...@revolutionlinux.com  | Owner:  
nobody
Status:  new| Milestone:  
1.2   
 Component:  Uncategorized  |   Version:  
1.1   
Resolution: |  Keywords:

 Stage:  Unreviewed | Has_patch:  0 

Needs_docs:  0  |   Needs_tests:  0 

Needs_better_patch:  0  |  
+---
Changes (by francis.girald...@revolutionlinux.com):

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

Comment:

 A small note : this warning is not raised while using sqlite3. It's
 reproducible under at least mysql.

-- 
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] #11998: IntegerField not validated for overflow

[Django]

#11998: IntegerField not validated for overflow
---+
 Reporter:  francis.girald...@revolutionlinux.com  |   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Uncategorized  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Let be this small model :

 class IntegerOverflowTest(models.Model):
 someint = models.IntegerField()

 For mysql, maximum values for signed integer is 2147483647 [1]

 In admin interface, defining a value more than the maximum raises this
 exception :

 Warning : Out of range value for column 'someint' at row 1

 I would have expected that the form to be validated and prompt the error
 gracefully.

 [1] http://dev.mysql.com/doc/refman/5.0/en/numeric-types.html

-- 
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] #11972: Title filter should not capitalize ordinals

[Django]

#11972: Title filter should not capitalize ordinals
+---
  Reporter:  schw...@gmail.com  | Owner:  nobody  
Status:  new| Milestone:  1.2 
 Component:  Template system|   Version:  1.1 
Resolution: |  Keywords:  title filter
 Stage:  Unreviewed | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by gonz):

 * cc: gonz (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
-~--~~~~--~~--~--~---

Re: [Django] #11978: 'Duplicate key value violates unique constraint' error while changing inline admin model

[Django]

#11978: 'Duplicate key value violates unique constraint' error while changing
inline admin model
-+--
  Reporter:  kozlenko| Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kozlenko):

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

Comment:

 This error resolved by adding new int primary key - error was because of
 updating id field.

 But it is new error now:
 {{{

 'SecondaryFormFormSet' object has no attribute 'new_objects' at
 django/contrib/admin/options.py in construct_change_message, line 523

 }}}

-- 
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] #10314: TestCase assert methods do not accept a msg parameter

[Django]

#10314: TestCase assert methods do not accept a msg parameter
+---
  Reporter:  wwinham| Owner:  nobody
Status:  closed | Milestone:
 Component:  Testing framework  |   Version:  1.0   
Resolution:  wontfix|  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 If you want to discuss a wontfix, the right place is django-dev.

-- 
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] #10314: TestCase assert methods do not accept a msg parameter

[Django]

#10314: TestCase assert methods do not accept a msg parameter
+---
  Reporter:  wwinham| Owner:  nobody
Status:  closed | Milestone:
 Component:  Testing framework  |   Version:  1.0   
Resolution:  wontfix|  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by christian.oud...@gmail.com):

 How would you suggest handling use cases such as the above code snippet
 without a msg parameter?

-- 
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] #11578: Include init.d script in source for downstream packaging

[Django]

#11578: Include init.d script in source for downstream packaging
-+--
  Reporter:  basti   | Owner:  nobody
Status:  closed  | Milestone:  1.2   
 Component:  Uncategorized   |   Version:  SVN   
Resolution:  wontfix |  Keywords:  init.d
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by russellm):

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

Comment:

 I'm not convinced that the Django repository is the right place for this.
 init.d scripts are highly OS dependent, and can even be OS version
 dependent. If package maintainers want to include scripts like this, I
 encourage them to do so, but I don't see what having this code in the
 Django repository does to improve that process.

 On top of the platform issue, there is also the issue that Django has
 historically treated deployment as a documentation issue. We have avoided
 providing Apache config files, wsgi scripts, or any other deployment
 artefact because local configuration of a webserver is something that
 always needs to be tuned to local needs.

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

[Changeset] r11602 - django/branches/releases/1.1.X/django/contrib/comments

[noreply]

Author: russellm
Date: 2009-10-08 08:32:23 -0500 (Thu, 08 Oct 2009)
New Revision: 11602

Modified:
   django/branches/releases/1.1.X/django/contrib/comments/admin.py
Log:
[1.1.X] Fixed #11995 -- Modified the admin site definition for comments so that 
users are shown as a raw id list. Thanks to James Bennett for the report and 
patch.

Backport of r11601 from trunk.

Modified: django/branches/releases/1.1.X/django/contrib/comments/admin.py
===
--- django/branches/releases/1.1.X/django/contrib/comments/admin.py 
2009-10-08 13:30:31 UTC (rev 11601)
+++ django/branches/releases/1.1.X/django/contrib/comments/admin.py 
2009-10-08 13:32:23 UTC (rev 11602)
@@ -20,6 +20,7 @@
 list_filter = ('submit_date', 'site', 'is_public', 'is_removed')
 date_hierarchy = 'submit_date'
 ordering = ('-submit_date',)
+raw_id_fields = ('user',)
 search_fields = ('comment', 'user__username', 'user_name', 'user_email', 
'user_url', 'ip_address')
 
 # Only register the default admin if the model is the built-in comment model


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

[Changeset] r11601 - django/trunk/django/contrib/comments

[noreply]

Author: russellm
Date: 2009-10-08 08:30:31 -0500 (Thu, 08 Oct 2009)
New Revision: 11601

Modified:
   django/trunk/django/contrib/comments/admin.py
Log:
Fixed #11995 -- Modified the admin site definition for comments so that users 
are shown as a raw id list. Thanks to James Bennett for the report and patch.

Modified: django/trunk/django/contrib/comments/admin.py
===
--- django/trunk/django/contrib/comments/admin.py   2009-10-01 16:15:27 UTC 
(rev 11600)
+++ django/trunk/django/contrib/comments/admin.py   2009-10-08 13:30:31 UTC 
(rev 11601)
@@ -20,6 +20,7 @@
 list_filter = ('submit_date', 'site', 'is_public', 'is_removed')
 date_hierarchy = 'submit_date'
 ordering = ('-submit_date',)
+raw_id_fields = ('user',)
 search_fields = ('comment', 'user__username', 'user_name', 'user_email', 
'user_url', 'ip_address')
 
 # Only register the default admin if the model is the built-in comment model


--~--~-~--~~~---~--~~
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] #11997: cache_control returns 200 OK response even page has not been changed.

[Django]

#11997: cache_control returns 200 OK response even page has not been changed.
--+-
 Reporter:  jtiai |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Cache system  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Provided code:
 {{{
 @cache_control(must_revalidate=True)
 @cache_page(60 * 60)
 def myview(request)
 return HttpResponse('test')
 }}}

 Symptoms:
 Returns always 200 OK response and complete cached content. Modified since
 and modified dates and ETags in request and response headers do match.

 Correct behavior:
 Return value 304 Not Modified if cache conditions are met and do not fetch
 data from cache nor execute view.

-- 
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] #11996: unique over more than one fields

[Django]

#11996: unique over more than one fields
---+
  Reporter:  robert| Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.1   
Resolution:  invalid   |  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by emulbreh):

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

Comment:

 Sounds like you are looking for
 
[http://docs.djangoproject.com/en/dev/ref/models/fields/#django.db.models.ManyToManyField.symmetrical
 ManyToManyField.symmetrical] - although the ticket summary suggests
 [http://docs.djangoproject.com/en/dev/ref/models/options/#unique-together
 Meta.unique_together].

-- 
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] #8576: Multiple AutoFields in a model

[Django]

#8576: Multiple AutoFields in a model
---+
  Reporter:  honeyman  | Owner:  nobody 
   
Status:  closed| Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  SVN
   
Resolution:  wontfix   |  Keywords:  multiple 
autofield
 Stage:  Design decision needed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 As mentioned in the comment when this was closed, the way to get the
 decision reconsidered is to bring it up on the developer's mailing list.

-- 
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] #11996: unique over more than one fields

[Django]

#11996: unique over more than one fields
--+-
 Reporter:  robert|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 i got conflicted with the following issue...
 if user_a has made a friendship with user_b, user_b shouldn't be able to
 make a friendship
 with user_a. so a primary key like: (a,b) -> (b,a) would be needed. it
 would really be a pleasant
 feature!!

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