Re: [Django] #6273: Support for passwd-like password changing

[Django]

#6273: Support for passwd-like password changing
--+-
  Reporter:  toxik| Owner:  justinlilly
Status:  new  | Milestone: 
 Component:  django-admin.py  |   Version:  SVN
Resolution:   |  Keywords: 
 Stage:  Accepted | Has_patch:  1  
Needs_docs:  0|   Needs_tests:  1  
Needs_better_patch:  1|  
--+-
Changes (by justinlilly):

  * needs_docs:  1 => 0

Comment:

 Added docs and changed passwd to change_password. Will need to do some
 more digging on the proper way to test these sorts of scripts.

-- 
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] #11812: Formset with select widget and extra fields won't validate

[Django]

#11812: Formset with select widget and extra fields won't validate
-+--
  Reporter:  Afief   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  invalid |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by kmtracey):

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

Comment:

 Please provide some actual code to show how to recreate the problem you
 are trying to report. I don't know what you mean by a "formset with extra
 fields", for example.  A formset contains forms, not fields.  You should
 be able to trim down your actual code to a very minimal example to
 demonstrate the problem, and post that.   As it is this ticket is too
 vague to be considered valid.

-- 
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] #11809: Unable to test a non-db dependent django app without db configuration

[Django]

#11809: Unable to test a non-db dependent django app without db configuration
+---
  Reporter:  Prabhu Subramanian   |   
  Owner:  nobody
Status:  new| 
Milestone:
 Component:  Testing framework  |   
Version:  1.1   
Resolution: |  
Keywords:
 Stage:  Unreviewed | 
Has_patch:  0 
Needs_docs:  0  |   
Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 Note you have said what you don't like without proposing what you would
 like instead.  Some special setting to tell the test runner no database is
 needed?  The test runner to figure out for itself if a database is needed?
 I don't see how the former is any better than just setting DATABASE_ENGINE
 to sqlite3.  The latter strikes me as more trouble than it is worth for
 the small fraction (I'm guessing) of users who are running no-database
 Django apps.  But I haven't given it a great deal of thought, particularly
 since you haven't actually said what it is you are proposing so perhaps
 you have something completely different in mind.

-- 
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] #11813: Formset with select widget and extra fields won't validate

[Django]

#11813: Formset with select widget and extra fields won't validate
-+--
  Reporter:  Afief   | Owner:  nobody
Status:  closed  | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  duplicate   |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by timo):

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

Comment:

 dup of #11812 (submitted twice)

-- 
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] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
  Reporter:  Glenn  | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 Apologies - I misunderstood your proposal. Chalk that one up to my morning
 coffee not kicking in yet. Now that I'm actually reading what you wrote,
 your proposal looks to be just what is required.

-- 
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] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
  Reporter:  Glenn  | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by Glenn):

 Nobody's suggested changing the constraints; I suspect you misunderstand
 what SET CONSTRAINTS ALL IMMEDIATE does.  See
 http://www.postgresql.org/docs/current/static/sql-set-constraints.html.
 Execute this at the end of a test case, just before it rolls back, so it
 executes the constraint checks as if the transaction was committed.

 I've been busy, but I'll try to get to this eventually if nobody gets to
 it first.

-- 
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] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
  Reporter:  Glenn  | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by russellm):

 @pcardune: The patch will become available about 30 seconds after somebody
 writes it.

 The solution here isn't to change the constraint definition. Constraints
 need to be DEFERRABLE, not IMMEDIATE - there are a number of tests that
 fail if constraint checks aren't deferred. To see which ones, run the test
 suite using MySQL with InnoDB. InnoDB only has IMMEDIATE mode for
 transactions, and fails a lot of tests as a result.

 The interim workaround - if you actually need transactions, use
 TransactionTestCase rather than TestCase. This is slower, but uses a
 database truncate rather than transaction rollback to flush the database.

 I don't know what the final solution will be, but I suspect it will
 involve reliable cleanup of the transaction on rollback, rather than
 changing the database so that the triggers aren't hit.

-- 
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] #11813: Formset with select widget and extra fields won't validate

[Django]

#11813: Formset with select widget and extra fields won't validate
---+
 Reporter:  Afief  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Forms  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Since a select field passes the first choice as it's default value(instead
 of None or '') a django formset with extra fields will interpret that form
 as partially filled and raise an error on any other required fields that
 aren't filled.

 The workaround I'm currently using is to set initial=(first choice) for
 that field

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

Re: [Django] #11812: Formset with select widget and extra fields won't validate

[Django]

#11812: Formset with select widget and extra fields won't validate
-+--
  Reporter:  Afief   | Owner:  nobody
Status:  new | Milestone:
 Component:  Forms   |   Version:  1.1   
Resolution:  |  Keywords:
 Stage:  Unreviewed  | Has_patch:  0 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  0   |  
-+--
Changes (by Afief):

  * 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] #11812: Formset with select widget and extra fields won't validate

[Django]

#11812: Formset with select widget and extra fields won't validate
---+
 Reporter:  Afief  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Forms  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 Since a select field passes the first choice as it's default value(instead
 of None or '') a django formset with extra fields will interpret that form
 as partially filled and raise an error on any other required fields that
 aren't filled.

 The workaround I'm currently using is to set initial=(first choice) for
 that field

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

[Django] #11811: No error raised on update(foreignkey=unsavedobject) on nullable fk

[Django]

#11811: No error raised on update(foreignkey=unsavedobject) on nullable fk
--+-
 Reporter:  Afief |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Database layer (models, ORM)  | Version:  1.1   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Found this while coding at 2AM:
 When there is a field that can be NULL, and you do something like this:
 obj1=Obj1(...)
 obj2=Obj2.objects.all().update(foreignobj=obj1)

 django will assign the fields to NULL.

 I'm not sure if this behaviour is made to be so by design, but it seems to
 me that if someone passes an unsaved object instead of None they made a
 mistake and django should raise an exception.

-- 
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] #11810: [gis] Typo in OpenLayers Admin JS

[Django]

#11810: [gis] Typo in OpenLayers Admin JS
---+
 Reporter:  rcoup  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  GIS| Version:  SVN   
 Keywords:  admin  |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 There's a minor typo in the GIS admin openlayers javascript, for
 !GeoAdmins where `modifiable=False`.

-- 
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] #11809: Unable to test a non-db dependent django app without db configuration

[Django]

#11809: Unable to test a non-db dependent django app without db configuration
---+
 Reporter:  Prabhu Subramanian   |   Owner:  
nobody
   Status:  new|   Milestone:   
 
Component:  Testing framework  | Version:  
1.1   
 Keywords: |   Stage:  
Unreviewed
Has_patch:  0  |  
---+
 We are able to write django applications that do not require database
 configurations. But when we test them using django test framework, the
 framework expects database configurations. Otherwise we get the below
 error.

 raise ImproperlyConfigured, "You haven't set the DATABASE_ENGINE setting
 yet."
 django.core.exceptions.ImproperlyConfigured: You haven't set the
 DATABASE_ENGINE setting yet.

 A workaround is to specify sqlite3 and let the test framework create in-
 memory database. But I don't think this is a good solution.

-- 
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] #11665: django.test.TestCase should flush constraints

[Django]

#11665: django.test.TestCase should flush constraints
+---
  Reporter:  Glenn  | Owner:  nobody
Status:  new| Milestone:  1.2   
 Component:  Testing framework  |   Version:  SVN   
Resolution: |  Keywords:
 Stage:  Accepted   | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Comment (by pcardune):

 Any idea when a patch will become available?  I just encountered this same
 problem.

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

Re: [Django] #11607: ForeignKeyRawIdWidget render throws uncaught exception if value does not exist

[Django]

#11607: ForeignKeyRawIdWidget render throws uncaught exception if value does not
exist
---+
  Reporter:  Rupe  | Owner:  nobody 
 
Status:  new   | Milestone: 
 
 Component:  django.contrib.admin  |   Version:  SVN
 
Resolution:|  Keywords:  
ForeignKeyRawIdWidget widget admin render uncaught exception
 Stage:  Accepted  | Has_patch:  1  
 
Needs_docs:  0 |   Needs_tests:  0  
 
Needs_better_patch:  0 |  
---+
Changes (by baumer1122):

 * cc: p...@lincolnloop.com (added)

Comment:

 Here's a patch (with test) that checks the exception being thrown.

-- 
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] #11808: Typo in admin's documentation

[Django]

#11808: Typo in admin's documentation
+---
  Reporter:  kratorius  | Owner:  nobody
Status:  new| Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Ready for checkin  | Has_patch:  1 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by timo):

  * needs_better_patch:  => 0
  * stage:  Unreviewed => Ready for checkin
  * 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] #11806: FormWizard.process_step() doesn't always have a validated Form.

[Django]

#11806: FormWizard.process_step() doesn't always have a validated Form.
+---
  Reporter:  kiowa  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution:  duplicate  |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by kmtracey):

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

Comment:

 Replying to [comment:2 mpaolini]:
 >
 > this is an old bug, I'm sure there are other tickets on this

 If you believed that then why did you not search for existing tickets?
 Which would have brought up #10882.  We don't need multiple tickets for
 the same problem.

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

Re: [Django] #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|  
--+-
Changes (by ubernostrum):

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

Comment:

 This was marked "wontfix" by a core developer. If you disagree, start a
 thread on the django-developers 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] #8874: problem with URLs on FastCGI after update to 1.0

[Django]

#8874: problem with URLs on FastCGI after update to 1.0
-+--
  Reporter:  kyprizel| Owner:  kyprizel
Status:  closed  | Milestone:  1.2 
 Component:  Core framework  |   Version:  SVN 
Resolution:  duplicate   |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Changes (by qingfeng):

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

Comment:

 fixed #8490

-- 
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] #11808: Typo in admin's documentation

[Django]

#11808: Typo in admin's documentation
---+
 Reporter:  kratorius  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  1  |  
---+
 There's a typo in the admin's documentation, see attached 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] #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:  reopened | Milestone:
 Component:  Template system  |   Version:
Resolution:   |  Keywords:
 Stage:  Unreviewed   | Has_patch:  1 
Needs_docs:  0|   Needs_tests:  0 
Needs_better_patch:  0|  
--+-
Changes (by sio4):

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

Comment:

 I'm newbie to django, and this page is the result of one of my few
 searches about django. It means, IMHO, maybe many newbies can confuse on
 this issue like me.

 my question is: "why we should use relative path for templates directory
 setting? It is always same in relative(for many cases) but it is different
 in absolute.(and how many times is it placed on outside of project?) then
 why we all do add three same lines into settings.py everytime? (import os,
 project_path=..., os.path.join...)" can I get some reasonable reason?

 "app_directories template loader" is not a good solution because the
 look is site specific rather than application specific.
 (app_directories template loader is usefull for drop-in applications
 instead.)

 please excuse my poor English. thank you for your consideration.

-- 
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] #11806: FormWizard.process_step() doesn't always have a validated Form.

[Django]

#11806: FormWizard.process_step() doesn't always have a validated Form.
+---
  Reporter:  kiowa  | Owner:  nobody
Status:  reopened   | Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution: |  Keywords:
 Stage:  Unreviewed | Has_patch:  0 
Needs_docs:  0  |   Needs_tests:  0 
Needs_better_patch:  0  |  
+---
Changes (by mpaolini):

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

Comment:

 in contrib/formtools/wizard.py
 {{{
 63  for i in range(current_step):
 64  form = self.get_form(i, request.POST)
 65  if request.POST.get("hash_%d" % i, '') !=
 self.security_hash(request, form):
 66  return self.render_hash_failure(request, i)
 67  self.process_step(request, form, i)
 }}}
 line 67: form passed to self.process_step is _never_ cleaned (happens for
 all forms before current_step)

 this is an old bug, I'm sure there are other tickets on this

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

Re: [Django] #11807: Admin inlines onetoone related object not saved

[Django]

#11807: Admin inlines onetoone related object not saved
--+-
  Reporter:  neme...@twilightzone.lu  | Owner:  nobody  
  
Status:  new  | Milestone:  
  
 Component:  django.contrib.admin |   Version:  1.1 
  
Resolution:   |  Keywords:  admin inline 
onetoone save
 Stage:  Design decision needed   | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  1|  
--+-
Comment (by neme...@twilightzone.lu):

 Sry for the initial formatting. What about leaving that decision to the
 app designer/developer by introducing a boolean flag for it? Default
 behaviour would be the current one - else save it as new object. Extending
 a model over several models isnt unusual, especially if you are going to
 remove normalization on a db scheme due to performance issues.

-- 
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] #11807: Admin inlines onetoone related object not saved

[Django]

#11807: Admin inlines onetoone related object not saved
--+-
  Reporter:  neme...@twilightzone.lu  | Owner:  nobody  
  
Status:  new  | Milestone:  
  
 Component:  django.contrib.admin |   Version:  1.1 
  
Resolution:   |  Keywords:  admin inline 
onetoone save
 Stage:  Design decision needed   | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  1|  
--+-
Changes (by kmtracey):

  * stage:  Unreviewed => Design decision needed

Old description:

> Hi there,
>
> I have the following models:
>
> class A(models.Model):
>id = models.AutoField(primary_key=True)
>
> class B(models.Model):
>mya = models.OneToOneField(A, primary_key=True)
>text = models.TextField(default='Init')
>
> In admin interface, I have used an inline to include B when
> changing/adding an A. Adding/Changing an A without touching the B inline
> results in A beeing saved, but not B. Changing the textfield from B into
> sth other than default and it works, but I want the default beeing saved
> too.
>
> Thanks!
> Jean

New description:

 Hi there,

 I have the following models:

 {{{
 #!python
 class A(models.Model):
id = models.AutoField(primary_key=True)

 class B(models.Model):
mya = models.OneToOneField(A, primary_key=True)
text = models.TextField(default='Init')
 }}}

 In admin interface, I have used an inline to include B when
 changing/adding an A. Adding/Changing an A without touching the B inline
 results in A beeing saved, but not B. Changing the textfield from B into
 sth other than default and it works, but I want the default beeing saved
 too.

 Thanks!
 Jean

Comment:

 First, I fixed the description formatting.  Please use preview (and wiki
 format) to make sure things are readable before submitting.

 Replying to [comment:1 AdamG]:
 > My guess is that `BaseModelFormSet.save_existing_objects()` is skipping
 the form because `form.has_changed()` is False.

 Yes the problem is likely related to the fact that the form has not been
 changed, though I think it is the has_changed in save_new that is causing
 the issue here.  Thing is, if nothing has changed, how is the admin code
 supposed to figure out that a new item should be created?  I don't believe
 it is always the case that you'd want admin creating objects with all
 defaults (actually I'm pretty sure there was once a bug because admin did
 that).  I am not sure that the admin interface, as it currently exists,
 supports what is being asked for here.  There is currently no explicit
 "add this item" checkbox (as there is for delete), thus the admin has to
 figure out the right thing to do.  It does that now by seeing if anything
 has changed since the form was presented to the user.  If yes, then an
 object is added.  If no, then no new object is created.  I don't quite see
 how to support this use case, and also the case where you don't want all-
 default objects created (which is also valid), without a pretty
 significant change in the admin interface 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] #11807: Admin inlines onetoone related object not saved

[Django]

#11807: Admin inlines onetoone related object not saved
--+-
  Reporter:  neme...@twilightzone.lu  | Owner:  nobody  
  
Status:  new  | Milestone:  
  
 Component:  django.contrib.admin |   Version:  1.1 
  
Resolution:   |  Keywords:  admin inline 
onetoone save
 Stage:  Unreviewed   | Has_patch:  0   
  
Needs_docs:  0|   Needs_tests:  0   
  
Needs_better_patch:  1|  
--+-
Changes (by AdamG):

  * needs_better_patch:  => 1
  * component:  Uncategorized => django.contrib.admin
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 The attached patch against trunk adds a regression test that fails and
 shows the problem.

 Note that when the submitted value is not the default value, it's saved
 correctly, so `test_onetoone_pk_inline_changed` passes. My guess is that
 `BaseModelFormSet.save_existing_objects()` is skipping the form because
 `form.has_changed()` is False.

-- 
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] #11806: FormWizard.process_step() doesn't always have a validated Form.

[Django]

#11806: FormWizard.process_step() doesn't always have a validated Form.
+---
  Reporter:  kiowa  | Owner:  nobody
Status:  closed | Milestone:
 Component:  Documentation  |   Version:  1.1   
Resolution:  invalid|  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:  => invalid
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 You've stated that the form isn't always guaranteed to be clean without
 providing an example of how that could happen.  Based on the documentation
 and a brief look at the code, that happening would seem to be a coding
 error rather than a documentation problem. So as written I believe this
 ticket is invalid.  Feel free to reopen with specifics on how to recreate
 a situation where process_step is called without a valid form, but the
 place to look for fixing it I believe will be in the code, not the
 documentation.

-- 
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] #8874: problem with URLs on FastCGI after update to 1.0

[Django]

#8874: problem with URLs on FastCGI after update to 1.0
-+--
  Reporter:  kyprizel| Owner:  kyprizel
Status:  assigned| Milestone:  1.2 
 Component:  Core framework  |   Version:  SVN 
Resolution:  |  Keywords:  
 Stage:  Accepted| Has_patch:  1   
Needs_docs:  0   |   Needs_tests:  0   
Needs_better_patch:  0   |  
-+--
Comment (by barbaros1420):

 Replying to [comment:2 kyprizel]:
 > I use nginx web server, configured to use the same PATH_INFO and
 SCRIPT_NAME,
 > so [http://code.djangoproject.com/ticket/8490] made problems for me.
 > http://www.oyun27.com
 >Is my config incorrect?

-- 
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] #2407: [patch] CGI Support for django

[Django]

#2407: [patch] CGI Support for django
--+-
  Reporter:  Martin Glueck   | Owner:  
nobody
Status:  closed   | Milestone:  
  
 Component:  Core framework   |   Version:  
SVN   
Resolution:  wontfix  |  Keywords:  
cgi   
 Stage:  Design decision needed   | Has_patch:  
1 
Needs_docs:  0|   Needs_tests:  
1 
Needs_better_patch:  1|  
--+-
Comment (by barbaros1420):

 Replying to [comment:18 Thomas Güttler]:
 > print in python code should go stderr (logfile):
 > http://www.oyun27.com
 > ===> diff -u cgi.py  ~modarch/django/trunk/django/core/servers/cgi.py
 > --- cgi.py  2007-05-07 16:49:30.313178117 +0200
 > +++ /home/modarch/django/trunk/django/core/servers/cgi.py
 2007-05-07 17:11:09.788411072 +0200
 > @@ -10,6 +10,7 @@
 >
 >  def runcgi():
 >  environ  = dict(os.environ.items())
 > +environ['PATH_INFO'] = environ.get('PATH_INFO',"/")
 >  environ['wsgi.input']= sys.stdin
 >  environ['wsgi.errors']   = sys.stderr
 >  environ['wsgi.version']  = (1,0)
 > @@ -26,6 +27,9 @@
 >
 >  headers_set  = []
 >  headers_sent = []
 > +
 > +stdout=sys.stdout
 > +sys.stdout=sys.stderr # print should go to stderr (logfile)
 >
 >  def write(data):
 >  if not headers_set:
 > @@ -34,13 +38,13 @@
 >  elif not headers_sent:
 >   # Before the first output, send the stored headers
 >   status, response_headers = headers_sent[:] = headers_set
 > - sys.stdout.write('Status: %s\r\n' % status)
 > + stdout.write('Status: %s\r\n' % status)
 >   for header in response_headers:
 > - sys.stdout.write('%s: %s\r\n' % header)
 > - sys.stdout.write('\r\n')
 > + stdout.write('%s: %s\r\n' % header)
 > + stdout.write('\r\n')
 >
 > -sys.stdout.write(data)
 > -sys.stdout.flush()
 > +stdout.write(data)
 > +stdout.flush()
 >
 >  def start_response(status,response_headers,exc_info=None):
 >  if exc_info:

 Thank you

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

Re: [Django] #17: Metasystem optimization: Share select_related in memory

[Django]

#17: Metasystem optimization: Share select_related in memory
---+
  Reporter:  adrian| Owner:  PhiR   

Status:  assigned  | Milestone: 

 Component:  Database layer (models, ORM)  |   Version:  SVN

Resolution:|  Keywords:  feature 
caching
 Stage:  Accepted  | Has_patch:  1  

Needs_docs:  1 |   Needs_tests:  0  

Needs_better_patch:  1 |  
---+
Comment (by barbaros1420):

 thank you very good article
 http://www.oyun27.com - http://www.oyunlar27.com - http://www.keloyun.com

-- 
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] #2134: [patch] add comment object to comments/posted template

[Django]

#2134: [patch] add comment object to comments/posted template
+---
  Reporter:  m...@hudora.de   | Owner:  alsleme
Status:  closed | Milestone: 
 Component:  HTTP handling  |   Version:  SVN
Resolution:  invalid|  Keywords: 
 Stage:  Accepted   | Has_patch:  1  
Needs_docs:  0  |   Needs_tests:  0  
Needs_better_patch:  0  |  
+---
Comment (by barbaros1420):

 Replying to [comment:27 Briace]:
 >
 > [http://www.aypearl.com/ wholesale jewelry],[http://www.aypearl.com/
 handmade jewelry], [http://www.aypearl.com/ wholesale handmade jewelry] ,
 >
 > [http://www.aypearl.com/ jewelry store],[http://www.aypearl.com/
 wholesale costume jewelry],[http://www.aypearl.com/ discount jewelry],
 >
 > [http://www.aypearl.com/ fashion jewelry],[http://www.aypearl.com/
 wholesale fashion jewelry],[http://www.aypearl.com/ bridal jewelry],
 >
 http://www.oyun27.com
 http://www.oyunlar27.com
 http://www.keloyun.com
 > [http://www.aypearl.com/ costume jewelry]
 {{{
 ???

-- 
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] #11807: Admin inlines onetoone related object not saved

[Django]

#11807: Admin inlines onetoone related object not saved
+---
 Reporter:  neme...@twilightzone.lu |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Uncategorized   | Version:  1.1   
 Keywords:  admin inline onetoone save  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Hi there,

 I have the following models:

 class A(models.Model):
id = models.AutoField(primary_key=True)

 class B(models.Model):
mya = models.OneToOneField(A, primary_key=True)
text = models.TextField(default='Init')

 In admin interface, I have used an inline to include B when
 changing/adding an A. Adding/Changing an A without touching the B inline
 results in A beeing saved, but not B. Changing the textfield from B into
 sth other than default and it works, but I want the default beeing saved
 too.

 Thanks!
 Jean

-- 
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] #11806: FormWizard.process_step() doesn't always have a validated Form.

[Django]

#11806: FormWizard.process_step() doesn't always have a validated Form.
---+
 Reporter:  kiowa  |   Owner:  nobody
   Status:  new|   Milestone:
Component:  Documentation  | Version:  1.1   
 Keywords: |   Stage:  Unreviewed
Has_patch:  0  |  
---+
 The FormWizard documentation says:
 {{{
 FormWizard.process_step()

 Hook for modifying the wizard's internal state, given a fully
 validated Form object. The Form is guaranteed to have clean, valid data.
 }}}

 But the form isn't always guaranteed to be clean - and thus give access to
 its '''cleaned_data''' mapping.

 To achieve this you will need in your process_step:
 {{{
 process_step(self, request, form, step):
 form.full_clean()
 }}}

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