[Django] #9511: Update Django Hebrew Translation for 1.0.1

[Django]

#9511: Update Django Hebrew Translation for 1.0.1
--+-
 Reporter:  Alex  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Translations  | Version:  1.0   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Title says it all.  It would be great if another speaker could review this
 before it goes in, all the translations should be correct, but since I'm
 not a frequent speaker they might not have the right tone.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

[Django] #9510: admin console CRUD operation reject unicode charactors

[Django]

#9510: admin console CRUD operation reject unicode charactors
--+-
 Reporter:  [EMAIL PROTECTED]  |   Owner:  nobody
   Status:  new   |   Milestone:  post-1.0  
Component:  django.contrib.admin  | Version:  1.0   
 Keywords:  admin Chinese error   |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 I test this on mysql. I create a model and a table in mysql, registered it
 on admin console.
 I try input Chinese charactor with add function, and exceptin thrown like:
 Warning at /admin/act/acttype/add/
 Incorrect string value: '\xE4\xB8\xAD\xE6\x96\x87' for column 'type_name'
 at row 1

 But the record can is created, with "?" character instead of normal input.

 I'd tried to modified the characterset of the table from "latin" to
 "utf8", but still the same. I'd also tried "gbk" charset, no change at
 all.

 Also the edit and delete function has the same exception throws. I think
 we should add a setting param to tell the program how to encode or decode
 the db input/output before db operations.

 To show the error for you I'd uploaded the warning page in the attachment
 list, please have a look.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

[Django] #9509: Documenation on user profiles is a bit skimpy.

[Django]

#9509: Documenation on user profiles is a bit skimpy.
---+
 Reporter:  dvingo |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords:  User Profile   |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Hello,
I've been trying to get user profiles working for almost 2 weeks now.
 I'm a first time django user, which is probably the cause of this problem.
 Nonetheless I've searched endlessly within your documentation for how to
 properly use User profiles.  I finally found the answer searching with
 google, the hard part was knowing what to search for.  The answer I found
 is contained here: http://sam.bluwiki.com/blog/2008/05/extending-user-
 model-profiles-in-django.php  I get how to setup the user profile, the
 hard part was understanding if you create the user object first, or the
 profile.  The blog clarified for me that the profile is it's own entity
 which you connect to a user (by assigning it).  So the base of my
 confusion was the relationship of a profile to a user and vice versa.  I'm
 not sure how many people out there have such problems, but I'm sure it
 can't hurt to include some extra info.

 Thank you for all your work!
 -Dan

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8630: Improve the comments framework customizability

[Django]

#8630: Improve the comments framework customizability
--+-
  Reporter:  thejaswi_puthraya| Owner:  carljm  
   
Status:  new  | Milestone:  
   
 Component:  django.contrib.comments  |   Version:  SVN 
   
Resolution:   |  Keywords:  comments, 
customization
 Stage:  Accepted | Has_patch:  1   
   
Needs_docs:  1|   Needs_tests:  1   
   
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

 * cc: [EMAIL PROTECTED] (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9483: Title template filter is broken

[Django]

#9483: Title template filter is broken
--+-
  Reporter:  hdevries | Owner:  hdevries 
Status:  assigned | Milestone:  post-1.0 
 Component:  Template system  |   Version:  SVN  
Resolution:   |  Keywords:  title template filter
 Stage:  Unreviewed   | Has_patch:  1
Needs_docs:  0|   Needs_tests:  0
Needs_better_patch:  0|  
--+-
Changes (by hdevries):

  * milestone:  => post-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?hl=en
-~--~~~~--~~--~--~---

[Django] #9508: FieldFile should define __hash__

[Django]

#9508: FieldFile should define __hash__
--+-
 Reporter:  graham_king   |   Owner:  nobody
   Status:  new   |   Milestone:  post-1.0  
Component:  Database layer (models, ORM)  | Version:  1.0   
 Keywords:  FieldFile hash|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 FieldFile defines !__eq!__ to compare on the ''name'' field, but does not
 define !__hash!__, hence two FieldFile will be equal but have a different
 hash. Example:

 {{{
 from django.db.models.fields.files import FileField, FieldFile

 f = FileField(upload_to='dir')
 ff1 = FieldFile(None, f, 'dir/file.ext')
 ff2 = FieldFile(None, f, 'dir/file.ext')

 print 'Equal?', ff1 == ff2
 print 'Hashes are equal?', hash(ff1) == hash(ff2)
 }}}

 I suggest adding the following to FieldFile:

 {{{
 def __hash__(self):
 return hash(self.name)
 }}}

 I haven't attached a patch because the change is only two lines - I'm
 happy too if requested.

 I noticed this because I'm comparing objects in different databases by
 comparing the hash of each of their fields.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9507: Broken examples in admin documentation

[Django]

#9507: Broken examples in admin documentation
+---
  Reporter:  john_scott | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.0   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  1  |  
+---
Changes (by SmileyChris):

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

Comment:

 With a function called `upper_case_name`, the output should match.
 Something like:
 {{{
 #!python
 return ("%s %s" % (obj.first_name, obj.last_name)).upper()
 }}}
 or probably this would be clearer:
 {{{
 #!python
 name = "%s %s" % (obj.first_name, obj.last_name)
 return name.upper()
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

[Django] #9507: Broken examples in admin documentation

[Django]

#9507: Broken examples in admin documentation
---+
 Reporter:  john_scott |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 Two examples in the
 [http://docs.djangoproject.com/en/dev/ref/contrib/admin/#list-display
 admin doc] incorrectly call .upper() on a tuple.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9308: Django fails to set nullable foreign key field to NULL before deleting the referenced record

[Django]

#9308: Django fails to set nullable foreign key field to NULL before deleting 
the
referenced record
---+
  Reporter:  egenix_viktor | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.0
   
Resolution:|  Keywords:  delete 
record foreign key constraint check NULL nullable field
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by bthomas):

 Django used to do this properly, but the change from #7778 broke this
 unintentionally. I re-opened #7778 with this fix, but your ticket
 describes the new problem better. Attached my original patch (with the
 line numbers slightly offset to match 1.0.x 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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8193: `__import__(mod, {}, {}, [''])` causes double import of modules ('module' and 'module' + '.')

[Django]

#8193: `__import__(mod, {}, {}, [''])` causes double import of modules ('module'
and 'module' + '.')
+---
  Reporter:  i_i| Owner:  nobody  
Status:  new| Milestone:  post-1.0
 Component:  Uncategorized  |   Version:  SVN 
Resolution: |  Keywords:  import  
 Stage:  Accepted   | Has_patch:  1   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  1  |  
+---
Comment (by mrts):

 As the patch is not up to date, I generated a new one as follows:

 `grep` rule for reviewing all invalid imports:
 {{{
 $ grep -Er "__import__.*\['']" . | grep -v '\.svn'
 }}}

 Small shell script for fixing most of them:
 {{{
 FILES_TO_FIX=`grep -lEr "__import__.*\['']" . | grep -v '\.svn'`
 sed -i "s/\(__import__(\)\([[:alnum:]._]\+\), {\(.*\)\[''])/\1\2,
 {\3[\2.split('.')[-1]])/" $FILES_TO_FIX
 echo "Fix the following manually:"
 grep -Er "__import__.*\['']" . | grep -v '\.svn'
 }}}

 Note that once Python 2.3 support is discontinued, `foo.rsplit('.',
 1)[-1]` should be used (`rsplit` was added in 2.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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #7778: Model subclasses cannot be deleted if a nullable foreign key relates to a model that relates back

[Django]

#7778: Model subclasses cannot be deleted if a nullable foreign key relates to a
model that relates back
-+--
  Reporter:  James Murty | Owner: 
Status:  closed  | Milestone:  post-1.0   
 Component:  Core framework  |   Version:  SVN
Resolution:  fixed   |  Keywords:  foreign key
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  1   |  
-+--
Changes (by bthomas):

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

Comment:

 Changing this back to fixed, since #9308 describes the problem better.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9308: Django fails to set nullable foreign key field to NULL before deleting the referenced record

[Django]

#9308: Django fails to set nullable foreign key field to NULL before deleting 
the
referenced record
---+
  Reporter:  egenix_viktor | Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  Database layer (models, ORM)  |   Version:  1.0
   
Resolution:|  Keywords:  delete 
record foreign key constraint check NULL nullable field
 Stage:  Unreviewed| Has_patch:  1  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by bthomas):

  * has_patch:  0 => 1

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8672: ModelForm.save() should implement force_insert and force_update, like Model.save()

[Django]

#8672: ModelForm.save() should implement force_insert and force_update, like
Model.save()
---+
  Reporter:  Richard Davies <[EMAIL PROTECTED]>  | Owner:  
nobody  
Status:  new   | 
Milestone:  post-1.0
 Component:  Database layer (models, ORM)  |   
Version:  SVN 
Resolution:|  
Keywords:  
 Stage:  Design decision needed| 
Has_patch:  1   
Needs_docs:  0 |   
Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Comment (by dc):

 After this patch ModelForm.save() signature will be different from
 Form.save(). Is this ok?
 Desired effect can already be achieved with
 {{{
 model = model_form.save(commit=False)
 model.save(force_insert=True)
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9433: File locking broken on AFP mounts

[Django]

#9433: File locking broken on AFP mounts
---+
  Reporter:  rndblnch  | Owner:  rndblnch
Status:  new   | Milestone:  
 Component:  File uploads/storage  |   Version:  1.0 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by rndblnch):

  * owner:  nobody => rndblnch

Comment:

 ok, I've submitted a better patch against trunk that follow the
 "Contributing to Django" advice for formatting.
 i'm volunteering to be assigned to this bug, and waiting the triagers/core
 developers to make a decision.
 with kind regards,
 renaud

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9498: generic inline formsets: object has no attribute 'fk'

[Django]

#9498: generic inline formsets: object has no attribute 'fk'
---+
  Reporter:  fredbartle| Owner:  brosner
Status:  assigned  | Milestone: 
 Component:  Contrib apps  |   Version:  SVN
Resolution:|  Keywords:  generic inline formsets
 Stage:  Accepted  | Has_patch:  1  
Needs_docs:  0 |   Needs_tests:  1  
Needs_better_patch:  0 |  
---+
Changes (by carljm):

 * cc: carljm (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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #6027: FileWrapper iterator drained by GzipMiddleware before content can be returned

[Django]

#6027: FileWrapper iterator drained by GzipMiddleware before content can be
returned
+---
  Reporter:  [EMAIL PROTECTED]  | Owner:  nobody
Status:  new| Milestone:
 Component:  Core framework |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by ahlongxp):

 I use this snippet
 {{{
 response = HttpResponse()
 response['Content-Type'] = mimetype
 response['Content-Length'] = uf.file.size
 response['Content-Disposition'] = ('attachment; filename=\"' +
 uf.file.name + "\"")
 for chunk in uf.file.chunks():
 response.write(chunk)
 return response
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

[Django] #9506: Missing i18n string in django.contrib.admin.options

[Django]

#9506: Missing i18n string in django.contrib.admin.options
--+-
 Reporter:  petar |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Translations  | Version:  SVN   
 Keywords:  i18n  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Source line 559:
 {{{ raise Http404('%s object with primary key %r does not exist.' %
 (force_unicode(opts.verbose_name), escape(object_id))) }}}

 Expected:
 {{{ raise Http404(_('%s object with primary key %r does not exist.') %
 (force_unicode(opts.verbose_name), escape(object_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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9502: Settings xref markup for trunk

[Django]

#9502: Settings xref markup for trunk
+---
  Reporter:  ramiro | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by ramiro):

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

Old description:

> This patch converts all the bare {{{``SETTING_NAME``}}} occurrences all
> over the trunk documentation as of r9330 to proper
> {{{:setting:SETTING_NAME}}} constructs as per
> http://docs.djangoproject.com/en/dev/internals/documentation/#todo,
> except for:
>
>  * `ref/settings.txt`
>  * `release/*`
>  * `internals/documentation.txt`
>
> replacements were performed with a locally modified
> `docs/_ext/literals_to_xrefs.py` script.
>
> It applies to the 1.0.X branch as of r9331 with some fuzz:
> {{{
> $ patch -p1 < ../xref-markup-settings-r9330.diff
> patching file docs/faq/admin.txt
> patching file docs/faq/models.txt
> patching file docs/howto/deployment/fastcgi.txt
> patching file docs/internals/contributing.txt
> patching file docs/intro/tutorial01.txt
> patching file docs/ref/contrib/admin.txt
> patching file docs/ref/contrib/comments/settings.txt
> patching file docs/ref/contrib/index.txt
> patching file docs/ref/databases.txt
> patching file docs/ref/django-admin.txt
> Hunk #2 succeeded at 164 (offset 4 lines).
> Hunk #3 succeeded at 185 with fuzz 1 (offset 4 lines).
> Hunk #4 succeeded at 249 (offset 4 lines).
> Hunk #5 succeeded at 263 (offset 4 lines).
> Hunk #6 succeeded at 312 (offset 4 lines).
> Hunk #7 succeeded at 347 (offset 4 lines).
> Hunk #8 succeeded at 552 (offset 32 lines).
> Hunk #9 succeeded at 656 (offset 32 lines).
> Hunk #10 succeeded at 810 (offset 74 lines).
> patching file docs/ref/forms/fields.txt
> patching file docs/ref/generic-views.txt
> patching file docs/ref/request-response.txt
> patching file docs/ref/templates/builtins.txt
> patching file docs/topics/cache.txt
> patching file docs/topics/db/transactions.txt
> patching file docs/topics/email.txt
> patching file docs/topics/files.txt
> patching file docs/topics/http/file-uploads.txt
> patching file docs/topics/http/sessions.txt
> patching file docs/topics/http/urls.txt
> patching file docs/topics/http/views.txt
> patching file docs/topics/i18n.txt
> patching file docs/topics/settings.txt
> patching file docs/topics/templates.txt
> patching file docs/topics/testing.txt
> Hunk #1 succeeded at 849 (offset -30 lines).
> }}}
> but Sphinx generates no warnings when running `make html`.

New description:

 This patch converts all the bare {{{``SETTING_NAME``}}} occurrences all
 over the trunk documentation as of r9330 to proper
 {{{:setting:`SETTING_NAME`}}} constructs as per
 http://docs.djangoproject.com/en/dev/internals/documentation/#todo, except
 for:

  * `ref/settings.txt`
  * `release/*`
  * `internals/documentation.txt`

 replacements were performed with a locally modified
 `docs/_ext/literals_to_xrefs.py` script.

 It applies to the 1.0.X branch as of r9331 as well, with some fuzz:
 {{{
 $ patch -p1 < ../xref-markup-settings-r9330.diff
 patching file docs/faq/admin.txt
 patching file docs/faq/models.txt
 patching file docs/howto/deployment/fastcgi.txt
 patching file docs/internals/contributing.txt
 patching file docs/intro/tutorial01.txt
 patching file docs/ref/contrib/admin.txt
 patching file docs/ref/contrib/comments/settings.txt
 patching file docs/ref/contrib/index.txt
 patching file docs/ref/databases.txt
 patching file docs/ref/django-admin.txt
 Hunk #2 succeeded at 164 (offset 4 lines).
 Hunk #3 succeeded at 185 with fuzz 1 (offset 4 lines).
 Hunk #4 succeeded at 249 (offset 4 lines).
 Hunk #5 succeeded at 263 (offset 4 lines).
 Hunk #6 succeeded at 312 (offset 4 lines).
 Hunk #7 succeeded at 347 (offset 4 lines).
 Hunk #8 succeeded at 552 (offset 32 lines).
 Hunk #9 succeeded at 656 (offset 32 lines).
 Hunk #10 succeeded at 810 (offset 74 lines).
 patching file docs/ref/forms/fields.txt
 patching file docs/ref/generic-views.txt
 patching file docs/ref/request-response.txt
 patching file docs/ref/templates/builtins.txt
 patching file docs/topics/cache.txt
 patching file docs/topics/db/transactions.txt
 patching file docs/topics/email.txt
 patching file docs/topics/files.txt
 patching file docs/topics/http/file-uploads.txt
 patching file docs/topics/http/sessions.txt
 patching file docs/topics/http/urls.txt
 patching file docs/topics/http/views.txt
 patching file docs/topics/i18n.txt
 patching file docs/topics/templates.txt
 patching file docs/topics/testing.txt
 Hunk #1 succeeded at 849 (offset -30 lines).
 }

Re: [Django] #2131: [patch] HttpResponseSendFile for serving static files handler-specific sendfile mechanism

[Django]

#2131: [patch] HttpResponseSendFile for serving static files handler-specific
sendfile mechanism
---+
  Reporter:  ymasuda[at]ethercube.com  | Owner:  alsleme 
Status:  new   | Milestone:  post-1.0
 Component:  Core framework|   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Design decision needed| Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by ahlongxp):

  * version:  => SVN

Comment:

 I'd really like to see this merged 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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #9505: Generic Inlines no longer work

[Django]

#9505: Generic Inlines no longer work
--+-
  Reporter:  SmileyChris  | Owner:  brosner
Status:  closed   | Milestone: 
 Component:  Forms|   Version:  SVN
Resolution:  duplicate|  Keywords: 
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Comment (by SmileyChris):

 Apologies Brian. I did a quick look through the timeline, dunno how I
 missed that :P

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #8187: Import PIL consistently and with exception handling, list as optional dependency in INSTALL

[Django]

#8187: Import PIL consistently and with exception handling, list as optional
dependency in INSTALL
+---
  Reporter:  jfkw   | Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Uncategorized  |   Version:  SVN 
Resolution:  fixed  |  Keywords:  PIL imaging easy_install
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by edrex):

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

Comment:

 I realized that the way of installing PIL listed above is invalid, should
 always be in a PIL module. Sorry for the noise.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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?hl=en
-~--~~~~--~~--~--~---