[Django] #13647: Duplicated import of deepcopy in django.db.models.query

[Django]

#13647: Duplicated import of deepcopy in django.db.models.query
--+-
 Reporter:  DaNmarner |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 Obviously deepcopy is being imported twice from copy and copycompat...so
 the legacy code should be gone.

-- 
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] #13644: "Add another" link doesn't appear in Inlines with many-to-many

[Django]

#13644: "Add another" link doesn't appear in Inlines with many-to-many
-+--
  Reporter:  mateusz.haligow...@nostromolabs.pl  | Owner:  
nobody  
Status:  new | Milestone:   
   
 Component:  django.contrib.admin|   Version:  1.2  
   
Resolution:  |  Keywords:  
admin inline
 Stage:  Unreviewed  | Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by carljm):

  * component:  Uncategorized => django.contrib.admin

Comment:

 This sounds like #13407, which is fixed. Are you definitely on a released
 1.2 version? Can you attach sample models.py and admin.py that show the
 symptom?

-- 
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] #12735: django shell is broken with IPython 0.11.x (bzr.r1219)

[Django]

#12735: django shell is broken with IPython 0.11.x (bzr.r1219)
--+-
  Reporter:  alperkanat   | Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Accepted | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by ramiro):

 Replying to [comment:3 ramiro]:
 > ... against the now stable 0.11 IPython release.

 Wrong. IPython 0.1 hasn't been released yet.

-- 
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] #13646: Wrong RE in comma_separated_int_list_re

[Django]

#13646: Wrong RE in comma_separated_int_list_re
-+--
 Reporter:  aledr|   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Uncategorized| Version:  1.2   
 Keywords:  comma separated  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 The actual RE validator in comma_separated_int_list_re for
 CommaSeparatedIntegerField will allow some kind of following values:


 {{{
 ',,,' '1,,2,3,'
 }}}


 It is

 {{{
 comma_separated_int_list_re = re.compile('^[\d,]+$')
 }}}

 and should be:

 {{{
 comma_separated_int_list_re = re.compile('^[\d,]*\d$')
 }}}

-- 
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] #13645: The “local flavor” add-ons for Turkey

[Django]

#13645: The “local flavor” add-ons for Turkey
+---
 Reporter:  rkirmizi|   Owner:  nobody
   Status:  new |   Milestone:
Component:  django.contrib.localflavor  | Version:  1.2   
 Keywords:  turkish local flavor|   Stage:  Unreviewed
Has_patch:  0   |  
+---
 i wanna add Turkish local flavor but i don't know where to start.

-- 
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] #13644: "Add another" link doesn't appear in Inlines with many-to-many

[Django]

#13644: "Add another" link doesn't appear in Inlines with many-to-many
-+--
  Reporter:  mateusz.haligow...@nostromolabs.pl  | Owner:  
nobody  
Status:  new | Milestone:   
   
 Component:  Uncategorized   |   Version:  1.2  
   
Resolution:  |  Keywords:  
admin inline
 Stage:  Unreviewed  | Has_patch:  0
   
Needs_docs:  0   |   Needs_tests:  0
   
Needs_better_patch:  0   |  
-+--
Changes (by mateusz.haligow...@nostromolabs.pl):

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

Comment:

 What if I want to try to fix 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-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] #13644: "Add another" link doesn't appear in Inlines with many-to-many

[Django]

#13644: "Add another" link doesn't appear in Inlines with many-to-many
+---
 Reporter:  mateusz.haligow...@nostromolabs.pl  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Uncategorized   | Version:  1.2   
 Keywords:  admin inline|   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I have created a model Offer with one-to-many Option fields (ie. Option
 model has ForeignKey to Offer). Option contained a ForeignKey to
 Accomodation. Then, I made the Admin for Offer with inline of Option.
 Everything worked fine and the "Add another" link appeared.

 Then, I had a note from my customer, who asked me to make Accomodation as
 many-to-many with Option. But then, the "Add another" disappeared".

-- 
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] #13641: The location of the get_connection() function does not correspond with the documentation

[Django]

#13641: The location of the get_connection() function does not correspond with 
the
documentation
+---
  Reporter:  caumons| Owner:  nobody
   
Status:  closed | Milestone:
   
 Component:  Documentation  |   Version:  1.1   
   
Resolution:  invalid|  Keywords:  email, connection, 
get_connection, SMTPConnection
 Stage:  Unreviewed | Has_patch:  0 
   
Needs_docs:  0  |   Needs_tests:  0 
   
Needs_better_patch:  0  |  
+---
Comment (by caumons):

 Yes, I was looking at the Django 1.2 documentation and therefore I thought
 that the code did not match the documentation. However, I think that it is
 not enough clear which part is exactly a new feature for the new 1.2
 version because the note is very tinny and a little difficult to know
 which features affect. Another developer also did not see a note like this
 in the template syntax part (with the new smart ifs) and confused him. So
 I propose to make this notes more visible.

-- 
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] #13643: Admin changelist page very slow with postgresql and a huge table

[Django]

#13643: Admin changelist page very slow with postgresql and a huge table
--+-
 Reporter:  marcob|   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Postgresql count(*) is a slooow operation because it forces a full table
 scan.
 It would be nice to have an admin option to disable full counts and only
 provide previous/next-based navigation.

 As a workaround you could get this LazyPaginator
 http://github.com/andymckay/lazy_paginator and write a bit of (ugly)
 monkey patching:

 {{{
 # Lazy pagination
 from lazypaginator import LazyPaginator, InvalidPage
 from django.contrib.admin.views import main
 _ChangeList = main.ChangeList
 _get_results = main.ChangeList.get_results

 class ChangeList(_ChangeList):
 def get_results(self, request):
 if not getattr(self.model_admin, 'lazy_pagination', False):
 return _get_results(self, request)

 paginator = LazyPaginator(self.query_set, self.list_per_page,
 max_safe_pages=5)
 full_result_count = result_count = paginator.max_safe_pages *
 self.list_per_page
 can_show_all = False
 multi_page = result_count > self.list_per_page

 # Get the list of objects to display on this page.
 try:
 result_list = paginator.page(self.page_num+1).object_list
 except InvalidPage:
 result_list = ()

 self.result_count = result_count
 self.full_result_count = full_result_count
 self.result_list = result_list
 self.can_show_all = can_show_all
 self.multi_page = multi_page
 self.paginator = paginator

 setattr(main, 'ChangeList', ChangeList)
 }}}

 Then you could use in your model admin:
 {{{
 lazy_pagination = True
 }}}

 Pro: no more changelist delay with huge table
 Con: wrong record count

 Ciao.
 Marco.

-- 
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] #13533: queries test fails under MySQL InnoDB

[Django]

#13533: queries test fails under MySQL InnoDB
---+
  Reporter:  russellm  | Owner:  nobody 
 
Status:  new   | Milestone:  1.3
 
 Component:  Database layer (models, ORM)  |   Version:  1.2-beta   
 
Resolution:|  Keywords:  innodb 
mysql
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by erikr):

 * cc: erikr (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] #4982: {% blocktrans %} does not escape % in text

[Django]

#4982: {% blocktrans %} does not escape % in text
+---
  Reporter:  nostgard   | Owner:  permon
  
Status:  reopened   | Milestone:
  
 Component:  Internationalization   |   Version:  SVN   
  
Resolution: |  Keywords:  
sprintsept14
 Stage:  Ready for checkin  | Has_patch:  1 
  
Needs_docs:  0  |   Needs_tests:  0 
  
Needs_better_patch:  1  |  
+---
Changes (by nasmon):

  * status:  closed => reopened
  * needs_better_patch:  0 => 1
  * resolution:  fixed =>

Comment:

 On Django 1.2.1:
 When using single % inside blocktrans, "django-admin.py makemessages"
 won't work and as %% inside the template, the output still is %%, due to
 the patch above. When removing the patch line, everything works ok.

-- 
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] #13641: The location of the get_connection() function does not correspond with the documentation

[Django]

#13641: The location of the get_connection() function does not correspond with 
the
documentation
+---
  Reporter:  caumons| Owner:  nobody
   
Status:  closed | Milestone:
   
 Component:  Documentation  |   Version:  1.1   
   
Resolution:  invalid|  Keywords:  email, connection, 
get_connection, SMTPConnection
 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:

> If we try to import the get_connection() function from django.core.mail
> as specified in the documentation we get the following ImportError in
> Django 1.1.1:
>
> Python 2.6.4 (r264:75706, Dec  7 2009, 18:43:55)
> [GCC 4.4.1] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> (InteractiveConsole)
> >>> from django.core.mail import get_connection
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: cannot import name get_connection
>
> Looking at the source code of the module situated at
> /usr/local/lib/python2.6/dist-packages/django/core/mail.py we can check
> that no get_connection() is declared in the module.
> If we want to create a connection to send emails, we have to instantiate
> the SMTPConnection class and then call its methods. For example:
>
> mailConnection = SMTPConnection()
> mailConnection.open()
> mailConnection.send_messages([email1, email2])
> mailConnection.close()
>
> get_connection(self, fail_silently=False) is a method inside the
> EmailMessage class situated in line 228 and used in line 266, not a
> function.
>
> The solution I see is to update the documentation referring to emails
> section.

New description:

 If we try to import the get_connection() function from django.core.mail as
 specified in the documentation we get the following ImportError in Django
 1.1.1:
 {{{
 Python 2.6.4 (r264:75706, Dec  7 2009, 18:43:55)
 [GCC 4.4.1] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> from django.core.mail import get_connection
 Traceback (most recent call last):
   File "", line 1, in 
 ImportError: cannot import name get_connection
 }}}
 Looking at the source code of the module situated at
 /usr/local/lib/python2.6/dist-packages/django/core/mail.py we can check
 that no get_connection() is declared in the module.
 If we want to create a connection to send emails, we have to instantiate
 the SMTPConnection class and then call its methods. For example:
 {{{
 mailConnection = SMTPConnection()
 mailConnection.open()
 mailConnection.send_messages([email1, email2])
 mailConnection.close()
 }}}
 get_connection(self, fail_silently=False) is a method inside the
 EmailMessage class situated in line 228 and used in line 266, not a
 function.

 The solution I see is to update the documentation referring to emails
 section.

Comment:

 Fixed formatting; please use preview.

 You seem to be looking at the doc for Django 1.2 (or current trunk) while
 using Django 1.1.1. `get_connection` is mentioned under the doc for email
 backends, which is flagged as new in 1.2:
 http://docs.djangoproject.com/en/dev/topics/email/#e-mail-backends. This
 function does exist in Django 1.2:

 {{{
 #!python
 >>> import django
 >>> django.get_version()
 '1.2.1'
 >>> from django.core.mail import get_connection
 >>>
 }}}

 `django.core.mail.get_connection` did not exist in 1.1 and is not
 mentioned in the 1.1 version of the doc
 (http://docs.djangoproject.com/en/1.1/topics/email/).

-- 
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] #13642: Request of translating model fileds functionality

[Django]

#13642: Request of translating model fileds functionality
---+
 Reporter:  caumons|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Internationalization   | Version:  1.2   
 Keywords:  translation, model fields  |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 It would be good to have the option to specify fields of the models
 translated into different languages. For example, if we have the model
 Django and it has the field description, it would be good being able to
 store it in different languages and retreive the desired one each time.
 One more thing is that the apps' names can not contain non ascii
 characters such as accents and that is very annoying when developing for
 example in Spanish.

-- 
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] #13641: The location of the get_connection() function does not correspond with the documentation

[Django]

#13641: The location of the get_connection() function does not correspond with 
the
documentation
---+
 Reporter:  caumons|   Owner:  
nobody
   Status:  new|   Milestone:   
 
Component:  Documentation  | Version:  
1.1   
 Keywords:  email, connection, get_connection, SMTPConnection  |   Stage:  
Unreviewed
Has_patch:  0  |  
---+
 If we try to import the get_connection() function from django.core.mail as
 specified in the documentation we get the following ImportError in Django
 1.1.1:

 Python 2.6.4 (r264:75706, Dec  7 2009, 18:43:55)
 [GCC 4.4.1] on linux2
 Type "help", "copyright", "credits" or "license" for more information.
 (InteractiveConsole)
 >>> from django.core.mail import get_connection
 Traceback (most recent call last):
   File "", line 1, in 
 ImportError: cannot import name get_connection

 Looking at the source code of the module situated at
 /usr/local/lib/python2.6/dist-packages/django/core/mail.py we can check
 that no get_connection() is declared in the module.
 If we want to create a connection to send emails, we have to instantiate
 the SMTPConnection class and then call its methods. For example:

 mailConnection = SMTPConnection()
 mailConnection.open()
 mailConnection.send_messages([email1, email2])
 mailConnection.close()

 get_connection(self, fail_silently=False) is a method inside the
 EmailMessage class situated in line 228 and used in line 266, not a
 function.

 The solution I see is to update the documentation referring to emails
 section.

-- 
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] #13488: Exceptions in GEOS I/O object destructor at process exit

[Django]

#13488: Exceptions in GEOS I/O object destructor at process exit
---+
  Reporter:  mro...@arinc.com  | Owner:  jbronn  
Status:  assigned  | Milestone:  
 Component:  GIS   |   Version:  1.2-beta
Resolution:|  Keywords:  gis 
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by bkonkle):

 I'm also getting this message upon exit.  I'm running Django on an OS X
 Snow Leopard laptop, using Postgres 8.3, GEOS 3.1.1, Proj 4.7.0, PostGIS
 1.3.6, and GDAL 1.6.3.  We haven't started running Django 1.2 on our
 Ubuntu 8.04 dev server yet, but when we do I'll check to see if the
 message shows up there as well.

-- 
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] #13640: add_filter in django/db/models/ sql/query.py causes exception when model have 'evaluate' attribute

[Django]

#13640: add_filter in django/db/models/ sql/query.py causes exception when model
have 'evaluate' attribute
---+
  Reporter:  LukaszKorzybski   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Old description:

> I was migrating some django project recently from django 1.0.4 to 1.2.
> In Django 1.2/1.1 I found that if model have 'evaluate' attribute then
> one will get exception in admin edit page for that model if the page
> contains inline forms with related models:
>
> Exception Value:  'Shipper' object has no attribute 'prepare'
> Exception Location: .../django/db/models/sql/expressions.py in
> __init__, line 12
>
> It is caused by the fact that add_filter function in django/db/models/
> sql/query.py does such a check:
>
> ...
> 1005.  elif hasattr(value, 'evaluate'):
> 1006.  # If value is a query expression, evaluate it
> 1007.  value = SQLEvaluator(value, self) ...
> 1008.  having_clause = value.contains_aggregate
> ...
>
> The problem is that "value" in this case is Shipper model which in
> have "evaluate" method so it is recognized as query expression here.
>
> Greetings,

New description:

 I was migrating some django project recently from django 1.0.4 to 1.2.
 In Django 1.2/1.1 I found that if model have 'evaluate' attribute then
 one will get exception in admin edit page for that model if the page
 contains inline forms with related models:
 {{{
 Exception Value:  'Shipper' object has no attribute 'prepare'
 Exception Location: .../django/db/models/sql/expressions.py in
 __init__, line 12
 }}}
 It is caused by the fact that add_filter function in
 django/db/models/sql/query.py does such a check:
 {{{
 ...
 1005.  elif hasattr(value, 'evaluate'):
 1006.  # If value is a query expression, evaluate it
 1007.  value = SQLEvaluator(value, self) ...
 1008.  having_clause = value.contains_aggregate
 ...
 }}}
 The problem is that "value" in this case is Shipper model which in
 have "evaluate" method so it is recognized as query expression here.

 Greetings,

Comment (by Alex):

 Updated the syntax.

-- 
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] #13640: add_filter in django/db/models/ sql/query.py causes exception when model have 'evaluate' attribute

[Django]

#13640: add_filter in django/db/models/ sql/query.py causes exception when model
have 'evaluate' attribute
---+
  Reporter:  LukaszKorzybski   | Owner:  nobody
Status:  new   | Milestone:
 Component:  Database layer (models, ORM)  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by LukaszKorzybski):

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

Comment:

 Ups I forgot to do some formatting of the text, sorry for that :/

-- 
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] #13640: add_filter in django/db/models/ sql/query.py causes exception when model have 'evaluate' attribute

[Django]

#13640: add_filter in django/db/models/ sql/query.py causes exception when model
have 'evaluate' attribute
--+-
 Reporter:  LukaszKorzybski   |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I was migrating some django project recently from django 1.0.4 to 1.2.
 In Django 1.2/1.1 I found that if model have 'evaluate' attribute then
 one will get exception in admin edit page for that model if the page
 contains inline forms with related models:

 Exception Value:  'Shipper' object has no attribute 'prepare'
 Exception Location: .../django/db/models/sql/expressions.py in
 __init__, line 12

 It is caused by the fact that add_filter function in django/db/models/
 sql/query.py does such a check:

 ...
 1005.  elif hasattr(value, 'evaluate'):
 1006.  # If value is a query expression, evaluate it
 1007.  value = SQLEvaluator(value, self) ...
 1008.  having_clause = value.contains_aggregate
 ...

 The problem is that "value" in this case is Shipper model which in
 have "evaluate" method so it is recognized as query expression here.

 Greetings,

-- 
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] #56: MySQL id columns should be UNSIGNED

[Django]

#56: MySQL id columns should be UNSIGNED
---+
  Reporter:  Manuzhai    | Owner:  
glassresistor
Status:  new   | Milestone:  1.3
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords:  mysql  
  
 Stage:  Design decision needed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * keywords:  => 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-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] #13639: Date Time format

[Django]

#13639: Date Time format
-+--
 Reporter:  ctao |   Owner:  
nobody
   Status:  new  |   Milestone: 
   
Component:  Forms| Version:  
1.2   
 Keywords:  forms widgets DateInput DateTimeInput TimeInput  |   Stage:  
Unreviewed
Has_patch:  1|  
-+--
 The change for formats.get_format looks much better than ever, but the
 forms/widgets.py missed some changed.

-- 
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] #6460: New feature : Multilingual Content

[Django]

#6460: New feature : Multilingual Content
---+
  Reporter:  g00fy | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  Internationalization  |   Version: 

Resolution:|  Keywords:  multilingual 
content i18n-nofix
 Stage:  Someday/Maybe | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

 * cc: alex.guent...@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-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] #13627: contributing.txt should mention how to reset your password

[Django]

#13627: contributing.txt should mention how to reset your password
+---
  Reporter:  zerok  | Owner:  nobody  
Status:  new| Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution: |  Keywords:  contributing
 Stage:  Ready for checkin  | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by erikr):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * 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] #7735: IPv6 support for runserver

[Django]

#7735: IPv6 support for runserver
+---
  Reporter:  jbalonso   | Owner:  jbalonso
Status:  assigned   | Milestone:  
 Component:  django-admin.py runserver  |   Version:  SVN 
Resolution: |  Keywords:  ipv6
 Stage:  Design decision needed | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by jbalonso):

 Replying to [comment:7 erikr]:
 > Is jbalonso still tracking this ticket? It's been quiet for a year.

 Yes, I'm still here.  It's been closer to two years, actually.

 > Also, why is this in design decision needed? It seems like a pretty
 normal thing to add, and the patch seems OK (although it will probably
 need updating to apply cleanly to trunk).

 I haven't been keeping the patch up-to-date (or even checking, for that
 matter), because I wanted to hear a "Yes, we'll take that" rather than
 chasing trunk on a whim and a prayer.

 That said, I'd happily brush it up again.

-- 
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] #6460: New feature : Multilingual Content

[Django]

#6460: New feature : Multilingual Content
---+
  Reporter:  g00fy | Owner:  nobody 

Status:  new   | Milestone: 

 Component:  Internationalization  |   Version: 

Resolution:|  Keywords:  multilingual 
content i18n-nofix
 Stage:  Someday/Maybe | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

Needs_better_patch:  0 |  
---+
Comment (by blubmitsahne):

 Overview of current implementations and alternatives documented in
 [wiki:ModelInterNationalization]

-- 
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] #56: MySQL id columns should be UNSIGNED

[Django]

#56: MySQL id columns should be UNSIGNED
---+
  Reporter:  Manuzhai    | Owner:  
glassresistor
Status:  new   | Milestone:  1.3
  
 Component:  Database layer (models, ORM)  |   Version:  SVN
  
Resolution:|  Keywords: 
  
 Stage:  Design decision needed| Has_patch:  1  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

 * cc: lukasz.m.dobrzan...@gmail.com (added)
  * has_patch:  0 => 1
  * version:  => SVN
  * milestone:  => 1.3

-- 
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] #13533: queries test fails under MySQL InnoDB

[Django]

#13533: queries test fails under MySQL InnoDB
---+
  Reporter:  russellm  | Owner:  nobody 
 
Status:  new   | Milestone:  1.3
 
 Component:  Database layer (models, ORM)  |   Version:  1.2-beta   
 
Resolution:|  Keywords:  innodb 
mysql
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by erikr):

  * keywords:  => innodb mysql

Comment:

 As of r13252? As far as I can see, this was introduced in r12970.

 I've played around with transaction isolation levels and query caching,
 but didn't get any results.

-- 
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] #12421: Foreign Key on Non-Primary Field fails due to lack of Index on Related Field w/ MySQL

[Django]

#12421: Foreign Key on Non-Primary Field fails due to lack of Index on Related
Field w/ MySQL
---+
  Reporter:  anonymous | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  worksforme|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Comment (by clouserw):

 Indeed, it looks like this won't occur after #11702.  I agree this is
 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.

Re: [Django] #13635: URLconfs should accept classes as views

[Django]

#13635: URLconfs should accept classes as views
-+--
  Reporter:  bfirsh  | Owner:  bfirsh 
Status:  new | Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  urlconf
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by lukeplant):

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

Comment:

 Personally, I think that we should instead encourage people to create view
 functions out of view classes:
 {{{
 #!python
 my_view = make_view(MyViewClass)
 }}}

 (where `make_view` is a very easy to write utility that would be included
 in core).  This makes it much easier to handle decorators, and insulates
 the URLconf from implementation details (like the fact that the view is
 implemented using a class).

 We had some discussion about this: http://groups.google.com/group/django-
 developers/browse_thread/thread/e23d9a5a58fe5891/23b9b3aa96bbb7f2?lnk=gst

 But not many people responded to my point of 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-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] #13638: Serializer regress tests have uncessary transaction management that is very slow

[Django]

#13638: Serializer regress tests have uncessary transaction management that is 
very
slow
---+
 Reporter:  Alex   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 We can just delete this and it still pases for me (tested under postgres
 and sqlite).

-- 
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] #13637: Generic Relations don't work correctly on a non-default database alias

[Django]

#13637: Generic Relations don't work correctly on a non-default database alias
---+
  Reporter:  andrewgodwin  | Owner:  
andrewgodwin
Status:  assigned  | Milestone: 
 
 Component:  Database layer (models, ORM)  |   Version:  SVN
 
Resolution:|  Keywords:  multi-db, 
truncation
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by andrewgodwin):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * version:  1.1 => SVN
  * owner:  nobody => andrewgodwin
  * needs_docs:  => 0
  * stage:  Unreviewed => Accepted

-- 
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] #13637: Generic Relations don't work correctly on a non-default database alias

[Django]

#13637: Generic Relations don't work correctly on a non-default database alias
--+-
 Reporter:  andrewgodwin  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:  multi-db, truncation  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Specifically, line 195 of contrib.contenttypes.generic uses
 django.db.connection directly - this needs to be fixed.

 It looks like it will need connection-choosing pushed inside the
 RelatedManager provided. I'm going to work on fixing this - just noting it
 as a separate ticket to #13528 (I found it while fixing that, but it's a
 separate issue, pretty much, it affects quoting as well as table name
 truncation).

-- 
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] #13636: Change fixture doctests to unit tests

[Django]

#13636: Change fixture doctests to unit tests
---+
 Reporter:  ericholscher   |   Owner:  nobody
   Status:  new|   Milestone:  1.3   
Component:  Testing framework  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 These have the most amount of flushing, which will slow down real test
 runs. I've gone ahead and done a good amount of this, it does touch
 management commands to have a return_output that you can pass into
 call_command, so it returns instead of prints for dumpdata and such.

-- 
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] #13635: URLconfs should accept classes as views

[Django]

#13635: URLconfs should accept classes as views
+---
 Reporter:  bfirsh  |   Owner:  bfirsh
   Status:  new |   Milestone:
Component:  Core framework  | Version:  SVN   
 Keywords:  urlconf |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 If a URLconf is passed a class, and isinstance(cls, type) is true, it
 should instantiate the class on each request and call it. This makes class
 based views (#6735) trivially thread safe.

-- 
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] #13621: regression in 1.2.1 from 1.2 AM PM time input no longer works correctly

[Django]

#13621: regression in 1.2.1 from 1.2 AM PM time input no longer works correctly
---+
  Reporter:  bufke | Owner:  zerok
Status:  new   | Milestone:   
 Component:  Forms |   Version:  1.2  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  0 |   Needs_tests:  1
Needs_better_patch:  0 |  
---+
Changes (by zerok):

  * owner:  nobody => zerok

-- 
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] #13634: Turn aggregation tests into unittests

[Django]

#13634: Turn aggregation tests into unittests
+---
  Reporter:  Alex   | Owner:  nobody
Status:  new| Milestone:
 Component:  Testing framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
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.

[Django] #13634: Turn aggregation tests into unittests

[Django]

#13634: Turn aggregation tests into unittests
---+
 Reporter:  Alex   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Testing framework  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 This removes a flush call, which is very expensive.

-- 
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] #13633: Add a widget_callback to forms, modelforms, etc

[Django]

#13633: Add a widget_callback to forms, modelforms, etc
---+
  Reporter:  russellm  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by russellm):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 #13095 is related to 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-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] #13095: modelform_factory, modelformset_factory, inlineformset_factory formfield_callback lamba function missing **kwargs

[Django]

#13095: modelform_factory, modelformset_factory, inlineformset_factory
formfield_callback lamba function missing **kwargs
---+
  Reporter:  hvdklauw  | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Forms |   Version:  SVN  
Resolution:|  Keywords:  inlineformset_factory
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by russellm):

 I'll probably end up fixing this as part of #13633, since there will be
 some overlap (especially when it comes to adding tests)

-- 
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] #13633: Add a widget_callback to forms, modelforms, etc

[Django]

#13633: Add a widget_callback to forms, modelforms, etc
--+-
 Reporter:  russellm  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Forms | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Modelforms currently support (although undocumented) a formfield_callback
 method that can be used to control the widgets that are used for a form
 field. We also support the definition of a 'widgets' attribute in the Meta
 of a modelform that allows you to override the widget for a particular
 model field based on the name of the attribute.

 We should be able to define a callback to alter the widget
 programatically, based on the form field that is being rendered.

-- 
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] #13631: IntegerField has no attributes max_value and min_value (1.2 regression)

[Django]

#13631: IntegerField has no attributes max_value and min_value (1.2 regression)
---+
  Reporter:  mila  | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  1 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by erikr):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * needs_tests:  => 0
  * needs_docs:  => 1

Comment:

 I haven't seen the old code, but it seems IntegerField now does min/max
 using django.core.validators. The fields are indeed not set in the code.
 I think the documentation is not very clear on whether or not these fields
 should exist.

 So, either the fields should be added, or the documentation should be
 clarified so that it doesn't suggests these fields being there.
 I don't see an easy alternative to get them from the field instance.

-- 
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] #7735: IPv6 support for runserver

[Django]

#7735: IPv6 support for runserver
+---
  Reporter:  jbalonso   | Owner:  jbalonso
Status:  assigned   | Milestone:  
 Component:  django-admin.py runserver  |   Version:  SVN 
Resolution: |  Keywords:  ipv6
 Stage:  Design decision needed | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by erikr):

 * cc: erom...@ripe.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-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] #13363: extra fields of Model.objects.extra() can't be filtered

[Django]

#13363: extra fields of Model.objects.extra() can't be filtered
--+-
  Reporter:  fetzig   | Owner:   
Status:  reopened | Milestone:   
 Component:  ORM aggregation  |   Version:  SVN  
Resolution:   |  Keywords:  queryset extra filter
 Stage:  Unreviewed   | Has_patch:  0
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by ris):

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

Comment:

 Sorry I know it's impolite to reopen tickets like this.

 I too would find this a very useful feature.

 I realize _similar_ functionality is possible using the where= clause, but
 allowing the selected parameter to be filtered against would mean you
 could re-use the same calculated parameter (multiple times) from within
 complex Q() statements.

 e.g. - currently in my app I am dynamically building a really very complex
 query using Q statements. Having to fall back to the QuerySet to perform
 the extra() from within this code would be quite painful and screw up my
 encapsulation.

-- 
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] #8424: Implement time filters

[Django]

#8424: Implement time filters
---+
  Reporter:  gnuvince  | Owner:  UloPe  
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version: 
   
Resolution:|  Keywords:  datetime 
filter hour minute second
 Stage:  Accepted  | Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  1  
   
Needs_better_patch:  1 |  
---+
Changes (by UloPe):

  * owner:  nobody => UloPe

Comment:

 (djangocon.eu 2010 sprint)
 I'll give this one a shot

-- 
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] #13632: lack of builtin range checking of id fields

[Django]

#13632: lack of builtin range checking of id fields
--+-
 Reporter:  anonymous |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 The lack of builtin range checking for id fields is a vulnerability.

 {{{
 /service/docserver/papers/3/ --> produces a document
 /service/docserver/papers/6578/ --> produces 404 page
 /service/docserver/papers/999/ --> throws OverflowError
 }}}

 Traceback is at http://paste.pocoo.org/show/218865/

 I think the last case should throw !DoesNotExist instead of causing server
 error.
 In the case at hand I used generic views and sqlite3 DB backend.
 Of course, one can check this himself all over the places, however that
 would be against the DRY principle.
 Not to mention, it would be complicated when using generic views.

-- 
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] #13621: regression in 1.2.1 from 1.2 AM PM time input no longer works correctly

[Django]

#13621: regression in 1.2.1 from 1.2 AM PM time input no longer works correctly
---+
  Reporter:  bufke | Owner:  nobody
Status:  new   | Milestone:
 Component:  Forms |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by zerok):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * component:  Uncategorized => Forms
  * needs_tests:  => 1
  * 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] #13624: Hide signatures from the debug pages

[Django]

#13624: Hide signatures from the debug pages
+---
  Reporter:  Kronuz | Owner:  erikr
Status:  assigned   | Milestone:  1.3  
 Component:  Documentation  |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by erikr):

  * needs_better_patch:  1 => 0
  * stage:  Accepted => Ready for checkin

Comment:

 Documentation patch updated :)

-- 
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] #13584: django.forms FileField does not allow empty files.

[Django]

#13584: django.forms FileField does not allow empty files.
---+
  Reporter:  jamesh| Owner:  nobody
Status:  new   | Milestone:  1.3   
 Component:  File uploads/storage  |   Version:  SVN   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by erikr):

  * owner:  erikr => nobody
  * needs_docs:  1 => 0
  * has_patch:  0 => 1
  * status:  assigned => new
  * needs_tests:  1 => 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.

[Django] #13631: IntegerField has no attributes max_value and min_value (1.2 regression)

[Django]

#13631: IntegerField has no attributes max_value and min_value (1.2 regression)
---+
 Reporter:  mila   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Forms  | Version:  1.2   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Attributes min_value and max_value are no longer set on IntegerField,
 FloatField and DecimalField in Django 1.2.

 Note these attributes are documented:
 
http://docs.djangoproject.com/en/dev/ref/forms/fields/#django.forms.IntegerField.max_value.
 [[BR]]I'm using them to generate some javascript validation.

-- 
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] #13624: Hide signatures from the debug pages

[Django]

#13624: Hide signatures from the debug pages
+---
  Reporter:  Kronuz | Owner:  erikr
Status:  assigned   | Milestone:  1.3  
 Component:  Documentation  |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  1  |  
+---
Changes (by adamnelson):

  * needs_better_patch:  0 => 1
  * component:  Core framework => Documentation
  * stage:  Ready for checkin => Accepted

Comment:

 Tick mark in the wrong spot in

 {{{
 ``'SIGNATURE``'
 }}}

-- 
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] #13628: Documentation should discourage the usage of doctests

[Django]

#13628: Documentation should discourage the usage of doctests
+---
  Reporter:  d0ugal | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by adamnelson):

  * needs_better_patch:  0 => 1

Comment:

 If a committer approves this, the grammar needs to be fixed in the 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-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] #13623: Code in intro-tutorial03 missing a import statement

[Django]

#13623: Code in intro-tutorial03 missing a import statement
--+-
  Reporter:  lescoutinh...@gmail.com  | Owner:  zerok   
Status:  new  | Milestone:  
 Component:  Documentation|   Version:  SVN 
Resolution:   |  Keywords:  tutorial
 Stage:  Accepted | Has_patch:  1   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by zerok):

  * has_patch:  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] #13623: Code in intro-tutorial03 missing a import statement

[Django]

#13623: Code in intro-tutorial03 missing a import statement
--+-
  Reporter:  lescoutinh...@gmail.com  | Owner:  zerok   
Status:  new  | Milestone:  
 Component:  Documentation|   Version:  SVN 
Resolution:   |  Keywords:  tutorial
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Comment (by zerok):

 Good point, but we should probably put that into a different ticket since
 this, I guess, requires an OK by James.

-- 
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] #13630: DatabaseOperations doesn't have same constructor with SQLITE and PostgreSQL backend

[Django]

#13630: DatabaseOperations doesn't have same constructor with SQLITE and 
PostgreSQL
backend
--+-
 Reporter:  calexium  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Using ''sqlite3'' backend on Django 1.2.1, the '''DatabaseOperations'''
 object is constructed without any parameter (no change from older
 versions).
 Example:

 {{{
 from django.db import backend

 backend.DatabaseOperations().quote_name(my_value)

 }}}

 But using ''postgresql_psycopg2'' backend, the '''DatabaseOperations'''
 constructor need a ''connection'' as parameter :
 Example:

 {{{
 from django.db import backend, connection

 backend.DatabaseOperations(connection).quote_name(my_value)
 }}}

 So this is not possible to have a code working with all backends.

-- 
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] #13622: Caching unicode characters with Memcached no longer works

[Django]

#13622: Caching unicode characters with Memcached no longer works
---+
  Reporter:  Chris Targett   | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  Cache system  |   Version:  1.2
  
Resolution:  worksforme|  Keywords:  
memcached
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 This may be a problem specific to using the old (now deprecated and
 unmaintained) cmemcache bindings. If you are using those old bindings you
 should switch to python-memcached, see:
 http://docs.djangoproject.com/en/dev/topics/cache/#memcached.

-- 
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] #13149: ForeignKeyRawIdWidget doesn't handle invalid values

[Django]

#13149: ForeignKeyRawIdWidget doesn't handle invalid values
---+
  Reporter:  acdha | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  django.contrib.admin  |   Version:  1.2  
Resolution:|  Keywords:  raw_id_fields
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  1
Needs_better_patch:  1 |  
---+
Changes (by petrikuitti...@yahoo.com):

  * needs_better_patch:  0 => 1
  * version:  1.1 => 1.2

Comment:

 Django 1.2+ needs to have patches in two files to get this issue fixed.

 changes to django/forms/models.py from line 984 (catch ValueError):

 {{{
 def to_python(self, value):
 if value in EMPTY_VALUES:
 return None
 try:
 key = self.to_field_name or 'pk'
 value = self.queryset.get(**{key: value})
 except (ValueError, self.queryset.model.DoesNotExist):
 raise ValidationError(self.error_messages['invalid_choice'])
 return value

 }}}

 And django/contrib/admin/widgets.py (catch ValueError as well):


 {{{
 def label_for_value(self, value):
 key = self.rel.get_related_field().name
 try:
 obj = self.rel.to._default_manager.using(self.db).get(**{key:
 value})
 return '%s' %
 escape(truncate_words(obj, 14))
 except (ValueError, self.rel.to.DoesNotExist):
 return ''

 }}}

 Applying both of these patches seems to fix the issue. It would be nice to
 have this fixed in the next Django 1.2.2 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-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] #13095: modelform_factory, modelformset_factory, inlineformset_factory formfield_callback lamba function missing **kwargs

[Django]

#13095: modelform_factory, modelformset_factory, inlineformset_factory
formfield_callback lamba function missing **kwargs
---+
  Reporter:  hvdklauw  | Owner:  nobody   
Status:  new   | Milestone:   
 Component:  Forms |   Version:  SVN  
Resolution:|  Keywords:  inlineformset_factory
 Stage:  Accepted  | Has_patch:  1
Needs_docs:  0 |   Needs_tests:  0
Needs_better_patch:  0 |  
---+
Comment (by aldaran):

 Ok is not critical for 1.2,

 but which is the best solution to have a workaround?
 We cannot use the Meta widgets = {} in the form...
 Ok, we can override the init method and override the widget.

-- 
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] #3680: Add cache control (ETag, Last Modified) to django.contrib.syndication

[Django]

#3680: Add cache control (ETag, Last Modified) to django.contrib.syndication
+---
  Reporter:  j...@jerf.org  | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  RSS framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by bfirsh):

 * cc: bfirsh (added)
  * component:  Contrib apps => RSS framework

Comment:

 Can't this be done with Django's existing caching tools now feeds are
 views?

 http://docs.djangoproject.com/en/1.2/topics/cache/

-- 
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] #13629: Admin Changelist: add app-model_name class to tag

[Django]

#13629: Admin Changelist: add app-model_name class to  tag
--+-
 Reporter:  naos  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  django.contrib.admin  | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Change form pages have "app-model_name" classes in body tag, for eg:[[BR]]
 . Change list pages don't,
 which[[BR]]
 makes them unrecognizable in JavaScript code.

 Example use case:
 I'm currently implementing jQuery tooltips for searchbars to give
 user[[BR]]
 information about which model's fields are searchable in each change list.

 Currently to achieve this I had to override ModelAdmin.changelist_view
 (to[[BR]]
 add model._meta to context) and change_list.html template. This is ok but
 I[[BR]]
 think it would be nice to have it already done in django?

-- 
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] #13528: db_table truncation is applied based on the properties of the default database

[Django]

#13528: db_table truncation is applied based on the properties of the default
database
---+
  Reporter:  russellm  | Owner:  
andrewgodwin
Status:  assigned  | Milestone:  1.3
 
 Component:  Database layer (models, ORM)  |   Version:  1.2-beta   
 
Resolution:|  Keywords: 
 
 Stage:  Accepted  | Has_patch:  0  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by andrewgodwin):

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

Comment:

 I'm working on this - my proposed solution is thus:

  - Deprecate Options.db_table (PendingDeprecationWarning for 1.3)
  - Add Options.get_db_table(using=db_alias)
  - Change all the places Django uses db_table to use get_db_table

 This should both solve the problem, and allow third-party apps to continue
 using db_table (as it's still valid if you've only got one database).

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #13218: django-syndication can't handle https URLs

[Django]

#13218: django-syndication can't handle https URLs
+---
  Reporter:  schaefer   | Owner:  bfirsh
Status:  new| Milestone:
 Component:  RSS framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by bfirsh):

  * stage:  Accepted => Ready for checkin

-- 
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] #13218: django-syndication can't handle https URLs

[Django]

#13218: django-syndication can't handle https URLs
+---
  Reporter:  schaefer   | Owner:  bfirsh
Status:  new| Milestone:
 Component:  RSS framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by bfirsh):

  * has_patch:  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] #13612: Settings.py should not be mandatory

[Django]

#13612: Settings.py should not be mandatory
--+-
  Reporter:  tonnzor  | Owner:  nobody
Status:  new  | Milestone:
 Component:  django-admin.py  |   Version:  SVN   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  1|  
--+-
Changes (by erikr):

  * needs_better_patch:  => 1
  * version:  1.2 => SVN
  * component:  Uncategorized => django-admin.py
  * 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] #13628: Documentation should discourage the usage of doctests

[Django]

#13628: Documentation should discourage the usage of doctests
+---
  Reporter:  d0ugal | Owner:  nobody
Status:  new| Milestone:  1.3   
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by d0ugal):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * 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] #13584: django.forms FileField does not allow empty files.

[Django]

#13584: django.forms FileField does not allow empty files.
---+
  Reporter:  jamesh| Owner:  erikr
Status:  assigned  | Milestone:  1.3  
 Component:  File uploads/storage  |   Version:  SVN  
Resolution:|  Keywords:   
 Stage:  Accepted  | Has_patch:  0
Needs_docs:  1 |   Needs_tests:  1
Needs_better_patch:  0 |  
---+
Changes (by erikr):

  * status:  new => assigned
  * needs_tests:  0 => 1
  * version:  1.1 => SVN
  * milestone:  => 1.3
  * owner:  nobody => erikr
  * needs_docs:  0 => 1
  * stage:  Unreviewed => Accepted

-- 
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] #13218: django-syndication can't handle https URLs

[Django]

#13218: django-syndication can't handle https URLs
+---
  Reporter:  schaefer   | Owner:  bfirsh
Status:  new| Milestone:
 Component:  RSS framework  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by bfirsh):

 * cc: bfirsh (added)
  * owner:  nobody => bfirsh

-- 
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] #13622: Caching unicode characters with Memcached no longer works

[Django]

#13622: Caching unicode characters with Memcached no longer works
---+
  Reporter:  Chris Targett   | Owner:  nobody 
  
Status:  closed| Milestone: 
  
 Component:  Cache system  |   Version:  1.2
  
Resolution:  worksforme|  Keywords:  
memcached
 Stage:  Accepted  | Has_patch:  0  
  
Needs_docs:  0 |   Needs_tests:  0  
  
Needs_better_patch:  0 |  
---+
Changes (by erikr):

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

Comment:

 Testing with django trunk, but a more recent version of the memcached
 module, it works:

 {{{
 >>> from django import VERSION
 >>> VERSION
 (1, 2, 1, 'alpha', 0)

 >>> import memcache
 >>> memcache.__version__
 '1.45'

 >>> from django.core.cache import cache
 >>> cache.set('test_key', u'\u2026')
 >>> cache.get('test_key')
 u'\u2026'
 }}}

 So I guess your memcached module is too old, or this was fixed after 1.2
 release.
 Closing as worksforme.

-- 
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] #13606: admin raw_id_fields fail to check against non-numerical input

[Django]

#13606: admin raw_id_fields fail to check against non-numerical input
---+
  Reporter:  petrikuitti...@yahoo.com  | Owner:  nobody
Status:  closed| Milestone:
 Component:  django.contrib.admin  |   Version:  1.2   
Resolution:  duplicate |  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 The previous ticket (#13149) is still open; the place to post information
 on what is necessary to get it fixed in current trunk code is there. It's
 one problem, there should be only one ticket for tracking getting it
 fixed. The version for that ticket being set to 1.1 just indicates that
 the problem has been around at least since 1.1, it does not mean the fix
 will be specific to 1.1. For any ticket the fix will be made to current
 trunk and backported to the current release branch (if necessary). If the
 existing patches on that ticket no longer work, then it should be marked
 patch needs improvement, or better yet a new patch should be uploaded that
 fixes the problem for current code. A second ticket to track the same
 problem is not helpful.

-- 
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] #12405: django.contrib.auth.views.logout() should support LOGOUT_REDIRECT_URL

[Django]

#12405: django.contrib.auth.views.logout() should support LOGOUT_REDIRECT_URL
-+--
  Reporter:  cmwslw  | Owner:  dloewenherz  
 
Status:  assigned| Milestone:   
 
 Component:  Authentication  |   Version:  1.1  
 
Resolution:  |  Keywords:  logout 
LOGOUT_REDIRECT_URL
 Stage:  Accepted| Has_patch:  0
 
Needs_docs:  1   |   Needs_tests:  1
 
Needs_better_patch:  0   |  
-+--
Comment (by anonymous):

 Please see ticket #11223.

-- 
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] #13623: Code in intro-tutorial03 missing a import statement

[Django]

#13623: Code in intro-tutorial03 missing a import statement
--+-
  Reporter:  lescoutinh...@gmail.com  | Owner:  zerok   
Status:  new  | Milestone:  
 Component:  Documentation|   Version:  SVN 
Resolution:   |  Keywords:  tutorial
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Comment (by erikr):

 For newbie-friendlyness, I think all snippets in the tutorial should have
 all the imports included - it's only 2 or 3 in most cases anyways. I
 remember struggling a bit with finding the right imports, when I first did
 the tutorial

-- 
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] #13552: pre_save & post_save model signals should also specify database to save

[Django]

#13552: pre_save & post_save model signals should also specify database to save
---+
  Reporter:  gmandx| Owner:  
andrewgodwin   
Status:  assigned  | Milestone: 

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

Resolution:|  Keywords:  signals 
multi-db pre_save post_save
 Stage:  Ready for checkin | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

  * stage:  Accepted => Ready for checkin

-- 
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] #13297: Cannot specify 'pk' in model default ordering

[Django]

#13297: Cannot specify 'pk' in model default ordering
---+
  Reporter:  anonymous | Owner:  gruszczy   
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  1.1
Resolution:|  Keywords:  ordering pk
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Comment (by gruszczy):

 Proper formatting of the code.

 {{{
 def get_field(self, name, many_to_many=True):
 """
 Returns the requested field by name. Raises FieldDoesNotExist on
 error.
 """
 if name == 'pk':
 return self.pk
 to_search = many_to_many and (self.fields + self.many_to_many) or
 self.fields
 for f in to_search:
 if f.name == name:
 return f
 raise FieldDoesNotExist('%s has no field named %r' %
 (self.object_name, name))
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #13297: Cannot specify 'pk' in model default ordering

[Django]

#13297: Cannot specify 'pk' in model default ordering
---+
  Reporter:  anonymous | Owner:  gruszczy   
Status:  new   | Milestone: 
 Component:  Database layer (models, ORM)  |   Version:  1.1
Resolution:|  Keywords:  ordering pk
 Stage:  Accepted  | Has_patch:  0  
Needs_docs:  0 |   Needs_tests:  0  
Needs_better_patch:  0 |  
---+
Changes (by gruszczy):

  * owner:  nobody => gruszczy

Comment:

 I can either change get_field in options to accept pk:

 def get_field(self, name, many_to_many=True):
 """
 Returns the requested field by name. Raises FieldDoesNotExist on
 error.
 """
 if name == 'pk':
 return self.pk
 to_search = many_to_many and (self.fields + self.many_to_many) or
 self.fields
 for f in to_search:
 if f.name == name:
 return f
 raise FieldDoesNotExist('%s has no field named %r' %
 (self.object_name, name))

 or check this inside get_validation_errors in
 django.core.management.validation. I don't know django core that well to
 decide, which way is better, but it seems to me, that get_field should
 return some good value also for 'pk'. If someone could make this decision,
 I will gladly make a patch and write some tests.

-- 
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] #13552: pre_save & post_save model signals should also specify database to save

[Django]

#13552: pre_save & post_save model signals should also specify database to save
---+
  Reporter:  gmandx| Owner:  
andrewgodwin   
Status:  assigned  | Milestone: 

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

Resolution:|  Keywords:  signals 
multi-db pre_save post_save
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  0 |   Needs_tests:  0  

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

  * has_patch:  0 => 1

Comment:

 I've attached a patch that implements a "using" keyword for pre_save,
 post_save, pre_delete, post_delete, and m2m_changed, along with modified
 docs and tests.

-- 
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] #13623: Code in intro-tutorial03 missing a import statement

[Django]

#13623: Code in intro-tutorial03 missing a import statement
--+-
  Reporter:  lescoutinh...@gmail.com  | Owner:  zerok   
Status:  new  | Milestone:  
 Component:  Documentation|   Version:  SVN 
Resolution:   |  Keywords:  tutorial
 Stage:  Accepted | Has_patch:  0   
Needs_docs:  0|   Needs_tests:  0   
Needs_better_patch:  0|  
--+-
Changes (by zerok):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * owner:  nobody => zerok
  * version:  1.1 => SVN
  * keywords:  => tutorial
  * needs_docs:  => 0
  * has_patch:  1 => 0
  * stage:  Unreviewed => Accepted

Comment:

 While in general I'd agree, the snippets usually only contain the imports
 that are necessary for a certain example. In the examples above for views,
 for instance, render_to_response is not imported explicitly since the
 Http404 class is the only relevant import.

 {{{
 urlpatterns = patterns('mysite.polls.views',
 (r'^$', 'index'),
 (r'^(?P\d+)/$', 'detail'),
 (r'^(?P\d+)/results/$', 'results'),
 (r'^(?P\d+)/vote/$', 'vote'),
 )
 }}}

 does not require the import since patterns was already introduced and no
 new function or required import is mentioned.

 {{{
 # ...
 urlpatterns = patterns('',
 (r'^polls/', include('mysite.polls.urls')),
 # ...
 }}}

 on the other hand might benefit from the additional import statement since
 "include" is "new". Surely, it was imported previously but it should be
 re-iterated here where this function is coming from.

 If you meant the second to last snippet on that page, then I agree ;-)

-- 
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] #13624: Hide signatures from the debug pages

[Django]

#13624: Hide signatures from the debug pages
+---
  Reporter:  Kronuz | Owner:  erikr
Status:  assigned   | Milestone:  1.3  
 Component:  Core framework |   Version:  SVN  
Resolution: |  Keywords:   
 Stage:  Ready for checkin  | Has_patch:  1
Needs_docs:  0  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by erikr):

  * needs_docs:  1 => 0
  * stage:  Accepted => Ready for checkin

Comment:

 Documentation patch 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] #13624: Hide signatures from the debug pages

[Django]

#13624: Hide signatures from the debug pages
-+--
  Reporter:  Kronuz  | Owner:  erikr
Status:  assigned| Milestone:  1.3  
 Component:  Core framework  |   Version:  SVN  
Resolution:  |  Keywords:   
 Stage:  Accepted| Has_patch:  1
Needs_docs:  1   |   Needs_tests:  0
Needs_better_patch:  0   |  
-+--
Changes (by erikr):

  * owner:  nobody => erikr
  * 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] #13606: admin raw_id_fields fail to check against non-numerical input

[Django]

#13606: admin raw_id_fields fail to check against non-numerical input
---+
  Reporter:  petrikuitti...@yahoo.com  | Owner:  nobody
Status:  reopened  | Milestone:
 Component:  django.contrib.admin  |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  1 
Needs_better_patch:  0 |  
---+
Changes (by anonymous):

  * status:  closed => reopened
  * has_patch:  0 => 1
  * resolution:  duplicate =>
  * needs_tests:  0 => 1

Comment:

 I know this a duplicate ticket, BUT the previous ticket for was Django
 version 1.1.1.
 Django 1.2+ needs to have patches in two files to get this issue fixed.

 changes to django/forms/models.py from line 984:

 {{{
 def to_python(self, value):
 if value in EMPTY_VALUES:
 return None
 try:
 key = self.to_field_name or 'pk'
 value = self.queryset.get(**{key: value})
 except (ValueError, self.queryset.model.DoesNotExist):
 raise ValidationError(self.error_messages['invalid_choice'])
 return value

 }}}

 And django/contrib/admin/widgets.py



 {{{
 def label_for_value(self, value):
 key = self.rel.get_related_field().name
 try:
 obj = self.rel.to._default_manager.using(self.db).get(**{key:
 value})
 return '%s' %
 escape(truncate_words(obj, 14))
 except (ValueError, self.rel.to.DoesNotExist):
 return ''

 }}}

 Applying both of these patches seems to fix the issue. It would be nice to
 have this fixed in the next Django 1.2.2 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-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] #11675: [patch] Support new memcached wrapper pylibmc

[Django]

#11675: [patch] Support new memcached wrapper pylibmc
--+-
  Reporter:  pipp...@yahoo.co.jp  | Owner:  otherjacob  
  
Status:  assigned | Milestone:  1.3 
  
 Component:  Cache system |   Version:  SVN 
  
Resolution:   |  Keywords:  cache pylibmc 
memcached.py
 Stage:  Accepted | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

  * milestone:  2.0 => 1.3

-- 
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] #11675: [patch] Support new memcached wrapper pylibmc

[Django]

#11675: [patch] Support new memcached wrapper pylibmc
--+-
  Reporter:  pipp...@yahoo.co.jp  | Owner:  otherjacob  
  
Status:  assigned | Milestone:  2.0 
  
 Component:  Cache system |   Version:  SVN 
  
Resolution:   |  Keywords:  cache pylibmc 
memcached.py
 Stage:  Accepted | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

 * cc: dan...@rulez.sk (added)
  * milestone:  1.3 => 2.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.

[Django] #13628: Documentation should discourage the usage of doctests

[Django]

#13628: Documentation should discourage the usage of doctests
---+
 Reporter:  d0ugal |   Owner:  nobody
   Status:  new|   Milestone:  1.3   
Component:  Documentation  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 At the moment the documentation described both doctest and unit tests
 without giving the reader and guidance to one or the other. It is
 generally agree'd that unit tests are a better choice. I have added a
 patch with a small patch that adds a note to reflect this.

 However, I'm not sure if this reflects a bigger problem - should unit
 tests be described first and docetests second so that the reader doesn't
 read through that section only to find out its not recommended? Or should
 the note be added to the top and further emphasised?

-- 
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] #13552: pre_save & post_save model signals should also specify database to save

[Django]

#13552: pre_save & post_save model signals should also specify database to save
---+
  Reporter:  gmandx| Owner:  
andrewgodwin   
Status:  assigned  | Milestone: 

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

Resolution:|  Keywords:  signals 
multi-db pre_save post_save
 Stage:  Accepted  | Has_patch:  0  

Needs_docs:  0 |   Needs_tests:  0  

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

  * owner:  nobody => andrewgodwin
  * 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] #12421: Foreign Key on Non-Primary Field fails due to lack of Index on Related Field w/ MySQL

[Django]

#12421: Foreign Key on Non-Primary Field fails due to lack of Index on Related
Field w/ MySQL
---+
  Reporter:  anonymous | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  worksforme|  Keywords:
 Stage:  Accepted  | Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by erikr):

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

Comment:

 I can not reproduce this with your model with Django trunk, because
 syncdb/sqlall refuse db_index=True unless I also set unique=True on
 License.name.


 {{{
 Error: One or more models did not validate:
 foo.item: Field 'name' under model 'License' must have a unique=True
 constraint.
 }}}


 Having written the model like this:
 {{{
 from django.db import models

 class Item(models.Model):
 license = models.ForeignKey('License', to_field="name", null=True)

 class Meta:
 db_table = 'testo_item'

 class License(models.Model):
 name = models.PositiveIntegerField(db_index=True)

 class Meta:
 db_table = 'testo_license'
 }}}

 The SQL becomes this, which is valid for InnoDB:
 {{{
 BEGIN;
 CREATE TABLE `testo_item` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `license_id` integer UNSIGNED
 )
 ;
 CREATE TABLE `testo_license` (
 `id` integer AUTO_INCREMENT NOT NULL PRIMARY KEY,
 `name` integer UNSIGNED NOT NULL UNIQUE
 )
 ;
 ALTER TABLE `testo_item` ADD CONSTRAINT `license_id_refs_name_a4fa988`
 FOREIGN KEY (`license_id`) REFERENCES `testo_license` (`name`);
 CREATE INDEX `testo_item_139668fe` ON `testo_item` (`license_id`);
 COMMIT;
 }}}

 The code will simply not allow me to set db_index unless I set unique.

 Closing this again as worksforme.

-- 
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] #13627: contributing.txt should mention how to reset your password

[Django]

#13627: contributing.txt should mention how to reset your password
---+
 Reporter:  zerok  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords:  contributing   |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 ... on djangoproject.com. Google is not reliable in this regard :-)

-- 
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] #11223: logout view of authentication broken

[Django]

#11223: logout view of authentication broken
-+--
  Reporter:  ttsmith | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by anonymous):

 I was about to submit the same bug. I think the right way is the one
 documented and proposed in this ticket.This will solve a lot of problems.
 Ticket #12405 is related to the same problem, although with a different
 approach. I think the best is to chose one of the proposed solution and
 solve this problem.

-- 
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] r13307 - django/branches/soc2010

[noreply]

Author: jacob
Date: 2010-05-27 04:38:59 -0500 (Thu, 27 May 2010)
New Revision: 13307

Added:
   django/branches/soc2010/test-refactor/
Log:
Created test-refactor SoC branch.


Copied: django/branches/soc2010/test-refactor (from rev 13306, django/trunk)

-- 
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] r13306 - django/branches/soc2010

[noreply]

Author: jacob
Date: 2010-05-27 04:37:20 -0500 (Thu, 27 May 2010)
New Revision: 13306

Added:
   django/branches/soc2010/app-loading/
Log:
Created SoC app loading branch.


Copied: django/branches/soc2010/app-loading (from rev 13305, django/trunk)

-- 
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] r13305 - django/branches/soc2010

[noreply]

Author: jacob
Date: 2010-05-27 04:35:51 -0500 (Thu, 27 May 2010)
New Revision: 13305

Added:
   django/branches/soc2010/query-refactor/
Log:
Created SoC query-refactor branch.


Copied: django/branches/soc2010/query-refactor (from rev 13304, django/trunk)

-- 
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] #13610: Missing ENGINE setting in settings.py doesn't produce error

[Django]

#13610: Missing ENGINE setting in settings.py doesn't produce error
-+--
  Reporter:  jtiai   | Owner:  gregmuellegger 
Status:  assigned| Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  settings config
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  1  
Needs_better_patch:  0   |  
-+--
Changes (by gregmuellegger):

  * status:  new => assigned
  * needs_better_patch:  => 0
  * needs_tests:  => 1
  * version:  1.2 => SVN
  * owner:  nobody => gregmuellegger
  * needs_docs:  => 0
  * has_patch:  0 => 1

Comment:

 I added a patch but it doesn't contain a test because I'm unsure how to
 test this issue.

 The syncdb command calls the django.db.__init__ module which raises an
 KeyError if no ENGINE is set. But this error is catched in
 django/core/management/__init__.py:258 so I also changed this file and
 moved some code out of the except clause to make spotting issues in
 management commands easier.

-- 
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] r13304 - django/branches

[noreply]

Author: jacob
Date: 2010-05-27 04:33:19 -0500 (Thu, 27 May 2010)
New Revision: 13304

Added:
   django/branches/soc2010/
Log:
Created SoC 2010 branch directory.


-- 
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] #13626: PROFANITIES_LIST should be part of the locale subsystem

[Django]

#13626: PROFANITIES_LIST should be part of the locale subsystem
--+-
  Reporter:  erik | Owner:  nobody
Status:  closed   | Milestone:
 Component:  django.contrib.comments  |   Version:  1.2   
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  0 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by Alex):

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

Comment:

 Profanities list is deprecated, and destined for removal, because it's
 horrifically unmaintained and a really terrible algorithm, as such it's
 not going to be made locale dependent.

-- 
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] #13626: PROFANITIES_LIST should be part of the locale subsystem

[Django]

#13626: PROFANITIES_LIST should be part of the locale subsystem
-+--
 Reporter:  erik |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  django.contrib.comments  | Version:  1.2   
 Keywords:   |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Since profanities are very language- and public-culture-dependent they
 should be part of the locale subsystem.

 If not removed completely (see #8794).

 see source:django/trunk/django/conf/global_settings.py#L441

-- 
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] #13624: Hide signatures from the debug pages

[Django]

#13624: Hide signatures from the debug pages
-+--
  Reporter:  Kronuz  | Owner:  nobody
Status:  new | Milestone:  1.3   
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  1   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by jacob):

  * needs_better_patch:  => 0
  * component:  Uncategorized => Core framework
  * needs_tests:  => 0
  * version:  => SVN
  * milestone:  => 1.3
  * needs_docs:  => 1
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 I think we mention in the docs somewhere which settings are *-ed out
 on those pages; if so, we should update that 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-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] #6735: Class-based generic views

[Django]

#6735: Class-based generic views
+---
  Reporter:  jkocherhans| Owner:  david
Status:  new| Milestone:   
 Component:  Generic views  |   Version:   
Resolution: |  Keywords:   
 Stage:  Accepted   | Has_patch:  1
Needs_docs:  1  |   Needs_tests:  0
Needs_better_patch:  0  |  
+---
Changes (by david):

  * owner:  telenieko => david
  * status:  assigned => new

Comment:

 Stealing that one for the djangocon.eu's sprint.

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