[Django] #15290: Border style issue in changelist

[Django]

#15290: Border style issue in changelist
--+-
 Reporter:  julien|  Owner:  nobody
   Status:  new   |  Milestone:  1.3   
Component:  django.contrib.admin  |Version:  1.2   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 Take this example:

 Model:
 {{{
 #!python
 from django.db import models

 class MyModel(models.Model):
 name = models.CharField(max_length=100, blank=True)
 title = models.CharField(max_length=100, blank=True)
 content = models.CharField(max_length=100, blank=True)
 }}}

 Admin:
 {{{
 #!python
 from django.contrib import admin

 from .models import MyModel

 class MyModelAdmin(admin.ModelAdmin):
 list_display = ('name', 'title', 'content')
 list_display_links = ('title',)

 admin.site.register(MyModel, MyModelAdmin)
 }}}

 The display link (here the 'title' field) is represented within a ``
 instead of a `` which is used for other regular display fields. The
 issue is that there is no CSS rule for displaying the left border of a
 `` cell. The attached patch fixes 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] #15180: reverse doesn't check default_args

[Django]

#15180: reverse doesn't check default_args
--+-
   Reporter:  olaf| Owner:  nobody  
 Status:  new | Milestone:  
  Component:  Core framework  |   Version:  1.3-beta
 Resolution:  |  Keywords:  resolve default_args
   Triage Stage:  Accepted| Has patch:  1   
Needs documentation:  0   |   Needs tests:  1   
Patch needs improvement:  0   |  
--+-
Changes (by julien):

  * milestone:  1.3 =>


Comment:

 This can't make it into 1.3 unless comprehensive regression tests are
 provided. Olaf, if you're interested in writing some tests, take a look at
 the guide available at
 http://docs.djangoproject.com/en/dev/topics/testing/
 Don't hesitate to ask questions on the django-users list too if need be.

-- 
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] #14355: "readonly" fields don't display their "help_text" in admin

[Django]

#14355: "readonly" fields don't display their "help_text" in admin
+---
   Reporter:  jester| Owner:  wamberg   

 Status:  assigned  | Milestone:  1.3   

  Component:  django.contrib.admin  |   Version:  1.2   

 Resolution:|  Keywords:  readonly 
help_text
   Triage Stage:  Ready for checkin | Has patch:  1 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---
Changes (by julien):

  * needs_better_patch:  1 => 0
  * needs_tests:  1 => 0
  * stage:  Accepted => Ready for checkin


Comment:

 Thank you alexbmeng, subsume and wamberg. Your latest patch looked good.
 I've just removed a line (`self.help_text = ...`) which was unnecessary
 and wrote some slightly more thorough tests. I believe this is RFC now.

-- 
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] #11058: list_display_links doesn't allow callables not defined in the model

[Django]

#11058: list_display_links doesn't allow callables not defined in the model
+---
   Reporter:  dvine | Owner:  acdha 

 Status:  assigned  | Milestone:  1.3   

  Component:  django.contrib.admin  |   Version:  SVN   

 Resolution:|  Keywords:  
list_display_links
   Triage Stage:  Ready for checkin | Has patch:  1 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---
Changes (by DrMeers):

  * stage:  Accepted => Ready for checkin


Comment:

 This makes sense to me; `list_display` is already validated; performing
 separate validation on `list_display_links` seems redundant. Nice simple
 solution Julien.

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

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

Re: [Django] #10917: admin/base.html should contain messages block

[Django]

#10917: admin/base.html should contain messages block
+---
   Reporter:  anonymous | Owner:  nobody

 Status:  new   | Milestone:  1.4   

  Component:  django.contrib.admin  |   Version:  1.1-beta-1

 Resolution:|  Keywords:  admin 
customization block messages
   Triage Stage:  Accepted  | Has patch:  1 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  1 |  
+---
Changes (by julien):

  * needs_better_patch:  0 => 1
  * milestone:  => 1.4


Comment:

 The patch looks good, though it doesn't apply any more. This new feature
 comes too late for 1.3 but I'd like to see it in 1.4.

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

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

Re: [Django] #15084: Unnecessary imports lead to ImportError

[Django]

#15084: Unnecessary imports lead to ImportError
+---
   Reporter:  vanschelven   | Owner:  nobody
 Status:  new   | Milestone:
  Component:  Internationalization  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  1 
Patch needs improvement:  1 |  
+---

Comment (by ramiro):

 Given the fact that the reported error condition can't be reproduced in a
 reduced test case, it would be nice if the OP describes the setup used in
 the production deployment where the problem happens.

-- 
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] #14130: Catching ImportError in manage.py considered dangerous

[Django]

#14130: Catching ImportError in manage.py considered dangerous
-+--
   Reporter:  Setok  | Owner:  nobody   
 
 Status:  new| Milestone:  1.3  
 
  Component:  Core framework |   Version:  1.1  
 
 Resolution: |  Keywords:  manage settings 
import sprintnov13
   Triage Stage:  Ready for checkin  | Has patch:  1
 
Needs documentation:  0  |   Needs tests:  0
 
Patch needs improvement:  0  |  
-+--
Changes (by ramiro):

  * stage:  Accepted => Ready for checkin


-- 
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] #11373: Change list layout breaks if no actions_form

[Django]

#11373: Change list layout breaks if no actions_form
+---
   Reporter:  manuel_razzari| Owner: 
 Status:  closed| Milestone: 
  Component:  django.contrib.admin  |   Version:  SVN
 Resolution:  fixed |  Keywords: 
   Triage Stage:  Accepted  | Has patch:  1  
Needs documentation:  0 |   Needs tests:  0  
Patch needs improvement:  0 |  
+---
Changes (by julien):

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


Comment:

 I can't seem to be able to reproduce this, so I assume it has been fixed
 in a previous changeset. If you disagree, please reopen and provide a
 concrete code example that we can test.

-- 
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] #13007: Django fails to log in when a cookie is set on the same domain containing a colon

[Django]

#13007: Django fails to log in when a cookie is set on the same domain 
containing a
colon
-+--
   Reporter:  Warlax | Owner:  nobody   
 
 Status:  reopened   | Milestone:  1.3  
 
  Component:  HTTP handling  |   Version:  SVN  
 
 Resolution: |  Keywords:  cookies, 
sprintdec2010
   Triage Stage:  Ready for checkin  | Has patch:  1
 
Needs documentation:  0  |   Needs tests:  0
 
Patch needs improvement:  0  |  
-+--

Comment (by lukeplant):

 Just a small note - 13007.1.diff is absolutely the right way to do it in
 trunk, but it will be a pain to backport to 1.2.X, due to [15298] and the
 fact that [14707] is a feature addition which is not backported to 1.2.X.
 So it looks like 13007.1.diff should be applied to trunk, 13007.diff to
 1.2.X.

-- 
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] #15058: sys.path.append()

[Django]

#15058: sys.path.append()
-+--
   Reporter:  daghenrik  | Owner:  nobody
 Status:  reopened   | Milestone:
  Component:  Documentation  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--

Comment (by grahamd):

 Please be careful about using the reference to 'PYTHONPATH' in
 documentation related to mod_wsgi setup. People know 'PYTHONPATH' as the
 environment variable used in command line Python and occasionally have
 seen people think that because it was mentioned and because they had
 already set 'PYTHONPATH' in the user environment that everything will work
 under Apache. This will not be the case because Apache/mod_wsgi runs as
 different user and will not inherit the users environment. I would
 personally therefore like to see any mention of 'PYTHONPATH' dropped and
 simple refer to it as something """Python module search path as defined by
 'sys.path'""" or something else similar.

 And yes I have been lazy in still not adding a separate page to the
 mod_wsgi documentation explaining better the whole sys.path, module search
 path stuff. :-)

-- 
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] #11513: Admin Change Page Redirects to Permission Denied

[Django]

#11513: Admin Change Page Redirects to Permission Denied
+---
   Reporter:  rlaager   | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * needs_tests:  1 => 0
  * milestone:  => 1.3


Comment:

 Thanks for the report rlaager. The behaviour should actually be slightly
 different from that in your patch. Like the 'add' view, it should redirect
 to the admin's root page if there are no appropriate 'change' permissions.
 The new patch fixes that and also contains thorougher tests for row level
 'change' permissions.

-- 
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] #15272: Context object name is translated string

[Django]

#15272: Context object name is translated string
-+--
   Reporter:  szczav | Owner:  nobody   
 
 Status:  new| Milestone:  1.3  
 
  Component:  Generic views  |   Version:  SVN  
 
 Resolution: |  Keywords:  generic views 
context verbose_name blocker
   Triage Stage:  Accepted   | Has patch:  1
 
Needs documentation:  0  |   Needs tests:  0
 
Patch needs improvement:  0  |  
-+--
Changes (by lrekucki):

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


Comment:

 Forgot about the flags 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] #15272: Context object name is translated string

[Django]

#15272: Context object name is translated string
-+--
   Reporter:  szczav | Owner:  nobody   
 
 Status:  new| Milestone:  1.3  
 
  Component:  Generic views  |   Version:  SVN  
 
 Resolution: |  Keywords:  generic views 
context verbose_name blocker
   Triage Stage:  Accepted   | Has patch:  1
 
Needs documentation:  1  |   Needs tests:  0
 
Patch needs improvement:  1  |  
-+--

Comment (by lrekucki):

 Replying to [comment:6 szczav]:
 > I've removed error message fixes (I'll create separate ticket on this)
 and added docs. Way how context variables are created is described in
 docs, so I've just rewritten it. By the way
 ```get_context_object_name()``` description for the
 ```SingleObjectMixin``` was completely wrong before.

 Looks good to me, but didn't actually run it, so someone should take a
 look at it.


 > Idea of #14018 is good but as I see its milestone is 2.0 so probably we
 have to stay with ```object_name``` concept.

 Not everything people set on Trac is accurate. IMHO, adding "name_plural"
 to Meta is fully backwards compatible. If it's actually worth the small
 improvements, is a different matter. But it's also out of scope for 1.3 as
 a new feature (could be added in 1.4). It definitely shouldn't block a
 release, so going with {{{object_name}}} is the right way 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] #15289: New transaction behavior only works if DEBUG=False

[Django]

#15289: New transaction behavior only works if DEBUG=False
+---
   Reporter:  apollo13  | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by ramiro):

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


-- 
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] #15058: sys.path.append()

[Django]

#15058: sys.path.append()
-+--
   Reporter:  daghenrik  | Owner:  nobody
 Status:  reopened   | Milestone:
  Component:  Documentation  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--

Comment (by aaugustin):

 Russell, I just attached a proposal, but I'm not sure it is what you had
 in mind.

 It should at least be more beginner-friendly than the current doc.

-- 
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] #15254: 1.1.4 release notes missing from trunk

[Django]

#15254: 1.1.4 release notes missing from trunk
-+--
   Reporter:  gwilson| Owner:  nobody
 Status:  closed | Milestone:
  Component:  Documentation  |   Version:  SVN   
 Resolution:  fixed  |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by aaugustin):

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


Comment:

 This was fixed at r15482.

-- 
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] #15185: Ability to make all list_display fields not clickable

[Django]

#15185: Ability to make all list_display fields not clickable
+---
   Reporter:  rm_   | Owner:  nobody

 Status:  new   | Milestone:

  Component:  django.contrib.admin  |   Version:  1.2   

 Resolution:|  Keywords:  
list_display_links
   Triage Stage:  Accepted  | Has patch:  0 

Needs documentation:  0 |   Needs tests:  0 

Patch needs improvement:  0 |  
+---

Comment (by julien):

 See #11561 for another use case where the `has_change_permission` gets in
 the way of displaying the change 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] #11561: raw_id_fields requires that the user has change permissions on the model class that is being linked to

[Django]

#11561: raw_id_fields requires that the user has change permissions on the model
class that is being linked to
+---
   Reporter:  dhowden@… | Owner:  nobody
   
 Status:  new   | Milestone:  2.0   
   
  Component:  django.contrib.admin  |   Version:  1.0   
   
 Resolution:|  Keywords:  raw_if_fields 
permissions
   Triage Stage:  Accepted  | Has patch:  0 
   
Needs documentation:  0 |   Needs tests:  0 
   
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * milestone:  => 2.0


Comment:

 #15185 is another use case where the `has_change_permission` gets in the
 way of displaying the change list. I'm getting more and more incline to
 introduce a new "list" (or "read", or "view", or "browse") standard
 permission so you can display the "change" list without having change
 permissions. A bit like the difference that exist between "r" and "w" in
 the Unix file system. Now that might be something for version 2.0 as I
 imagine this would be seriously backwards incompatible.

-- 
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] #14705: Model Field Order not influenced by MRO of superclasses

[Django]

#14705: Model Field Order not influenced by MRO of superclasses
--+-
   Reporter:  vanschelven | Owner:  russellm
 Status:  new | Milestone:  1.3 
  Component:  Core framework  |   Version:  SVN 
 Resolution:  |  Keywords:  
   Triage Stage:  Accepted| Has patch:  1   
Needs documentation:  0   |   Needs tests:  0   
Patch needs improvement:  1   |  
--+-
Changes (by ambv):

  * owner:  nobody => russellm


Comment:

 The reason I introduced `model_bases` instead of rearranging half the
 framework around changes in `parents` was to keep the patch minimal (e.g.
 easier to get right). On top of that, I believe in backwards compatibility
 and I'm not sure if there isn't some 3rd party code using `parents` in
 ways that could have been broken by changing that.

 I am willing to help with any refactoring of Meta necessary. However, this
 is naturally milestone 1.4, e.g. over 9 months away. Could you please
 reassess whether we could integrate the patch as it is? Without that
 change I will need to basically fork Django until another stable release.
 This is not easy to monkey 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] #717: If-Modified-Since checked for exact match

[Django]

#717: If-Modified-Since checked for exact match
---+
   Reporter:  Maniac | Owner: 
 adrian   
 Status:  reopened | Milestone: 
  
  Component:  HTTP handling|   Version: 
  
 Resolution:   |  Keywords: 
 http middleware conditional get if-modified-since
   Triage Stage:  Accepted | Has patch: 
 1
Needs documentation:  0|   Needs tests: 
 0
Patch needs improvement:  0|  
---+
Changes (by aaugustin):

 * cc: aaugustin (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] #717: If-Modified-Since checked for exact match

[Django]

#717: If-Modified-Since checked for exact match
---+
   Reporter:  Maniac | Owner: 
 adrian   
 Status:  reopened | Milestone: 
  
  Component:  HTTP handling|   Version: 
  
 Resolution:   |  Keywords: 
 http middleware conditional get if-modified-since
   Triage Stage:  Accepted | Has patch: 
 1
Needs documentation:  0|   Needs tests: 
 0
Patch needs improvement:  0|  
---+
Changes (by aaugustin):

  * needs_better_patch:  1 => 0
  * needs_tests:  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.

Re: [Django] #717: If-Modified-Since checked for exact match

[Django]

#717: If-Modified-Since checked for exact match
---+
   Reporter:  Maniac | Owner: 
 adrian   
 Status:  reopened | Milestone: 
  
  Component:  HTTP handling|   Version: 
  
 Resolution:   |  Keywords: 
 http middleware conditional get if-modified-since
   Triage Stage:  Accepted | Has patch: 
 1
Needs documentation:  0|   Needs tests: 
 1
Patch needs improvement:  1|  
---+

Comment (by aaugustin):

 New patch:
 - builds upon julianb's last patch, but does much less changes to
 django/views/decorators/http.py,
 - adds a `parse_http_date` function in `django.utils.http` that implements
 a RFC-compliant parsing of HTTP dates, and uses it wherever ad-hoc parsing
 was implemented; that function may be simplified with
 email.Utils.parsedate if RFC compliance is not required;
 - adds tests for !ConditionalGetMiddleware (fairly similar to the tests in
 conditional_processing, but those test the decorators and not the
 middleware),
 - fixes a related test that used UTC instead of GMT.

-- 
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] #6669: @transaction.commit_on_success does not rollback when it should

[Django]

#6669: @transaction.commit_on_success does not rollback when it should
+---
   Reporter:  james@…   | Owner:  
nobody 
 Status:  closed| Milestone:
 
  Component:  Database layer (models, ORM)  |   Version:  SVN   
 
 Resolution:  fixed |  Keywords:  
transaction, commit
   Triage Stage:  Accepted  | Has patch:  0 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---
Changes (by shai):

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


Comment:

 Fixed by [15493] (a fix for #9964, based on the patch mentioned in my
 earlier comment, and including the test quoted above).

-- 
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] #9964: Transaction middleware closes the transaction only when it's marked as dirty

[Django]

#9964: Transaction middleware closes the transaction only when it's marked as
dirty
+---
   Reporter:  ishirav   | Owner:  
mtredinnick 
 Status:  closed| Milestone:  1.3   
  
  Component:  Database layer (models, ORM)  |   Version:  
1.0-beta-1  
 Resolution:  fixed |  Keywords:  
transactions
   Triage Stage:  Ready for checkin | Has patch:  1 
  
Needs documentation:  0 |   Needs tests:  0 
  
Patch needs improvement:  0 |  
+---

Comment (by shai):

 Thanks a lot for the commit and kind words. Please note that, as the tests
 in that patch now pass -- specifically,
 `transactions_regress.tests.test_failing_query_transaction_closed` -- this
 also fixes #6669.

-- 
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] #14129: Fix Slovenian translation plural-forms

[Django]

#14129: Fix Slovenian translation plural-forms
+---
   Reporter:  gasperzejn| Owner:  jezdez
 Status:  new   | Milestone:  1.3   
  Component:  Translations  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by jezdez):

 FYI, we can't really fix this bug in Django since Transifex handles plural
 forms for us. I've filed a bug report there to make sure we don't forget
 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] #12990: New Field Type: JSONField

[Django]

#12990: New Field Type: JSONField
+---
   Reporter:  paltman   | Owner:  
nobody  
 Status:  new   | Milestone:
  
  Component:  Database layer (models, ORM)  |   Version:  
1.2-beta
 Resolution:|  Keywords:
  
   Triage Stage:  Design decision needed| Has patch:  1 
  
Needs documentation:  0 |   Needs tests:  0 
  
Patch needs improvement:  0 |  
+---
Changes (by NicoEchaniz):

 * cc: NicoEchaniz (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] #15281: Staticfiles sever view should use generator

[Django]

#15281: Staticfiles sever view should use generator
--+-
   Reporter:  FunkyBob| Owner:  
 
 Status:  new | Milestone:  1.4 
 
  Component:  django.contrib.staticfiles  |   Version:  SVN 
 
 Resolution:  |  Keywords:  
generator
   Triage Stage:  Accepted| Has patch:  1   
 
Needs documentation:  0   |   Needs tests:  1   
 
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

  * owner:  jezdez =>


-- 
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] #15281: Staticfiles sever view should use generator

[Django]

#15281: Staticfiles sever view should use generator
--+-
   Reporter:  FunkyBob| Owner:  jezdez  
 
 Status:  new | Milestone:  1.4 
 
  Component:  django.contrib.staticfiles  |   Version:  SVN 
 
 Resolution:  |  Keywords:  
generator
   Triage Stage:  Accepted| Has patch:  1   
 
Needs documentation:  0   |   Needs tests:  1   
 
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

  * milestone:  1.3 => 1.4


Comment:

 Hm, not sure actually that we can fix this in 1.3 since a lot more core
 things seem to be involved in that. E.g. I wasn't able to let the static
 view tests pass with that patch. Pushing to 1.4 since we are so close to a
 RC.

-- 
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] #15289: New transaction behavior only works if DEBUG=False

[Django]

#15289: New transaction behavior only works if DEBUG=False
--+-
 Reporter:  apollo13  |  Owner:  nobody
   Status:  new   |  Milestone:  1.3   
Component:  Database layer (models, ORM)  |Version:  SVN   
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  
--+-
 CursorDebugWrapper defines it's own !__getattr!__ and as such eliminates
 the effect of
 
http://code.djangoproject.com/browser/django/trunk/django/db/backends/util.py?rev=15493#L18
 I also never get a dirty transaction if in autocommit mode, is this wanted
 behavior? Patch for the first one would be just removing !__getattr!__,
 not sure about the later 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] #14806: No template tag to support contextual translations

[Django]

#14806: No template tag to support contextual translations
+---
   Reporter:  jtiai | Owner:  nobody
 Status:  new   | Milestone:  1.4   
  Component:  Internationalization  |   Version:  SVN   
 Resolution:|  Keywords:  i18n  
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by jezdez):

  * version:  1.3-alpha => SVN
  * milestone:  => 1.4


Comment:

 Unfortunately we are in feature freeze mode, pushing to 1.4.

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

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

Re: [Django] #5518: Capitalized verbose names for models (was: [newform-admin] - capitalized verbose names for models)

[Django]

#5518: Capitalized verbose names for models
-+--
   Reporter:  Petr Marhoun   | 
Owner:  nobody 
 Status:  reopened   | 
Milestone: 
  Component:  Internationalization   |   
Version:  newforms-admin 
 Resolution: |  
Keywords:  admin, verbose_name, nfa-someday i18n-nofix
   Triage Stage:  Accepted   | Has 
patch:  0  
Needs documentation:  0  |   Needs 
tests:  0  
Patch needs improvement:  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] #15288: ManyToManyField doesn't highlight currently selected items in Admin where target is a proxy object.

[Django]

#15288: ManyToManyField doesn't highlight currently selected items in Admin 
where
target is a proxy object.
---+
 Reporter:  anonymous  |  Owner:  nobody
   Status:  new|  Milestone:
Component:  Forms  |Version:  1.2   
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  
---+
 I've implemented my own single-table inheritance by creating a base class
 with all the fields I need, plus a 'type' field to contain the subclass
 objects should be instantiated as.

 I've got two subclasses which are proxies for the main class, each with a
 custom model manager to filter results by the appropriate class.

 This works almost everywhere except in the admin area. I've got a
 ManyToMany relationship defined on a class that references one of these
 proxy objects.

 When I select some of these proxy objects in the admin and save the form,
 the database is correctly updated, but the select form widget doesn't
 highlight the selected items.

 This affects at least django 1.2.3 to 1.2.4.

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

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

Re: [Django] #15125: UpdateView should introspect form_class instead of requiring you to pass the model

[Django]

#15125: UpdateView should introspect form_class instead of requiring you to pass
the model
-+--
   Reporter:  sontek | Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Generic views  |   Version:  SVN   
 Resolution: |  Keywords:
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by jezdez):

  * needs_better_patch:  1 => 0
  * stage:  Accepted => Ready for checkin


-- 
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] #14282: Add Guatemala to Localflavors

[Django]

#14282: Add Guatemala to Localflavors
--+-
   Reporter:  dmonroy | Owner:  nobody  
  
 Status:  new | Milestone:  1.4 
  
  Component:  django.contrib.localflavor  |   Version:  1.2 
  
 Resolution:  |  Keywords:  
Guatemalan
   Triage Stage:  Accepted| Has patch:  1   
  
Needs documentation:  1   |   Needs tests:  1   
  
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

  * milestone:  1.3 => 1.4


Comment:

 Pushed to 1.4 since we are way over the feature freeze date.

-- 
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] #14249: Inactive users have less permissions then anonymous users with custom backend

[Django]

#14249: Inactive users have less permissions then anonymous users with custom
backend
--+-
   Reporter:  hvdklauw| Owner:  nobody   
 Status:  closed  | Milestone:  1.3  
  Component:  Authentication  |   Version:  1.3-alpha
 Resolution:  fixed   |  Keywords:   
   Triage Stage:  Accepted| Has patch:  1
Needs documentation:  0   |   Needs tests:  0
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

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


Comment:

 Closing after giving this a bit more 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] #15272: Context object name is translated string

[Django]

#15272: Context object name is translated string
-+--
   Reporter:  szczav | Owner:  nobody   
 
 Status:  new| Milestone:  1.3  
 
  Component:  Generic views  |   Version:  SVN  
 
 Resolution: |  Keywords:  generic views 
context verbose_name blocker
   Triage Stage:  Accepted   | Has patch:  1
 
Needs documentation:  1  |   Needs tests:  0
 
Patch needs improvement:  1  |  
-+--
Changes (by vicvicvic):

 * cc: victor.andree@… (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] #13007: Django fails to log in when a cookie is set on the same domain containing a colon

[Django]

#13007: Django fails to log in when a cookie is set on the same domain 
containing a
colon
-+--
   Reporter:  Warlax | Owner:  nobody   
 
 Status:  reopened   | Milestone:  1.3  
 
  Component:  HTTP handling  |   Version:  SVN  
 
 Resolution: |  Keywords:  cookies, 
sprintdec2010
   Triage Stage:  Ready for checkin  | Has patch:  1
 
Needs documentation:  0  |   Needs tests:  0
 
Patch needs improvement:  0  |  
-+--
Changes (by jezdez):

  * stage:  Accepted => Ready for checkin


-- 
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] #12982: Add get_or_set method to cache API (was: Pony: cache.get_or_set())

[Django]

#12982: Add get_or_set method to cache API
--+-
   Reporter:  Alex| Owner:  jmeed
 Status:  assigned| Milestone:  1.4  
  Component:  Core framework  |   Version:  SVN  
 Resolution:  |  Keywords:  cache
   Triage Stage:  Accepted| Has patch:  1
Needs documentation:  0   |   Needs tests:  0
Patch needs improvement:  0   |  
--+-
Changes (by jezdez):

  * milestone:  1.3 => 1.4


Comment:

 Removing 1.3 milestone since we are way over the feature freeze.

-- 
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] #13007: Django fails to log in when a cookie is set on the same domain containing a colon

[Django]

#13007: Django fails to log in when a cookie is set on the same domain 
containing a
colon
-+--
   Reporter:  Warlax | Owner:  nobody   
 
 Status:  reopened   | Milestone:  1.3  
 
  Component:  HTTP handling  |   Version:  SVN  
 
 Resolution: |  Keywords:  cookies, 
sprintdec2010
   Triage Stage:  Accepted   | Has patch:  1
 
Needs documentation:  0  |   Needs tests:  0
 
Patch needs improvement:  0  |  
-+--

Comment (by aaugustin):

 #7183 was a duplicate.

-- 
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] #7183: sessionid broken by jsession

[Django]

#7183: sessionid broken by jsession
--+-
   Reporter:  mbeattie| Owner:  nobody  
 Status:  closed  | Milestone:  
  Component:  HTTP handling   |   Version:  SVN 
 Resolution:  duplicate   |  Keywords:  wsgi session
   Triage Stage:  Design decision needed  | Has patch:  1   
Needs documentation:  0   |   Needs tests:  1   
Patch needs improvement:  1   |  
--+-
Changes (by aaugustin):

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


Comment:

 The original cause of the problem is the colon in the cookie name. This
 problem is discussed at length is #13007.

-- 
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] #10762: Gzip Middleware Should Compress 201 (Created) Responses

[Django]

#10762: Gzip Middleware Should Compress 201 (Created) Responses
+---
   Reporter:  rwagner@… | Owner:  nobody
 
 Status:  new   | Milestone:
 
  Component:  HTTP handling |   Version:  SVN   
 
 Resolution:|  Keywords:  
middleware gzip
   Triage Stage:  Design decision needed| Has patch:  1 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---

Comment (by aaugustin):

 The comment in `gzip.py` say: "It's not worth compressing non-OK or really
 short responses."

 If non-OK responses are not worth compressing because they are expected to
 be short, testing their length is enough, which means the check on
 `response.status_code` should be removed.

 If there is another reason why non-OK responses should not be compressed,
 the proper check is `200 <= response.status_code < 300`, and the reason
 should be explained in a comment.

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

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

Re: [Django] #6880: django.http.get_host() breaks reverse proxying on apache

[Django]

#6880: django.http.get_host() breaks reverse proxying on apache
--+-
   Reporter:  Kellen  | Owner:  nobody  
 
 Status:  new | Milestone:  
 
  Component:  HTTP handling   |   Version:  SVN 
 
 Resolution:  |  Keywords:  redirect 
httpresponseredirect get_host reverse proxy squid apache
   Triage Stage:  Design decision needed  | Has patch:  1   
 
Needs documentation:  0   |   Needs tests:  0   
 
Patch needs improvement:  0   |  
--+-

Comment (by aaugustin):

 #9064 shows that it is complicated to interpret `X-FORWARDED-HOST` when
 there is more than one proxy. It is also unnecessary when the proxies are
 properly configured. So it may be a good idea to drop it. That would close
 both this bug and #9064.

 Attached patch:
 - no longer interprets the `X-FORWARDED-HOST` header, as suggested in
 #6548, #9064, and `get_hostpatch.txt` posted by Kellen above,
 - removes a complicated warning in the docs about that header.

 This will certainly not make it in 1.3 so `versionchanged` must be changed
 to something other than 1.3 when applying the patch.

 Obviously, that would be slightly backwards incompatible, but `get_host`
 is already broken anyway for people who expect it to handle proxies. Is it
 necessary to mention it in the release notes?

-- 
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] #15287: Error messages in generic views are partialy translated

[Django]

#15287: Error messages in generic views are partialy translated
-+--
   Reporter:  szczav | Owner:  nobody   
  
 Status:  new| Milestone:   
  
  Component:  Generic views  |   Version:  SVN  
  
 Resolution: |  Keywords:  generic views 
http404 translation error
   Triage Stage:  Unreviewed | Has patch:  1
  
Needs documentation:  0  |   Needs tests:  0
  
Patch needs improvement:  0  |  
-+--
Changes (by szczav):

  * needs_better_patch:  => 0
  * has_patch:  0 => 1
  * 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] #15287: Error messages in generic views are partialy translated

[Django]

#15287: Error messages in generic views are partialy translated
-+--
 Reporter:  szczav   |  Owner:  nobody  
  
   Status:  new  |  Milestone:  
  
Component:  Generic views|Version:  SVN 
  
 Keywords:  generic views http404 translation error  |   Triage Stage:  
Unreviewed
Has patch:  0|  
-+--
 Http404 error messages in class based generic views are not translated,
 but model names passed to them are. Example:
 raise Http404("No %s available" % model._meta.verbose_name)

 Messages should be translated completely or not translated at all. As I
 see in Django source code they are almost always not translated. I think
 that ```model._meta.verbose_name``` should be replaced by
 ```model._meta.object_name```.

 It's related with #12418.

-- 
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] #15272: Context object name is translated string

[Django]

#15272: Context object name is translated string
-+--
   Reporter:  szczav | Owner:  nobody   
 
 Status:  new| Milestone:  1.3  
 
  Component:  Generic views  |   Version:  SVN  
 
 Resolution: |  Keywords:  generic views 
context verbose_name blocker
   Triage Stage:  Accepted   | Has patch:  1
 
Needs documentation:  1  |   Needs tests:  0
 
Patch needs improvement:  1  |  
-+--

Comment (by szczav):

 I've removed error message fixes (I'll create separate ticket on this) and
 added docs. Way how context variables are created is described in docs, so
 I've just rewritten it. By the way ```get_context_object_name()```
 description for the ```SingleObjectMixin``` was completely wrong before.

 Idea of #14018 is good but as I see its milestone is 2.0 so probably we
 have to stay with ```object_name``` concept.

-- 
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] #9064: Redirect is broken when HTTP_X_FORWARDED_HOST contains multiple hosts

[Django]

#9064: Redirect is broken when HTTP_X_FORWARDED_HOST contains multiple hosts
-+--
   Reporter:  Artur  | Owner:  nobody
 Status:  new| Milestone:
  Component:  HTTP handling  |   Version:  1.0   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  1  |  
-+--

Comment (by aaugustin):

 The question here is "how to use `X-FORWARDED-HOST`?", but #6880 asks
 "should we use `X-FORWARDED-HOST` at all?" and contains a patch to not use
 it anymore. If this patch is applied, the problem discussed here vanishes.

 `get_host` is the only place in Django that uses the non-standard `X
 -FORWARDED-HOST` header. I think removing it is the correct way to go:
 - Like mtredinnick said, reverse proxies are supposed to do the rewrites
 both on the request and the response.
 - Developers with a weird proxy setup may write their own middleware to do
 tweak headers.
 - People using the remote address for geolocation are facing  very
 difficult problem, for which Django can not provide a generic solution.
 Consider the setup below: you would probably want the address of the
 Internet-facing proxy; how is Django supposed to find it in the list of 5
 IPs in `X-FORWARDED-HOST`?
 {{{
 user on private network -> internal proxy -> Internet-facing proxy ->
 load-balancer -> reverse proxy -> Django
 }}}

 Finally, even if a decent solution was found for this problem, there would
 still be a parallel issue with `is_secure` (see also #6548) as proxies can
 convert from HTTP to HTTPS and vice-versa. I do not know how that one
 could be resolved.

-- 
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] #14705: Model Field Order not influenced by MRO of superclasses

[Django]

#14705: Model Field Order not influenced by MRO of superclasses
--+-
   Reporter:  vanschelven | Owner:  nobody
 Status:  new | Milestone:  1.3   
  Component:  Core framework  |   Version:  SVN   
 Resolution:  |  Keywords:
   Triage Stage:  Accepted| Has patch:  1 
Needs documentation:  0   |   Needs tests:  0 
Patch needs improvement:  1   |  
--+-
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * stage:  Ready for checkin => Accepted


Comment:

 This patch appears to be headed broadly in the right direction, and it
 works, but I'm not convinced that it's quite right yet.

 In particular, the fact that it is introducing a new `model_bases`
 attribute to the Meta class when `parents` already exists concerns me.
 Granted, the two aren't completely identical -- parents doesn't include
 any abstract classes, for example -- but it strikes me that the right
 solution here isn't just to add a new block of almost identical metadata,
 but to adjust the existing metadata, and adjust the existing usage.

 The Meta class is in bad need of some housekeeping -- I'd rather not
 knowingly add to that housekeeping 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.

Re: [Django] #6548: django behind apache ssl proxy

[Django]

#6548: django behind apache ssl proxy
--+-
   Reporter:  laureline.guerin@…  | Owner:  
nobody
 Status:  closed  | Milestone:  
  
  Component:  HTTP handling   |   Version:  
SVN   
 Resolution:  duplicate   |  Keywords:  
  
   Triage Stage:  Design decision needed  | Has patch:  
0 
Needs documentation:  0   |   Needs tests:  
0 
Patch needs improvement:  0   |  
--+-
Changes (by aaugustin):

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


Comment:

 This is a duplicate of #6880. The issue in both tickets is that Django
 tries to perform some magic by using the non-standard (and insecure) X
 -Forwarded-For header, and that breaks redirects.

 The latest patch for #6880 implements the first option offered by the OP:
 remove test for X-FORWARDED-HOST in get_host.

-- 
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] #14129: Fix Slovenian translation plural-forms

[Django]

#14129: Fix Slovenian translation plural-forms
+---
   Reporter:  gasperzejn| Owner:  jezdez
 Status:  new   | Milestone:  1.3   
  Component:  Translations  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by jezdez):

  * owner:  nobody => jezdez
  * status:  reopened => 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] #11576: FilterSpec and Null values

[Django]

#11576: FilterSpec and Null values
+---
   Reporter:  twiinz@…  | Owner:  nobody
 Status:  closed| Milestone:
  Component:  django.contrib.admin  |   Version:  1.0   
 Resolution:  duplicate |  Keywords:  FilterSpec
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by julien):

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


Comment:

 Dupe of #8528.

-- 
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] #12646: Flawed error display in admin when using fieldsets.

[Django]

#12646: Flawed error display in admin when using fieldsets.
+---
   Reporter:  schinckel | Owner:  nobody   
 Status:  closed| Milestone:   
  Component:  django.contrib.admin  |   Version:  1.1  
 Resolution:  fixed |  Keywords:  design_ux
   Triage Stage:  Accepted  | Has patch:  0
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---
Changes (by julien):

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


Comment:

 I'm pretty sure this was fixed in [14999].

-- 
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] #13735: Broken filter block

[Django]

#13735: Broken filter block
+---
   Reporter:  tonnzor   | Owner:  nobody
 Status:  new   | Milestone:
  Component:  django.contrib.admin  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by julien):

 I can't seem to be able to reproduce this. Could you provide some source
 code that we can test?

-- 
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] #15284: CSRF/Ajax/jQuery example could break other site JS

[Django]

#15284: CSRF/Ajax/jQuery example could break other site JS
-+--
   Reporter:  LukeMaurer | Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Documentation  |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Accepted   | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--

Comment (by lukeplant):

 I was aware of that problem with beforeSend, but I hadn't realised that
 you could actually alter the XHR request in ajaxSend. This is potentially
 fragile (the docs only give examples of reading the XHR object, not
 altering it), but it seems unlikely to break, so I agree that we should
 change 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] #14129: Fix Slovenian translation plural-forms

[Django]

#14129: Fix Slovenian translation plural-forms
+---
   Reporter:  gasperzejn| Owner:  nobody
 Status:  reopened  | Milestone:  1.3   
  Component:  Translations  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by jezdez):

  * milestone:  => 1.3


Comment:

 Yeah, we can do this, is the attached patch the one to commit?

-- 
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] #14129: Fix Slovenian translation plural-forms

[Django]

#14129: Fix Slovenian translation plural-forms
+---
   Reporter:  gasperzejn| Owner:  nobody
 Status:  reopened  | Milestone:
  Component:  Translations  |   Version:  1.2   
 Resolution:|  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by gasperzejn):

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


Comment:

 After a discussion with fellow translators, we've decided we should adopt
 the new equation.

 Can we do this before 1.3 release?

-- 
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] #14129: Fix Slovenian translation plural-forms

[Django]

#14129: Fix Slovenian translation plural-forms
+---
   Reporter:  gasperzejn| Owner:  nobody
 Status:  closed| Milestone:
  Component:  Translations  |   Version:  1.2   
 Resolution:  invalid   |  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---

Comment (by claudep):

 Yes, the current equation is valid. It's just that more and more projects
 are using another one. Read the rationale here:
 https://answers.launchpad.net/launchpad/+question/18324
 See also: http://translate.sourceforge.net/wiki/l10n/pluralforms

 But as sl coordinator, you are the one to decide :-)

-- 
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] #14129: Fix Slovenian translation plural-forms

[Django]

#14129: Fix Slovenian translation plural-forms
+---
   Reporter:  gasperzejn| Owner:  nobody
 Status:  closed| Milestone:
  Component:  Translations  |   Version:  1.2   
 Resolution:  invalid   |  Keywords:
   Triage Stage:  Accepted  | Has patch:  1 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by gasperzejn):

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


Comment:

 Uh, seems I made a mistake and haven't double checked the plural equation
 after a bug report from a user.

 Please discard this patch as the current plural equation is valid. I'm
 closing this bug as invalid.

 Thanks.

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

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

Re: [Django] #15285: Example in Topic/Testing refer to django.utils.unittest

[Django]

#15285: Example in Topic/Testing refer to django.utils.unittest
---+
   Reporter:  kamal.mustafa@…  | Owner:  nobody 
 Status:  new  | Milestone: 
  Component:  Documentation|   Version:  1.2
 Resolution:   |  Keywords:  testing
   Triage Stage:  Accepted | Has patch:  0  
Needs documentation:  0|   Needs tests:  0  
Patch needs improvement:  0|  
---+
Changes (by lrekucki):

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


Comment:

 This is an error in the docs.

-- 
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] #15286: PendingDeprecationWarning shown even when LOCALE_PATHS contains /locale

[Django]

#15286: PendingDeprecationWarning shown even when LOCALE_PATHS contains /locale
--+-
 Reporter:  claudep   |  Owner:  nobody
   Status:  new   |  Milestone:  1.3   
Component:  Internationalization  |Version:  1.3-beta  
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  1 |  
--+-
 The new PendingDeprecationWarning about a project /locale directory does
 appear even when you add this directory in settings.LOCALE_PATH. I find
 this unneeded and distracting.

-- 
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] #13833: Fix for Indonesian localization (formats.py) (was: Fix for Indonesian localization)

[Django]

#13833: Fix for Indonesian localization (formats.py)
-+--
   Reporter:  rodin  | Owner:  nobody
 Status:  new| Milestone:  1.3   
  Component:  Translations   |   Version:  1.2   
 Resolution: |  Keywords:
   Triage Stage:  Ready for checkin  | Has patch:  1 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--
Changes (by claudep):

 * cc: claude@… (added)
  * needs_better_patch:  1 => 0
  * milestone:  => 1.3
  * stage:  Accepted => Ready for checkin


Comment:

 Thanks, the patch looks good.

 Note however that there are still many references that seem to use the ":"
 for hour separation, notably CLDR:
 http://unicode.org/repos/cldr/trunk/common/main/id.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] #13948: The sort arrows on the UI for the admin list display are backwards

[Django]

#13948: The sort arrows on the UI for the admin list display are backwards
+---
   Reporter:  jsdalton  | Owner:  nobody
 Status:  new   | Milestone:  1.3   
  Component:  django.contrib.admin  |   Version:  SVN   
 Resolution:|  Keywords:
   Triage Stage:  Ready for checkin | Has patch:  0 
Needs documentation:  0 |   Needs tests:  0 
Patch needs improvement:  0 |  
+---
Changes (by julien):

  * stage:  Accepted => Ready for checkin
  * milestone:  => 1.3


Comment:

 Hopefully the patch is trivial enough to allow me to RFC 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] #15132: The runserver command is missing --verbosity and --traceback

[Django]

#15132: The runserver command is missing --verbosity and --traceback
-+--
   Reporter:  cardonbj   | Owner:  nobody
 Status:  closed | Milestone:
  Component:  django-admin.py runserver  |   Version:  1.2   
 Resolution:  wontfix|  Keywords:
   Triage Stage:  Unreviewed | Has patch:  0 
Needs documentation:  0  |   Needs tests:  0 
Patch needs improvement:  0  |  
-+--

Comment (by admackin):

 Surely it should do what it used to do in the past? According to the
 discussion here, it existed in an old SVN revision:

 http://groups.google.com/group/django-
 
users/browse_thread/thread/83d603b7aa6bc067/98bbee8c4bbfe824?lnk=gst=runserver+traceback#98bbee8c4bbfe824

 So if it could have worked once, can't it be made to work again?

 (I've got a similar problem to the OP -- this is something I would dearly
 like to reappear)

-- 
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] #14206: contrib:admin dynamic list_display support

[Django]

#14206: contrib:admin dynamic list_display support
+---
   Reporter:  gabejackson   | Owner:  nobody
 
 Status:  new   | Milestone:
 
  Component:  django.contrib.admin  |   Version:  1.2   
 
 Resolution:|  Keywords:  list_display 
override dynamic admin
   Triage Stage:  Accepted  | Has patch:  0 
 
Needs documentation:  0 |   Needs tests:  0 
 
Patch needs improvement:  0 |  
+---

Comment (by julien):

 This could be implemented in a similar way as `get_readonly_fields`.

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

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

Re: [Django] #14251: app-labels (still) not translated

[Django]

#14251: app-labels (still) not translated
-+--
   Reporter:  sehmaschine@…  | Owner:  nobody   
  
 Status:  closed | Milestone:   
  
  Component:  django.contrib.admin   |   Version:  1.2  
  
 Resolution:  duplicate  |  Keywords:  
soc2010/app-loading
   Triage Stage:  Fixed on a branch  | Has patch:  0
  
Needs documentation:  0  |   Needs tests:  0
  
Patch needs improvement:  0  |  
-+--
Changes (by julien):

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


Comment:

 Dupe of #10436.

-- 
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] #15285: Example in Topic/Testing refer to django.utils.unittest

[Django]

#15285: Example in Topic/Testing refer to django.utils.unittest
-+--
 Reporter:  kamal.mustafa@…  |  Owner:  nobody
   Status:  new  |  Milestone:
Component:  Documentation|Version:  1.2   
 Keywords:  testing  |   Triage Stage:  Unreviewed
Has patch:  0|  
-+--
 I'm reading http://docs.djangoproject.com/en/1.2/topics/testing/ and
 there's example:-

 {{{
 from django.utils import unittest
 from myapp.models import Animal

 class AnimalTestCase(unittest.TestCase):
 def setUp(self):
 self.lion = Animal.objects.create(name="lion", sound="roar")
 self.cat = Animal.objects.create(name="cat", sound="meow")

 def testSpeaking(self):
 self.assertEqual(self.lion.speak(), 'The lion says "roar"')
 self.assertEqual(self.cat.speak(), 'The cat says "meow"')
 }}}

 And this is how I installed Django:-

 {{{
 $ mkvirtualenv testdjango
 $ pip install Django==1.2
 $ python
 >>> import django
 >>> django.get_version()
 '1.2'
 >>> import django.utils.unittest
 Traceback (most recent call last):
   File "", line 1, in 
 ImportError: No module named unittest
 >>> from django.utils import unittest
 Traceback (most recent call last):
   File "", line 1, in 
 ImportError: cannot import name unittest
 }}}

 Got the same result with "pip install Django==1.2.4"

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

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

Re: [Django] #14832: Impossible to create inline objects if form validates but is unchanged

[Django]

#14832: Impossible to create inline objects if form validates but is unchanged
+---
   Reporter:  julien| Owner:  nobody   
 Status:  new   | Milestone:   
  Component:  django.contrib.admin  |   Version:  1.2  
 Resolution:|  Keywords:  sprintdec2010
   Triage Stage:  Accepted  | Has patch:  0
Needs documentation:  0 |   Needs tests:  0
Patch needs improvement:  0 |  
+---

Comment (by julien):

 #15174 was closed as dupe (different use case but essentially 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] #15174: Add a required inline on django admin

[Django]

#15174: Add a required inline on django admin
+---
   Reporter:  zodman| Owner:  nobody
   
 Status:  closed| Milestone:
   
  Component:  django.contrib.admin  |   Version:  SVN   
   
 Resolution:  duplicate |  Keywords:  
inlines,formset,admin
   Triage Stage:  Accepted  | Has patch:  0 
   
Needs documentation:  0 |   Needs tests:  0 
   
Patch needs improvement:  0 |  
+---
Changes (by julien):

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


Comment:

 This is essentially a dupe of #14832. That is one tough problem to
 solve...

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