[Django] #2017: Standardisation of urlpatterns in django.contrib.comments

[Django]

#2017: Standardisation of urlpatterns in django.contrib.comments
---+
 Reporter:  Simon Greenhill, [EMAIL PROTECTED]  |   Owner:  adrian
 Type:  defect |  Status:  new   
 Priority:  normal |   Milestone:
Component:  Contrib apps   | Version:
 Severity:  normal |Keywords:
---+
 django.contrib.comment's urls are in
 django/contrib/comments/urls/comments.py, ( i.e. so you have to include(
 django.contrib.comments.urls.comments ) ), in contrast stuff like
 django.contrib.admin's is directly in django/contrib/admin/urls.py =>
 include ( django.contrib.urls ).

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

Re: [Django] #1278: Potentially useful get_setting templatetag

[Django]

#1278: Potentially useful get_setting templatetag
-+--
 Reporter:  matt |Owner:  adrian
 Type:  enhancement  |   Status:  new   
 Priority:  normal   |Milestone:
Component:  Template system  |  Version:  SVN   
 Severity:  minor|   Resolution:
 Keywords:   |  
-+--
Changes (by anonymous):

  * priority:  lowest => normal

Comment:

 This would be very useful when developing - getting rid of hardcoded media
 paths being the major example. It's easy to pass .settings to
 views in render and use settings.MEDIA_URL, but you can't do this for
 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-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

[Django] #2016: [patch] Decorator for template tags that load objects

[Django]

#2016: [patch] Decorator for template tags that load objects
---+
 Reporter:  [EMAIL PROTECTED]  |   Owner:  adrian
 Type:  enhancement|  Status:  new   
 Priority:  normal |   Milestone:
Component:  Template system| Version:
 Severity:  normal |Keywords:
---+
 The django.template module includes two convenient decorators for making
 certain common template tags, simple_tag for inserting strings and
 inclusion_tag for including other templates. Another common idiom is
 loading an object into the template. For example:
 
 {{{
 {% get_recent_articles 4 as recent_articles %}
 }}}
 
 This patch includes an object_tag decorator that makes this kind of tag
 easy.
 
 I'm new to Django and don't know how this fits in with the refactoring
 going on now, but I found it quite useful.

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

Re: [Django] #1527: Makefile for HTML documentation

[Django]

#1527: Makefile for HTML documentation
+---
 Reporter:  Andy Dustman <[EMAIL PROTECTED]>  |Owner:  jacob   
 Type:  enhancement |   Status:  new 
 Priority:  low |Milestone:  Version 0.92
Component:  Documentation   |  Version:  SVN 
 Severity:  trivial |   Resolution:  
 Keywords:  |  
+---
Changes (by Andy Dustman <[EMAIL PROTECTED]>):

 * cc: [EMAIL PROTECTED] (added)
  * version:  magic-removal => SVN

Comment:

 Switched to SVN version since magic-removal is no longer relevant.

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

Re: [Django] #1584: [patch] auto_now_add fields set to NULL on update

[Django]

#1584: [patch] auto_now_add fields set to NULL on update
+---
 Reporter:  Andy Dustman <[EMAIL PROTECTED]>  |Owner:  adrian  
 Type:  defect  |   Status:  new 
 Priority:  normal  |Milestone:  Version 0.92
Component:  Database wrapper|  Version:  SVN 
 Severity:  normal  |   Resolution:  
 Keywords:  |  
+---
Changes (by Andy Dustman <[EMAIL PROTECTED]>):

 * cc: [EMAIL PROTECTED] (added)
  * milestone:  => Version 0.92
  * version:  magic-removal => SVN

Comment:

 With the demise/merging of magic-removal, this is still an issue in the
 trunk. Presumably other people who are watching this bug would have spoken
 up if the patch didn't work, and it's simple enough that it's "obviously"
 correct (for sufficiently large values of obvious).

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

Re: [Django] #2014: [patch] Error messages of RequiredIfOtherField* validators are not userfriendly

[Django]

#2014: [patch] Error messages of RequiredIfOtherField* validators are not
userfriendly
--+-
 Reporter:  Steven Armstrong  |Owner:  adrian
 Type:  enhancement   |   Status:  new   
 Priority:  normal|Milestone:
Component:  Validators|  Version:  SVN   
 Severity:  normal|   Resolution:
 Keywords:|  
--+-
Changes (by anonymous):

  * component:  Admin interface => Validators

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

[Django] #2015: [patch] syncdb initial sql data regexp breaks if empty string is inserted

[Django]

#2015: [patch] syncdb initial sql data regexp breaks if empty string is inserted
--+-
 Reporter:  Steven Armstrong  |   Owner:  adrian
 Type:  defect|  Status:  new   
 Priority:  high  |   Milestone:
Component:  Tools | Version:  SVN   
 Severity:  normal|Keywords:
--+-
 The regexp ''sql_expr'' in
 ''management.py:get_sql_initial_data_for_model'' breaks if the inital sql
 data inserts empty strings.
 
 e.g. in the sql below, the inserts for field2 and field3 break.
 {{{
 insert into mytable (field1, field2, field3) values ('bla', '', "");
 }}}
 
 The attached patch fixes 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-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

[Changeset] r2997 - in django/trunk: django/db/models tests/modeltests/or_lookups

[noreply]

Author: lukeplant
Date: 2006-05-26 18:41:43 -0500 (Fri, 26 May 2006)
New Revision: 2997

Modified:
   django/trunk/django/db/models/query.py
   django/trunk/tests/modeltests/or_lookups/models.py
Log:
Fixed bug with QuerySet.exclude() failing to do negations on Q objects, and
at the same time generalised exclude/QNot so that they work for 'external'
Q objects i.e. ones that simply have 'get_sql' defined.


Modified: django/trunk/django/db/models/query.py
===
--- django/trunk/django/db/models/query.py  2006-05-26 21:28:12 UTC (rev 
2996)
+++ django/trunk/django/db/models/query.py  2006-05-26 23:41:43 UTC (rev 
2997)
@@ -291,22 +291,26 @@
 
 def filter(self, *args, **kwargs):
 "Returns a new QuerySet instance with the args ANDed to the existing 
set."
-return self._filter_or_exclude(Q, *args, **kwargs)
+return self._filter_or_exclude(None, *args, **kwargs)
 
 def exclude(self, *args, **kwargs):
 "Returns a new QuerySet instance with NOT (args) ANDed to the existing 
set."
 return self._filter_or_exclude(QNot, *args, **kwargs)
 
-def _filter_or_exclude(self, qtype, *args, **kwargs):
+def _filter_or_exclude(self, mapper, *args, **kwargs):
+# mapper is a callable used to transform Q objects,
+# or None for identity transform
+if mapper is None:
+mapper = lambda x: x
 if len(args) > 0 or len(kwargs) > 0:
 assert self._limit is None and self._offset is None, \
 "Cannot filter a query once a slice has been taken."
 
 clone = self._clone()
 if len(kwargs) > 0:
-clone._filters = clone._filters & qtype(**kwargs)
+clone._filters = clone._filters & mapper(Q(**kwargs))
 if len(args) > 0:
-clone._filters = clone._filters & reduce(operator.and_, args)
+clone._filters = clone._filters & reduce(operator.and_, 
map(mapper, args))
 return clone
 
 def complex_filter(self, filter_obj):
@@ -318,7 +322,7 @@
 if hasattr(filter_obj, 'get_sql'):
 return self._filter_or_exclude(None, filter_obj)
 else:
-return self._filter_or_exclude(Q, **filter_obj)
+return self._filter_or_exclude(None, **filter_obj)
 
 def select_related(self, true_or_false=True):
 "Returns a new QuerySet instance with '_select_related' modified."
@@ -582,9 +586,12 @@
 
 class QNot(Q):
 "Encapsulates NOT (...) queries as objects"
+def __init__(self, q):
+"Creates a negation of the q object passed in."
+self.q = q
 
 def get_sql(self, opts):
-tables, joins, where, params = super(QNot, self).get_sql(opts)
+tables, joins, where, params = self.q.get_sql(opts)
 where2 = ['(NOT (%s))' % " AND ".join(where)]
 return tables, joins, where2, params
 

Modified: django/trunk/tests/modeltests/or_lookups/models.py
===
--- django/trunk/tests/modeltests/or_lookups/models.py  2006-05-26 21:28:12 UTC 
(rev 2996)
+++ django/trunk/tests/modeltests/or_lookups/models.py  2006-05-26 23:41:43 UTC 
(rev 2997)
@@ -89,6 +89,10 @@
 >>> Article.objects.filter(Q(headline__startswith='Hello')).in_bulk([1,2])
 {1: Hello}
 
+# Demonstrating exclude with a Q object
+>>> Article.objects.exclude(Q(headline__startswith='Hello'))
+[Goodbye]
+
 # The 'complex_filter' method supports framework features such as 
 # 'limit_choices_to' which normally take a single dictionary of lookup 
arguments
 # but need to support arbitrary queries via Q objects too.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

Re: [Django] #1919: filter truncatewords wipes newlines from string, so not chainable with markup filters

[Django]

#1919: filter truncatewords wipes newlines from string, so not chainable with
markup filters
-+--
 Reporter:  derelm   |Owner:  adrian 
 Type:  enhancement  |   Status:  new
 Priority:  low  |Milestone:  Version 1.0
Component:  Template system  |  Version:  SVN
 Severity:  minor|   Resolution: 
 Keywords:   |  
-+--
Comment (by Tom Tobin <[EMAIL PROTECTED]>):

 I've attached a patch that will cause the `truncatewords` filter to
 preserve all whitespace (including leading and trailing whitespace).

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

Re: [Django] #2014: [patch] Error messages of RequiredIfOtherField* validators are not userfriendly

[Django]

#2014: [patch] Error messages of RequiredIfOtherField* validators are not
userfriendly
--+-
 Reporter:  Steven Armstrong  |Owner:  adrian
 Type:  enhancement   |   Status:  new   
 Priority:  normal|Milestone:
Component:  Admin interface   |  Version:  SVN   
 Severity:  normal|   Resolution:
 Keywords:|  
--+-
Changes (by anonymous):

  * type:  defect => enhancement

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

[Django] #2014: [patch] Error messages of RequiredIfOtherField* validators are not userfriendly

[Django]

#2014: [patch] Error messages of RequiredIfOtherField* validators are not
userfriendly
--+-
 Reporter:  Steven Armstrong  |   Owner:  adrian
 Type:  defect|  Status:  new   
 Priority:  normal|   Milestone:
Component:  Admin interface   | Version:  SVN   
 Severity:  normal|Keywords:
--+-
 When working with RequiredIfOtherFieldEquals and
 RequiredIfOtherFieldDoesNotEqual validators the error messages can be
 quite user unfriendly.
 
 Assuming you have a select-box named 'action' where the currently selected
 option has a value of 2 and a label of 'Forward Message to' you get error
 messages like:[[BR]]
 ''This field must be given if action is 2''
 
 That sort of let's the user sit there feeling dumb. 2, where does that 2
 come from and what does it mean ???
 
 With the attached patch applied you can have error messages like:[[BR]]
 ''This field must be given if action is Forward Message to''
 
 The label is passed as a third, optional, argument to the validators
 constructor.
 
 e.g.:[[BR]]
 RequiredIfOtherFieldEquals('action', 2)
 
 becomes:[[BR]]
 RequiredIfOtherFieldEquals('action', 2, 'Forward Message to')
 
 This is a backwards compatible change.

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

[Django] #2013: management.py: initial SQL data doesn't recognize empty strings properly

[Django]

#2013: management.py: initial SQL data doesn't recognize empty strings properly
---+
 Reporter:  [EMAIL PROTECTED]  |   Owner:  adrian
 Type:  defect |  Status:  new   
 Priority:  normal |   Milestone:
Component:  Core framework | Version:  SVN   
 Severity:  major  |Keywords:
---+
 The regular expressions for get_sql_initial_data_for_model() don't detect
 empty strings properly.
 
 For e.g.
 
 {{{
 INSERT INTO myapp_person (first_name, last_name) VALUES ('', 'Lennon');
 }}}
 would cause the following when manage.py sqlreset myapp is run:
 {{{
 INSERT INTO myapp_person (first_name, last_name) VALUES (
 ', 'Lennon');
 }}}
 
 Here's the patch to fix the problem:
 
 {{{
 Index: management.py
 ===
 --- management.py   (revision 2995)
 +++ management.py   (working copy)
 @@ -334,8 +334,8 @@
 
  r"""(   # each statement is...
  (?: # one or more chunks of ...
  (?:[^;'"]+) # not the end of a statement or start of a quote
 -  | (?:'[^']+') # something in single quotes
 -  | (?:"[^"]+") # something in double quotes
 +  | (?:'[^']*') # something in single quotes
 +  | (?:"[^"]*") # something in double quotes
  )+)""", re.VERBOSE)
 
  # Find custom SQL, if it's available.
 }}}

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

Re: [Django] #2008: Negative offset in DB query set array-slicing fails silently

[Django]

#2008: Negative offset in DB query set array-slicing fails silently
--+-
 Reporter:  [EMAIL PROTECTED]|Owner:  adrian
 Type:  defect|   Status:  closed
 Priority:  normal|Milestone:
Component:  Database wrapper  |  Version:  SVN   
 Severity:  normal|   Resolution:  fixed 
 Keywords:|  
--+-
Changes (by adrian):

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

Comment:

 Fixed in [2992].

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

Re: [Django] #1543: [patch] syncdb bug with importing initial sql data

[Django]

#1543: [patch] syncdb bug with importing initial sql data
--+-
 Reporter:  Nebojsa Djordjevic   |
Owner:  adrian   
 Type:  defect|   
Status:  closed   
 Priority:  normal|
Milestone:   
Component:  Tools |  
Version:  magic-removal
 Severity:  normal|   
Resolution:  fixed
 Keywords:|  
--+-
Changes (by adrian):

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

Comment:

 Fixed in [2985].

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

Re: [Django] #1103: startproject should create a 'cron job' and 'archive' binary for sessions

[Django]

#1103: startproject should create a 'cron job' and 'archive' binary for sessions
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  enhancement  |   Status:  new   
 Priority:  low  |Milestone:
Component:  Core framework   |  Version:
 Severity:  minor|   Resolution:
 Keywords:   |  
-+--
Changes (by adrian):

  * priority:  normal => low
  * severity:  normal => minor

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

[Changeset] r2995 - django/trunk/django/db/models

[noreply]

Author: adrian
Date: 2006-05-26 14:28:55 -0500 (Fri, 26 May 2006)
New Revision: 2995

Modified:
   django/trunk/django/db/models/loading.py
Log:
Fixed #1732 -- AttributeErrors in models are no longer ignored by the model 
validator.

Modified: django/trunk/django/db/models/loading.py
===
--- django/trunk/django/db/models/loading.py2006-05-26 19:02:23 UTC (rev 
2994)
+++ django/trunk/django/db/models/loading.py2006-05-26 19:28:55 UTC (rev 
2995)
@@ -17,9 +17,15 @@
 _app_list = []
 for app_name in settings.INSTALLED_APPS:
 try:
-_app_list.append(__import__(app_name, '', '', ['models']).models)
-except (ImportError, AttributeError), e:
-pass
+mod = __import__(app_name, '', '', ['models'])
+except ImportError:
+pass # Assume this app doesn't have a models.py in it.
+ # GOTCHA: It may have a models.py that raises ImportError.
+else:
+try:
+_app_list.append(mod.models)
+except AttributeError:
+pass # This app doesn't have a models.py in it.
 return _app_list
 
 def get_app(app_label):


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

Re: [Django] #1732: MR branch #2799, user stupidity in models.py leads to mysteriously missing tables list in admin view

[Django]

#1732: MR branch #2799, user stupidity in models.py leads to mysteriously 
missing
tables list in admin view
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian   
 Type:  enhancement |   Status:  closed   
 Priority:  low |Milestone:   
Component:  Admin interface |  Version:  magic-removal
 Severity:  minor   |   Resolution:  fixed
 Keywords:  |  
+---
Changes (by adrian):

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

Comment:

 (In [2995]) Fixed #1732 -- AttributeErrors in models are no longer ignored
 by the model validator.

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

Re: [Django] #1732: MR branch #2799, user stupidity in models.py leads to mysteriously missing tables list in admin view

[Django]

#1732: MR branch #2799, user stupidity in models.py leads to mysteriously 
missing
tables list in admin view
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian   
 Type:  enhancement |   Status:  new  
 Priority:  low |Milestone:   
Component:  Admin interface |  Version:  magic-removal
 Severity:  minor   |   Resolution:   
 Keywords:  |  
+---
Comment (by adrian):

 This is happening because {{{django.db.models.loading.get_apps}}} silently
 passes on {{{ImportError}}}, so that people can have apps without models
 in them. But the {{{CharacterField}}} is causing an {{{ImportError}}},
 which is getting silently eaten by {{{get_apps()}}}. H...

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

Re: [Django] #1154: SSI from Apache mod_include directive to django fails

[Django]

#1154: SSI from Apache mod_include directive to django fails
---+
 Reporter:  Brian Ray <[EMAIL PROTECTED]>  |Owner:  adrian  
 Type:  defect |   Status:  closed  
 Priority:  normal |Milestone:  Version 0.93
Component:  Core framework |  Version:  SVN 
 Severity:  normal |   Resolution:  wontfix 
 Keywords:  mod_python, SSI|  
---+
Changes (by adrian):

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

Comment:

 I'm inclined to leave this as a wontfix, because it's such an edge case.

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

Re: [Django] #1120: Development server ignores changing the TIME_ZONE information

[Django]

#1120: Development server ignores changing the TIME_ZONE information
-+--
 Reporter:  Marek Kubica |Owner:  adrian
 Type:  defect   |   Status:  closed
 Priority:  low  |Milestone:
Component:  django-admin.py  |  Version:
 Severity:  minor|   Resolution:  worksforme
 Keywords:   |  
-+--
Changes (by adrian):

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

Comment:

 Please reopen with more information, such as your OS, database engine and
 Django version, if this is still an issue.

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

Re: [Django] #1673: Misleading error message if pysqlite2 is not installed

[Django]

#1673: Misleading error message if pysqlite2 is not installed
--+-
 Reporter:  anonymous |Owner:  adrian
 Type:  enhancement   |   Status:  closed
 Priority:  normal|Milestone:
Component:  Database wrapper  |  Version:
 Severity:  minor |   Resolution:  fixed 
 Keywords:|  
--+-
Changes (by adrian):

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

Comment:

 (In [2993]) Fixed #1673 -- Every database backend now raises
 ImproperlyConfigured if the relevant Python database module raises
 ImportError

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

Re: [Django] #87: [patch] Oracle database support

[Django]

#87: [patch] Oracle database support
-+--
 Reporter:  [EMAIL PROTECTED]   |Owner:  adrian 
 Type:  enhancement  |   Status:  closed 
 Priority:  normal   |Milestone:  Version 1.0
Component:  Database wrapper |  Version: 
 Severity:  normal   |   Resolution:  duplicate  
 Keywords:  oracle database db sequence  |  
-+--
Changes (by adrian):

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

Comment:

 #1990 has superceded this ticket.

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

Re: [Django] #667: [patch] extra_lookup_kwargs and extra_context in infodicts should accept callbacks

[Django]

#667: [patch] extra_lookup_kwargs and extra_context in infodicts should accept
callbacks
---+
 Reporter:  hugo   |Owner:  jacob 
 Type:  enhancement|   Status:  closed
 Priority:  normal |Milestone:
Component:  Generic views  |  Version:
 Severity:  normal |   Resolution:  fixed 
 Keywords: |  
---+
Changes (by adrian):

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

Comment:

 Closing for the reason outlined by lukeplant in the previous comment.

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

Re: [Django] #674: ImageField display use undocumented thumbnails for change_list display

[Django]

#674: ImageField display use undocumented thumbnails for change_list display
--+-
 Reporter:  nesh   |Owner:  
adrian
 Type:  defect|   Status:  
closed
 Priority:  normal|Milestone:   
 
Component:  Admin interface   |  Version:   
 
 Severity:  normal|   Resolution:  
fixed 
 Keywords:|  
--+-
Changes (by adrian):

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

Comment:

 This was fixed a few weeks ago.

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

Re: [Django] #779: [patch] Allow callables in extra_lookup_kwargs of generic views

[Django]

#779: [patch] Allow callables in extra_lookup_kwargs of generic views
---+
 Reporter:  Tom Tobin <[EMAIL PROTECTED]>  |Owner:  jacob 
 Type:  enhancement|   Status:  closed
 Priority:  normal |Milestone:
Component:  Generic views  |  Version:
 Severity:  normal |   Resolution:  fixed 
 Keywords: |  
---+
Changes (by adrian):

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

Comment:

 I'm closing this, as generic views no longer take
 {{{extra_lookup_kwargs}}}.

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

Re: [Django] #811: [patch] IPv6 address field support

[Django]

#811: [patch] IPv6 address field support
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian  
 Type:  enhancement |   Status:  reopened
 Priority:  low |Milestone:  
Component:  Core framework  |  Version:  SVN 
 Severity:  minor   |   Resolution:  
 Keywords:  |  
+---
Changes (by adrian):

  * priority:  normal => low
  * severity:  normal => minor

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

Re: [Django] #862: Which field caused method_save to bomb out?

[Django]

#862: Which field caused method_save to bomb out?
+---
 Reporter:  garthk  |Owner:  adrian 
 Type:  defect  |   Status:  closed 
 Priority:  normal  |Milestone: 
Component:  Metasystem  |  Version: 
 Severity:  normal  |   Resolution:  wontfix
 Keywords:  |  
+---
Changes (by adrian):

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

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

[Changeset] r2992 - in django/trunk: django/db/models tests/modeltests/basic

[noreply]

Author: lukeplant
Date: 2006-05-26 13:41:03 -0500 (Fri, 26 May 2006)
New Revision: 2992

Modified:
   django/trunk/django/db/models/query.py
   django/trunk/tests/modeltests/basic/models.py
Log:
Made negative indexing on QuerySet instances raise an assertion error 
(previously
it just returned incorrect results).


Modified: django/trunk/django/db/models/query.py
===
--- django/trunk/django/db/models/query.py  2006-05-26 17:54:19 UTC (rev 
2991)
+++ django/trunk/django/db/models/query.py  2006-05-26 18:41:03 UTC (rev 
2992)
@@ -95,6 +95,9 @@
 
 def __getitem__(self, k):
 "Retrieve an item or slice from the set of results."
+assert (not isinstance(k, slice) and (k >= 0)) \
+or (isinstance(k, slice) and (k.start is None or k.start >= 0) and 
(k.stop is None or k.stop >= 0)), \
+"Negative indexing is not supported."
 if self._result_cache is None:
 if isinstance(k, slice):
 # Offset:

Modified: django/trunk/tests/modeltests/basic/models.py
===
--- django/trunk/tests/modeltests/basic/models.py   2006-05-26 17:54:19 UTC 
(rev 2991)
+++ django/trunk/tests/modeltests/basic/models.py   2006-05-26 18:41:03 UTC 
(rev 2992)
@@ -283,6 +283,16 @@
 ...
 AssertionError: Cannot combine queries once a slice has been taken.
 
+# Negative slices are not supported, due to database constraints.
+# (hint: inverting your ordering might do what you need).
+>>> Article.objects.all()[-1]
+Traceback (most recent call last):
+...
+AssertionError: Negative indexing is not supported.
+>>> Article.objects.all()[0:-5]
+Traceback (most recent call last):
+...
+AssertionError: Negative indexing is not supported.
 
 # An Article instance doesn't have access to the "objects" attribute.
 # That's only available on the class.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

[Changeset] r2991 - django/trunk/django/contrib/admin/views

[noreply]

Author: adrian
Date: 2006-05-26 12:54:19 -0500 (Fri, 26 May 2006)
New Revision: 2991

Modified:
   django/trunk/django/contrib/admin/views/main.py
Log:
Fixed #1403 -- 'Add' green plus sign no longer appears in admin change forms 
for fields whose related models don't have an admin

Modified: django/trunk/django/contrib/admin/views/main.py
===
--- django/trunk/django/contrib/admin/views/main.py 2006-05-26 17:30:40 UTC 
(rev 2990)
+++ django/trunk/django/contrib/admin/views/main.py 2006-05-26 17:54:19 UTC 
(rev 2991)
@@ -118,7 +118,7 @@
 self.raw_id_admin = use_raw_id_admin(field)
 self.is_date_time = isinstance(field, models.DateTimeField)
 self.is_file_field = isinstance(field, models.FileField)
-self.needs_add_label = field.rel and isinstance(field.rel, 
models.ManyToOneRel) or isinstance(field.rel, models.ManyToManyRel) and 
field.rel.to._meta.admin
+self.needs_add_label = field.rel and (isinstance(field.rel, 
models.ManyToOneRel) or isinstance(field.rel, models.ManyToManyRel)) and 
field.rel.to._meta.admin
 self.hidden = isinstance(self.field, models.AutoField)
 self.first = False
 


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

[Changeset] r2990 - django/trunk/django/core/handlers

[noreply]

Author: adrian
Date: 2006-05-26 12:30:40 -0500 (Fri, 26 May 2006)
New Revision: 2990

Modified:
   django/trunk/django/core/handlers/base.py
Log:
Fixed #1023 -- Base handler no longer calls mail_admins() on SystemExit, in 
case of forked processes called from views. Thanks, Hugo

Modified: django/trunk/django/core/handlers/base.py
===
--- django/trunk/django/core/handlers/base.py   2006-05-26 16:30:42 UTC (rev 
2989)
+++ django/trunk/django/core/handlers/base.py   2006-05-26 17:30:40 UTC (rev 
2990)
@@ -95,6 +95,8 @@
 return callback(request, **param_dict)
 except exceptions.PermissionDenied:
 return http.HttpResponseForbidden('Permission denied')
+except SystemExit:
+pass # See http://code.djangoproject.com/ticket/1023
 except: # Handle everything else, including SuspiciousOperation, etc.
 if settings.DEBUG:
 return self.get_technical_error_response(request)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

Re: [Django] #1023: mail_admins called even on SystemExit

[Django]

#1023: mail_admins called even on SystemExit
+---
 Reporter:  hugo|Owner:  adrian
 Type:  defect  |   Status:  closed
 Priority:  normal  |Milestone:
Component:  Core framework  |  Version:
 Severity:  normal  |   Resolution:  fixed 
 Keywords:  |  
+---
Changes (by adrian):

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

Comment:

 (In [2990]) Fixed #1023 -- Base handler no longer calls mail_admins() on
 SystemExit, in case of forked processes called from views. Thanks, Hugo

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

Re: [Django] #1055: Models should have better default __str__() and __repr__() methods

[Django]

#1055: Models should have better default __str__() and __repr__() methods
---+
 Reporter:  GomoX <[EMAIL PROTECTED]>  |Owner:  adrian
 Type:  defect |   Status:  closed
 Priority:  normal |Milestone:
Component:  Database wrapper   |  Version:
 Severity:  normal |   Resolution:  fixed 
 Keywords: |  
---+
Changes (by adrian):

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

Comment:

 This was fixed a while back.

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

Re: [Django] #1236: Django hiding exceptions

[Django]

#1236: Django hiding exceptions
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  russellm
 Type:  defect   |   Status:  closed  
 Priority:  normal   |Milestone:  
Component:  Template system  |  Version:  0.9 
 Severity:  normal   |   Resolution:  fixed   
 Keywords:   |  
-+--
Changes (by adrian):

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

Comment:

 I believe this has been 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-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

Re: [Django] #1266: Default filter URLENCODE enhacement

[Django]

#1266: Default filter URLENCODE enhacement
-+--
 Reporter:  mordaha  |Owner:  adrian 
 Type:  defect   |   Status:  closed 
 Priority:  normal   |Milestone: 
Component:  Template system  |  Version: 
 Severity:  normal   |   Resolution:  wontfix
 Keywords:   |  
-+--
Changes (by adrian):

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

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

Re: [Django] #1415: magic-removal .. user object not working correctly

[Django]

#1415: magic-removal .. user object not working correctly
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian 
 Type:  defect   |   Status:  closed 
 Priority:  normal   |Milestone: 
Component:  Core framework   |  Version: 
 Severity:  normal   |   Resolution:  invalid
 Keywords:   |  
-+--
Changes (by adrian):

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

Comment:

 Looks like that was the problem. (See last comment.)

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

Re: [Django] #1972: OneToOneField and ForeignKey Crashes Admin

[Django]

#1972: OneToOneField and ForeignKey Crashes Admin
+---
 Reporter:  [EMAIL PROTECTED]   |Owner:  adrian
 Type:  defect  |   Status:  new   
 Priority:  highest |Milestone:
Component:  Admin interface |  Version:  SVN   
 Severity:  critical|   Resolution:
 Keywords:  models onetoone foreignkey  |  
+---
Comment (by [EMAIL PROTECTED]):

 From discussion on #django on IRC, it appears that every class needs at
 least one explicit member data field. Unfortunately, the fact that List "
 has-many" Item classes doesn't count.
 
 This should probably throw errors in syncdb etc.

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

[Changeset] r2989 - django/trunk/django/contrib/sites

[noreply]

Author: adrian
Date: 2006-05-26 11:30:42 -0500 (Fri, 26 May 2006)
New Revision: 2989

Modified:
   django/trunk/django/contrib/sites/managers.py
Log:
Fixed #1985 -- Got CurrentSiteManager working

Modified: django/trunk/django/contrib/sites/managers.py
===
--- django/trunk/django/contrib/sites/managers.py   2006-05-26 11:16:58 UTC 
(rev 2988)
+++ django/trunk/django/contrib/sites/managers.py   2006-05-26 16:30:42 UTC 
(rev 2989)
@@ -7,20 +7,14 @@
 def __init__(self, field_name='site'):
 super(CurrentSiteManager, self).__init__()
 self.__field_name = field_name
+self.__is_validated = False
 
-def contribute_to_class(self, *args, **kwargs):
-# This method is overridden purely to check for errors in
-# self.field_name. We can't do this in __init__() because of
-# how Managers are implemented -- self.model isn't available
-# until after contribute_to_class() is called.
-super(CurrentSiteManager, self).contribute_to_class(*args, **kwargs)
-try:
-self.model._meta.get_field(self.__field_name)
-except FieldDoesNotExist:
-raise ValueError, "%s couldn't find a field named %s in %s." % \
-(self.__class__.__name__, self.__field_name, 
self.model._meta.object_name)
-self.__lookup = self.__field_name + '__id__exact'
-del self.__field_name
-
 def get_query_set(self):
-return super(SiteLimitManager, 
self).get_query_set().filter(**{self.__lookup: settings.SITE_ID})
+if not self.__is_validated:
+try:
+self.model._meta.get_field(self.__field_name)
+except FieldDoesNotExist:
+raise ValueError, "%s couldn't find a field named %s in %s." % 
\
+(self.__class__.__name__, self.__field_name, 
self.model._meta.object_name)
+self.__is_validated = True
+return super(CurrentSiteManager, 
self).get_query_set().filter(**{self.__field_name + '__id__exact': 
settings.SITE_ID})


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

Re: [Django] #1985: CurrentSiteManager can't find field

[Django]

#1985: CurrentSiteManager can't find field
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect  |   Status:  closed
 Priority:  normal  |Milestone:
Component:  Core framework  |  Version:
 Severity:  normal  |   Resolution:  fixed 
 Keywords:  |  
+---
Changes (by adrian):

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

Comment:

 (In [2989]) Fixed #1985 -- Got CurrentSiteManager working

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

[Django] #2012: We need a central place to list things that are being developed

[Django]

#2012: We need a central place to list things that are being developed
---+
 Reporter:  ubernostrum|   Owner:  jacob
 Type:  defect |  Status:  new  
 Priority:  normal |   Milestone:   
Component:  Documentation  | Version:   
 Severity:  normal |Keywords:   
---+
 Currently, finding out whether something is being worked on, or is
 currently non-functional, is somewhat difficult; this can involve a lot of
 digging through Trac and hunting for wiki pages (and sometimes the wiki
 pages aren't linked off the index, let alone listed with the "under
 discussion" links). It'd be nice to have some place, possibly a prominent
 link on the wiki, which documents these things.
 
 At the current moment, I'm thinking of something like mentioning clearly
 that model subclassing for post-m-r trunk is still being worked on, and
 pointing out that schema evolution is also being worked on, since those
 seem to be the top two most-often-asked questions right now.

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

Re: [Django] #1985: CurrentSiteManager can't find field

[Django]

#1985: CurrentSiteManager can't find field
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect  |   Status:  new   
 Priority:  normal  |Milestone:
Component:  Core framework  |  Version:
 Severity:  normal  |   Resolution:
 Keywords:  |  
+---
Old description:

> The code (taken from docs) in rev [2970] ..
> 
> from django.db import models
> from django.contrib.sites.models import Site
> from django.contrib.sites.managers import CurrentSiteManager
> 
> class Photo(models.Model):
> photo = models.FileField(upload_to='/home/photos')
> photographer_name = models.CharField(maxlength=100)
> pub_date = models.DateField()
> publish_on = models.ForeignKey(Site)
> objects = models.Manager()
> on_site = CurrentSiteManager('publish_on')
> 
> Does not work, gives following error. Changing publish_on to site also
> does the same. Environment OSX and mysql, svn version [2970]
> 
> raise ValueError, "%s couldn't find a field named %s in %s." % \
> ValueError: CurrentSiteManager couldn't find a field named publish_on in
> Photo

New description:

 The code (taken from docs) in rev [2970] ..
 
 {{{
 from django.db import models
 from django.contrib.sites.models import Site
 from django.contrib.sites.managers import CurrentSiteManager
 
 class Photo(models.Model):
 photo = models.FileField(upload_to='/home/photos')
 photographer_name = models.CharField(maxlength=100)
 pub_date = models.DateField()
 publish_on = models.ForeignKey(Site)
 objects = models.Manager()
 on_site = CurrentSiteManager('publish_on')
 }}}
 
 Does not work, gives following error. Changing publish_on to site also
 does the same. Environment OSX and mysql, svn version [2970]
 
 raise ValueError, "%s couldn't find a field named %s in %s." % \
 ValueError: CurrentSiteManager couldn't find a field named publish_on in
 Photo

Comment (by adrian):

 Fixed formatting in description.

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

Re: [Django] #1999: Layout breaks with large fonts in documentation left sidebar.

[Django]

#1999: Layout breaks with large fonts in documentation left sidebar.
-+--
 Reporter:  anonymous|Owner:  adrian
 Type:  defect   |   Status:  new   
 Priority:  low  |Milestone:
Component:  Admin interface  |  Version:  SVN   
 Severity:  minor|   Resolution:
 Keywords:   |  
-+--
Changes (by adrian):

  * priority:  normal => low

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

Re: [Django] #1995: Comments system: Change "Forgotten your password?" to "Forgot your password?"

[Django]

#1995: Comments system: Change "Forgotten your password?" to "Forgot your
password?"
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian 
 Type:  defect   |   Status:  closed 
 Priority:  lowest   |Milestone: 
Component:  Core framework   |  Version:  SVN
 Severity:  trivial  |   Resolution:  wontfix
 Keywords:   |  
-+--
Changes (by adrian):

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

Comment:

 "Forgotten your password," in which the "Have you" is implied, is fine
 English. If your editor thinks otherwise, you can change the template in
 your particular Django installation.

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

[Django] #2011: update (sk) slovak translation

[Django]

#2011: update (sk) slovak translation
--+-
 Reporter:  [EMAIL PROTECTED],org  |   Owner:  adrian
 Type:  defect|  Status:  new   
 Priority:  normal|   Milestone:
Component:  Admin interface   | Version:
 Severity:  normal|Keywords:
--+-
 update (sk) slovak translation

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

Re: [Django] #200: Add a Decimal type and a Currency type

[Django]

#200: Add a Decimal type and a Currency type
--+-
 Reporter:  Moof <[EMAIL PROTECTED]>  |Owner:  adrian
 Type:  enhancement   |   Status:  new   
 Priority:  normal|Milestone:
Component:  Database wrapper  |  Version:
 Severity:  normal|   Resolution:
 Keywords:|  
--+-
Comment (by anonymous):

 Anyone happen to make any progress on support for a currency field?

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

[Django] #2010: Update for Dutch translation

[Django]

#2010: Update for Dutch translation
---+
 Reporter:  [EMAIL PROTECTED]  |   Owner:  hugo 
 Type:  enhancement|  Status:  new  
 Priority:  normal |   Milestone:   
Component:  Translations   | Version:  SVN  
 Severity:  normal |Keywords:  dutch
---+
 Various sentences had either typos, grammatical issues, were inconsistent
 with the rest of the text or didn't reflect the intended meaning.
 This patch should pull these more in line with more accurate Dutch.

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

Re: [Django] #1996: New Dutch translations

[Django]

#1996: New Dutch translations
--+-
 Reporter:  Rudolph   |Owner:  hugo  
 Type:  enhancement   |   Status:  closed
 Priority:  normal|Milestone:
Component:  Translations  |  Version:  SVN   
 Severity:  normal|   Resolution:  fixed 
 Keywords:|  
--+-
Changes (by hugo):

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

Comment:

 fixed in [2988]

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

[Changeset] r2987 - django/trunk/django/conf/locale/el/LC_MESSAGES

[noreply]

Author: hugo
Date: 2006-05-26 06:14:09 -0500 (Fri, 26 May 2006)
New Revision: 2987

Modified:
   django/trunk/django/conf/locale/el/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/el/LC_MESSAGES/django.po
Log:
fixed broken el_GR translation, thx Jeroen


Modified: django/trunk/django/conf/locale/el/LC_MESSAGES/django.mo
===
(Binary files differ)

Modified: django/trunk/django/conf/locale/el/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/el/LC_MESSAGES/django.po2006-05-26 
05:37:21 UTC (rev 2986)
+++ django/trunk/django/conf/locale/el/LC_MESSAGES/django.po2006-05-26 
11:14:09 UTC (rev 2987)
@@ -18,81 +18,81 @@
 
 #: contrib/comments/models.py:67 contrib/comments/models.py:166
 msgid "object ID"
-msgstr "ID "
+msgstr "ID αντικειμένου"
 
 #: contrib/comments/models.py:68
 msgid "headline"
-msgstr "���"
+msgstr "Επικεφαλίδα"
 
 #: contrib/comments/models.py:69 contrib/comments/models.py:90
 #: contrib/comments/models.py:167
 msgid "comment"
-msgstr "��"
+msgstr "σχόλιο"
 
 #: contrib/comments/models.py:70
 msgid "rating #1"
-msgstr " #1"
+msgstr "κατάταξη #1"
 
 #: contrib/comments/models.py:71
 msgid "rating #2"
-msgstr "�� #2"
+msgstr "βαθμολογία #2"
 
 #: contrib/comments/models.py:72
 msgid "rating #3"
-msgstr "�� #3"
+msgstr "βαθμολογία #3"
 
 #: contrib/comments/models.py:73
 msgid "rating #4"
-msgstr "�� #4"
+msgstr "βαθμολογία #4"
 
 #: contrib/comments/models.py:74
 msgid "rating #5"
-msgstr "�� #5"
+msgstr "βαθμολογία #5"
 
 #: contrib/comments/models.py:75
 msgid "rating #6"
-msgstr "�� #6"
+msgstr "βαθμολογία #6"
 
 #: contrib/comments/models.py:76
 msgid "rating #7"
-msgstr "�� #7"
+msgstr "βαθμολογία #7"
 
 #: contrib/comments/models.py:77
 msgid "rating #8"
-msgstr "�� #8"
+msgstr "βαθμολογία #8"
 
 #: contrib/comments/models.py:82
 msgid "is valid rating"
-msgstr "� �� ��"
+msgstr "είναι έγκυρη βαθμολογία"
 
 #: contrib/comments/models.py:83 contrib/comments/models.py:169
 msgid "date/time submitted"
-msgstr "��/��� "
+msgstr "ημερομηνία/ώρα υποβολής"
 
 #: contrib/comments/models.py:84 contrib/comments/models.py:170
 msgid "is public"
-msgstr "� ���"
+msgstr "είναι δημόσιο"
 
 #: contrib/comments/models.py:85 contrib/admin/views/doc.py:289
 msgid "IP address"
-msgstr "IP �"
+msgstr "IP διεύθυνση"
 
 #: contrib/comments/models.py:86
 msgid "is removed"
-msgstr "� ���"
+msgstr "είναι διεγραμμένο"
 
 #: contrib/comments/models.py:86
 msgid ""
 "Check this box if the comment is inappropriate. A \"This comment has been "
 "removed\" message will be displayed instead."
 msgstr ""
-"�  �� � ��� �� �� � �. ���  �� �� "
-"\" �� �� ��  �."
+"Σημειώστε αυτό το κουτί εάν το σχόλιο είναι ανάρμοστο. Ένα Αυτό το σχόλιο "
+"εσβήσθει\" μήνυμα θα εμφανιστεί αντί αυτού."
 
 #: contrib/comments/models.py:91
 #, fuzzy
 msgid "comments"
-msgstr "��"
+msgstr "σχόλιο"
 
 #: contrib/comments/models.py:131 contrib/comments/models.py:207
 msgid "Content object"
@@ -110,38 +110,38 @@
 
 #: contrib/comments/models.py:168
 msgid "person's name"
-msgstr "� ��"
+msgstr "όνομα ατόμου"
 
 #: contrib/comments/models.py:171
 msgid "ip address"
-msgstr "ip �"
+msgstr "ip διεύθυνση"
 
 #: contrib/comments/models.py:173
 msgid "approved by staff"
-msgstr "��� ��� �� �"
+msgstr "εγκεκριμένο από το προσωπικό"
 
 #: contrib/comments/models.py:176
 #, fuzzy
 msgid "free comment"
-msgstr " ��"
+msgstr "Ελεύθερο σχόλιο"
 
 #: contrib/comments/models.py:177
 #, fuzzy
 msgid "free comments"
-msgstr " ��"
+msgstr "Ελεύθερα σχόλια"
 
 #: contrib/comments/models.py:233
 msgid "score"
-msgstr "��"
+msgstr "βαθμολογία"
 
 #: contrib/comments/models.py:234
 msgid "score date"
-msgstr "�� ���"
+msgstr "ημερομηνία βαθμολογίας"
 
 #: contrib/comments/models.py:237
 #, fuzzy
 msgid "karma score"
-msgstr "��"
+msgstr "βαθμολογία"
 
 #: contrib/comments/models.py:238
 msgid "karma scores"
@@ -159,9 +159,9 @@
 "\n"
 "%(text)s"
 msgstr ""
-" �� �� � ��� %(��)��\n"
+"Αυτο το σχόλιο σημειώθει απο %(χρήστη)ες\n"
 "\n"
-"%(���)�"
+"%(κείμενο)α"
 
 #: contrib/comments/models.py:265
 msgid "flag date"
@@ -182,7 +182,7 @@
 
 #: contrib/comments/models.py:278
 msgid "deletion date"
-msgstr "�� �"
+msgstr "ημερομηνία διαγραφής"
 
 #: contrib/comments/models.py:280
 msgid "moderator deletion"
@@ -199,7 +199,7 @@
 
 #: contrib/comments/views/karma.py:19
 msgid "Anonymous users cannot vote"
-msgstr " ��� ��� ��� �� "
+msgstr "Ανώνυμοι χρήστες δέν μπορούν να ψηφήσουν"
 
 #: contrib/comments/views/karma.py:23
 msgid "Invalid comment ID"
@@ 

Re: [Django] #2009: Feed of comments pr. item using the contrib.comments app

[Django]

#2009: Feed of comments pr. item using the contrib.comments app
+---
 Reporter:  EspenG  |Owner:  adrian
 Type:  enhancement |   Status:  new   
 Priority:  normal  |Milestone:
Component:  Core framework  |  Version:
 Severity:  normal  |   Resolution:
 Keywords:  |  
+---
Comment (by ubernostrum):

 I'm not really certain this is something that's within the scope of
 Django; it's easy enough to build whatever type of feed you want, but
 trying to supply every type of feed someone might want "out of the box" is
 a hopeless task.

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

Re: [Django] #2000: [patch] allow generic views to respond with non text/html content types

[Django]

#2000: [patch] allow generic views to respond with non text/html content types
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  jacob
 Type:  enhancement  |   Status:  new  
 Priority:  normal   |Milestone:   
Component:  Generic views|  Version:   
 Severity:  normal   |   Resolution:   
 Keywords:   |  
-+--
Comment (by EspenG):

 Sorry about that then. I taugth that when the default was 'None' I had to
 pass along a mimetype every time, but as you say that was wrong then.

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

[Django] #2009: Feed of comments pr. item using the contrib.comments app

[Django]

#2009: Feed of comments pr. item using the contrib.comments app
+---
 Reporter:  EspenG  |   Owner:  adrian
 Type:  enhancement |  Status:  new   
 Priority:  normal  |   Milestone:
Component:  Core framework  | Version:
 Severity:  normal  |Keywords:
+---
 I was just working on my blog, and found out that i wanted an rss feed
 with the comments for each blog post. Since I'm using the
 django.conrib.comments application it should not be hard to work out as
 long as the application got the functions :-)

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

Re: [Django] #1987: CharField with treating UTF-8 encoding

[Django]

#1987: CharField with treating UTF-8 encoding
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  enhancement  |   Status:  new   
 Priority:  low  |Milestone:
Component:  Core framework   |  Version:  SVN   
 Severity:  normal   |   Resolution:
 Keywords:   |  
-+--
-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---