Re: [Django] #15667: Implement template-based widget rendering

[Django]

#15667: Implement template-based widget rendering
---+
   Reporter:  brutasse |Owner:  brutasse
   Type:  New feature  |   Status:  new
  Milestone:  1.4  |Component:  Forms
Version:   | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  0
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+
Changes (by dmclain):

 * cc: dmclain (added)


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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  reopened
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+---

Comment (by lawgon):

 apologies - my first time

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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  closed
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:  fixed| Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+---
Changes (by lawgon):

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


Comment:

 attached the patch with tests

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

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

Re: [Django] #15495: makemessages excludes all strings from Javascript after a comment

[Django]

#15495: makemessages excludes all strings from Javascript after a comment
+
   Reporter:  lrekucki  |Owner:  nedbatchelder
   Type:  Bug   |   Status:  assigned
  Milestone:|Component:  Internationalization
Version:  SVN   | Severity:  Normal
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+
Changes (by nedbatchelder):

 * owner:  nobody => nedbatchelder
 * 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14045: makemessage miss some gettext in javascript

[Django]

#14045: makemessage miss some gettext in javascript
+
   Reporter:  shaohao   |Owner:  nedbatchelder
   Type:  Bug   |   Status:  new
  Milestone:|Component:  Internationalization
Version:  1.2   | Severity:  Normal
 Resolution:| Keywords:  xgettext
   Triage Stage:  Accepted  |Has patch:  0
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  0 |
+
Changes (by nedbatchelder):

 * type:  Uncategorized => Bug


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

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

Re: [Django] #14045: makemessage miss some gettext in javascript

[Django]

#14045: makemessage miss some gettext in javascript
-+-
   Reporter:  shaohao|Owner:  nedbatchelder
   Type: |   Status:  new
  Uncategorized  |Component:  Internationalization
  Milestone: | Severity:  Normal
Version:  1.2| Keywords:  xgettext
 Resolution: |Has patch:  0
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by nedbatchelder):

 * owner:  nobody => nedbatchelder
 * status:  reopened => new
 * type:   => Uncategorized
 * severity:   => Normal


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

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

Re: [Django] #7704: JS comments put after statements break make-messages.py output

[Django]

#7704: JS comments put after statements break make-messages.py output
-+-
   Reporter:  robbyd |Owner:  nedbatchelder
   Type:  Bug|   Status:  assigned
  Milestone: |Component:  Core (Management
Version:  1.0|  commands)
 Resolution: | Severity:  Normal
   Triage Stage:  Accepted   | Keywords:  djangojs, make-
Needs documentation:  0  |  messages
Patch needs improvement:  0  |Has patch:  0
 |  Needs tests:  0
-+-
Changes (by nedbatchelder):

 * owner:  nobody => nedbatchelder
 * 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Changeset] r16022 - in django/trunk: django/contrib/auth django/contrib/messages django/contrib/messages/tests docs/internals docs/ref/contrib/admin docs/ref/templates docs/topics

[noreply]

Author: lukeplant
Date: 2011-04-07 15:01:23 -0700 (Thu, 07 Apr 2011)
New Revision: 16022

Modified:
   django/trunk/django/contrib/auth/context_processors.py
   django/trunk/django/contrib/auth/models.py
   django/trunk/django/contrib/messages/api.py
   django/trunk/django/contrib/messages/tests/base.py
   django/trunk/docs/internals/deprecation.txt
   django/trunk/docs/ref/contrib/admin/index.txt
   django/trunk/docs/ref/templates/api.txt
   django/trunk/docs/topics/auth.txt
Log:
Fixed #15757 - removed remaining instances of get_and_delete_messages

Thanks to void for the report, and julien for the bulk of the patch.

Modified: django/trunk/django/contrib/auth/context_processors.py
===
--- django/trunk/django/contrib/auth/context_processors.py  2011-04-06 
11:19:37 UTC (rev 16021)
+++ django/trunk/django/contrib/auth/context_processors.py  2011-04-07 
22:01:23 UTC (rev 16022)
@@ -1,5 +1,4 @@
 from django.utils.functional import lazy, memoize, SimpleLazyObject
-from django.contrib import messages
 
 # PermWrapper and PermLookupDict proxy the permissions system into objects that
 # the template system can understand.
@@ -55,6 +54,5 @@
 
 return {
 'user': SimpleLazyObject(get_user),
-'messages': messages.get_messages(request),
 'perms':  lazy(lambda: PermWrapper(get_user()), PermWrapper)(),
 }

Modified: django/trunk/django/contrib/auth/models.py
===
--- django/trunk/django/contrib/auth/models.py  2011-04-06 11:19:37 UTC (rev 
16021)
+++ django/trunk/django/contrib/auth/models.py  2011-04-07 22:01:23 UTC (rev 
16022)
@@ -445,9 +445,6 @@
 def has_module_perms(self, module):
 return _user_has_module_perms(self, module)
 
-def get_and_delete_messages(self):
-return []
-
 def is_anonymous(self):
 return True
 

Modified: django/trunk/django/contrib/messages/api.py
===
--- django/trunk/django/contrib/messages/api.py 2011-04-06 11:19:37 UTC (rev 
16021)
+++ django/trunk/django/contrib/messages/api.py 2011-04-07 22:01:23 UTC (rev 
16022)
@@ -15,35 +15,26 @@
 
 def add_message(request, level, message, extra_tags='', fail_silently=False):
 """
-Attempts to add a message to the request using the 'messages' app, falling
-back to the user's message_set if MessageMiddleware hasn't been enabled.
+Attempts to add a message to the request using the 'messages' app.
 """
 if hasattr(request, '_messages'):
 return request._messages.add(level, message, extra_tags)
 if not fail_silently:
-raise MessageFailure('Without the django.contrib.messages '
-'middleware, messages can only be added to '
-'authenticated users.')
+raise MessageFailure('You cannot add messages without installing '
+'django.contrib.messages.middleware.MessageMiddleware')
 
 
 def get_messages(request):
 """
 Returns the message storage on the request if it exists, otherwise returns
-user.message_set.all() as the old auth context processor did.
+an empty list.
 """
 if hasattr(request, '_messages'):
 return request._messages
+else:
+return []
 
-def get_user():
-if hasattr(request, 'user'):
-return request.user
-else:
-from django.contrib.auth.models import AnonymousUser
-return AnonymousUser()
 
-return lazy(memoize(get_user().get_and_delete_messages, {}, 0), list)()
-
-
 def get_level(request):
 """
 Returns the minimum level of messages to be recorded.

Modified: django/trunk/django/contrib/messages/tests/base.py
===
--- django/trunk/django/contrib/messages/tests/base.py  2011-04-06 11:19:37 UTC 
(rev 16021)
+++ django/trunk/django/contrib/messages/tests/base.py  2011-04-07 22:01:23 UTC 
(rev 16022)
@@ -10,7 +10,6 @@
 from django.contrib.messages.storage import default_storage, base
 from django.contrib.messages.storage.base import Message
 from django.core.urlresolvers import reverse
-from django.contrib.auth.models import User
 
 
 def skipUnlessAuthIsInstalled(func):
@@ -222,10 +221,10 @@
 for msg in data['messages']:
 self.assertContains(response, msg)
 
-def test_middleware_disabled_anon_user(self):
+def test_middleware_disabled(self):
 """
-Tests that, when the middleware is disabled and a user is not logged
-in, an exception is raised when one attempts to store a message.
+Tests that, when the middleware is disabled, an exception is raised
+when one attempts to store a message.
 """
 settings.MESSAGE_LEVEL = constants.DEBUG
 settings.INSTALLED_APPS = list(settings.INSTALLED_APPS)
@@ -251,10 

Re: [Django] #15696: Add pre_insert signal to loaddata command

[Django]

#15696: Add pre_insert signal to loaddata command
-+-
   Reporter:  jonash |Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  Core (Serialization)
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  nonrel
 Resolution: |Has patch:  0
   Triage Stage: |  Needs tests:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by jonash):

 Any way to get this into trunk soon?

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

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

Re: [Django] #15757: get_and_delete_messages, removed in [15975], is still alive

[Django]

#15757: get_and_delete_messages, removed in [15975], is still alive
-+-
   Reporter:  void   |Owner:  nobody
   Type:  Bug|   Status:  reopened
  Milestone:  1.4|Component:  contrib.auth
Version:  SVN| Severity:  Release blocker
 Resolution: | Keywords:
   Triage Stage:  Ready for  |Has patch:  1
  checkin|  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by lukeplant):

 * stage:  Accepted => Ready for checkin


Comment:

 Thanks Julien.

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

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

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Unreviewed   |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-

Comment (by isagalaev):

 Tom, since you're hacking on it so actively :-) how about adding another
 test somewhere near read_limited_stream that would test reading from a GET
 request that doesn't have a Content-length header? It would test the
 situation with some generic view code always calling request.read()
 irregardless of the request type. The sensible thing to do here is not to
 break and just give it an empty string.

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

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

[Django] #15786: Wrong SQL for OneToOneField with exclude() using F() parameter

[Django]

#15786: Wrong SQL for OneToOneField with exclude() using F() parameter
-+-
 Reporter:  gerdemb  | Owner:  nobody
 Type:  Bug  |Status:  new
Milestone:   | Component:  Database layer (models, ORM)
  Version:  1.3  |  Severity:  Normal
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  0|
-+-
 {{{
 class U(models.Model):
 pass

 class P(models.Model):
 c = models.CharField(max_length=256)
 u = models.OneToOneField(U)

 class L(models.Model):
 u1 = models.ForeignKey(U, related_name='u1')
 u2 = models.ForeignKey(U, related_name='u2')


 # This query works
 q0 = models.L.objects.filter(u1__p=F('u2__p'))
 print q0.query
 list(q0)
 print ""
 # This query generates broken SQL
 q1 = models.L.objects.exclude(u1__p=F('u2__p'))
 print q1.query
 list(q1)
 }}}

 Output:


 {{{
 SELECT "library_l"."id", "library_l"."u1_id", "library_l"."u2_id" FROM
 "library_l" INNER JOIN "library_u" ON ("library_l"."u2_id" =
 "library_u"."id") INNER JOIN "library_p" ON ("library_u"."id" =
 "library_p"."u_id") INNER JOIN "library_u" T4 ON ("library_l"."u1_id" =
 T4."id") INNER JOIN "library_p" T5 ON (T4."id" = T5."u_id") WHERE T5."id"
 =  "library_p"."id"
 
 SELECT "library_l"."id", "library_l"."u1_id", "library_l"."u2_id" FROM
 "library_l" INNER JOIN "library_u" ON ("library_l"."u2_id" =
 "library_u"."id") INNER JOIN "library_p" ON ("library_u"."id" =
 "library_p"."u_id") WHERE NOT (("library_l"."u1_id" IN (SELECT U4."u_id"
 FROM "library_l" U0 INNER JOIN "library_u" U1 ON (U0."u2_id" = U1."id")
 INNER JOIN "library_p" U2 ON (U1."id" = U2."u_id") INNER JOIN "library_p"
 U4 ON (U3."id" = U4."u_id") WHERE U4."id" =  U2."id") AND
 "library_l"."u1_id" IS NOT NULL))
 Traceback (most recent call last):
   File "./manage.py", line 11, in 
 execute_manager(settings)
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/core/management/__init__.py", line
 438, in execute_manager
 utility.execute()
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/core/management/__init__.py", line
 379, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/core/management/base.py", line 191,
 in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/core/management/base.py", line 220,
 in execute
 output = self.handle(*args, **options)
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/core/management/base.py", line 351,
 in handle
 return self.handle_noargs(**options)
   File
 
"/home/gerdemb/Desktop/vagabooks/vagabooks/vagabooks/library/management/commands/foo.py",
 line 17, in handle_noargs
 list(q1)
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/db/models/query.py", line 83, in
 __len__
 self._result_cache.extend(list(self._iter))
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/db/models/query.py", line 269, in
 iterator
 for row in compiler.results_iter():
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/db/models/sql/compiler.py", line
 672, in results_iter
 for rows in self.execute_sql(MULTI):
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/db/models/sql/compiler.py", line
 727, in execute_sql
 cursor.execute(sql, params)
   File "/usr/local/lib/python2.6/dist-
 packages/Django-1.2.3-py2.6.egg/django/db/backends/util.py", line 15, in
 execute
 return self.cursor.execute(sql, params)
   File "/usr/local/lib/python2.6/dist-
 
packages/Django-1.2.3-py2.6.egg/django/db/backends/postgresql_psycopg2/base.py",
 line 44, in execute
 return self.cursor.execute(query, args)
 django.db.utils.DatabaseError: missing FROM-clause entry for table "u3"
 LINE 1: ...1."id" = U2."u_id") INNER JOIN "library_p" U4 ON (U3."id" = ...

 }}}

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

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

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Unreviewed   |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-

Comment (by tomchristie):

 Updated patch (limited_stream_lazy.diff)
 Thanks to Ivan's testing it turns out the defered creation of the
 LimitedStream isn't necessary.
 This should do the job 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
---+-
   Reporter:  tomchristie  |Owner:  tomchristie
   Type:  Bug  |   Status:  new
  Milestone:  1.3  |Component:  HTTP handling
Version:  1.3-rc1  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Unreviewed   |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-
Changes (by isagalaev):

 * cc: Maniac@… (added)
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


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

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

Re: [Django] #12379: Simplified Chinese(CN) localflavor package

[Django]

#12379: Simplified Chinese(CN) localflavor package
-+-
   Reporter:  xiaket |Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  contrib.localflavor
  Milestone: | Severity:  Normal
Version: | Keywords:  CN localflavor
 Resolution: |Has patch:  1
   Triage Stage:  Ready for  |  Needs tests:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by DaNmarner):

 Thanks lrekucki, it must be my script for auto-cleaning ~ and pyc files.
 cn_localflavor_r15942.diff is the patch to apply.

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

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

Re: [Django] #12379: Simplified Chinese(CN) localflavor package

[Django]

#12379: Simplified Chinese(CN) localflavor package
-+-
   Reporter:  xiaket |Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  contrib.localflavor
  Milestone: | Severity:  Normal
Version: | Keywords:  CN localflavor
 Resolution: |Has patch:  1
   Triage Stage:  Ready for  |  Needs tests:  0
  checkin|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by lrekucki):

 * stage:  Accepted => Ready for checkin


Comment:

 Your last patch deletes ".../apps/test/static/test/backup~" (I presume it
 got there by accident), so I fixed that and some trailing whitespace.

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

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

Re: [Django] #15763: MultiPartParser's LimitBytes is now redundant.

[Django]

#15763: MultiPartParser's LimitBytes is now redundant.
-+-
   Reporter: |Owner:  nobody
  tomchristie|   Status:  closed
   Type: |Component:  HTTP handling
  Cleanup/optimization   | Severity:  Normal
  Milestone: | Keywords:
Version:  1.3|Has patch:  0
 Resolution:  duplicate  |  Needs tests:  0
   Triage Stage: |
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by tomchristie):

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


Comment:

 See #15785 for fixing the underlying 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #15762: WSGIRequest should wrap the test client wsgi.input in LimitedStream

[Django]

#15762: WSGIRequest should wrap the test client wsgi.input in LimitedStream
---+-
   Reporter:  tomchristie  |Owner:  nobody
   Type:  Bug  |   Status:  closed
  Milestone:   |Component:  Testing framework
Version:  1.3  | Severity:  Normal
 Resolution:  duplicate| Keywords:
   Triage Stage:  Unreviewed   |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+-
Changes (by tomchristie):

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


Comment:

 See #15785 for fixing the underlying 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

[Django] #15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input stream. (Violation of WSGI spec & under-defined behaviour)

[Django]

#15785: HttpRequest.read(NUM_BYTES) can read beyond the end of wsgi.input 
stream.
(Violation of WSGI spec & under-defined behaviour)
-+--
 Reporter:  tomchristie  | Owner:  tomchristie
 Type:  Bug  |Status:  new
Milestone:  1.3  | Component:  HTTP handling
  Version:  1.3-rc1  |  Severity:  Normal
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  1|
-+--
 Okay, this is the underlying cause behind #15762 and #15763.
 I've marked those as duplicates of this ticket.

 Please see discussion on this bug here:
 https://groups.google.com/forum/#!topic/django-developers/VG1ueWTSs_g

 The problem is now that HttpRequest exposes a read() method, user code can
 do something like:

 {{{
 request_content = json.load(request)
 }}}

 at the moment that will:

 * break the wsgi spec, as the client app is contracted not to attempt to
 read more than CONTENT-LENGTH bytes from wsgi.input
 * result in under-defined behaviour, although it appears to work right
 now.
 * break when used in the test client, as per #15762

 I've attached a patch with tests for this issue, which:

 * Changes WSGIRequest._stream to be a property that is (always)
 instantiated as a !LimitedStream when first accessed.
 * Removes some redundant code in !HttpRequest and !MultiPartParser.
 * Fixes some minor bugs in tests/regressiontests/requests/tests.py
 * Adds two tests for !MultiPartParser to check graceful behaviour on
 truncated or empty multipart requests.
 * Adds a test for !TestClient request.read(LARGE_BUFFER) behaviour.

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

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

Re: [Django] #15781: Multiple databases with same model names causing get errors

[Django]

#15781: Multiple databases with same model names causing get errors
--+-
   Reporter:  anonymous   |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  Uncategorized
Version:  1.2 | Severity:  Normal
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+-
Changes (by anonymous):

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


Comment:

 Work around is to include:

  from everyone import Person as SomeOtherModelName

 then use SomeOtherModelName.objects.get(pk=emplid)

 This seems like a cluge?

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

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

Re: [Django] #12379: Simplified Chinese(CN) localflavor package

[Django]

#12379: Simplified Chinese(CN) localflavor package
---+---
   Reporter:  xiaket   |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  contrib.localflavor
Version:   | Severity:  Normal
 Resolution:   | Keywords:  CN localflavor
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+---
Changes (by DaNmarner):

 * needs_better_patch:  1 => 0


Comment:

 The tests have been rewritten (with unittest) and run.

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

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

Re: [Django] #15064: DJANGO_SETTINGS_MODULE doesn't work with runserver

[Django]

#15064: DJANGO_SETTINGS_MODULE doesn't work with runserver
-+-
   Reporter:  olau   |Owner:  nobody
   Type: |   Status:  new
  Uncategorized  |Component:  Core (Management
  Milestone: |  commands)
Version:  1.2| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-

Comment (by gordl):

 Replying to [comment:2 gordl]:
 > And, what's worse is that when populating the settings via the command
 line, the overridden settings are never loaded.  If I have a custom set of
 settings for certain management commands
 > {{{
 > manage.py mymanagementcommand --settings=custom_settings
 > }}}
 > The settings specified are not loaded.
 Sorry, ignore this. Turns out I had some code that import used django.conf
 settings at import time that caused the standard settings.py to be used.

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

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

Re: [Django] #6623: commit_manually decorator: Better error message (show exception)

[Django]

#6623: commit_manually decorator: Better error message (show exception)
-+-
   Reporter:  guettli|Owner:  jacob
   Type: |   Status:  assigned
  Cleanup/optimization   |Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-

Comment (by jart):

 I submitted a trivial patch for this three years ago and I'm still getting
 emails?  Seriously?

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

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

Re: [Django] #15784: Internal Server Error

[Django]

#15784: Internal Server Error
-+-
   Reporter:  berfam |Owner:  nobody
   Type:  Uncategorized  |   Status:  closed
  Milestone: |Component:  Uncategorized
Version:  1.2| Severity:  Normal
 Resolution:  invalid| Keywords:
   Triage Stage:  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by lrekucki):

 * status:  new => closed
 * needs_better_patch:   => 0
 * resolution:   => invalid
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  New feature => Uncategorized


Comment:

 I fail to see how this is related to 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #6623: commit_manually decorator: Better error message (show exception)

[Django]

#6623: commit_manually decorator: Better error message (show exception)
-+-
   Reporter:  guettli|Owner:  jacob
   Type: |   Status:  assigned
  Cleanup/optimization   |Component:  Database layer
  Milestone: |  (models, ORM)
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * severity:   => Normal


Comment:

 The problem persists in Django 1.3... I spent 6 hours trying to DEBUG it.
 I used autocommit in the same code I found out real cause of problem. Hope
 it helps someone :)

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

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

Re: [Django] #8320: Admin Transaction Management Error

[Django]

#8320: Admin Transaction Management Error
-+-
   Reporter:  holdenweb  |Owner:  nobody
   Type:  Uncategorized  |   Status:  reopened
  Milestone: |Component:  contrib.admin
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:  admin transaction
   Triage Stage:  Accepted   |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

 * type:   => Uncategorized
 * severity:   => Normal


Comment:

 If somebody came to this issue maybe:
 http://code.djangoproject.com/ticket/6623 will help something. I got
 problems in Django 1.3 / PostgresSQL, there is problem with
 commit_manually decorator - it hides real exception which in my case was
 MultipleObjectsFound thrown by .get() function...

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

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

[Django] #15784: Internal Server Error

[Django]

#15784: Internal Server Error
-+--
 Reporter:  berfam   | Owner:  nobody
 Type:  New feature  |Status:  new
Milestone:   | Component:  Uncategorized
  Version:  1.2  |  Severity:  Normal
 Keywords:   |  Triage Stage:  Unreviewed
Has patch:  0|
-+--
 Internal Server Error
 The server encountered an internal error or misconfiguration and was
 unable to complete your request.

 Please contact the server administrator, webmaster@localhost and inform
 them of the time the error occurred, and anything you might have done that
 may have caused the error.

 More information about this error may be available in the server error
 log.


 This is what shows up when I try and open Fitday and log in.  I just
 ordered the premium the other day and now this is what I encounter

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

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

Re: [Django] #15776: Delete Regression in Django 1.3

[Django]

#15776: Delete Regression in Django 1.3
-+-
   Reporter: |Owner:  nobody
  aaron.l.madison@…  |   Status:  new
   Type:  Bug|Component:  Database layer
  Milestone:  1.3|  (models, ORM)
Version:  1.3| Severity:  Release blocker
 Resolution: | Keywords:  db mysql delete
   Triage Stage: |Has patch:  0
  Unreviewed |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by anonymous):

 Based on the relationship structure, the proper delete order would be

 PropertyItem
 Coverage
 ItemRateCode
 Item
 Location
 Version
 Policy

 I think the confusion is coming because a 'Location' must tie to a
 'Version', and 'Item' must tie to a 'Version', but an item could also be
 tied to a specific 'Location'. Whatever is calculating the dependency
 order is getting confused with this relationship.



 Replying to [comment:2 aaron.l.madison@…]:
 > I put some print statements in the django.db.models.deletion.py in the
 Collector.delete method where it does
 > {{{
 > # delete instances
 > for model, instances in self.data.iteritems():
 > query = sql.DeleteQuery(model)
 > pk_list = [obj.pk for obj in instances]
 > print "Deleting:", model, pk_list
 > #query.delete_batch(pk_list, self.using)
 > }}}
 >
 > The output is:
 >
 > {{{
 > (delete_bug)amadison@dev-aaron:~/projects/delete_bug/project$
 ./manage.py test myapp
 > Creating test database for alias 'default'...
 > Deleting:  [1L]
 > Deleting:  [1L]
 > Deleting:  [1L]
 > Deleting:  [2L, 1L]
 > Deleting:  [2L, 1L]
 > Deleting:  [2L, 1L]
 > Deleting:  [2L, 1L]
 >
 > }}}
 >
 > the SQL error is happening (i am fairly sure) because the version is
 trying to be deleted before the Item.

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

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

Re: [Django] #15736: test.client.RequestFactory doesn't support sessions

[Django]

#15736: test.client.RequestFactory doesn't support sessions
-+-
   Reporter:  slinkp |Owner:  nobody
   Type:  Uncategorized  |   Status:  new
  Milestone: |Component:  Uncategorized
Version:  1.3| Severity:  Normal
 Resolution: | Keywords:
   Triage Stage:  Unreviewed |Has patch:  0
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  0  |
-+-
Changes (by prestontimmons):

 * cc: prestontimmons (added)


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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  assigned
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---

Comment (by lawgon):

 cool - I haven't used svn for some years now. svn add did the trick. I
 will just test everything out and upload tomorrow. Thanks for you patience

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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  assigned
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---

Comment (by julien):

 My svn skills are a bit rusty but I think you need to 'svn add' the new
 file before running diff. I've also found this:
 http://stackoverflow.com/questions/4248768/including-new-files-in-svn-diff

 If you're still struggling, I suggest you ask for help on the django-users
 list. Thank you!

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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  assigned
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---

Comment (by lawgon):

 all ready, but I am confused as how to combine everything in one patch.
 svn diff gives me the changes in forms.py. I have also created an in.py in
 
http://code.djangoproject.com/browser/django/trunk/tests/regressiontests/forms/localflavor
 - how do I add this to the patch?

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

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

Re: [Django] #15783: Class FileProxyMixin has invalid attribute definition

[Django]

#15783: Class FileProxyMixin has invalid attribute definition
--+
   Reporter:  sebzur  |Owner:  nobody
   Type:  Bug |   Status:  new
  Milestone:  |Component:  File uploads/storage
Version:  1.3 | Severity:  Normal
 Resolution:  | Keywords:
   Triage Stage:  Unreviewed  |Has patch:  0
Needs documentation:  0   |  Needs tests:  0
Patch needs improvement:  0   |
--+
Changes (by sebzur):

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


Comment:

 I think I was not not much verbose with the ticket, so some more info
 below:

 The error occurs when handling uploded file, that was not save and is in
 fact InMemoryUploadedFile object. Then, InMemoryUploadedFile instance does
 not have fileno attribute working correctly.

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

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

[Django] #15783: Class FileProxyMixin has invalid attribute definition

[Django]

#15783: Class FileProxyMixin has invalid attribute definition
+-
 Reporter:  sebzur  | Owner:  nobody
 Type:  Bug |Status:  new
Milestone:  | Component:  File uploads/storage
  Version:  1.3 |  Severity:  Normal
 Keywords:  |  Triage Stage:  Unreviewed
Has patch:  0   |
+-
 In: '''django/core/files/utils.py''' line 12, in the definition of class
 `class FileProxyMixin` used in
 form fileds to handle file uploads, there is:


 {{{
 fileno = property(lambda self: self.file.fileno)
 }}}

 which proxies to self.file.fileno... *but* self.file has no fileno
 attribute, which
 produces an error on the access try...

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

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

Re: [Django] #3357: Make Django's server optionally multithreaded

[Django]

#3357: Make Django's server optionally multithreaded
-+-
   Reporter: |Owner:  adrian
  treborhudson@… |   Status:  closed
   Type: |Component:  django-admin.py
  Uncategorized  |  runserver
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  post10
 Resolution:  wontfix|Has patch:  1
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by egenix_viktor):

 * type:   => Uncategorized
 * severity:   => Normal


Comment:

 Workaround for multi-threaded development, if you really need that. It is
 useful if you have to debug long polling (Comet) connections or stream
 content to the client, which would need more than one HTTP connection open
 at the same time. Create a new main script in your Django project
 directory with the following contents and use that to run your project
 inside the debugger (like Wing IDE):

 {{{
 """ Start Django in multithreaded mode

 It is NOT for deployment. It allows for debugging Django
 while serving multiple requests at once in multi-threaded mode.

 """

 import os, sys

 HOST = '127.0.0.1'
 PORT = 8000

 DJANGO_PROJECT_DIR = os.path.dirname(__file__)
 PARENT_DIR, DJANGO_PROJECT_NAME = DJANGO_PROJECT_DIR.rsplit(os.sep, 1)

 sys.path.append(DJANGO_PROJECT_DIR)
 os.environ['DJANGO_SETTINGS_MODULE'] = '%s.settings' % DJANGO_PROJECT_NAME

 import django
 import django.core.handlers.wsgi

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

 if __name__ == '__main__':
 import wsgiref, SocketServer
 from wsgiref import simple_server
 class ThreadedWSGIServer(SocketServer.ThreadingMixIn,
 simple_server.WSGIServer):
 pass
 httpd = simple_server.make_server(
 HOST, PORT, application, server_class=ThreadedWSGIServer)
 print 'Serving on port %s:%d' % (HOST, PORT)
 httpd.serve_forever()
 }}}

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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  assigned
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---

Comment (by lawgon):

 ok - will do - good thing you are removing doctests - they are a pain to
 write.

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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  assigned
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---

Comment (by julien):

 You may add your unittests either in
 source:django/trunk/tests/regressiontests/localflavor or
 source:django/trunk/tests/regressiontests/forms/localflavor , whichever
 makes more sense to you ;)

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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  assigned
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---

Comment (by russellm):

 One of the features of 1.3 is that we replaced almost all the doctests in
 Django with unit tests. Going forward, we're only adding unit tests.

 So - any patch being proposed for trunk needs to include unittests not
 doctests.

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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  assigned
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---

Comment (by lawgon):

 you want unittests in addition to doctests? or instead of doctests? I have
 the unittests, but since I could not find unittests for other phonenumber
 flavors, I did not put them.

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

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

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  assigned
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 OK I see. Could you rewrite your tests using unittest, and also combine
 all changes within one single diff patch? 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #14608: Adding a INPhoneNumberField to indian localflavor

[Django]

#14608: Adding a INPhoneNumberField to indian localflavor
---+---
   Reporter:  lawgon   |Owner:  lawgon
   Type:  New feature  |   Status:  assigned
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:  india phone
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  0|
---+---
Changes (by lawgon):

 * needs_tests:  1 => 0


Comment:

 tests are there in 'in.py' uploaded 7 weeks back. I have unchecked the
 'needs tests' 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.

Re: [Django] #8798: Add DEPhoneNumberField to German localflavor module

[Django]

#8798: Add DEPhoneNumberField to German localflavor module
---+---
   Reporter:  jezdez   |Owner:  jezdez
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  contrib.localflavor
Version:  SVN  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---
Changes (by julien):

 * type:  Uncategorized => New feature


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

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

Re: [Django] #8798: Add DEPhoneNumberField to German localflavor module

[Django]

#8798: Add DEPhoneNumberField to German localflavor module
-+-
   Reporter:  jezdez |Owner:  jezdez
   Type: |   Status:  new
  Uncategorized  |Component:  contrib.localflavor
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * type:   => Uncategorized
 * severity:   => Normal


Comment:

 Patch needs improvement as per the dicussion above. Tests also need to be
 rewritten using unittest.

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

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

Re: [Django] #8934: Add ARPhoneNumberField to Argentina localflavor module

[Django]

#8934: Add ARPhoneNumberField to Argentina localflavor module
---+---
   Reporter:  fperetti |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  contrib.localflavor
Version:  1.0  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  1|  Needs tests:  1
Patch needs improvement:  0|
---+---
Changes (by julien):

 * needs_docs:  0 => 1
 * type:   => New feature
 * severity:   => Normal
 * needs_tests:  0 => 1


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

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

Re: [Django] #9042: Add MXPostalCodeField, MXRFCField and MXCURPField to Mexico localflavor module

[Django]

#9042: Add MXPostalCodeField, MXRFCField and MXCURPField to Mexico localflavor
module
---+---
   Reporter:  marco|Owner:  marco
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  contrib.localflavor
Version:  1.0  | Severity:  Normal
 Resolution:   | Keywords:
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  1|  Needs tests:  1
Patch needs improvement:  0|
---+---
Changes (by julien):

 * needs_docs:  0 => 1
 * type:   => New feature
 * severity:   => Normal
 * needs_tests:  0 => 1


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

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

Re: [Django] #10456: Canada localflavor improvements/fixes

[Django]

#10456: Canada localflavor improvements/fixes
+---
   Reporter:  mmulley   |Owner:  nobody
   Type:  Bug   |   Status:  new
  Milestone:|Component:  contrib.localflavor
Version:  SVN   | Severity:  Normal
 Resolution:| Keywords:  localflavor ca
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  1 |
+---
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 This looks great, although the patch is now a bit old and would need to be
 updated. Tests should also be rewritten using unittest.

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

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

Re: [Django] #10895: Improvements in BRCPFField and BRCNPJField in localflavor.br.forms

[Django]

#10895: Improvements in BRCPFField and BRCNPJField in localflavor.br.forms
-+-
   Reporter:  luizvital  |Owner:  waa
   Type: |   Status:  assigned
  Uncategorized  |Component:  contrib.localflavor
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  localflavor
 Resolution: |  brcpffield, brcpnjfield, br,
   Triage Stage:  Accepted   |  localflavor
Needs documentation:  0  |Has patch:  1
Patch needs improvement:  1  |  Needs tests:  0
-+-
Changes (by julien):

 * needs_better_patch:  0 => 1
 * type:   => Uncategorized
 * severity:   => Normal


Comment:

 Thanks for the great work. Could you now update the tests to use unittest?

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

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

Re: [Django] #11517: Chilean(cl) localflavor car plate field.

[Django]

#11517: Chilean(cl) localflavor car plate field.
-+-
   Reporter:  alej0  |Owner:  nobody
   Type:  New|   Status:  new
  feature|Component:  contrib.localflavor
  Milestone: | Severity:  Normal
Version:  SVN| Keywords:  chile, patente, car
 Resolution: |  plate, field
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  1  |  Needs tests:  1
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * needs_docs:  0 => 1
 * needs_tests:  0 => 1


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

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

Re: [Django] #11537: localflavor for india's state choices are not tuples

[Django]

#11537: localflavor for india's state choices are not tuples
+---
   Reporter:  zbyte64   |Owner:  lars
   Type:  Bug   |   Status:  assigned
  Milestone:|Component:  contrib.localflavor
Version:  SVN   | Severity:  Normal
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  1 |
+---
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 Thanks a lot for this. Could you please rewrite the tests using unittest
 before we can check this in?

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

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

Re: [Django] #12379: Simplified Chinese(CN) localflavor package

[Django]

#12379: Simplified Chinese(CN) localflavor package
---+---
   Reporter:  xiaket   |Owner:  nobody
   Type:  New feature  |   Status:  new
  Milestone:   |Component:  contrib.localflavor
Version:   | Severity:  Normal
 Resolution:   | Keywords:  CN localflavor
   Triage Stage:  Accepted |Has patch:  1
Needs documentation:  0|  Needs tests:  0
Patch needs improvement:  1|
---+---
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 Great work, thank you. Before we check this in, could you rewrite the
 tests using unittest?

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

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

Re: [Django] #12595: Localflavor bad arguments handling

[Django]

#12595: Localflavor bad arguments handling
+---
   Reporter:  sayane|Owner:
   Type:  Bug   |   Status:  new
  Milestone:|Component:  contrib.localflavor
Version:| Severity:  Normal
 Resolution:| Keywords:
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  1
Patch needs improvement:  0 |
+---
Changes (by julien):

 * needs_tests:  0 => 1


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

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

Re: [Django] #12710: South Korea (KR) localflavor package

[Django]

#12710: South Korea (KR)  localflavor package
-+-
   Reporter: |Owner:  nobody
  darjeeling |   Status:  new
   Type:  New|Component:  contrib.localflavor
  feature| Severity:  Normal
  Milestone: | Keywords:  localflavor south
Version: |  korea
 Resolution: |Has patch:  1
   Triage Stage:  Accepted   |  Needs tests:  1
Needs documentation:  1  |
Patch needs improvement:  0  |
-+-
Changes (by julien):

 * needs_docs:  0 => 1
 * needs_tests:  0 => 1


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

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

Re: [Django] #14015: django.contrib.localflavor.it added italian phone number validation

[Django]

#14015: django.contrib.localflavor.it added italian phone number validation
-+-
   Reporter: |Owner:  nobody
  VoodooChile|   Status:  new
   Type: |Component:  contrib.localflavor
  Uncategorized  | Severity:  Normal
  Milestone: | Keywords:
Version:  1.2|  django.contrib.localflavor.it
 Resolution: |  ITPhoneNumberField form phone
   Triage Stage:  Accepted   |  number validation
Needs documentation:  1  |Has patch:  1
Patch needs improvement:  1  |  Needs tests:  1
-+-
Changes (by julien):

 * needs_docs:  0 => 1
 * type:   => Uncategorized
 * severity:   => Normal
 * needs_tests:  0 => 1
 * needs_better_patch:  0 => 1


Comment:

 Could you please provide a diff patch instead of the whole files? It'd be
 great if you could also write some doc, and some tests either in
 source:django/trunk/tests/regressiontests/localflavor or
 source:django/trunk/tests/regressiontests/forms/localflavor ?

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

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

Re: [Django] #14765: Unnecessary usage of NodeList in ForNode (template rendering)

[Django]

#14765: Unnecessary usage of NodeList in ForNode (template rendering)
-+---
   Reporter:  anonymous  |Owner:  nobody
   Type:  Bug|   Status:  new
  Milestone: |Component:  Template system
Version:  SVN| Severity:  Normal
 Resolution: | Keywords:  ForNode render
   Triage Stage:  Accepted   |Has patch:  1
Needs documentation:  0  |  Needs tests:  0
Patch needs improvement:  1  |
-+---
Changes (by julien):

 * needs_better_patch:  0 => 1


Comment:

 Patch needs improvement as per Adrian's 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 
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en.