Re: [Django] #11621: Django copies .pyo files for a new project/app

[Django]

#11621: Django copies .pyo files for a new project/app
-+--
  Reporter:  stevemilner | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by stevemilner):

 Oops ...

 {{{
 if not f.endswith('.py'):
 }}}

-- 
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] #11621: Django copies .pyo files for a new project/app

[Django]

#11621: Django copies .pyo files for a new project/app
-+--
  Reporter:  stevemilner | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by stevemilner):

 What if we switched this on it's ear and instead and did:

 {{{
 if !f.endswith('.py'):
 }}}

 that way other implementations (such as jython) which may create files
 with different bytecode suffixes don't get items copied as well. Just a
 thought.

-- 
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] #11621: Django copies .pyo files for a new project/app

[Django]

#11621: Django copies .pyo files for a new project/app
-+--
  Reporter:  stevemilner | Owner:  nobody
Status:  new | Milestone:
 Component:  Core framework  |   Version:  SVN   
Resolution:  |  Keywords:
 Stage:  Accepted| Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Accepted
  * 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
-~--~~~~--~~--~--~---

Re: [Django] #11611: can't place two comment forms in one template. Because "prefix" attribute is not supported in __init__ of this form

[Django]

#11611: can't place two comment forms in one template. Because "prefix" 
attribute
is not supported in __init__ of this form
--+-
  Reporter:  oduvan   | Owner:  nobody
Status:  closed   | Milestone:
 Component:  django.contrib.comments  |   Version:  1.0   
Resolution:  invalid  |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by russellm):

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

Comment:

 @oduvan - the "bug" may be "unexpected", but you haven't described what
 the problem _is_. The report is so short that it doesn't actually contain
 any information. *PLEASE* - I'm begging you - EXPLAIN THE PROBLEM.

 Closing again until we have an actual problem description.

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

Re: [Django] #11620: Tutorial part II, page 1, gives error message when followed.

[Django]

#11620: Tutorial part II, page 1, gives error message when followed.
+---
  Reporter:  thegreygeek| Owner:  nobody 
Status:  closed | Milestone: 
 Component:  Documentation  |   Version:  1.1-beta-1 
Resolution:  worksforme |  Keywords:  tutorial part II, admin
 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:  => worksforme
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 Eggs are a Python thing.  For a normal Django install, you don't need to
 uncomment that line to get admin working.  The fact that uncommenting it
 for you makes admin work would seem to imply you are running Django out of
 an egg file, which seems odd if you don't even know what eggs are.  You
 might want to post on IRC or django-users including information about how
 you installed Django to get an explanation for why you need that template
 loader enabled.  I don't see that there's a bug in the tutorial here,
 though, as plenty of people have followed it after using the linked
 install instructions, and not needed to uncomment that line to get admin
 working.

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

[Django] #11620: Tutorial part II, page 1, gives error message when followed.

[Django]

#11620: Tutorial part II, page 1, gives error message when followed.
-+--
 Reporter:  thegreygeek  |   Owner:  nobody
   Status:  new  |   Milestone:
Component:  Documentation| Version:  1.1-beta-1
 Keywords:  tutorial part II, admin  |   Stage:  Unreviewed
Has_patch:  0|  
-+--
 Admin screen will not run when tutorial is followed.

 I hacked around and found that making a change in '''settings.py''' will
 correct the error.

 I uncommented the line

 '''django.template.loaders.eggs.load_template_source'''

 and that found the correct template and admin ran.

 EGGS?  must be inside joke.

-- 
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] #11611: can't place two comment forms in one template. Because "prefix" attribute is not supported in __init__ of this form

[Django]

#11611: can't place two comment forms in one template. Because "prefix" 
attribute
is not supported in __init__ of this form
--+-
  Reporter:  oduvan   | Owner:  nobody
Status:  reopened | Milestone:
 Component:  django.contrib.comments  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by Alex):

 If you could just clearly describe what the bug is, what the expectation
 is and what actually happens in a c omment that would be good.

-- 
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] #11611: can't place two comment forms in one template. Because "prefix" attribute is not supported in __init__ of this form

[Django]

#11611: can't place two comment forms in one template. Because "prefix" 
attribute
is not supported in __init__ of this form
--+-
  Reporter:  oduvan   | Owner:  nobody
Status:  reopened | Milestone:
 Component:  django.contrib.comments  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Comment (by oduvan):

 and I'm sorry again. How can I fix description of ticket? Or I must open
 one more 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] #11611: can't place two comment forms in one template. Because "prefix" attribute is not supported in __init__ of this form

[Django]

#11611: can't place two comment forms in one template. Because "prefix" 
attribute
is not supported in __init__ of this form
--+-
  Reporter:  oduvan   | Owner:  nobody
Status:  reopened | Milestone:
 Component:  django.contrib.comments  |   Version:  1.0   
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by oduvan):

  * status:  closed => reopened
  * resolution:  invalid =>
  * summary:  How can I add prifix attribute, to CommentForm? => can't
  place two comment forms in one template.
  Because "prefix" attribute is not supported in
  __init__ of this form

Comment:

 I'm sorry. But this bug, was so unexpected for me, that's why report was
 so short.

-- 
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] #11583: Incomplete HTML Escaping

[Django]

#11583: Incomplete HTML Escaping
-+--
  Reporter:  rlaa...@wiktel.com  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Uncategorized   |   Version:  1.0   
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Comment (by Tomasz Elendt ):

 Replying to [comment:5 kmtracey]:
 > Replying to [comment:3 anonymous]:
 > > First change in `admin_list.py` is the same as one of mine in #11502.
 I believe I made my patch correctly.
 >
 > No, it's not correct -- the diff isn't from the root of the django tree.
 The first file here is listed simply as "templatetags/admin_list.py", but
 there is no "templatetags" directory in the root of the django tree, so
 whoever goes to apply the patch has to find the right place within the
 django tree (presumably django/contrib/admin) to apply the diff.  It's
 better if the person applying the patch doesn't have to guess where it
 goes.
 >
 > As the fix here is now entirely duplicated by the latest patch for
 #11502, which is relative to django root, I'm closing this one in favor of
 that one.

 Sorry, that was me in comment no. 3 — I forgot to sign my name. And I was
 thinking about my patch (in ticket #11502).

-- 
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] #11583: Incomplete HTML Escaping

[Django]

#11583: Incomplete HTML Escaping
-+--
  Reporter:  rlaa...@wiktel.com  | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Uncategorized   |   Version:  1.0   
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Changes (by kmtracey):

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

Comment:

 Replying to [comment:3 anonymous]:
 > First change in `admin_list.py` is the same as one of mine in #11502. I
 believe I made my patch correctly.

 No, it's not correct -- the diff isn't from the root of the django tree.
 The first file here is listed simply as "templatetags/admin_list.py", but
 there is no "templatetags" directory in the root of the django tree, so
 whoever goes to apply the patch has to find the right place within the
 django tree (presumably django/contrib/admin) to apply the diff.  It's
 better if the person applying the patch doesn't have to guess where it
 goes.

 As the fix here is now entirely duplicated by the latest patch for #11502,
 which is relative to django root, I'm closing this one in favor of that
 one.

-- 
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] #11583: Incomplete HTML Escaping

[Django]

#11583: Incomplete HTML Escaping
-+--
  Reporter:  rlaa...@wiktel.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  Uncategorized   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Comment (by Tomasz Elendt ):

 Ok. I also pulled the second change (in `widgets.py`) to my 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] #11583: Incomplete HTML Escaping

[Django]

#11583: Incomplete HTML Escaping
-+--
  Reporter:  rlaa...@wiktel.com  | Owner:  nobody
Status:  new | Milestone:
 Component:  Uncategorized   |   Version:  1.0   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Comment (by anonymous):

 First change in `admin_list.py` is the same as one of mine in #11502. I
 believe I made my patch 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
-~--~~~~--~~--~--~---

Re: [Django] #11534: Very Bad Grammar in Admin Bulk Delete Warning

[Django]

#11534: Very Bad Grammar in Admin Bulk Delete Warning
---+
  Reporter:  hanksims  | Owner:  nobody
Status:  new   | Milestone:
 Component:  django.contrib.admin  |   Version:  1.0   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by kmtracey):

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

Comment:

 #11619 reported this again.

-- 
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] #11619: Grammar error on admin site

[Django]

#11619: Grammar error on admin site
+---
  Reporter:  slypete| Owner:  nobody
Status:  closed | Milestone:  1.2   
 Component:  Uncategorized  |   Version:  SVN   
Resolution:  duplicate  |  Keywords:
 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 has already been reported in #11534.

-- 
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] #11013: Named imports in urls

[Django]

#11013: Named imports in urls
-+--
  Reporter:  gruszczy| Owner:  nobody
Status:  reopened| Milestone:
 Component:  Core framework  |   Version:  1.1-beta-1
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Comment (by lacker):

 Wow, I ran into this too. I was quite surprised that "from
 django.conf.urls.defaults import *" has side effects involving functions
 that are imported but not visibly used. It seems unpythonic, since the
 standard python advice is to avoid importing * whenever possible. For
 example, whenever I write code in my urls.py, I run the risk of squashing
 or accidentally referring to variables that got introduced in the import.
 Would it be possible to make this work without the import *?

-- 
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] #11619: Grammar error on admin site

[Django]

#11619: Grammar error on admin site
---+
 Reporter:  slypete|   Owner:  nobody
   Status:  new|   Milestone:  1.2   
Component:  Uncategorized  | Version:  SVN   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The admin site displays the following string:

 Are you sure you want to delete the selected note objects? All of the
 following objects and '''it's''' related items will be deleted:

 It's as in '''it is''' related items. The correct grammar is '''its''':

 Are you sure you want to delete the selected note objects? All of the
 following objects and its related items will be deleted:

-- 
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] #9081: [patch] More flexible render_to_response()

[Django]

#9081: [patch] More flexible render_to_response()
-+--
  Reporter:  bhagany | Owner:  ccahoon
Status:  new | Milestone: 
 Component:  HTTP handling   |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Design decision needed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Comment (by bhagany):

 Man, I am confused as to what 'Accepted' from a core committer means.

 @ccahoon - it's true, the HttpResponse(render_to_string(..), ..) syntax is
 pretty much exactly what render_to_response does.  I guess I am confused
 as to why render_to_response is there in the first place, if there's that
 much decision/discussion to be had around something like this?  I just
 want a consistent, and easy way to render responses.  render_to_response
 is easier by a hair, but I can't get the consistency I need out of it.
 That's the only reason for this 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] #7623: Multi-table inheritance does not allow linking new instance of child model to existing parent model instance.

[Django]

#7623: Multi-table inheritance does not allow linking new instance of child 
model
to existing parent model instance.
--+-
  Reporter:  brooks.tra...@gmail.com  | Owner:  nobody  
  
Status:  new  | Milestone:  
  
 Component:  Core framework   |   Version:  SVN 
  
Resolution:   |  Keywords:  
model-inheritance, multi-table-inheritance
 Stage:  Design decision needed   | Has_patch:  1   
  
Needs_docs:  1|   Needs_tests:  1   
  
Needs_better_patch:  1|  
--+-
Comment (by kmtracey):

 #11618 was a dup.

-- 
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] #11618: Child models overwrite data of Parent model

[Django]

#11618: Child models overwrite data of Parent model
---+
  Reporter:  truebr...@openttd.org | Owner:  nobody
Status:  closed| Milestone:
 Component:  Database layer (models, ORM)  |   Version:  SVN   
Resolution:  duplicate |  Keywords:
 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:

 It's a use case not currently supported by inheritance, already covered by
 #7623, I believe.

-- 
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] #11617: Enhance User Message System

[Django]

#11617: Enhance User Message System
-+--
  Reporter:  ckarrie | Owner:  nobody  
Status:  closed  | Milestone:  1.2 
 Component:  Authentication  |   Version:  1.0 
Resolution:  duplicate   |  Keywords:  user message enhancement
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by ckarrie):

 You're right, is a duplicate of [ticket:4604] and [ticket:3995], I'm sorry

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

Re: [Django] #11617: Enhance User Message System

[Django]

#11617: Enhance User Message System
-+--
  Reporter:  ckarrie | Owner:  nobody  
Status:  closed  | Milestone:  1.2 
 Component:  Authentication  |   Version:  1.0 
Resolution:  duplicate   |  Keywords:  user message enhancement
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 It's a more direct duplicate of #3995.

-- 
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] #4604: session-based messages

[Django]

#4604: session-based messages
--+-
  Reporter:  Sean Patrick Hogan   | Owner:  
leahculver
Status:  new  | Milestone:  
1.2   
 Component:  Contrib apps |   Version:  
SVN   
Resolution:   |  Keywords:  
  
 Stage:  Accepted | Has_patch:  
1 
Needs_docs:  0|   Needs_tests:  
0 
Needs_better_patch:  1|  
--+-
Comment (by ckarrie):

 Replying to [comment:58 Travis Cline]:
 > FYI I took ideas from the patch and separated it into middleware:
 http://www.djangosnippets.org/snippets/1002/
 >
 > Also added optional type for messages so you render them differently
 (e.g. http://traviscline.com/blog/2008/08/23/django-middleware-session-
 backed-messaging/)


 seems to be the same idea as [ticket:11617]: Enhance User Message System

-- 
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] #11618: Child models overwrite data of Parent model

[Django]

#11618: Child models overwrite data of Parent model
--+-
 Reporter:  truebr...@openttd.org |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  SVN   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Given the next set of models:


 {{{
 class Project(models.Model):
   name = models.IntegerField()

 class Subversion_Project(Project):
   revision = models.IntegerField()

 class Mercurial_Project(Project):
   revision = models.CharField(max_length=64)
 # This model is not used below, but it shows the intention of my database
 design
 }}}


 And the code:

 {{{

 project = Project(name = 1)
 project.save()
 sproject = Subversion_Project(project_ptr = project)
 sproject.save()
 }}}


 The latter command overwrites the content of 'project' with all empty
 fields. When you print project.name or sproject.project.name before the
 save() it still is fine. After the save() it updates the project with
 empty values.

 My solution is:

 {{{

 sproject = Subversion_Project(project_ptr = project)
 for f in project._meta.local_fields: setattr(sproject, f.name,
 getattr(project, f.name))
 }}}


 Which is, putting it mildly, silly. Is this a bug, or do I expect too much
 of the system?

-- 
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] #11617: Enhance User Message System

[Django]

#11617: Enhance User Message System
-+--
  Reporter:  ckarrie | Owner:  nobody  
Status:  new | Milestone:  1.2 
 Component:  Authentication  |   Version:  1.0 
Resolution:  |  Keywords:  user message enhancement
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by ramiro):

 oops, I meant #4604

-- 
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] #11617: Enhance User Message System

[Django]

#11617: Enhance User Message System
-+--
  Reporter:  ckarrie | Owner:  nobody  
Status:  new | Milestone:  1.2 
 Component:  Authentication  |   Version:  1.0 
Resolution:  |  Keywords:  user message enhancement
 Stage:  Unreviewed  | Has_patch:  0   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by ramiro):

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

Comment:

 I'm tempted to close this as a d uplicate of #4606 where the addition of a
 type to the message is one of the proposed/asked for features of a new
 messaging system.

-- 
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] #11617: Enhance User Message System

[Django]

#11617: Enhance User Message System
--+-
 Reporter:  ckarrie   |   Owner:  nobody
   Status:  new   |   Milestone:  1.2   
Component:  Authentication| Version:  1.0   
 Keywords:  user message enhancement  |   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Hi,

 I would like to see a enhanced user message system that allows to specify
 some base types of the message.

 For example:

  * message_type = 'Error'
  * message_type = 'Success'
  * message_type = 'Notice'

 That would be very practicable if you do an custom action and want to
 display as a user message, if it has failed or not.

 An example for validating a Model using a Admin Action for further
 calculations could look like this:

 {{{
 #!python
 # admin.py (fictional code)

 def validate(modeladmin, request, queryset):
 for q in queryset.all():
 message = u"%s: %s" %(q.name, q.validate())
 if q.is_valid:
 message_type = 'Success'
 else:
 message_type = 'Error'
 request.user.message_set.create(message=message,
 message_type=message_type)
 validate.short_description = "Validate for Agl"
 }}}

-- 
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 bronger):

 Actually, I think we should consider them separate issues.  #3011 is a
 large beast, and this one is pretty light-weight, so I'm afraid of waiting
 for a solution much longer than necessary.  Additionally, we discuss about
 changing Django's default behaviour here, whereas #3011 talks about
 extensibility.  I think that Django should support more usernames out-of-
 the-box.

 The demand that occurs again and again (on the mainglist and in the
 tickets) is that you have to include existing user databases.  In my case,
 we must authenticate against an external Windows Active Directory with
 pre-existing usernames.  I think that this is an important use case, and I
 think that characters like dot, dash, and plus are pretty common outside
 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] #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 bronger):

 So we should close this one, and post links to #6588 and this one to
 #3011?

-- 
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 anonymous):

 The basic problem involves having a username/restrictive user model in
 general... see #3011

-- 
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 bronger):

 I think it's time to merge the ideas on this one.

 According to this issue, we want to have all alphanumeric characters from
 Unicode allowed in usernames.  According to #6588, also dots should be
 allowed, and according to
 , dashes
 might be highly sensible, too.

 So what about `re.compile(r'^...@.\w]+$', re.U)`?  Or do we need even more?
 (E.g. `:#*+~'$%&()[]{}!^`)

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