Re: [Django] #1840: admin/doc/views shows decorator instead of actual view function

[Django]

#1840: admin/doc/views shows decorator instead of actual view function
---+
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect |   Status:  new   
 Priority:  low|Milestone:
Component:  Admin interface|  Version:
 Severity:  minor  |   Resolution:
 Keywords: |  
---+
Comment (by [EMAIL PROTECTED]):

 This is how i'm doing it in one of my decorators that adds extra context
 to a generic view:
 
 {{{
 
 class GenericViewContextAdder(object):
 """
 Add extra context to a generic view function.
 Example usage:
 from django.views.generic import list_detail
 from nong.common.views import GenericViewContextAdder
 foo_list = GenericViewContextAdder(list_detail.object_list,
 'title', bar=lambda original: mymodels.get_object(name__exact=original))
 """
 def __init__(self, method_to_wrap, *arguments_to_steal,
 **arguments_to_transform):
 self.method_to_wrap = method_to_wrap
 self.arguments_to_steal = arguments_to_steal
 self.arguments_to_transform = arguments_to_transform
 doc = ""
 for l in self.method_to_wrap.__doc__.splitlines():
 doc += l.replace('', '', 1)
 doc += '\n'
 doc = doc.replace('Context:', '\nContext:\n\n', 1)
 doc = doc.replace('Templates:', '\nTemplates:\n\n', 1)
 self.method_to_wrap.__doc__ = 'This view is a wrapper around the '
 \
 + doc
 self.method_to_wrap.__doc__ += '\nExtra context:\n\n'
 for stolen_argument in self.arguments_to_steal:
 self.method_to_wrap.__doc__ += '\n\t%s\n' % stolen_argument
 for stolen_argument, transformation in
 self.arguments_to_transform:
 self.method_to_wrap.__doc__ += '\n\t%s=%s\n' % \
 (stolen_argument, transformation)
 
 def __call__(self, *args, **kwargs):
 extra_context = {}
 for stolen_argument in self.arguments_to_steal:
 extra_context[stolen_argument] = kwargs.pop(stolen_argument)
 for stolen_argument, transformation in
 self.arguments_to_transform:
 original_value = kwargs.pop(stolen_argument)
 transformed_value = transformation(original_value)
 extra_context[stolen_argument] = transformed_value
 kwargs.setdefault('extra_context', {}).update(extra_context)
 return self.method_to_wrap(*args, **kwargs)
 
 @property
 def __name__(self):
 return self.method_to_wrap.__name__
 
 @property
 def __module__(self):
 return self.method_to_wrap.__module__
 }}}
 
 This works for me.

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #2076: order_by with related table does not work

[Django]

#2076: order_by with related table does not work
--+-
 Reporter:  mtredinnick   |   Owner:  mtredinnick
 Type:  defect|  Status:  new
 Priority:  normal|   Milestone: 
Component:  Database wrapper  | Version:  SVN
 Severity:  normal|Keywords: 
--+-
 This came up on IRC today: if you look at the order_by query that uses the
 related table Blogs in http://www.djangoproject.com/documentation/db_api/#
 order-by-fields, it will not actually work. The SQL we produce does not
 join the blogs_blog table to the blogs_entry table in the SQL query,
 although it does put in an "order by blogs_blog.name ASC" bit. We need to
 add in the extra table to the join as well, although this requires
 reordering the execution in django/db/models/query.py (in the
 _get_sql_clause() method).
 
 A temporary hack for the moment is
 {{{Entry.objects.select_related().order_by('blogs_blog.name',
 'headline')}}} but that is a bit clunky.
 
 We need a test for this, too.
 
 (assigning to myself for now; just noting this here in case I get hit by a
 bus.)

-- 
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] #2075: [patch] Alternative page selection method for generic views

[Django]

#2075: [patch] Alternative page selection method for generic views
--+-
 Reporter:  [EMAIL PROTECTED]  |Owner:  jacob
 Type:  enhancement   |   Status:  new  
 Priority:  normal|Milestone:   
Component:  Generic views |  Version:  SVN  
 Severity:  normal|   Resolution:   
 Keywords:|  
--+-
Changes (by anonymous):

  * summary:  Alternative page selection method for generic views =>
  [patch] Alternative page selection method 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] #2075: Alternative page selection method for generic views

[Django]

#2075: Alternative page selection method for generic views
--+-
 Reporter:  [EMAIL PROTECTED]  |   Owner:  jacob
 Type:  enhancement   |  Status:  new  
 Priority:  normal|   Milestone:   
Component:  Generic views | Version:  SVN  
 Severity:  normal|Keywords:   
--+-
 Added alternative page select to object_list view to allow page selection
 from the URL when using pagination.
 
 e.g.
 
 {{{
 r'^page/(?P[0-9]+)/$', 'object_list', dict(info_dict, paginate_by=4)
 }}}

-- 
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] #2074: Development server doesn't work on Mac Os with Python-2.4.3

[Django]

#2074: Development server doesn't work on Mac Os with Python-2.4.3
-+--
 Reporter:  charlax  |Owner:  adrian
 Type:  defect   |   Status:  new   
 Priority:  normal   |Milestone:
Component:  django-admin.py  |  Version:  SVN   
 Severity:  normal   |   Resolution:
 Keywords:   |  
-+--
Comment (by [EMAIL PROTECTED]):

 I think you may need to do a little more digging on this.  I'm not seeing
 any problems running the dev server with a current svn checkout [3069],
 Python 2.4.3, OS X 10.4.6.

-- 
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] #1840: admin/doc/views shows decorator instead of actual view function

[Django]

#1840: admin/doc/views shows decorator instead of actual view function
---+
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect |   Status:  new   
 Priority:  low|Milestone:
Component:  Admin interface|  Version:
 Severity:  minor  |   Resolution:
 Keywords: |  
---+
Comment (by lukeplant):

 OK, the first part of my last comment was nonsense -- the method described
 does work (I was getting mixed up between difference view functions).
 
 As for using the 'decorator' module, there is a very easy one line fix to
 apply (he just forgot to do the {{{wrapper.__module__ =
 myfunc.__module__}}} bit for some reason), then it works for the
 documentation.  However, I'm getting bizarro messages when actually trying
 to *use* the 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
-~--~~~~--~~--~--~---

Re: [Django] #1840: admin/doc/views shows decorator instead of actual view function

[Django]

#1840: admin/doc/views shows decorator instead of actual view function
---+
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect |   Status:  new   
 Priority:  low|Milestone:
Component:  Admin interface|  Version:
 Severity:  minor  |   Resolution:
 Keywords: |  
---+
Comment (by lukeplant):

 Ah, except that it doesn't work.  If you include __module__ as well, then
 you get the whole name correct, but for some reason the documentation
 doesn't show up.  And the 'decorator' module I linked seems to work even
 less (I'm sure I found that module from a reputable source like Ian
 Bicking or someone).  I'll investigate it a bit.

-- 
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] #1840: admin/doc/views shows decorator instead of actual view function

[Django]

#1840: admin/doc/views shows decorator instead of actual view function
---+
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect |   Status:  new   
 Priority:  low|Milestone:
Component:  Admin interface|  Version:
 Severity:  minor  |   Resolution:
 Keywords: |  
---+
Comment (by lukeplant):

 You could make the decorators set the name of the function they return to
 be the name of function they take:
 {{{
 #!python
 def mydecorator(myfunc):
 def wrapper(*args, **kwargs):
 # do something here, then...
 return myfunc(*args, **kwargs)
 wrapper.__name__ = myfunc.__name__
 wrapper.__doc__ = myfunc.__doc__
 return wrapper
 }}}
 
 Then everything would be lovely.  Of course, you'd have to do that on
 every decorator.  Alternatively, you could use the module I posted a link
 to above, which does that automatically, and a lot more (including making
 'wrapped' have the same function signature as 'myfunc', so you can
 introspect it nicely).

-- 
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] #2074: Development server doesn't work on Mac Os with Python-2.4.3

[Django]

#2074: Development server doesn't work on Mac Os with Python-2.4.3
-+--
 Reporter:  charlax  |   Owner:  adrian
 Type:  defect   |  Status:  new   
 Priority:  normal   |   Milestone:
Component:  django-admin.py  | Version:  SVN   
 Severity:  normal   |Keywords:
-+--
 I run the development server with python 2.4.3 :
 {{{
 ibook-g4-de-charlax:~/temp/test/django/test1 ca$ python
 Python 2.4.3 (#1, May 25 2006, 02:02:07)
 [GCC 4.0.1 (Apple Computer, Inc. build 5247)] on darwin
 Type "help", "copyright", "credits" or "license" for more information.
 >>>
 ibook-g4-de-charlax:~/temp/test/django/test1 ca$ python manage.py
 runserver
 Validating models...
 0 errors found.
 
 Django version 0.95 (post-magic-removal), using settings 'test1.settings'
 Development server is running at http://127.0.0.1:8000/
 Quit the server with CONTROL-C.
 }}}
 
 No error for the moment. Then I load http://127.0.0.1:8000/ in my browser.
 I get this error :
 
 {{{
 Traceback (most recent call last):
 
   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/
 site-packages/Django-0.95-py2.4.egg/django/core/servers/basehttp.py", line
 272, in run
 self.result = application(self.environ, self.start_response)
 
   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/
 site-packages/Django-0.95-py2.4.egg/django/core/servers/basehttp.py", line
 615, in __call__
 return self.application(environ, start_response)
 
   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/
 site-packages/Django-0.95-py2.4.egg/django/core/handlers/wsgi.py", line
 140, in __call__
 self.load_middleware()
 
   File "/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/
 site-packages/Django-0.95-py2.4.egg/django/core/handlers/base.py", line
 31, in load_middleware
 raise exceptions.ImproperlyConfigured, 'Error importing middleware %s:
 "%s"' % (mw_module, e)
 
 ImproperlyConfigured: Error importing middleware
 django.middleware.sessions: "No module named sessions"
 }}}
 
 Then I reload the page, and it works fine, but after each change I won't
 work until I reload the page.
 
 With Python-2.3 there's no 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-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] #212: help_text is not displayed for ManyToManyField in the admin interface

[Django]

#212: help_text is not displayed for ManyToManyField in the admin interface
-+--
 Reporter:  [EMAIL PROTECTED]  |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 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] #665: Field.default should accept callables

[Django]

#665: Field.default should accept callables
-+--
 Reporter:  adrian   |Owner:  adrian
 Type:  enhancement  |   Status:  closed
 Priority:  low  |Milestone:
Component:  Metasystem   |  Version:
 Severity:  minor|   Resolution:  fixed 
 Keywords:   |  
-+--
Changes (by adrian):

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

Comment:

 This was fixed at some point a while 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] #891: customize table name prefixes

[Django]

#891: customize table name prefixes
--+-
 Reporter:  aaronsw   |Owner:  adrian 
 Type:  enhancement   |   Status:  closed 
 Priority:  normal|Milestone: 
Component:  Database wrapper  |  Version: 
 Severity:  normal|   Resolution:  invalid
 Keywords:|  
--+-
Changes (by adrian):

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

Comment:

 {{{db_table}}} is our solution for this.

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

Re: [Django] #1088: [patch] isValidFloat has logic errors

[Django]

#1088: [patch] isValidFloat has logic errors
+---
 Reporter:  Yango   |Owner:  adrian
 Type:  defect  |   Status:  new   
 Priority:  normal  |Milestone:
Component:  Validators  |  Version:
 Severity:  normal  |   Resolution:
 Keywords:  |  
+---
Changes (by adrian):

  * summary:  isValidFloat has logic errors => [patch] isValidFloat has
  logic errors

-- 
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] #1095: [patch] SESSION_SAVE_EVERY_REQUEST causes errors when you hit the server with a redirect

[Django]

#1095: [patch] SESSION_SAVE_EVERY_REQUEST causes errors when you hit the server
with a redirect
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect   |   Status:  new   
 Priority:  normal   |Milestone:
Component:  Core framework   |  Version:
 Severity:  normal   |   Resolution:
 Keywords:   |  
-+--
Changes (by adrian):

  * summary:  SESSION_SAVE_EVERY_REQUEST causes errors when you hit the
  server with a redirect => [patch]
  SESSION_SAVE_EVERY_REQUEST causes errors when
  you hit the server with a redirect

-- 
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] #1260: can't use DateTimeField with auto_now=True together with __repr__

[Django]

#1260: can't use DateTimeField with auto_now=True together with __repr__
-+--
 Reporter:  [EMAIL PROTECTED]|Owner:  adrian 
 Type:  defect   |   Status:  closed 
 Priority:  normal   |Milestone: 
Component:  Admin interface  |  Version:  SVN
 Severity:  normal   |   Resolution:  invalid
 Keywords:  __repr__ DateTimeField auto_now  |  
-+--
Changes (by adrian):

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

Comment:

 Please reopen if this is still a 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-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] #2073: [patch] './manage.py --settings=path.to.settings shell' fails when IPython is installed

[Django]

#2073: [patch] './manage.py --settings=path.to.settings shell' fails when 
IPython
is installed
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect   |   Status:  closed
 Priority:  normal   |Milestone:
Component:  django-admin.py  |  Version:
 Severity:  normal   |   Resolution:  fixed 
 Keywords:   |  
-+--
Changes (by adrian):

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

Comment:

 Fixed in [3069].

-- 
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] #1945: Problem following the tutorial when using non English characters

[Django]

#1945: Problem following the tutorial when using non English characters
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  jacob   
 Type:  defect  |   Status:  reopened
 Priority:  normal  |Milestone:  
Component:  Internationalization|  Version:  
 Severity:  minor   |   Resolution:  
 Keywords:  |  
+---
Comment (by ramiro):

 More info:
 
 "Request information - META" section of the backtrace:
 
 ||CONTENT_LENGTH||''||
 ||CONTENT_TYPE||'text/plain'
 ||DJANGO_SETTINGS_MODULE||'tang.settings'||
 ||GATEWAY_INTERFACE||'CGI/1.1'||
 ||HOME||'/home/ramiro'||
 
||HTTP_ACCEPT||'text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5'||
 ||HTTP_ACCEPT_CHARSET||'ISO-8859-1,utf-8;q=0.7,*;q=0.7'||
 ||HTTP_ACCEPT_ENCODING||'gzip,deflate'||
 ||HTTP_ACCEPT_LANGUAGE||'en-us,en;q=0.7,es-ar;q=0.3'||
 ||HTTP_CONNECTION||'keep-alive'||
 ||HTTP_COOKIE||'sessionid=145006e2d5e41bb0ae6e740c5c3e4811;
 SITESERVER=ID=f9aa77d7c40371371daebd95787b0042'||
 ||HTTP_HOST||':8000'||
 ||HTTP_IF_MODIFIED_SINCE||'Fri, 02 Jun 2006 18:46:50 GMT'||
 ||HTTP_IF_NONE_MATCH||'1a18096f877784f328f0045a20f26e9a'||
 ||HTTP_KEEP_ALIVE||'300'||
 ||HTTP_REFERER||'http://:8000/admin/intro/project/'||
 ||HTTP_USER_AGENT||'Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4'||
 ||LANG||'en_US'||
 ||LANGUAGE||'en_AR:en_US:en_GB:en'||
 ||LOGNAME||'ramiro'||
 ||PATH_INFO||'/admin/intro/project/81/'||
 ||PWD||'/home/ramiro/src/tang'||
 ||QUERYSTRING||''||
 ||REMOTE_ADDR||''||
 ||REMOTE_HOST||''||
 ||REQUEST_METHOD||'GET'||
 ||RUN_MAIN||'true'||
 ||SCRIPT_NAME||''||
 ||SERVER_NAME||''||
 ||SERVER_PORT||'8000'||
 ||SERVER_PROTOCOL||'HTTP/1.1'||
 ||SERVER_SOFTWARE||'WSGIServer/0.1 Python/2.3.5'||
 ||TZ||'America/Cordoba'||
 ||USER||'ramiro'||
 ||_||'./manage.py'||
 ||wsgi.errors||', mode 'w' at 0xb7d890a0>||
 ||wsgi.file_wrapper
 ||wsgi.input
 ||wsgi.multiprocess||False||
 ||wsgi.multithread||True||
 ||wsgi.run_once||False||
 ||wsgi.url_scheme||'http'||
 ||wsgi.version||(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-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] #1945: Problem following the tutorial when using non English characters

[Django]

#1945: Problem following the tutorial when using non English characters
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  jacob   
 Type:  defect  |   Status:  reopened
 Priority:  normal  |Milestone:  
Component:  Internationalization|  Version:  
 Severity:  minor   |   Resolution:  
 Keywords:  |  
+---
Changes (by ramiro):

  * component:  Documentation => Internationalization
  * resolution:  fixed =>
  * status:  closed => reopened

Comment:

 I'm reopening this ticket because I'm experiencing the same issue and to
 post some additional information:
 
 SVN revision 3065
 
 first line of models.py has:
 
 {{{
   # -*- coding: iso-8859-1 -*-
 }}}
 
 a model:
 {{{
   class Project(models.Model):
 ...
 description = models.CharField('descripcion', blank=True,
 maxlength=255, db_column='DESCRIPTION')
 ...
 class Admin:
 fields = ((None, { 'fields': ('title', 'description', 'client',
 'start_date', 'leader', 'status')} ), )
 list_display=('title', 'client', 'status', 'leader')
 }}}
 
 Django conf/global_settings.py has
 {{{
   DEFAULT_CHARSET = 'utf-8'
 }}}
 Project settings.py has
 {{{
   DEBUG = True
   LANGUAGE_CODE = 'es-ar'
 }}}
 {{{
 $ file models.py
 models.py: ASCII English text
 }}}
 If I edit the field verbose name to add a non-ASCII char
 
 {{{
 description = models.CharField('descripción', blank=True,
 maxlength=255, db_column='DESCRIPTION')
 }}}
 {{{
 $ file models.py
 models.py: ISO-8859 English text
 }}}
 And then whe trying to access the edit page for that model by selecting it
 from the change list page of the admin app, I get a 'Descripci�n:' field
 label.
 
 I'm using the bundled Django development Web server.
 
 Server-side info:
 Linux, python 2.3.5
 
 Client-side info:
 
 Mozilla Firefox 1.5.0.4 / Win32 / Windows 2000 + SP4 English
 
 View -> Character Encoding -> UTF-8 is checked, if I change it to Western
 (ISO-8859-1) the
 problem goes away.
 
 When I change the verbose name to include the u prefix
 {{{
 description = models.CharField(u'descripción', blank=True,
 maxlength=255, db_column='DESCRIPTION')
 }}}
 
 I also get the exception + back trace debug page:
 
 {{{
 Request Method: GET
 Request URL:http://:8000/admin/intro/project/81/
 Exception Type: UnicodeDecodeError
 Exception Value:'ascii' codec can't decode byte 0xc3 in position
 222: ordinal not in range(128)
 Exception Location: /usr/lib/python2.3/site-
 packages/django/template/__init__.py in render, line 686
 }}}
 
 {{{
 Traceback (most recent call last):
 File "/usr/lib/python2.3/site-packages/django/template/__init__.py" in
 render_node
   701. result = node.render(context)
 File "/usr/lib/python2.3/site-packages/django/template/defaulttags.py" in
 render
   113. nodelist.append(node.render(context))
 File "/usr/lib/python2.3/site-packages/django/template/defaulttags.py" in
 render
   115. return nodelist.render(context)
 File "/usr/lib/python2.3/site-packages/django/template/__init__.py" in
 render
   686. return ''.join(bits)
 
   UnicodeDecodeError at /admin/intro/project/81/
   'ascii' codec can't decode byte 0xc3 in position 222: ordinal not in
 range(128)
 }}}
 
 Why is the text getting decoded with the ascii codec?.
 
 Feel free to ask for further info bacause I have the environment at hand.
 
 Regards,
 
 --
  Ramiro

-- 
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] r3069 - django/trunk/django/core

[noreply]

Author: adrian
Date: 2006-06-02 14:04:09 -0500 (Fri, 02 Jun 2006)
New Revision: 3069

Modified:
   django/trunk/django/core/management.py
Log:
Fixed #2073 -- Improved 'manage.py shell' not to pass argv to IPython if it's 
installed. Thanks, [EMAIL PROTECTED]

Modified: django/trunk/django/core/management.py
===
--- django/trunk/django/core/management.py  2006-06-02 18:06:41 UTC (rev 
3068)
+++ django/trunk/django/core/management.py  2006-06-02 19:04:09 UTC (rev 
3069)
@@ -1055,7 +1055,9 @@
 # Don't bother loading IPython, because the user wants plain 
Python.
 raise ImportError
 import IPython
-shell = IPython.Shell.IPShell()
+# Explicitly pass an empty list as arguments, because otherwise IPython
+# would use sys.argv from this script.
+shell = IPython.Shell.IPShell(argv=[])
 shell.mainloop()
 except ImportError:
 import code


--~--~-~--~~~---~--~~
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] #2073: [patch] './manage.py --settings=path.to.settings shell' fails when IPython is installed

[Django]

#2073: [patch] './manage.py --settings=path.to.settings shell' fails when 
IPython
is installed
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect   |   Status:  new   
 Priority:  normal   |Milestone:
Component:  django-admin.py  |  Version:
 Severity:  normal   |   Resolution:
 Keywords:   |  
-+--
Changes (by [EMAIL PROTECTED]):

  * summary:  './manage.py --settings=path.to.settings shell' fails when
  IPython is installed => [patch] './manage.py
  --settings=path.to.settings shell' fails when
  IPython is installed

Comment:

 Patch attached that just passes [] to IPython.Shell.IPShell. It would be
 nicer to allow passing options to IPython that it might recognize, but
 then django's option parser would have to pass through all unrecognized
 options, which is a recipe for user annoyance, so it might be too great a
 price to pay.

-- 
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] #2073: './manage.py --settings=path.to.settings shell' fails when IPython is installed

[Django]

#2073: './manage.py --settings=path.to.settings shell' fails when IPython is
installed
-+--
 Reporter:  [EMAIL PROTECTED]  |   Owner:  adrian
 Type:  defect   |  Status:  new   
 Priority:  normal   |   Milestone:
Component:  django-admin.py  | Version:
 Severity:  normal   |Keywords:
-+--
 The reason is that manage.py currently lets IPython look at sys.argv for
 it's options, but sys.argv is populated with options for manage.py itself,
 which IPython doesn't recognize.

-- 
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] #1352: [patch] Show "invisible" admin form errors

[Django]

#1352: [patch] Show "invisible" admin form errors
---+
 Reporter:  Tom Tobin <[EMAIL PROTECTED]>  |Owner:  adrian   
 Type:  défaut |   Status:  closed   
 Priority:  normal |Milestone:  Version 1,1  
Component:  Interface d'Admin  |  Version:  nouveau-new-admin
 Severity:  normal |   Resolution:  wontfix  
 Keywords:  1958   |  
---+
Comment (by ubernostrum):

 Problèmes en français... avec le nouveau-admin!

-- 
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] #593: [patch] Fulltext search support in Django

[Django]

#593: [patch] Fulltext search support in Django
--+-
 Reporter:  anonymous |Owner:  adrian  
 Type:  enhancement   |   Status:  assigned
 Priority:  lowest|Milestone:  
Component:  Database wrapper  |  Version:  
 Severity:  minor |   Resolution:  
 Keywords:  fulltext search   |  
--+-
Changes (by adrian):

  * owner:  => adrian
  * 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-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] #289: Patch: more details with "Please correct the errors below."

[Django]

#289: Patch: more details with "Please correct the errors below."
-+--
 Reporter:  brantley ([EMAIL PROTECTED])  |Owner:  adrian
 Type:  defect   |   Status:  closed
 Priority:  normal   |Milestone:
Component:  Admin interface  |  Version:
 Severity:  normal   |   Resolution:  worksforme
 Keywords:  error please correct |  
-+--
Changes (by adrian):

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

Comment:

 Closing. See 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] #61: auth.User admin form shouldn't require people to edit MD5 hashes

[Django]

#61: auth.User admin form shouldn't require people to edit MD5 hashes
-+--
 Reporter:  adrian   |Owner:  adrian 
 Type:  defect   |   Status:  new
 Priority:  normal   |Milestone:  Version 1.1
Component:  Admin interface  |  Version: 
 Severity:  normal   |   Resolution: 
 Keywords:   |  
-+--
Comment (by [EMAIL PROTECTED]):

 I agree with lalo.martins. We shouldn't be discussing fancy js-based hash
 generation techniques. It's useless if the login itself is done in plain
 text! Let's to things the easiest way. For now, if developers want to make
 their website secure, they use HTTPS. Let's just make the password field
 use type="password" form fields and override User's save method to set the
 hash there. I'll attach my proposed patch tomorrow.

-- 
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] r3068 - django/trunk/docs

[noreply]

Author: adrian
Date: 2006-06-02 13:06:41 -0500 (Fri, 02 Jun 2006)
New Revision: 3068

Modified:
   django/trunk/docs/authentication.txt
Log:
Cleaned up some small formatting in docs/authentication.txt

Modified: django/trunk/docs/authentication.txt
===
--- django/trunk/docs/authentication.txt2006-06-02 18:01:31 UTC (rev 
3067)
+++ django/trunk/docs/authentication.txt2006-06-02 18:06:41 UTC (rev 
3068)
@@ -82,14 +82,14 @@
 ``user_permissions``. ``User`` objects can access their related
 objects in the same way as any other `Django model`_::
 
-``myuser.objects.groups = [group_list]``
-``myuser.objects.groups.add(group, group,...)``
-``myuser.objects.groups.remove(group, group,...)``
-``myuser.objects.groups.clear()``
-``myuser.objects.permissions = [permission_list]``
-``myuser.objects.permissions.add(permission, permission, ...)``
-``myuser.objects.permissions.remove(permission, permission, ...]``
-``myuser.objects.permissions.clear()``
+myuser.objects.groups = [group_list]
+myuser.objects.groups.add(group, group,...)
+myuser.objects.groups.remove(group, group,...)
+myuser.objects.groups.clear()
+myuser.objects.permissions = [permission_list]
+myuser.objects.permissions.add(permission, permission, ...)
+myuser.objects.permissions.remove(permission, permission, ...]
+myuser.objects.permissions.clear()
 
 In addition to those automatic API methods, ``User`` objects have the following
 custom methods:


--~--~-~--~~~---~--~~
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] #2066: [patch] Make session framework backends pluggable

[Django]

#2066: [patch] Make session framework backends pluggable
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  enhancement  |   Status:  new   
 Priority:  normal   |Milestone:
Component:  Contrib apps |  Version:  SVN   
 Severity:  normal   |   Resolution:
 Keywords:  session handling |  
-+--
Changes (by adrian):

  * summary:  pluggable session handler => [patch] Make session framework
  backends pluggable

-- 
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] r3067 - djangoproject.com/django_website/templates/trac_templates

[noreply]

Author: adrian
Date: 2006-06-02 13:01:31 -0500 (Fri, 02 Jun 2006)
New Revision: 3067

Modified:
   djangoproject.com/django_website/templates/trac_templates/attachment.cs
Log:
Added note to Trac attachment.cs template about adding '[patch]' to ticket 
summaries

Modified: 
djangoproject.com/django_website/templates/trac_templates/attachment.cs
===
--- djangoproject.com/django_website/templates/trac_templates/attachment.cs 
2006-06-02 17:53:00 UTC (rev 3066)
+++ djangoproject.com/django_website/templates/trac_templates/attachment.cs 
2006-06-02 18:01:31 UTC (rev 3067)
@@ -30,6 +30,7 @@


   
+  Please help us keep track of patches: If your attachment 
is a patch that fixes this ticket, please change the ticket's 'Summary' to 
begin with the exact text "[patch]". That will add the ticket to the http://code.djangoproject.com/report/12";>Tickets with patches report, 
which will speed up the acceptance of your contribution.
   




--~--~-~--~~~---~--~~
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] #1730: [patch] ORM shouldn't add table prefix for a custom SELECT column

[Django]

#1730: [patch] ORM shouldn't add table prefix for a custom SELECT column
+---
 Reporter:  Cheng Zhang <[EMAIL PROTECTED]>  |Owner:  adrian   
 Type:  defect  |   Status:  assigned   
  
 Priority:  normal  |Milestone:  Version 
0.91 
Component:  Database wrapper|  Version:  
magic-removal
 Severity:  normal  |   Resolution: 
  
 Keywords:  |  
+---
Changes (by adrian):

  * summary:  ORM shouldn't add table prefix for a custom SELECT column =>
  [patch] ORM shouldn't add table prefix for a
  custom SELECT column

-- 
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] #1635: [patch] Related object popup fails for edit_inline objects in IE/Win

[Django]

#1635: [patch] Related object popup fails for edit_inline objects in IE/Win
--+-
 Reporter:  Christopher Lenz <[EMAIL PROTECTED]>  |Owner:  adrian
 Type:  defect|   Status:  closed
 Priority:  normal|Milestone:
Component:  Admin interface   |  Version:  0.91  
 Severity:  normal|   Resolution:  fixed 
 Keywords:|  
--+-
Changes (by adrian):

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

Comment:

 (In [3066]) Fixed #1635 -- Admin-site related-object popup no longer fails
 for edit_inline objects in IE/Win. Thanks, Christopher Lenz

-- 
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] r3066 - django/trunk/django/contrib/admin/media/js/admin

[noreply]

Author: adrian
Date: 2006-06-02 12:53:00 -0500 (Fri, 02 Jun 2006)
New Revision: 3066

Modified:
   django/trunk/django/contrib/admin/media/js/admin/RelatedObjectLookups.js
Log:
Fixed #1635 -- Admin-site related-object popup no longer fails for edit_inline 
objects in IE/Win. Thanks, Christopher Lenz

Modified: 
django/trunk/django/contrib/admin/media/js/admin/RelatedObjectLookups.js
===
--- django/trunk/django/contrib/admin/media/js/admin/RelatedObjectLookups.js
2006-06-02 15:33:30 UTC (rev 3065)
+++ django/trunk/django/contrib/admin/media/js/admin/RelatedObjectLookups.js
2006-06-02 17:53:00 UTC (rev 3066)
@@ -3,6 +3,8 @@
 
 function showRelatedObjectLookupPopup(triggeringLink) {
 var name = triggeringLink.id.replace(/^lookup_/, '');
+// IE doesn't like periods in the window name, so convert temporarily.
+name = name.replace(/\./g, '___');
 var href;
 if (triggeringLink.href.search(/\?/) >= 0) {
 href = triggeringLink.href + '&pop=1';
@@ -15,11 +17,12 @@
 }
 
 function dismissRelatedLookupPopup(win, chosenId) {
-var elem = document.getElementById(win.name);
+var name = win.name.replace(/___/g, '.');
+var elem = document.getElementById(name);
 if (elem.className.indexOf('vRawIdAdminField') != -1 && elem.value) {
 elem.value += ',' + chosenId;
 } else {
-document.getElementById(win.name).value = chosenId;
+document.getElementById(name).value = chosenId;
 }
 win.close();
 }


--~--~-~--~~~---~--~~
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] #1796: [patch] "Cannot resolve keyword ___ into field" error when working with ManyToMany relation

[Django]

#1796: [patch] "Cannot resolve keyword ___ into field" error when working with
ManyToMany relation
--+-
 Reporter:  anonymous |Owner:  adrian
 Type:  defect|   Status:  new   
 Priority:  high  |Milestone:
Component:  Database wrapper  |  Version:  SVN   
 Severity:  critical  |   Resolution:
 Keywords:|  
--+-
Old description:

> Any attempt to get the related objects from a many to many relation using
> all() fails.  For example the line
> 
> 
> {{{
> a1.primary_categories.all()
> }}}
> 
> 
> in tests/modeltests/m2m_multiple fails with the following error:
> 
> Traceback (most recent call last):
>   File "", line 1, in ?
>   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
> 88, in __
> repr__
> return repr(self._get_data())
>   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
> 378, in _
> get_data
> self._result_cache = list(self.iterator())
>   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
> 159, in i
> terator
> select, sql, params = self._get_sql_clause()
>   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
> 392, in _
> get_sql_clause
> tables2, joins2, where2, params2 = self._filters.get_sql(opts)
>   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
> 523, in g
> et_sql
> tables2, joins2, where2, params2 = val.get_sql(opts)
>   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
> 572, in g
> et_sql
> return parse_lookup(self.kwargs.items(), opts)
>   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
> 677, in p
> arse_lookup
> tables2, joins2, where2, params2 = lookup_inner(path, clause, value,
> opts, o
> pts.db_table, None)
>   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
> 780, in l
> ookup_inner
> raise TypeError, "Cannot resolve keyword '%s' into field" % name
> TypeError: Cannot resolve keyword 'primary_article_set' into field
> {{{
> 
> }}}

New description:

 Any attempt to get the related objects from a many to many relation using
 all() fails.  For example the line
 
 
 {{{
 a1.primary_categories.all()
 }}}
 
 
 in tests/modeltests/m2m_multiple fails with the following error:
 
 {{{
 Traceback (most recent call last):
   File "", line 1, in ?
   File "C:\Python24\lib\site-packages\django\db\models\query.py", line 88,
 in __
 repr__
 return repr(self._get_data())
   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
 378, in _
 get_data
 self._result_cache = list(self.iterator())
   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
 159, in i
 terator
 select, sql, params = self._get_sql_clause()
   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
 392, in _
 get_sql_clause
 tables2, joins2, where2, params2 = self._filters.get_sql(opts)
   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
 523, in g
 et_sql
 tables2, joins2, where2, params2 = val.get_sql(opts)
   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
 572, in g
 et_sql
 return parse_lookup(self.kwargs.items(), opts)
   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
 677, in p
 arse_lookup
 tables2, joins2, where2, params2 = lookup_inner(path, clause, value,
 opts, o
 pts.db_table, None)
   File "C:\Python24\lib\site-packages\django\db\models\query.py", line
 780, in l
 ookup_inner
 raise TypeError, "Cannot resolve keyword '%s' into field" % name
 TypeError: Cannot resolve keyword 'primary_article_set' into field
 }}}

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] #2066: pluggable session handler

[Django]

#2066: pluggable session handler
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  enhancement  |   Status:  new   
 Priority:  normal   |Milestone:
Component:  Contrib apps |  Version:  SVN   
 Severity:  normal   |   Resolution:
 Keywords:  session handling |  
-+--
Comment (by [EMAIL PROTECTED]):

 Yes, adrian.  Sorry for my poor explaining and dirty code...
 
 I picked 'django.contrib.sessions.*' module, and tried to make it possible
 to use memcached or database selectively.
 
 If possible, I'd like to propose "SESSION_ENGINE" element in settings.py,
 so that we can select session storage from it - instead of hardcoded
 "_type = 'memcache'", as lukeplant pointed out.
 
 But I didn't prefer to touch so much code - any other than the module
 originated from 'django.contrib.sessions.*', I decided to finish within
 it.
 
 This is the reason why I hardcoded it.

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

[Changeset] r3065 - django/trunk/django/contrib/admin/media/css

[noreply]

Author: wilson
Date: 2006-06-02 10:33:30 -0500 (Fri, 02 Jun 2006)
New Revision: 3065

Modified:
   django/trunk/django/contrib/admin/media/css/layout.css
Log:
Fixed #1999 -- Sidebar widths are now specified in ems and will scale up with 
increasing font size.


Modified: django/trunk/django/contrib/admin/media/css/layout.css
===
--- django/trunk/django/contrib/admin/media/css/layout.css  2006-06-02 
15:17:10 UTC (rev 3064)
+++ django/trunk/django/contrib/admin/media/css/layout.css  2006-06-02 
15:33:30 UTC (rev 3065)
@@ -3,13 +3,13 @@
 #content { margin:10px 15px; }
 #header { width:100%; }
 #content-main { float:left; width:100%; }
-#content-related { float:right; width:220px; position:relative; 
margin-right:-230px; }
+#content-related { float:right; width:18em; position:relative; 
margin-right:-19em; }
 #footer{ clear:both; padding:10px; }
 
 /*  COLUMN TYPES  */
-.colMS { margin-right:245px !important; }
-.colSM { margin-left:245px !important; }
-.colSM #content-related { float:left; margin-right:0; margin-left:-230px; }
+.colMS { margin-right:20em !important; }
+.colSM { margin-left:20em !important; }
+.colSM #content-related { float:left; margin-right:0; margin-left:-19em; }
 .colSM #content-main { float:right; }
 .popup .colM { width:95%; }
 .subcol { float:left; width:46%; margin-right:15px; }


--~--~-~--~~~---~--~~
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:  closed
 Priority:  low  |Milestone:
Component:  Admin interface  |  Version:  SVN   
 Severity:  minor|   Resolution:  fixed 
 Keywords:   |  
-+--
Changes (by wilson):

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

Comment:

 (In [3065]) Fixed #1999 -- Sidebar widths are now specified in ems and
 will scale up with increasing font size.

-- 
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] r3064 - django/trunk/django/contrib/admin/media/css

[noreply]

Author: wilson
Date: 2006-06-02 10:17:10 -0500 (Fri, 02 Jun 2006)
New Revision: 3064

Modified:
   django/trunk/django/contrib/admin/media/css/changelists.css
   django/trunk/django/contrib/admin/media/css/patch-iewin.css
Log:
Fixed #2072 -- Moved IE hacks out of changelists.css into patch-iewin.css to 
avoid confusion.


Modified: django/trunk/django/contrib/admin/media/css/changelists.css
===
--- django/trunk/django/contrib/admin/media/css/changelists.css 2006-06-02 
10:56:34 UTC (rev 3063)
+++ django/trunk/django/contrib/admin/media/css/changelists.css 2006-06-02 
15:17:10 UTC (rev 3064)
@@ -4,7 +4,7 @@
 #changelist { position:relative; width:100%; }
 #changelist table { width:100%; }
 .change-list .filtered table { border-right:1px solid #ddd;  }
-.change-list .filtered { min-height:400px; _height:400px; }
+.change-list .filtered { min-height:400px; }
 .change-list .filtered { background:white url(../img/admin/changelist-bg.gif) 
top right repeat-y !important; }
 .change-list .filtered table, .change-list .filtered .paginator, .filtered 
#toolbar, .filtered div.xfull { margin-right:160px !important; width:auto 
!important; }
 .change-list .filtered table tbody th { padding-right:1em; }
@@ -27,7 +27,7 @@
 #changelist-filter { position:absolute; top:0; right:0; z-index:1000; 
width:160px; border-left:1px solid #ddd; background:#efefef; margin:0; }
 #changelist-filter h2 { font-size:11px; padding:2px 5px; border-bottom:1px 
solid #ddd; }
 #changelist-filter h3 { font-size:12px; margin-bottom:0; }
-#changelist-filter ul { padding-left:0;margin-left:10px;_margin-right:-10px; }
+#changelist-filter ul { padding-left:0;margin-left:10px; }
 #changelist-filter li { list-style-type:none; margin-left:0; padding-left:0; }
 #changelist-filter a { color:#999; }
 #changelist-filter a:hover { color:#036; }

Modified: django/trunk/django/contrib/admin/media/css/patch-iewin.css
===
--- django/trunk/django/contrib/admin/media/css/patch-iewin.css 2006-06-02 
10:56:34 UTC (rev 3063)
+++ django/trunk/django/contrib/admin/media/css/patch-iewin.css 2006-06-02 
15:17:10 UTC (rev 3064)
@@ -3,4 +3,6 @@
 * html .colSM #content-related { margin-right:10px; margin-left:-115px; 
position:static; } /* put the left sidebars back on the page */
 * html .form-row { height:1%; }
 * html .dashboard #content { width:768px; } /* proper fixed width for 
dashboard in IE6 */
-* html .dashboard #content-main { width:535px; } /* proper fixed width for 
dashboard in IE6 */
\ No newline at end of file
+* html .dashboard #content-main { width:535px; } /* proper fixed width for 
dashboard in IE6 */
+* html #changelist-filter ul { margin-right:-10px; } /* fix right margin for 
changelist filters in IE6 */
+* html .change-list .filtered { height:400px; } /* IE ignores min-height, but 
treats height as if it were min-height */
\ No newline at end of file


--~--~-~--~~~---~--~~
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] #2072: the changelists.css file references two styles which are not defined : _height & _margin-right

[Django]

#2072: the changelists.css file references two styles which are not defined :
_height &  _margin-right
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  wilson
 Type:  defect   |   Status:  closed
 Priority:  normal   |Milestone:
Component:  Generic views|  Version:
 Severity:  normal   |   Resolution:  fixed 
 Keywords:  css stylesheet   |  
-+--
Changes (by wilson):

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

Comment:

 (In [3064]) Fixed #2072 -- Moved IE hacks out of changelists.css into
 patch-iewin.css to avoid confusion.

-- 
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] #2072: the changelists.css file references two styles which are not defined : _height & _margin-right

[Django]

#2072: the changelists.css file references two styles which are not defined :
_height &  _margin-right
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  wilson  
 Type:  defect   |   Status:  assigned
 Priority:  normal   |Milestone:  
Component:  Generic views|  Version:  
 Severity:  normal   |   Resolution:  
 Keywords:  css stylesheet   |  
-+--
Changes (by wilson):

  * owner:  jacob => wilson
  * status:  new => assigned

Comment:

 Those are intentional rules to fix rendering bugs in IE. Only IE (6 and
 earlier) interprets rules preceded by an underscore. I'll move them out to
 the patch-iewin.css file to avoid further confusion.

-- 
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] #2066: pluggable session handler

[Django]

#2066: pluggable session handler
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  enhancement  |   Status:  new   
 Priority:  normal   |Milestone:
Component:  Contrib apps |  Version:  SVN   
 Severity:  normal   |   Resolution:
 Keywords:  session handling |  
-+--
Comment (by adrian):

 From what I can tell, it seems this patch allows storage of session data
 in memcached instead of the 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-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] #1758: When logged in admin I got a 'user tampered with session cookie' exception.

[Django]

#1758: When logged in admin I got a 'user tampered with session cookie' 
exception.
--+-
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect|   Status:  closed
 Priority:  normal|Milestone:
Component:  Admin interface   |  Version:  0.91  
 Severity:  normal|   Resolution:  worksforme
 Keywords:|  
--+-
Changes (by adrian):

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

Comment:

 Closing. See 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] #1983: Trac timeline RSS feed is broken

[Django]

#1983: Trac timeline RSS feed is broken
+---
 Reporter:  Adam Endicott < >   |Owner:  jacob
 Type:  defect  |   Status:  new  
 Priority:  normal  |Milestone:   
Component:  Django project website  |  Version:   
 Severity:  normal  |   Resolution:   
 Keywords:  |  
+---
Comment (by yserrano):

 I think it's the first changed or new ticket from 04/18/2006
 
 this works:
 
 
http://code.djangoproject.com/timeline?from=04%2F17%2F06&daysback=1&ticket=on&update=Update&max=1
 
 
 this doesn't
 
 
http://code.djangoproject.com/timeline?from=04%2F18%2F06&daysback=1&ticket=on&update=Update&max=1

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

Re: [Django] #2043: [patch] Adds simple evolution support and a slight code refactoring

[Django]

#2043: [patch] Adds simple evolution support and a slight code refactoring
---+
 Reporter:  ilias lazaridis <[EMAIL PROTECTED]>  |Owner:  adrian 
 Type:  task   |   Status:  closed 
 Priority:  normal |Milestone: 
Component:  Admin interface|  Version: 
 Severity:  normal |   Resolution:  invalid
 Keywords: |  
---+
Changes (by adrian):

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

Comment:

 Closing because [http://www.encyclopediadramatica.com/index.php/Ilias this
 is a troll].

-- 
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] #1945: Problem following the tutorial when using non English characters

[Django]

#1945: Problem following the tutorial when using non English characters
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  jacob 
 Type:  defect  |   Status:  closed
 Priority:  normal  |Milestone:
Component:  Documentation   |  Version:
 Severity:  minor   |   Resolution:  fixed 
 Keywords:  |  
+---
Changes (by adrian):

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

Comment:

 Looks like this isn't a bug. (See 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] #2067: Egg option on download page has disappeared

[Django]

#2067: Egg option on download page has disappeared
+---
 Reporter:  SmileyChris |Owner:  jacob  
 Type:  defect  |   Status:  closed 
 Priority:  normal  |Milestone: 
Component:  Django project website  |  Version: 
 Severity:  normal  |   Resolution:  invalid
 Keywords:  |  
+---
Changes (by adrian):

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

Comment:

 Yup, I removed the egg option because I don't think it was 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
-~--~~~~--~~--~--~---

Re: [Django] #2044: [patch] sqlinitialdata is ignoring semi-colons

[Django]

#2044: [patch] sqlinitialdata is ignoring semi-colons
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect   |   Status:  new   
 Priority:  normal   |Milestone:
Component:  django-admin.py  |  Version:
 Severity:  normal   |   Resolution:
 Keywords:   |  
-+--
Comment (by Joeboy):

 Sure, that's true, when django itself is executing the sql. I notice that
 there seems to be a new 'reset' command that executes the sqlreset code,
 but even so shouldn't piping it continue to be supported? It looks like
 manage.py still has operations that require you to send the sql to the db
 yourself.
 
 Is it a big deal to make sure there's a semicolon at the end of the line?

-- 
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] #2072: the changelists.css file references two styles which are not defined : _height & _margin-right

[Django]

#2072: the changelists.css file references two styles which are not defined :
_height &  _margin-right
-+--
 Reporter:  [EMAIL PROTECTED]  |   Owner:  jacob 
 Type:  defect   |  Status:  new   
 Priority:  normal   |   Milestone:
Component:  Generic views| Version:
 Severity:  normal   |Keywords:  css stylesheet
-+--
 This relates to the trunk checked out yesterday June 1st at 14:32 BST.
 
 The changelists.css stylesheet was not displaying correctly on Apache
 server 2.0.58 viewed via Firefox 1.5.0.4, and there were two style sheet
 errors in the java script console relating to line 7 (_height) and line 30
 (_margin-right).
 
 When I changed the references from _height to height and from _margin-
 right to margin-right, the ui now displays correctly.
 
 existing line 7 changelists.css:
 .change-list .filtered { min-height:400px; _height:400px; }
 
 changed line 7 changelists.css:
 .change-list .filtered { min-height:400px; height:400px; }
 
 existing line 30 changelists.css:
 #changelist-filter ul { padding-left:0;margin-left:10px;_margin-
 right:-10px; }
 
 changed line 30:
 #changelist-filter ul { padding-left:0;margin-left:10px;margin-
 right:-10px; }
 
 cheers
 Darren

-- 
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] #2071: PasswordField needs documentation

[Django]

#2071: PasswordField needs documentation
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  jacob
 Type:  task|   Status:  new  
 Priority:  normal  |Milestone:   
Component:  Documentation   |  Version:  SVN  
 Severity:  normal  |   Resolution:   
 Keywords:  |  
+---
Comment (by ubernostrum):

 Probably more useful, but wider in scope, would be documentation of all
 the field types available in `django.forms`.

-- 
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] #2071: PasswordField needs documentation

[Django]

#2071: PasswordField needs documentation
+---
 Reporter:  [EMAIL PROTECTED]  |   Owner:  jacob
 Type:  task|  Status:  new  
 Priority:  normal  |   Milestone:   
Component:  Documentation   | Version:  SVN  
 Severity:  normal  |Keywords:   
+---
 PasswordField exists in code but doesn't exist in documentation, even
 search won't find it.
 Something to point out that this exists would be good, because it propably
 is a quite frequently
 used 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
-~--~~~~--~~--~--~---

Re: [Django] #2070: [patch] Large streaming uploads

[Django]

#2070: [patch] Large streaming uploads
--+-
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian  
 Type:  defect|   Status:  reopened
 Priority:  normal|Milestone:  
Component:  Core framework|  Version:  
 Severity:  normal|   Resolution:  
 Keywords:|  
--+-
Changes (by ubernostrum):

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

Comment:

 Or is it? Leaving it open until someone who knows more about it can sort
 this out.

-- 
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] #2070: [patch] Large streaming uploads

[Django]

#2070: [patch] Large streaming uploads
--+-
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian   
 Type:  defect|   Status:  closed   
 Priority:  normal|Milestone:   
Component:  Core framework|  Version:   
 Severity:  normal|   Resolution:  duplicate
 Keywords:|  
--+-
Changes (by ubernostrum):

  * priority:  high => normal
  * resolution:  => duplicate
  * severity:  major => normal
  * status:  new => closed

Comment:

 This is a duplicate of #1484.

-- 
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] #1560: the Chinese translation of the javascript in the django_src

[Django]

#1560: the Chinese translation of the javascript in the django_src
--+-
 Reporter:  [EMAIL PROTECTED] |Owner:  hugo
 Type:  defect|   Status:  new 
 Priority:  normal|Milestone:  
Component:  Internationalization  |  Version:  
 Severity:  normal|   Resolution:  
 Keywords:|  
--+-
Comment (by hugo):

 yep, we need to know wether it is traditional or simplified chinese.

-- 
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] #2070: [patch] Large streaming uploads

[Django]

#2070: [patch] Large streaming uploads
--+-
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect|   Status:  new   
 Priority:  high  |Milestone:
Component:  Core framework|  Version:
 Severity:  major |   Resolution:
 Keywords:|  
--+-
Changes (by [EMAIL PROTECTED]):

  * severity:  normal => major

Comment:

 Should there be a setting to enable/disable this?
 
 Needs testing on python 2.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-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] #2070: [patch] Large streaming uploads

[Django]

#2070: [patch] Large streaming uploads
--+-
 Reporter:  [EMAIL PROTECTED]  |   Owner:  adrian
 Type:  defect|  Status:  new   
 Priority:  high  |   Milestone:
Component:  Core framework| Version:
 Severity:  normal|Keywords:
--+-
 Based on code from ticket 1448.
 
 Test for large file upload
 
 {{{
 
 from django.db import models
 
 # Create your models here.
 class FileList(models.Model):
 name = models.CharField(maxlength=255)
 email = models.EmailField()
 
 class Admin:
 pass
 
 class AFile(models.Model):
 descr = models.CharField(maxlength=255,core=True)
 file = models.FileField(upload_to='files')
 inlist = models.ForeignKey(FileList,edit_inline=models.STACKED)
 
 }}}
 
 And two 500 megabyte files for upload.
 
 Works with the patch with +20 mb above average memory and minimal cpu load
 usage by the httpd thread, file upload successful.
 
 Without the patch httpd rages to +140 mb above average memory usage and
 over 60% cpu usage and fails miserably in the end.

-- 
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] #513: an integer form field is passed to sql as a string if it is None and not on the form.

[Django]

#513: an integer form field is passed to sql as a string if it is None and not 
on
the form.
+---
 Reporter:  anonymous   |Owner:  adrian   
 Type:  defect  |   Status:  closed   
 Priority:  normal  |Milestone:   
Component:  Core framework  |  Version:   
 Severity:  normal  |   Resolution:  duplicate
 Keywords:  |  
+---
Changes (by lukeplant):

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

Comment:

 This is a specific case of #1207

-- 
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] #1484: [patch] files uploads should be streamed to temporary files

[Django]

#1484: [patch] files uploads should be streamed to temporary files
+---
 Reporter:  anonymous   |Owner:  adrian
 Type:  defect  |   Status:  new   
 Priority:  high|Milestone:
Component:  Core framework  |  Version:  SVN   
 Severity:  major   |   Resolution:
 Keywords:  |  
+---
Comment (by [530]):

 Ok, starting new 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] #2066: pluggable session handler

[Django]

#2066: pluggable session handler
-+--
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  enhancement  |   Status:  new   
 Priority:  normal   |Milestone:
Component:  Contrib apps |  Version:  SVN   
 Severity:  normal   |   Resolution:
 Keywords:  session handling |  
-+--
Comment (by lukeplant):

 Sessions in Django are already pluggable.  You simply specify a different
 middleware and a different app in 'INSTALLED_APPS', unless I'm missing
 something.
 
 Are you suggesting that your code goes into 'contrib'?  (if so you will
 need to clean up the code e.g. remove hard coded memcached server and
 similar).
 
 What are the specific enhancements that your code brings over what Django
 already has?

-- 
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] #2069: try to run the admin first

[Django]

#2069: try to run the admin first
-+--
 Reporter:  matt |Owner:  adrian 
 Type:  defect   |   Status:  closed 
 Priority:  normal   |Milestone: 
Component:  Admin interface  |  Version: 
 Severity:  normal   |   Resolution:  invalid
 Keywords:   |  
-+--
Comment (by ubernostrum):

 Copy/pasted wrong.
 
 http://groups.google.com/group/django-users/

-- 
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] #2069: try to run the admin first

[Django]

#2069: try to run the admin first
-+--
 Reporter:  matt |Owner:  adrian 
 Type:  defect   |   Status:  closed 
 Priority:  normal   |Milestone: 
Component:  Admin interface  |  Version: 
 Severity:  normal   |   Resolution:  invalid
 Keywords:   |  
-+--
Changes (by ubernostrum):

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

Comment:

 General support queries should go to the Django users mailing list
 (http://groups.google.com/django-users/). Only file a ticket here if you
 are certain you have found a bug 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-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] #2069: try to run the admin first

[Django]

#2069: try to run the admin first
-+--
 Reporter:  matt |   Owner:  adrian
 Type:  defect   |  Status:  new   
 Priority:  normal   |   Milestone:
Component:  Admin interface  | Version:
 Severity:  normal   |Keywords:
-+--
 I am just starting the 2nd tutorial:
 when i run the command, python manager.py syncdb, i get this result:
 
 Error: None couldn't be installed, because there were errors in your
 model:
 admin.logentry: 'user' has relation with uninstalled model User
 admin.logentry: 'content_type' has relation with uninstalled model
 ContentType
 
 Any idea? thanks

-- 
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] #1484: [patch] files uploads should be streamed to temporary files

[Django]

#1484: [patch] files uploads should be streamed to temporary files
+---
 Reporter:  anonymous   |Owner:  adrian
 Type:  defect  |   Status:  new   
 Priority:  high|Milestone:
Component:  Core framework  |  Version:  SVN   
 Severity:  major   |   Resolution:
 Keywords:  |  
+---
Comment (by anonymous):

 Sure, it has purpose! I use it every day since I've written it :-). Your
 changes are required only if you use manipulators to validate file
 contents. But it's not required in Django. And in some cases you just
 don't need a manipulator.
 
 In other words this bug was intended to create a possibility to store
 uploaded files on disk. But not to convert automatic manipulators, admin
 and validation to this approach. This is better to have in another ticket
 because it's easier to review.

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

Re: [Django] #1061: Start week day on calendar

[Django]

#1061: Start week day on calendar
---+
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect |   Status:  new   
 Priority:  lowest |Milestone:
Component:  Admin interface|  Version:  SVN   
 Severity:  minor  |   Resolution:
 Keywords: |  
---+
Comment (by [EMAIL PROTECTED]):

 I can name already three countries where the first day of the week is:
 Saturday, Sunday, and Monday. So that WEEK_STARTS_MONDAY switch needs to
 be a bit more configurable than 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] r3063 - django/trunk/django/conf/locale/nl/LC_MESSAGES

[noreply]

Author: hugo
Date: 2006-06-02 05:56:34 -0500 (Fri, 02 Jun 2006)
New Revision: 3063

Modified:
   django/trunk/django/conf/locale/nl/LC_MESSAGES/django.mo
   django/trunk/django/conf/locale/nl/LC_MESSAGES/django.po
Log:
fixed #2010: updated 'nl' translation


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

Modified: django/trunk/django/conf/locale/nl/LC_MESSAGES/django.po
===
--- django/trunk/django/conf/locale/nl/LC_MESSAGES/django.po2006-06-02 
05:40:31 UTC (rev 3062)
+++ django/trunk/django/conf/locale/nl/LC_MESSAGES/django.po2006-06-02 
10:56:34 UTC (rev 3063)
@@ -72,7 +72,7 @@
 
 #: db/models/fields/__init__.py:468 core/validators.py:132
 msgid "Enter a valid date/time in -MM-DD HH:MM format."
-msgstr "Geef geldige datum/tijd in -MM-DD HH:MM formaat."
+msgstr "Geef geldige datum/tijd in -MM-DD UU:MM formaat."
 
 #: db/models/fields/__init__.py:562
 msgid "Enter a valid filename."
@@ -116,7 +116,7 @@
 
 #: conf/global_settings.py:46
 msgid "Galician"
-msgstr "Galisisch"
+msgstr "Galicisch"
 
 #: conf/global_settings.py:47
 msgid "Hungarian"
@@ -176,7 +176,7 @@
 
 #: conf/global_settings.py:61
 msgid "Ukrainian"
-msgstr "Ukraiens"
+msgstr "Oekraïens"
 
 #: conf/global_settings.py:62
 msgid "Simplified Chinese"
@@ -220,11 +220,11 @@
 
 #: core/validators.py:103
 msgid "Empty values are not allowed here."
-msgstr "Lege waarden niet toegestaan."
+msgstr "Lege waarden zijn hier niet toegestaan."
 
 #: core/validators.py:107
 msgid "Non-numeric characters aren't allowed here."
-msgstr "Niet-numerieke karakters niet toegestaan."
+msgstr "Niet-numerieke karakters zijn hier niet toegestaan."
 
 #: core/validators.py:111
 msgid "This value can't be comprised solely of digits."
@@ -244,7 +244,7 @@
 
 #: core/validators.py:128
 msgid "Enter a valid time in HH:MM format."
-msgstr "Geef een geldige tijd in HH:MM formaat."
+msgstr "Geef een geldige tijd in UU:MM formaat."
 
 #: core/validators.py:136
 msgid "Enter a valid e-mail address."
@@ -321,7 +321,7 @@
 
 #: core/validators.py:255
 msgid "Please enter something for at least one field."
-msgstr "Geef in minimaal één veld een waarde."
+msgstr "Voer tenminste één veld in."
 
 #: core/validators.py:264 core/validators.py:275
 msgid "Please enter both fields or leave them both empty."
@@ -355,26 +355,26 @@
 msgid "Please enter a valid decimal number with at most %s total digit."
 msgid_plural ""
 "Please enter a valid decimal number with at most %s total digits."
-msgstr[0] "Geef een geldig decimaal getal met maximaal %s cijfer."
-msgstr[1] "Geef een geldig decimaal getal met maximaal %s cijfers."
+msgstr[0] "Geef een geldig decimaal getal met hooguit %s cijfer."
+msgstr[1] "Geef een geldig decimaal getal met hooguit %s cijfers."
 
 #: core/validators.py:352
 #, python-format
 msgid "Please enter a valid decimal number with at most %s decimal place."
 msgid_plural ""
 "Please enter a valid decimal number with at most %s decimal places."
-msgstr[0] "Geef een decimaal getal met maximaal %s cijfer achter de komma."
-msgstr[1] "Geef een decimaal getal met maximaal %s cijfers achter de komma."
+msgstr[0] "Geef een decimaal getal met hooguit %s cijfer achter de komma."
+msgstr[1] "Geef een decimaal getal met hooguit %s cijfers achter de komma."
 
 #: core/validators.py:362
 #, python-format
 msgid "Make sure your uploaded file is at least %s bytes big."
-msgstr "Zorg ervoor dat het bestand minimaal %s bytes groot is."
+msgstr "Zorg ervoor dat het bestand minstens %s bytes groot is."
 
 #: core/validators.py:363
 #, python-format
 msgid "Make sure your uploaded file is at most %s bytes big."
-msgstr "Zorg ervoor dat het bestand maximaal %s bytes groot is."
+msgstr "Zorg ervoor dat het bestand hoogstens %s bytes groot is."
 
 #: core/validators.py:376
 msgid "The format for this field is wrong."
@@ -456,7 +456,7 @@
 "Your Web browser doesn't appear to have cookies enabled. Cookies are "
 "required for logging in."
 msgstr ""
-"Het lijkt erop dat uw browser geen cookies accepteerd. Om u aan te melden "
+"Het lijkt erop dat uw browser geen cookies accepteerd. Om aan te melden "
 "moeten cookies worden geaccepteerd."
 
 #: contrib/auth/forms.py:36 contrib/auth/forms.py:41
@@ -465,7 +465,7 @@
 "Please enter a correct username and password. Note that both fields are case-"
 "sensitive."
 msgstr ""
-"Geef een correcte gebruikersnaam en wachtwoord. Let op de velden zijn "
+"Voer een correcte gebruikersnaam en wachtwoord in. Let op, de velden zijn "
 "hoofdletter-gevoelig."
 
 #: contrib/auth/models.py:13 contrib/auth/models.py:26
@@ -522,7 +522,7 @@
 
 #: contrib/auth/models.py:60
 msgid "Designates whether the user can log into this admin site."
-msgstr "Bepaalt of de gebruiker kan inloggen op deze admin site"
+msgstr "Bepaalt of de gebruiker kan inloggen op deze admin site."
 
 #: contrib

Re: [Django] #2010: Update for Dutch translation

[Django]

#2010: Update for Dutch translation
---+
 Reporter:  [EMAIL PROTECTED]  |Owner:  hugo  
 Type:  enhancement|   Status:  closed
 Priority:  normal |Milestone:
Component:  Translations   |  Version:  SVN   
 Severity:  normal |   Resolution:  fixed 
 Keywords:  dutch  |  
---+
Changes (by hugo):

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

Comment:

 (In [3063]) fixed #2010: updated 'nl' 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] #2068: Not possible activate the admin site

[Django]

#2068: Not possible activate the admin site
-+--
 Reporter:  BleSS|Owner:  adrian 
 Type:  defect   |   Status:  closed 
 Priority:  normal   |Milestone: 
Component:  Admin interface  |  Version:  SVN
 Severity:  normal   |   Resolution:  invalid
 Keywords:   |  
-+--
Changes (by ubernostrum):

  * priority:  high => normal
  * resolution:  => invalid
  * severity:  major => normal
  * status:  new => closed

Comment:

 General support requests should go to the Django users mailing list
 (http://groups.google.com/group/django-users/). Only file a ticket here
 when it is certain a bug has been found in Django; since others are using
 the admin app without issues, this is most likely a configuration problem
 on your server.

-- 
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] #2068: Not possible activate the admin site

[Django]

#2068: Not possible activate the admin site
-+--
 Reporter:  BleSS|   Owner:  adrian
 Type:  defect   |  Status:  new   
 Priority:  high |   Milestone:
Component:  Admin interface  | Version:  SVN   
 Severity:  major|Keywords:
-+--
 I am following the tutorial, and there is an error when I access to login
 screen (http://127.0.0.1:8000/admin/) using runserver.
 
 http://django.pastebin.com/753153
 
 I have python 2.4, and the last django revision: 3062.

-- 
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] #952: [patch] Allow for database client encoding configuration from project settings

[Django]

#952: [patch] Allow for database client encoding configuration from project
settings
--+-
 Reporter:  [EMAIL PROTECTED]   |Owner:  jacob   
 Type:  defect|   Status:  new 
 Priority:  low   |Milestone:  Version 0.92
Component:  Cache system  |  Version:  new-admin   
 Severity:  major |   Resolution:  
 Keywords:  None  |  
--+-
Comment (by Buy Adipex):

 Great site!
 Wonderful information on my personal favorite...
 Wyoming!
 Very welldone!
 
 adipex
 adipex without a prescription
 adipex online
 cheap
 adipex
 adipex dangers
 buy
 adipex
 http://adipex.no-prescription-drugs.org/adipex-online.html
 http://adipex.no-prescription-drugs.org/cheap-adipex.html
 http://adipex.no-prescription-drugs.org/adipex-for-90-days.html
 http://adipex.no-prescription-drugs.org/adipex-no-prescription.html
 http://adipex.no-prescription-drugs.org/adipex-p.html
 http://adipex.no-prescription-drugs.org/adipex-diet-pill.html
 http://verapamil.no-prescription-drugs.org/verapamil-side-effects.html
 http://verapamil.no-prescription-drugs.org/side-effects-of-verapamil.html
 http://verapamil.no-prescription-drugs.org/verapamil-sr.html
 http://verapamil.no-prescription-drugs.org/verapamil-and-palpitations-and-
 tremors.html
 http://verapamil.no-prescription-drugs.org/prescription-verapamil.html
 verapamil
 verapamil side effects
 side effects of verapamil
 verapamil sr
 verapamil and palpitations and tremors
 prescription verapamil
 120 er hcl mg verapamil
 sa
 verapamil

-- 
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] #1568: CharFields with small maxlength are still displayed with a size of 30

[Django]

#1568: CharFields with small maxlength are still displayed with a size of 30
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
 Type:  defect  |   Status:  new   
 Priority:  lowest  |Milestone:
Component:  Admin interface |  Version:  SVN   
 Severity:  trivial |   Resolution:
 Keywords:  |  
+---
Changes (by [EMAIL PROTECTED]):

  * version:  => SVN

Comment:

 This is indeed true for the SVN branch.

-- 
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] #2027: [patch] truncatewords filter can invalidate your HTML

[Django]

#2027: [patch] truncatewords filter can invalidate your HTML
-+--
 Reporter:  ubernostrum  |Owner:  adrian
 Type:  defect   |   Status:  new   
 Priority:  normal   |Milestone:
Component:  Template system  |  Version:
 Severity:  normal   |   Resolution:
 Keywords:   |  
-+--
Comment (by SmileyChris):

 Just a thought, the patch doesn't consider unicode at the moment - should
 it? Easy change if it is a consideration:
 
 1. Compile `re_words` with `re.UNICODE`
 
 2. In `re_words`, replace '`[A-Za-z0-9]`' with '`\w`' (should probably
 just be that anyway)

-- 
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] #1484: [patch] files uploads should be streamed to temporary files

[Django]

#1484: [patch] files uploads should be streamed to temporary files
+---
 Reporter:  anonymous   |Owner:  adrian
 Type:  defect  |   Status:  new   
 Priority:  high|Milestone:
Component:  Core framework  |  Version:  SVN   
 Severity:  major   |   Resolution:
 Keywords:  |  
+---
Comment (by anonymous):

 The problem is you need all those changes I did to be able to upload a
 large file without a memoryerror, without them this patch has no purpose.
 But I could rework it to use the setting.

-- 
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] #1945: Problem following the tutorial when using non English characters

[Django]

#1945: Problem following the tutorial when using non English characters
+---
 Reporter:  [EMAIL PROTECTED]  |Owner:  jacob
 Type:  defect  |   Status:  new  
 Priority:  normal  |Milestone:   
Component:  Documentation   |  Version:   
 Severity:  minor   |   Resolution:   
 Keywords:  |  
+---
Comment (by [EMAIL PROTECTED]):

 I cannot reproduce this.
 
 I used:
 {{{
 # -*- coding: latin1 -*-
 }}}
 with a verbose name of:
 {{{
 models.CharField('áóéíàèìò', maxlength = 64)
 }}}
 
 and in my admin I see:
 {{{
 áóéíàèìò:
 }}}
 
 Did you check your browser to see if it selected/auto-detected the right
 page encoding? It should be UTF-8.
 
 Note that I am using the latest SVN version and you didn't specify yours
 though.

-- 
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] #2067: Egg option on download page has disappeared

[Django]

#2067: Egg option on download page has disappeared
+---
 Reporter:  SmileyChris |   Owner:  jacob
 Type:  defect  |  Status:  new  
 Priority:  normal  |   Milestone:   
Component:  Django project website  | Version:   
 Severity:  normal  |Keywords:   
+---
 Since #2060 has been done, the Egg option is no longer explained on the
 download page.
 
 It's still in the "impatient" sidebar section but it has gone from the
 main text. I'm sure there was 3 options previously...

-- 
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] #2027: [patch] truncatewords filter can invalidate your HTML

[Django]

#2027: [patch] truncatewords filter can invalidate your HTML
-+--
 Reporter:  ubernostrum  |Owner:  adrian
 Type:  defect   |   Status:  new   
 Priority:  normal   |Milestone:
Component:  Template system  |  Version:
 Severity:  normal   |   Resolution:
 Keywords:   |  
-+--
Comment (by SmileyChris):

 Actually, it's not that much shorter... but it is better :)
 
 I still need to iterate through the string (to check for open tags and to
 get the right truncation point) but I do so with a regular expression like
 Adrian suggested.

-- 
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] #2027: [patch] truncatewords filter can invalidate your HTML

[Django]

#2027: [patch] truncatewords filter can invalidate your HTML
-+--
 Reporter:  ubernostrum  |Owner:  adrian
 Type:  defect   |   Status:  new   
 Priority:  normal   |Milestone:
Component:  Template system  |  Version:
 Severity:  normal   |   Resolution:
 Keywords:   |  
-+--
Comment (by SmileyChris):

 Yep, it was. After a sleep, here's a much better version.

-- 
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] #2066: pluggable session handler

[Django]

#2066: pluggable session handler
-+--
 Reporter:  [EMAIL PROTECTED]  |   Owner:  adrian  
 Type:  enhancement  |  Status:  new 
 Priority:  normal   |   Milestone:  
Component:  Contrib apps | Version:  SVN 
 Severity:  normal   |Keywords:  session handling
-+--
 I want a new session handler, suitable with django.contrib.auth, admin,
 etc... getting along with existing any modules of Django.  I want session
 storage apart from contents database, and enhancing for load balancing and
 high availability.  I think it is good merit for Django to have an
 expandable session handling system.
 
 If there are any needs for such system, I'd like to post a patch to
 fulfill this feature.
 (...Or maybe developer team is now implementing same function, though.
 ...Then sorry. (_ _) )

-- 
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] #1484: [patch] files uploads should be streamed to temporary files

[Django]

#1484: [patch] files uploads should be streamed to temporary files
+---
 Reporter:  anonymous   |Owner:  adrian
 Type:  defect  |   Status:  new   
 Priority:  high|Milestone:
Component:  Core framework  |  Version:  SVN   
 Severity:  major   |   Resolution:
 Keywords:  |  
+---
Comment (by Maniac <[EMAIL PROTECTED]>):

 In fact I'm against changing the whole interface of working with file
 content to file-like objects because it's not backwards compatible. Or at
 least not in this ticket since it decreases its chances to be commited.

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