Re: [Django] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  Alex
Status:  reopened  | Milestone:  
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by rizumu):

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

Comment:

 sorry, didn't mean to close it

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

Re: [Django] #10061: incorrect logout link in admin

[Django]

#10061: incorrect logout link in admin
---+
  Reporter:  lashni| Owner:  Alex
Status:  closed| Milestone:  
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:  worksforme|  Keywords:  
 Stage:  Accepted  | Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by rizumu):

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

Comment:

 Upon patching the logout link now works for me with a second custom admin.
 I have one at /admin/ and another at /manage/ I tried with both regular
 users and superuers.

 However going to /admin/logout/ (or /manage/logout/) if already logged out
 returns a sign-in page that when signed into immediately logs out, and
 returns to /admin/ (/manage/) with the regular login page. That is
 different than behaviour when running one admin site and a logged out user
 visits /admin/logout/. That would show the 'successful logout template'.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10295: pk name attribute not provided in tag

[Django]

#10295: pk name attribute not provided in  tag
+---
  Reporter:  kausikram  | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Serialization  |   Version:  1.0
Resolution: |  Keywords:  pk name
 Stage:  Unreviewed | Has_patch:  0  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by kausikram):

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

[Django] #10301: Refactor Serializer to support iteratation

[Django]

#10301: Refactor Serializer to support iteratation
---+
 Reporter:  paulegan   |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Serialization  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 The [source:django/trunk/django/core/serializers/base.py Serializer]
 interface forces the result to be fully materialised before use.  This
 prevents it's use for streaming responses.

 Currently the closest you can come is something like the following, but
 the response doesn't return until the xml document is complete:
 {{{
 #!python
 response = HttpResponse(content_type='text/xml')
 serializer = serializers.get_serializer("xml")()
 serializer.serialize(queryset.iterator(), stream=response)
 return response
 }}}

 The attached patch adds an `iterator` method to `Serializer` which yields
 the serialised data in chunks.  This allows the serialisation of large
 query sets to be streamed to a response without using much memory:
 {{{
 #!python
 serializer = serializers.get_serializer("xml")()
 xml_iter = serializer.iterator(queryset.iterator(), chunk_size=100)
 return HttpResponse(xml_iter, content_type='text/xml')
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10300: Custom File Storage Backend broken by recent SVN commit.

[Django]

#10300: Custom File Storage Backend broken by recent SVN commit.
---+
  Reporter:  erikcw| Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  File uploads/storage  |   Version:  SVN
   
Resolution:|  Keywords:  file upload 
storage s3
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Comment (by erikcw):

 Ok, found the revision.  Everything works great up to r9765.  When I "svn
 up -r 9766" the problem begins.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #694: [patch] TEMPLATE_DIRS should allow project root relative paths

[Django]

#694: [patch] TEMPLATE_DIRS should allow project root relative paths
--+-
  Reporter:  nirvdrum | Owner:  adrian
Status:  closed   | Milestone:
 Component:  Template system  |   Version:
Resolution:  wontfix  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by aljungberg):

 The posted solution, to have a settings file for every installation
 location, is insufficient for our needs. That solution creates two
 distinct problems:

  1. Every developer on the project is forced to have one or more settings
 files as they check out the project source code into different folders. Or
 each developer hacks their settings.py file to match their own situation
 which leads to merge conflicts.
  2. Requiring manual changes between production and test environments
 increases the risk of problems that only occur during production
 deployment.

 We implemented the alternative solution from adrian's last comment and I
 will share it here for quick reference for other users who run into this
 particular limitation.

 In settings.py,
 {{{
 import os
 PROJECT_PATH = os.path.abspath(os.path.split(__file__)[0])

 TEMPLATE_DIRS = (
 os.path.join(PROJECT_PATH, "templates"),
 )
 }}}

 If this ticket is revisited in the future it is my opinion that it should
 be implemented as suggested to promote 'batteries included' and 'keep it
 simple' philosophies 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 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #10300: Custom File Storage Backend broken by recent SVN commit.

[Django]

#10300: Custom File Storage Backend broken by recent SVN commit.
---+
  Reporter:  erikcw| Owner:  nobody 
   
Status:  new   | Milestone: 
   
 Component:  File uploads/storage  |   Version:  SVN
   
Resolution:|  Keywords:  file upload 
storage s3
 Stage:  Unreviewed| Has_patch:  0  
   
Needs_docs:  0 |   Needs_tests:  0  
   
Needs_better_patch:  0 |  
---+
Changes (by mtredinnick):

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

Comment:

 Well, the next step is to work out which revision caused the problem.
 Since r9700 works and r9800+ doesn't work, use binary searching to find
 the version that breaks things. It will be at most seven checkouts and
 tests (and probably less, since not all those commits are to the same
 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 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #10300: Custom File Storage Backend broken by recent SVN commit.

[Django]

#10300: Custom File Storage Backend broken by recent SVN commit.
+---
 Reporter:  erikcw  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  File uploads/storage| Version:  SVN   
 Keywords:  file upload storage s3  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 I just did an svn update to the latest trunk (from r9700), and now my file
 upload backend storage isn't behaving correctly.  A 6MB file is being
 uploaded to my backend storage as a 1 byte file.  When I revert by to
 r9700, the code behaves as intended.

 My backend is a slightly modified (added encryption) version of the S3
 backend from http://code.welldev.org/django-storages/wiki/Home

 If any other info would be helpful in tracking this down, let me know and
 I'll post it.

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

Re: [Django] #10294: Tutorial 4 uses incorrect variable

[Django]

#10294: Tutorial 4 uses incorrect variable
+---
  Reporter:  nic| Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution:  duplicate  |  Keywords:  tutorial
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Comment (by nic):

 If this is a duplicate, should the documentation make this more explicit?
 When you copy over the new views and change the IDs to
 {{{object}}}-related names for the generic view, you do get the type error
 described in #7253. Clearer documentation (or perhaps a tarball with the
 final code for comparison) would do much to help, especially for a
 beginner's tutorial.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #5786: Relax character restrictions on auth usernames

[Django]

#5786: Relax character restrictions on auth usernames
-+--
  Reporter:  Armin Ronacher  | Owner:  luli
Status:  assigned| Milestone:  
 Component:  Contrib apps|   Version:  SVN 
Resolution:  |  Keywords:  auth
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Changes (by bronger):

 * cc: bron...@physik.rwth-aachen.de (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] #10294: Tutorial 4 uses incorrect variable

[Django]

#10294: Tutorial 4 uses incorrect variable
+---
  Reporter:  nic| Owner:  nobody  
Status:  closed | Milestone:  
 Component:  Documentation  |   Version:  SVN 
Resolution:  duplicate  |  Keywords:  tutorial
 Stage:  Unreviewed | Has_patch:  0   
Needs_docs:  0  |   Needs_tests:  0   
Needs_better_patch:  0  |  
+---
Changes (by dc):

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

Comment:

 Duplicate of #7253 and #5300

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #7048: Support clearing FileFields with ModelForms

[Django]

#7048: Support clearing FileFields with ModelForms
---+
  Reporter:  jarrow| Owner:  brosner 
Status:  assigned  | Milestone:  post-1.0
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Comment (by kmtracey):

 (Oh and forgot to mention assuming the wider scope, #10299 has been closed
 as a dupe.)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10299: Enhance FileField form field with "delete" checkbox when file is loaded

[Django]

#10299: Enhance FileField form field with "delete" checkbox when file is loaded
-+--
  Reporter:  Valera_Grishin  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by kmtracey):

 Yeah, if you read it closely the solution is for !ModelForms in general.
 I updated the summary to reflect that.

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

Re: [Django] #7048: Support clearing FileFields with ModelForms

[Django]

#7048: Support clearing FileFields with ModelForms
---+
  Reporter:  jarrow| Owner:  brosner 
Status:  assigned  | Milestone:  post-1.0
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:|  Keywords:  
 Stage:  Accepted  | Has_patch:  1   
Needs_docs:  0 |   Needs_tests:  1   
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

  * summary:  Support clearing FileFields in the admin if blank=True =>
  Support clearing FileFields with ModelForms

Comment:

 Updated summary to reflect scope of the ticket -- discussion and patch
 indicate the solution here will not be admin-specific.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10299: Enhance FileField form field with "delete" checkbox when file is loaded

[Django]

#10299: Enhance FileField form field with "delete" checkbox when file is loaded
-+--
  Reporter:  Valera_Grishin  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by Alex):

 Karen, I agree that it wasn't immediately obvious, however if you take a
 look at the patch it does appear that the new Field and Widgets are in the
 forms dir, so they darn well better be reusable ;).

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10299: Enhance FileField form field with "delete" checkbox when file is loaded

[Django]

#10299: Enhance FileField form field with "delete" checkbox when file is loaded
-+--
  Reporter:  Valera_Grishin  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by kmtracey):

 The title of #7048 specifically mentions "admin", thus it isn't
 immediately obvious that this broader issue is a dupe.  It's quite
 possible the solution envisioned for #7048 will be general and
 useful/accessible outside of admin, but it would be nice, if that is the
 case, if that were made more clear.  It isn't immediately obvious to me
 from a brief scan of that ticket.

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

Re: [Django] #10299: Enhance FileField form field with "delete" checkbox when file is loaded

[Django]

#10299: Enhance FileField form field with "delete" checkbox when file is loaded
-+--
  Reporter:  Valera_Grishin  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

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

Comment:

 This is a dupe of #7048.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10299: Enhance FileField form field with "delete" checkbox when file is loaded

[Django]

#10299: Enhance FileField form field with "delete" checkbox when file is loaded
-+--
  Reporter:  Valera_Grishin  | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Valera_Grishin):

 * cc: valera.gris...@gmail.com (added)
  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #10299: Enhance FileField form field with "delete" checkbox when file is loaded

[Django]

#10299: Enhance FileField form field with "delete" checkbox when file is loaded
+---
 Reporter:  Valera_Grishin  |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Forms   | Version:
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Currently Django displays the FileField and ImageField with file upload
 HTML widget only. This allows for uploading the new file or image and
 overwritting already stored file or image with a newer version. But it
 doesn't give you an option to delete the uploaded file or image. To
 overcome this problem one must provide a separate CheckboxInput and handle
 its logic in a view specifically to delete the file.

 So, the point is to enhance the FileField and ImageField widgets with
 checkbox which appear in HTML only when file or image is already loaded.
 The proposed label for checkbox is "Delete". When checkbox is ticked and
 new file is not provided the correspoding file (or image) must be deleted
 on server.

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

Re: [Django] #9598: create_user should allow specifying more fields

[Django]

#9598: create_user should allow specifying more fields
-+--
  Reporter:  to.roma.from.dj...@qwertty.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by rdaysky):

 dc, I think you’re missing the point. From your reasoning one might
 conclude the create_user method should be removed as well, and maybe
 Django should not exist because Web sites can already be achieved with
 other means? Python is a great language because it allows concise code,
 and having one statement do the job of three would be beneficial IMO.

 == Alternate proposal ==

 On second thoughts, I’ve come up with a solution which is closer to Django
 spirit. What’s the problem with create_user? Its save() is needless if
 more fields are to be populated. So let’s just add a ‘commit’ argument,
 default True, that would control whether save() is called. This would be
 immediately familiar to any Django user.

 At the same time, additional arguments don’t really hinder one’s ability
 to memorise. One has to memorise when one needs things that don’t work,
 not when one doesn’t need things that would work.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10298: get_list_or_404 documentation

[Django]

#10298: get_list_or_404  documentation
---+
 Reporter:  Dagur  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.0   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The documentation needs to be fixed
 (http://docs.djangoproject.com/en/dev/topics/http/shortcuts/#get-list-
 or-404)

 get_list_or_404 is not equivalent to doing:

 {{{
 def my_view(request):
 my_objects = MyModel.objects.filter(published=True) if not my_objects:
 raise Http404
 }}}
 because my_objects is a queryset but the function will return a list.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #5786: Relax character restrictions on auth usernames

[Django]

#5786: Relax character restrictions on auth usernames
-+--
  Reporter:  Armin Ronacher  | Owner:  luli
Status:  assigned| Milestone:  
 Component:  Contrib apps|   Version:  SVN 
Resolution:  |  Keywords:  auth
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  1   |  
-+--
Comment (by dc):

 Also, see #6588 for a patches.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #6588: Admin interface doesn't allow to use dots in usernames

[Django]

#6588: Admin interface doesn't allow to use dots in usernames
-+--
  Reporter:  anonymous   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  django.contrib.admin|   Version:  newforms-admin
Resolution:  worksforme  |  Keywords:  nfa-someday   
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by dc):

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

Comment:

 Duplicate of #5786

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9788: Make user profile a property

[Django]

#9788: Make user profile a property
+---
  Reporter:  jonat...@urbanmapping.com  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Authentication |   Version:  1.0   
Resolution:  invalid|  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by anonymous):

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

Comment:

 > dir() offered up an already built-in solution to this problem

 Looks like problem is solved. Reopen if i am wrong.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9598: create_user should allow specifying more fields

[Django]

#9598: create_user should allow specifying more fields
-+--
  Reporter:  to.roma.from.dj...@qwertty.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  Authentication  |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by dc):

 -1 for the change. Can already be achieved with

 {{{
 user = User(**kwargs)
 user.set_password('password')
 user.save()
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10295: pk name attribute not provided in tag

[Django]

#10295: pk name attribute not provided in  tag
+---
  Reporter:  kausikram  | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Serialization  |   Version:  1.0
Resolution: |  Keywords:  pk name
 Stage:  Unreviewed | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by Alex):

 kausikram: Please provides a diff against the root of the tree, instead of
 multiple complete files.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10295: pk name attribute not provided in tag

[Django]

#10295: pk name attribute not provided in  tag
+---
  Reporter:  kausikram  | Owner:  nobody 
Status:  new| Milestone: 
 Component:  Serialization  |   Version:  1.0
Resolution: |  Keywords:  pk name
 Stage:  Unreviewed | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Changes (by kausikram):

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

Comment:

 Attached two files :

 * python.py (change in line#33)
 * xml_serializer.py(change in line#47)

 of the serializers module which will now add an extra attribute name to
 the object tag when serializing into json,python or xml.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #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:  1   
Needs_better_patch:  0 |  
---+
Comment (by mizatservercave):

 New patch uploaded.  Fixes mod_python support.

 This patch is now used on a production website and shows phenomenal
 performance.

 The production use-case for this patch is a "members-only" upload/download
 area which requires extensive permissions checking and custom auditing.
 This patch makes it possible to do all the logic needed while remaining
 completely within the Django framework, and without sacrificing
 performance while either uploading or downloading.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10297: Error - Editing post, which consist a uload image from imagefield

[Django]

#10297: Error - Editing post, which consist a uload image from imagefield
---+
  Reporter:  anonymous | Owner:  nobody  
Status:  closed| Milestone:  
 Component:  django.contrib.admin  |   Version:  SVN 
Resolution:  duplicate |  Keywords:  upload image
 Stage:  Unreviewed| Has_patch:  0   
Needs_docs:  0 |   Needs_tests:  0   
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 This sounds like #10121, which was fixed a couple of days ago.  If you are
 running r9840 or higher please reopen with details of the model where you
 are seeing this problem.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-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] #10296: Unescaped output from FileField.url

[Django]

#10296: Unescaped output from FileField.url
--+-
 Reporter:  masklinn  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  File uploads/storage  | Version:  1.0   
 Keywords:  filefield url escaping quote  |   Stage:  Unreviewed
Has_patch:  1 |  
--+-
 {{{FileField.url}}} doesn't escape its output, resulting in validation
 errors if the URL contains spaces and breakages if it contains non-ascii
 characters or {{{?}}}.

 This is related to #5160 basically the same bug using the old
 {{{FileField}}} and the {{{get_FOO_url}}} method.

 The patch attached fixes the issue, but is fairly hacky in that
 self.storage.url returns the complete url (including scheme and netloc) so
 {{{:}}} has to be ignored on top of {{{/}}}. It would be nice to use
 {{{urllib.urlsplit}}} and escape only the {{{path}}}, but that breaks in
 case there's a {{{?}}} in the file path.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10295: pk name attribute not provided in tag

[Django]

#10295: pk name attribute not provided in  tag
---+
 Reporter:  kausikram  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Serialization  | Version:  1.0   
 Keywords:  pk name|   Stage:  Unreviewed
Has_patch:  0  |  
---+
 when django serializes an object it creates an object tag having the
 primary key value as an attribute pk="value" and then provides the other
 fields as its children. however it never mentions the name of the primary
 key anywhere. This turns to be disadvantageous when the primary key is not
 the default id field but something custom specified in the model.

 Support by providing a name attribute for the object tag, similar to that
 provided for the fields tag would be much appreciated.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #3672: newforms: DateField doesn't handle date output formats

[Django]

#3672: newforms: DateField doesn't handle date output formats
+---
  Reporter:  ores...@gmail.com  | Owner:  ajs   
 
Status:  new| Milestone:  post-1.0  
 
 Component:  Forms  |   Version:  SVN   
 
Resolution: |  Keywords:  DateField l10n 
localization format input output
 Stage:  Accepted   | Has_patch:  1 
 
Needs_docs:  0  |   Needs_tests:  0 
 
Needs_better_patch:  0  |  
+---
Changes (by marxis.r...@googlemail.com):

  * milestone:  => post-1.0

Comment:

 Hello

 i think

   def format_value(self, value):
 if isinstance(value, datetime.date) or isinstance(value,
 datetime.datetime):
 return value.strftime(self.format)
 else:
 return value

 needs to be changed to:

   def format_value(self, value):
 if isinstance(value, datetime.date) or isinstance(value,
 datetime.datetime):
 try:
 return value.strftime(self.format)
 except:
 return value
 else:
 return value

 Otherwise the value.strftime(self.format) would crash the form (form
 render returns "") if the field-value does not validate on calling
 form.is_valid()

 If my approach is wrong please let me know. I'm very new to django/python
 :)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #10294: Tutorial 4 uses incorrect variable

[Django]

#10294: Tutorial 4 uses incorrect variable
---+
 Reporter:  nic|   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  SVN   
 Keywords:  tutorial   |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 I could also be doing something wrong here, but it looks like a line in
 the section where you create generic views is incorrect. Here's the
 current line:

 {{{(r'^(?P\d+)/vote/$', 'mysite.polls.views.vote'),}}}

 It seems to me that the {{{poll_id}}} should have been changed to
 {{{object_id}}}. I'm brand new to Python (and Django), so I'm not certain
 that's the complete solution, but it seemed to fix the generic views
 problems I had. (Also, sorry I didn't attach a patch even though it seems
 simple to me; very overwhelmed first-timer here.)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9268: Pass custom form values from post-comment to preview-comment

[Django]

#9268: Pass custom form values from post-comment to preview-comment
--+-
  Reporter:  taojian  | Owner:  stuartk
Status:  new  | Milestone:  post-1.0   
 Component:  django.contrib.comments  |   Version:  SVN
Resolution:   |  Keywords:  comment preview
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by stuartk):

  * owner:  anonymous => stuartk
  * status:  assigned => new

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
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] #9268: Pass custom form values from post-comment to preview-comment

[Django]

#9268: Pass custom form values from post-comment to preview-comment
--+-
  Reporter:  taojian  | Owner:  anonymous  
Status:  assigned | Milestone:  post-1.0   
 Component:  django.contrib.comments  |   Version:  SVN
Resolution:   |  Keywords:  comment preview
 Stage:  Unreviewed   | Has_patch:  0  
Needs_docs:  0|   Needs_tests:  0  
Needs_better_patch:  0|  
--+-
Changes (by anonymous):

  * owner:  nobody => anonymous
  * needs_better_patch:  => 0
  * status:  new => assigned
  * needs_tests:  => 0
  * needs_docs:  => 0

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