Re: [Django] #14082: modelform_factory should use the form's metaclass

[Django]

#14082: modelform_factory should use the form's metaclass
-+-
   Reporter:  jspiros|  Owner:  Honza_Kral
   Type:  Bug| Status:  reopened
  Milestone: |  Component:  Forms
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:  ModelForm,
   Triage Stage:  Accepted   |  ModelFormMetaclass,
Needs documentation:  0  |  modelform_factory
Patch needs improvement:  0  |  Has patch:  1
 |Needs tests:  0
 |  Easy pickings:  0
-+-
Changes (by melinath):

 * type:  New feature => Bug
 * needs_tests:  1 => 0
 * easy:   => 0


Comment:

 Updated the patch to r16322 - tests run with no unexpected failures. Added
 tests that fail iff the patch is not applied. Changed type to Bug since an
 erroneous behavior is being corrected.

-- 
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] #13956: Indefinite args for simpletags and inclusion tags

[Django]

#13956: Indefinite args for simpletags and inclusion tags
-+-
   Reporter:  melinath   |  Owner:  gregmuellegger
   Type:  New| Status:  assigned
  feature|  Component:  Template system
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  simple_tag,
 Resolution: |  simpletag
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+-
Changes (by melinath):

 * needs_better_patch:  1 => 0


Comment:

 Updated the patch to r16322. Applies cleanly with no unexpected test
 failures.

-- 
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] #16152: Add Sybase Advantage Database Server to 3rd Party DB List

[Django]

#16152: Add Sybase Advantage Database Server to 3rd Party DB List
-+---
   Reporter:  mike.hagman@…  |  Owner:  nobody
   Type:  New feature| Status:  new
  Milestone: |  Component:  Documentation
Version:  SVN|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
-+---

Comment (by russellm):

 There's one minor issue that requires clarification -- What's the
 relationship with Sybase SQL Anywhere and Sybase Advantage? Is it
 appropriate for both links to exist, or does one link deprecate the other?

 If the original poster can clarify this point, I'm happy for this to go
 direct to Ready For Checkin -- The change is trivial, so no patch 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] #16153: Admin.py ignores some models when registering...

[Django]

#16153: Admin.py ignores some models when registering...
---+---
   Reporter:  jake.logemann@…  |  Owner:  nobody
   Type:  Bug  | Status:  closed
  Milestone:   |  Component:  contrib.admin
Version:  1.3  |   Severity:  Normal
 Resolution:  worksforme   |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
---+---
Changes (by julien):

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


Comment:

 I can't reproduce this problem given the code you've provided. I suspect
 it could be because the user doesn't have the proper User Permission. Or
 there might also be something weird caused by the "`import *"` -- try
 importing specifically the models that you need and see whether that fixes
 it. In any case, it is not apparent that there is a bug in Django. You may
 reopen this ticket if you can provide a reproducible test case, otherwise
 you should ask for help on django-users.

-- 
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] #16153: Admin.py ignores some models when registering...

[Django]

#16153: Admin.py ignores some models when registering...
-+---
 Reporter:  jake.logemann@…  |  Owner:  nobody
 Type:  Bug  | Status:  new
Milestone:   |  Component:  contrib.admin
  Version:  1.3  |   Severity:  Normal
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
-+---
 In my Admin.py for an app (called buildings.py) I import all of the models
 and list them, or try to at least. Log will display on the Admin page
 while BankAccount wont. I've restarted the dev server, tried deleting the
 .pyc file. Im out of ideas. Im using the most basic form of
 admin.site.register that I can, but I've tried defining the class and it
 doesnt help.

 {{{
 from apps.buildings.models import *

 class LogAdmin(admin.ModelAdmin):
   list_display = ('building', 'title', 'body', 'logged_at')
   list_display_links = ('title',)
   list_filter = ('logged_at', 'visibility')
   search_fields = ['building']

 admin.site.register(BankAccount)
 admin.site.register(Log,  LogAdmin)
 }}}

 Log is viewable in the admin area, bank accounts are not.
 Here are the models...
 {{{
 from datetime import datetime
 from django.db import models
 from django.contrib.auth.models import User
 from django.contrib.contenttypes.models import ContentType
 from django.contrib.contenttypes import generic

 from apps.world.models import *

 VISI_LOG_CHOICES = (
 (0, u'Admin-Only'),
 (1, u'Owner-Only'),
 (2, u'Managers'),
 (3, u'Employees'),
 (4, u'Public'),
 )

 class Log(models.Model):
   building = models.ForeignKey(Building, related_name='log_building')
   title = models.CharField(max_length=255, verbose_name="Job Title")
   body = models.CharField(max_length=255, verbose_name="Job Title")
   visibility = models.IntegerField(choices=VISI_LOG_CHOICES)
   logged_at = models.DateTimeField( default = datetime.now() )


   def __unicode__(self):
 return self.title

 class BankAccount(models.Model):
   nickname = models.CharField( max_length = 50, blank = True )
   rate = models.DecimalField( max_digits = 6, decimal_places = 4,
 default='0.' )
   balance  = models.DecimalField(
  max_digits = 19,
  decimal_places = 2,
  default = '0.00'
 )}}}
 Seems like a bug to me! Maybe my eyes are tired.

-- 
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] #16089: Adding/Removing admin Inlines on the fly

[Django]

#16089: Adding/Removing admin Inlines on the fly
-+-
   Reporter:  sheep2 |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  1
  decision needed|  Easy pickings:  0
Needs documentation:  1  |
Patch needs improvement:  1  |
-+-

Comment (by julien):

 What doesn't feel right with this proposal is that it is explicitly about
 *undoing* things. There are at least two problems with that: a) It is too
 tightly coupled with the admin's internal implementation and therefore it
 is likely to diminish the admin's flexibility in the long term; and b)
 Instead of undoing something that has been done, it is best to not do it
 in the first place (i.e. don't register an inline only to unregister it
 later).

 The usual pattern in the admin is to provide hooks to *override*
 behaviours, not *undo* them. Currently inlines can only be registered
 declaratively with `ModelAdmin.inlines`, so to allow the flexibility that
 you're after it would be best to follow the usual pattern and wrap the
 declarative registration with a hook that can be overridden. See for
 example `ModelAdmin.get_prepopulated_fields()` or
 `ModelAdmin.get_readonly_fields()`.

 Inlines are also currently registered very early in the process, when the
 `ModelAdmin` class is instantiated. To make this work you would also have
 to move that registration later in the process (e.g. in the views) so that
 inlines can be selectively registered based on the request.

-- 
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] #16152: Add Sybase Advantage Database Server to 3rd Party DB List

[Django]

#16152: Add Sybase Advantage Database Server to 3rd Party DB List
---+---
 Reporter:  mike.hagman@…  |  Owner:  nobody
 Type:  New feature| Status:  new
Milestone: |  Component:  Documentation
  Version:  1.2|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
---+---
 Could you please add "Sybase Advantage Database Server" to the list of 3rd
 Party databases listed under the heading "Using a 3rd-party database
 backend" at the bottom of this site
 https://docs.djangoproject.com/en/dev/ref/databases/

 Here is the link to the Advantage Database Server Django support.
 http://code.google.com/p/adsdb-django/

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

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

Re: [Django] #16136: Error was: cannot import name utils

[Django]

#16136: Error was: cannot import name utils
-+-
   Reporter: |  Owner:  nobody
  kurvenschubser@…   | Status:  reopened
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by ramiro):

 I suspect this is strongly related:

 http://groups.google.com/group/django-
 users/browse_thread/thread/c354aa000fcbc87a?hl=en

 i.e. the cause of this breakage is a Python web stack setup problem in the
 hosting provider.

-- 
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] #16136: Error was: cannot import name utils

[Django]

#16136: Error was: cannot import name utils
-+-
   Reporter: |  Owner:  nobody
  kurvenschubser@…   | Status:  reopened
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by ramiro):

 Replying to [comment:12 anonymous]:
 > I just got a call from the sysadmin. They checked the settings.py and
 some other files, reset the server but to no avail. Tomorrow they are
 gonna upgrade to Py26. I am not holding my breath though, because I tried
 running locally with Py26 and Py25 (which they are using now) and they
 both worked equally well.

 Can you provide us with details of the mod_wsgi setups (embedded mode v.
 daemon mode, etc.) both in your shared hosting provider and in your local
 test environment?

-- 
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] #16136: Error was: cannot import name utils

[Django]

#16136: Error was: cannot import name utils
-+-
   Reporter: |  Owner:  nobody
  kurvenschubser@…   | Status:  reopened
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by anonymous):

 I just got a call from the sysadmin. They checked the settings.py and some
 other files, reset the server but to no avail. Tomorrow they are gonna
 upgrade to Py26. I am not holding my breath though, because I tried
 running locally with Py26 and Py25 (which they are using now) and they
 both worked equally well.

-- 
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] #16151: More informative message than "No fixtures found"

[Django]

#16151: More informative message than "No fixtures found"
--+--
 Reporter:  lsaffre   |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Milestone:|  Component:  Core (Serialization)
  Version:  1.3   |   Severity:  Normal
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
--+--
 When I run loaddata with a long list of fixture labels, and if for some of
 these there are no fixtures, then Django issues several times the message
 "No fixtures found." It would be more informative to mention the fixture
 name in  that message. I suggest to change one line in
 django/core/management/commands/loaddata.py:

 {{{
  if fixture_object_count == 0:
  if verbosity >= 1:
  self.stdout.write("No fixtures found.\n")
 }}}

 Change this to:

 {{{
  if fixture_object_count == 0:
  if verbosity >= 1:
  self.stdout.write("No %r fixtures found.\n" % fixture_name)
 }}}

-- 
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] #16089: Adding/Removing admin Inlines on the fly

[Django]

#16089: Adding/Removing admin Inlines on the fly
-+-
   Reporter:  sheep2 |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  1
  decision needed|  Easy pickings:  0
Needs documentation:  1  |
Patch needs improvement:  1  |
-+-

Comment (by sheep2):

 Replying to [comment:1 julien]:
 > Thanks for the suggestion. I do see how this could be useful in some
 cases. It needs further design discussion for the implementation, though.
 Fair enough, do you think there are design problems this fix would cause?

-- 
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] #16146: Calling functions with arguments inside a template

[Django]

#16146: Calling functions with arguments inside a template
-+-
   Reporter:  pmandel@…  |  Owner:  nobody
   Type:  New| Status:  closed
  feature|  Component:  Template system
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:  template, function
 Resolution:  wontfix|  Has patch:  0
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by lukeplant):

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


Comment:

 This change really would not fit with our template language at all, and
 there are many corner cases which mean that it simply will not behave the
 way you'd expect equivalent Python code to behave. For instance, there is
 the fact that `foo.bar` can mean `foo.bar` or `foo['bar']` or `foo.bar()`
 (or even `foo().bar` etc). The aim and ethos of Django templates is not to
 reproduce the full power of Python in the template language - in fact the
 opposite: you should not have to understand Python semantics to be able to
 write templates, or, very importantly, maintain templates written by other
 people.

 I don't know what you mean by "just try to include the request as an
 argument to the function call" - the template does not necessarily have
 any access to the request object.

 Regarding other ways to do this, instead of packing data a separate
 dictionary, you could directly annotate the objects you're passing into
 the template with any additional data, either as arbitrary attributes, or
 in a dictionary called e.g. 'extra' which is then attached to the object.
 So in the template you'd have `{% if a.extra.read %}`. This provides a
 simplified interface for the template to use.

 If you still disagree, please bring it up on the django-devs list -
 although I very strongly suspect that all the other core devs will say the
 same.

-- 
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] #16149: Allow disabling choices in a

[Django]

#16149: Allow disabling choices in a 
---+---
 Reporter:  scjody |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Milestone: |  Component:  Uncategorized
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
---+---
 We need to be able to disable choices in a , which is done by
 setting the disabled attribute on the  tag, for example:
 {{{Bananas}}}

 Currently we're doing this by subclassing the Select widget:
 http://djangosnippets.org/snippets/2453/

 It would be nice if the built in Select widget supported this.  One way
 would be to replace the existing render_option method with what I've
 written, and I can prepare a patch if desired, but this approach changes
 the format of the "choices" data structure to something that won't be
 understood by other widgets.  Perhaps these widgets should be improved
 too, but I don't want to do this unless the patch has a chance of being
 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] #9245: Using choices in a mode field forces use of TypedChoiceField in a form field

[Django]

#9245: Using choices in a mode field forces use of TypedChoiceField in a form
field
+--
   Reporter:  Tarken|  Owner:  badri
   Type:  Bug   | Status:  reopened
  Milestone:|  Component:  Forms
Version:  1.0   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  1 |  Easy pickings:  0
+--
Changes (by s.kuzmenko@…):

 * cc: s.kuzmenko@… (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] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
-+-
   Reporter: |  Owner:  bendavis78
  bendavis78 | Status:  closed
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:  admin sort
Version:  SVN|  multisort ordering order
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by kmtracey):

 Thanks Luke!

-- 
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] #16146: Calling functions with arguments inside a template

[Django]

#16146: Calling functions with arguments inside a template
-+-
   Reporter:  pmandel@…  |  Owner:  nobody
   Type:  New| Status:  reopened
  feature|  Component:  Template system
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:  template, function
 Resolution: |  Has patch:  0
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by anonymous):

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


Comment:

 Thanks for the update.  I'm mostly worried that people will start writing
 custom template tags to do just this (especially since it's a common
 feature in other web templating languages), similar to
 http://djangosnippets.org/snippets/424/.  Is the goal to provide an
 additional layer of security against people who only have access to the
 templates?  I agree that this is a fine goal, but I think that the
 alternatives (either pre-packing information you know you're going to want
 or being forced to write a custom template tag for each additional method
 you want to use) are un-pythonic and un-djangonic enough to warrant some
 kind of change.

 Perhaps just try to include the request as an argument to the function
 call, and don't if there's a TypeError for a mismatched number of
 arguments?

-- 
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] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
-+-
   Reporter: |  Owner:  bendavis78
  bendavis78 | Status:  closed
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:  admin sort
Version:  SVN|  multisort ordering order
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by lukeplant):

 Fixed in [16322]. The bug was really an old one - the existing way of
 changing the colour of those headers was a hack that worked if the cell
 wasn't too tall. I've done it properly 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.

[Changeset] r16322 - in django/trunk/django/contrib/admin/media: css img/admin

[noreply]

Author: lukeplant
Date: 2011-06-03 06:43:23 -0700 (Fri, 03 Jun 2011)
New Revision: 16322

Added:
   django/trunk/django/contrib/admin/media/img/admin/nav-bg-selected.gif
Modified:
   django/trunk/django/contrib/admin/media/css/base.css
Log:
Fixed visual bug with sorted column headers in changelist having dark band at 
top in some cases.

Modified: django/trunk/django/contrib/admin/media/css/base.css
===
--- django/trunk/django/contrib/admin/media/css/base.css2011-06-03 
11:54:47 UTC (rev 16321)
+++ django/trunk/django/contrib/admin/media/css/base.css2011-06-03 
13:43:23 UTC (rev 16322)
@@ -310,8 +310,8 @@
 display: block;
 }
 
-table thead th.sorted {
-background-position: bottom left !important;
+thead th.sorted {
+background: #c5c5c5 url(../img/admin/nav-bg-selected.gif) top left 
repeat-x;
 }
 
 table thead th.sorted a {

Added: django/trunk/django/contrib/admin/media/img/admin/nav-bg-selected.gif
===
(Binary files differ)


Property changes on: 
django/trunk/django/contrib/admin/media/img/admin/nav-bg-selected.gif
___
Added: svn:mime-type
   + application/octet-stream

-- 
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] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
-+-
   Reporter: |  Owner:  bendavis78
  bendavis78 | Status:  closed
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:  admin sort
Version:  SVN|  multisort ordering order
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by kmtracey):

 Hmm, screenshot was from Chromium 12.0.742.68 (86550) Ubuntu 10.04 but I
 am seeing similar behavior on Firefox (both 3.6.17 and 4.0.1). On further
 playing with it the behavior is not as consistent as I first thought --
 the headers can wrap without the bar appearing but then when I add another
 sort column the bar may appear, it may disappear if I remove one or may
 not...I've not yet figured out the pattern to what makes it show up.

-- 
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] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
-+-
   Reporter: |  Owner:  bendavis78
  bendavis78 | Status:  closed
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:  admin sort
Version:  SVN|  multisort ordering order
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by lukeplant):

 Cancel that - with a larger icon I can reproduce this, on several
 browsers, so it is an issue.

-- 
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] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
-+-
   Reporter: |  Owner:  bendavis78
  bendavis78 | Status:  closed
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:  admin sort
Version:  SVN|  multisort ordering order
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by lukeplant):

 I can't reproduce that with most recent Firefox, Opera or Chrome. It looks
 like you are using Chrome - what version? I tested Chrome 11 and 13, and
 couldn't reproduce that issue. That makes it seem like an old Chrome bug
 that is fixed in recent versions. I'm not sure we'll be able to do
 anything about that, unless there is an obvious work around.

-- 
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] #16148: get_object_or_404 hook feature

[Django]

#16148: get_object_or_404 hook feature
-+-
   Reporter: |  Owner:  nobody
  havelove@… | Status:  closed
   Type:  New|  Component:  Core (Other)
  feature|   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  0
 Resolution:  wontfix|Needs tests:  0
   Triage Stage:  Design |  Easy pickings:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by lukeplant):

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


Comment:

 I agree with aaugustin, closing on that basis. Thanks for the suggestion
 though.

-- 
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] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
-+-
   Reporter: |  Owner:  bendavis78
  bendavis78 | Status:  closed
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:  admin sort
Version:  SVN|  multisort ordering order
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by lukeplant):

 There was already a bug with multiple columns that have the same sort
 field, but the changes made it much worse. Fixing it properly requires one
 bit of code getting uglier, but another getting nicer. Done in [16319]

 I've tested in proper IE6 and 7, and ironed out bugs (with some hacks).
 It's not exactly the same as other browsers, but good enough. Since these
 were major bugs, I just committed straight away - [16321]. Testing in IE8
 and 9 would be appreciated - I don't have VMs for them.

 I've also committed the more advanced UI - [16320]

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

[Changeset] r16321 - in django/trunk/django/contrib/admin: media/css templates/admin

[noreply]

Author: lukeplant
Date: 2011-06-03 04:54:47 -0700 (Fri, 03 Jun 2011)
New Revision: 16321

Modified:
   django/trunk/django/contrib/admin/media/css/base.css
   django/trunk/django/contrib/admin/templates/admin/change_list_results.html
Log:
Internet Explorer fixes for admin sorting UI

Modified: django/trunk/django/contrib/admin/media/css/base.css
===
--- django/trunk/django/contrib/admin/media/css/base.css2011-06-03 
11:54:39 UTC (rev 16320)
+++ django/trunk/django/contrib/admin/media/css/base.css2011-06-03 
11:54:47 UTC (rev 16321)
@@ -329,12 +329,15 @@
 table thead th.sorted a span.text {
display: block;
float: left;
+   cursor: pointer; /* IE needs this */
 }
 
 table thead th.sorted a span.sortpos {
display: block;
float: right;
font-size: .6em;
+   text-align: right;
+   cursor: pointer; /* IE needs this */
 }
 
 table thead th.sorted a img {

Modified: 
django/trunk/django/contrib/admin/templates/admin/change_list_results.html
===
--- django/trunk/django/contrib/admin/templates/admin/change_list_results.html  
2011-06-03 11:54:39 UTC (rev 16320)
+++ django/trunk/django/contrib/admin/templates/admin/change_list_results.html  
2011-06-03 11:54:47 UTC (rev 16321)
@@ -65,8 +65,12 @@
 var popup = $('#sorting-popup-div');
 var img = $('#primary-sort-icon');
 /* These next lines seems necessary to prime the popup: */
-popup.offset({left:-1000, top:0});
+popup.offset({left:0, top:-1000});
 popup.show();
+if ($.browser.msie) {
+// Can't find a way to make IE autosize the div.
+popup.width(300);
+}
 var popupWidth = popup.width();
 popup.hide();
 
@@ -107,7 +111,10 @@
 }
 });
 
-$('#sorting-popup-dismiss').click(hidePopup);
+$('#sorting-popup-dismiss').click(function(ev) {
+hidePopup();
+ev.preventDefault()
+});
 });
 })(django.jQuery);
 //-->

-- 
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] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
-+-
   Reporter: |  Owner:  bendavis78
  bendavis78 | Status:  closed
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:  admin sort
Version:  SVN|  multisort ordering order
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by lukeplant):

 In [16320]:
 {{{
 #!CommitTicketReference repository="" revision="16320"
 Improved UI for advanced sorting controls.

 Now allows individual fields to be removed/toggled.

 Refs #11868
 }}}

-- 
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] #11868: Multiple sort in admin changelist

[Django]

#11868: Multiple sort in admin changelist
-+-
   Reporter: |  Owner:  bendavis78
  bendavis78 | Status:  closed
   Type:  New|  Component:  contrib.admin
  feature|   Severity:  Normal
  Milestone:  1.4|   Keywords:  admin sort
Version:  SVN|  multisort ordering order
 Resolution:  fixed  |  Has patch:  1
   Triage Stage:  Accepted   |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  0  |
-+-

Comment (by lukeplant):

 In [16319]:
 {{{
 #!CommitTicketReference repository="" revision="16319"
 Fixed various bugs related to having multiple columns in admin
 list_display with the same sort field

 Thanks to julien for the report

 Refs #11868
 }}}

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

[Changeset] r16319 - in django/trunk: django/contrib/admin/templatetags django/contrib/admin/views tests/regressiontests/admin_views

[noreply]

Author: lukeplant
Date: 2011-06-03 04:54:29 -0700 (Fri, 03 Jun 2011)
New Revision: 16319

Modified:
   django/trunk/django/contrib/admin/templatetags/admin_list.py
   django/trunk/django/contrib/admin/views/main.py
   django/trunk/tests/regressiontests/admin_views/models.py
   django/trunk/tests/regressiontests/admin_views/tests.py
Log:
Fixed various bugs related to having multiple columns in admin list_display 
with the same sort field

Thanks to julien for the report

Refs #11868

Modified: django/trunk/django/contrib/admin/templatetags/admin_list.py
===
--- django/trunk/django/contrib/admin/templatetags/admin_list.py
2011-06-02 19:50:48 UTC (rev 16318)
+++ django/trunk/django/contrib/admin/templatetags/admin_list.py
2011-06-03 11:54:29 UTC (rev 16319)
@@ -85,7 +85,7 @@
 # We need to know the 'ordering field' that corresponds to each
 # item in list_display, and we need other info, so do a pre-pass
 # on list_display
-list_display_info = SortedDict()
+ordering_field_columns = cl.get_ordering_field_columns()
 for i, field_name in enumerate(cl.list_display):
 admin_order_field = None
 text, attr = label_for_field(field_name, cl.model,
@@ -93,36 +93,20 @@
 return_attr = True
 )
 if attr:
-admin_order_field = getattr(attr, "admin_order_field", None)
-if admin_order_field is None:
-ordering_field_name = field_name
-else:
-ordering_field_name = admin_order_field
-list_display_info[ordering_field_name] = dict(text=text,
-  attr=attr,
-  index=i,
-  
admin_order_field=admin_order_field,
-  field_name=field_name)
-
-del admin_order_field, text, attr
-
-ordering_fields = cl.get_ordering_fields()
-
-for ordering_field_name, info in list_display_info.items():
-if info['attr']:
 # Potentially not sortable
 
 # if the field is the action checkbox: no sorting and special class
-if info['field_name'] == 'action_checkbox':
+if field_name == 'action_checkbox':
 yield {
-"text": info['text'],
+"text": text,
 "class_attrib": mark_safe(' 
class="action-checkbox-column"')
 }
 continue
 
-if not info['admin_order_field']:
+admin_order_field = getattr(attr, "admin_order_field", None)
+if not admin_order_field:
 # Not sortable
-yield {"text": info['text']}
+yield {"text": text}
 continue
 
 # OK, it is sortable if we got this far
@@ -131,9 +115,9 @@
 new_order_type = 'asc'
 sort_pos = 0
 # Is it currently being sorted on?
-if ordering_field_name in ordering_fields:
-order_type = ordering_fields.get(ordering_field_name).lower()
-sort_pos = ordering_fields.keys().index(ordering_field_name) + 1
+if i in ordering_field_columns:
+order_type = ordering_field_columns.get(i).lower()
+sort_pos = ordering_field_columns.keys().index(i) + 1
 th_classes.append('sorted %sending' % order_type)
 new_order_type = {'asc': 'desc', 'desc': 'asc'}[order_type]
 
@@ -141,27 +125,21 @@
 o_list = []
 make_qs_param = lambda t, n: ('-' if t == 'desc' else '') + str(n)
 
-for f, ot in ordering_fields.items():
-try:
-colnum = list_display_info[f]['index']
-except KeyError:
-continue
-
-if f == ordering_field_name:
+for j, ot in ordering_field_columns.items():
+if j == i: # Same column
 # We want clicking on this header to bring the ordering to the
 # front
-o_list.insert(0, make_qs_param(new_order_type, colnum))
+o_list.insert(0, make_qs_param(new_order_type, j))
 else:
-o_list.append(make_qs_param(ot, colnum))
+o_list.append(make_qs_param(ot, j))
 
-if ordering_field_name not in ordering_fields:
-colnum = list_display_info[ordering_field_name]['index']
-o_list.insert(0, make_qs_param(new_order_type, colnum))
+if i not in ordering_field_columns:
+o_list.insert(0, make_qs_param(new_order_type, i))
 
 o_list = '.'.join(o_list)
 
 yield {
-"text": info['text'],
+"text": text,
 "sortable": True,
 "ascending": order_type == "asc",
 "sort_pos": sort_pos,

Modified: django/trunk/django/contrib/admin/views/main.py

Re: [Django] #7135: Databrowse doesn't handle model inheritance

[Django]

#7135: Databrowse doesn't handle model inheritance
+
   Reporter:  admackin  |  Owner:  nobody
   Type:  Bug   | Status:  new
  Milestone:|  Component:  contrib.databrowse
Version:  1.0   |   Severity:  Normal
 Resolution:|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  1
Needs documentation:  0 |Needs tests:  1
Patch needs improvement:  0 |  Easy pickings:  0
+

Comment (by oz):

 databrowse has been broken for 3 years and no-one seems to mind. OneToOne
 fields don't work, nor do nullalbe ForeignKeys (ticket #15792).
 Both have patches that solve the problem, yet are still open for a long
 long time. It's a shame since it renders databrowse (which is potentially
 awesome) useless for many projects.

-- 
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] #16147: {% include %} tag raises TemplateDoesNotExist at compile time of parent template if TEMPLATE_DEBUG is True

[Django]

#16147: {% include %} tag raises TemplateDoesNotExist at compile time of parent
template if TEMPLATE_DEBUG is True
-+-
   Reporter:  mrmachine  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:  include template
   Triage Stage:  Design |  TemplateDoesNotExist TEMPLATE_DEBUG
  decision needed|  Has patch:  1
Needs documentation:  0  |Needs tests:  1
Patch needs improvement:  1  |  Easy pickings:  0
-+-

Comment (by aaugustin):

 The original reporter found the explanation for this optimization and
 posted it on IRC:
 https://code.djangoproject.com/ticket/598#comment:2

-- 
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] #16147: {% include %} tag raises TemplateDoesNotExist at compile time of parent template if TEMPLATE_DEBUG is True

[Django]

#16147: {% include %} tag raises TemplateDoesNotExist at compile time of parent
template if TEMPLATE_DEBUG is True
-+-
   Reporter:  mrmachine  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone:  1.4|  Component:  Template system
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:  include template
   Triage Stage:  Design |  TemplateDoesNotExist TEMPLATE_DEBUG
  decision needed|  Has patch:  1
Needs documentation:  0  |Needs tests:  1
Patch needs improvement:  1  |  Easy pickings:  0
-+-
Changes (by aaugustin):

 * needs_docs:   => 0
 * has_patch:  0 => 1
 * stage:  Unreviewed => Design decision needed
 * needs_tests:   => 1
 * needs_better_patch:   => 1


Comment:

 Replying to:
 > Why does Django try to execute the {% include %} when it contains a hard
 coded string at compile time at all?
 [[BR]]

 This feature (or bug) has "always" existed. I couldn't find an explanation
 in the code or the commit messages.

 - It was added at r1349, which introduced the `{% include %}` tag.
 - It was moved from django/core/template/loader.py to
 django/template/loader_tags.py at r1443, and not changed since then.

 Both changes were committed by Adrian in Nov '05.

 Hopefully the discussion on the mailing list will help sort it out:
 https://groups.google.com/group/django-
 developers/browse_thread/thread/f1c2e3664c8aace2

 

 Technically, the problem is the implementation of
 `django.template.loader_tags.ConstantIncludeNode`: the template resolution
 with `get_template` should be moved from `__init__` to `render`.
 I'm attaching a patch that fixes it with the minimum amount of changes,
 just to show the idea. However:

 - after the patch, `ConstantIncludeNode` and `IncludeNode` are very
 similar; some refactoring would be useful,
 - it breaks the test suite.

-- 
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] #672: get_absolute_url isn't nice

[Django]

#672: get_absolute_url isn't nice
-+-
   Reporter:  ian@…  |  Owner:  adrian
   Type:  defect | Status:  closed
  Milestone: |  Component:  contrib.syndication
Version:  SVN|   Severity:  minor
 Resolution:  fixed  |   Keywords:
   Triage Stage: |  Has patch:  0
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  0
Patch needs improvement:  1  |
-+-
Changes (by ed hardy):

 * needs_better_patch:  0 => 1
 * easy:   => 0


Comment:

 of our lives. Whether it's measuring your heartbeat while out http://www.topedhardycloting.com;>ed hardy for cheap
 exercising or adding to your attire on those special occasions, http://www.topedhardycloting.com;>ed hardy of our lives.
 Whether it's measuring your heartbeat while out http://www.wholesaletiffanyoutlets.com;>wholesale custom
 jewelry exercising or adding to your attire on those special
 occasions, http://www.wholesaletiffanyoutlets.com;>best
 fashion jewelry of our lives. Whether it's measuring your
 heartbeat while out http://www.designersbrianatwood.com;>gray
 platform pumps SANDALS exercising or adding to your attire on
 those special occasions, http://www.designersbrianatwood.com;>moncler knock off of
 our lives. Whether it's measuring your heartbeat while out http://www.louboutinhelsuksale.com;>tory burch sandals
 exercising or adding to your attire on those special occasions, http://www.louboutinhelsuksale.com;>jimmy chew

-- 
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] #16148: get_object_or_404 hook feature

[Django]

#16148: get_object_or_404 hook feature
-+-
   Reporter: |  Owner:  nobody
  havelove@… | Status:  new
   Type:  New|  Component:  Core (Other)
  feature|   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage:  Design |  Easy pickings:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-
Changes (by aaugustin):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Uncategorized => Core (Other)
 * needs_tests:   => 0
 * stage:  Unreviewed => Design decision needed


Comment:

 A discussion is taking place on the mailing list.

 This sounds too specific for core, IMO.

-- 
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] #16136: Error was: cannot import name utils

[Django]

#16136: Error was: cannot import name utils
-+-
   Reporter: |  Owner:  nobody
  kurvenschubser@…   | Status:  reopened
   Type: |  Component:  Uncategorized
  Uncategorized  |   Severity:  Normal
  Milestone: |   Keywords:
Version:  1.3|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage: |  Easy pickings:  0
  Unreviewed |
Needs documentation:  0  |
Patch needs improvement:  0  |
-+-

Comment (by aaugustin):

 I don't see anything in your settings that could trigger a circular
 import.

 There's something unexpected that happens only on your production server.

 The two tickets Ramiro linked to above were never fully understood. It'd
 be nice to nail down the root cause of this problem.

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

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