Re: [Django] #16682: KeyboardInterrupt not handled properly in transaction aborting

[Django]

#16682: KeyboardInterrupt not handled properly in transaction aborting
-+---
   Reporter:  mtredinnick|  Owner:  nobody
   Type:  Uncategorized  | Status:  closed
  Milestone:  1.4|  Component:  contrib.admin
Version:  SVN|   Severity:  Normal
 Resolution:  needsinfo  |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+---
Changes (by Innogsnap):

 * type:  Bug => Uncategorized
 * version:  1.3 => SVN
 * component:  Database layer (models, ORM) => contrib.admin
 * milestone:   => 1.4


Comment:

 Hi there You do have a superb posting. At times make an article regarding
 car dealer supplies. The primary reason for that is due to the fact I deal
 in auto dealership supplies for vehicles of various models.

-- 
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] #16730: serializing forms which use FilteredSelectMultiple

[Django]

#16730: serializing forms which use FilteredSelectMultiple
-+-
   Reporter: |  Owner:  nobody
  alan.kesselmann@…  | Status:  new
   Type:  Bug|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  1  |
-+-

Comment (by julien):

 By the way, it would be interesting to hear if the patch in #16059
 improves the general usability of that widget for you. It doesn't address
 the specific selection issue that you're reporting here 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.

[Django] #16734: urlresolvers doesn't get a script prefix from manage.py

[Django]

#16734: urlresolvers doesn't get a script prefix from manage.py
---+
 Reporter:  d00gs  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Core (Management commands)
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
 The script prefix for `django.core.urlresolvers` doesn't get set to
 anything when being called through `manage.py`, because of course it
 doesn't know what that value should be. This is a problem if you're
 rendering views (or otherwise reversing urls) from a `manage.py` command
 (as one of my sites does to send emails).

 This is solvable by calling `set_script_prefix` from `settings.py`, but
 that feels kind of dirty since it's then about to be rewritten in the WSGI
 handler.

 I don't know what a good solution to this would be. Perhaps it would be
 nice to be able to set a global default script path somewhere that would
 then get incorporated into the default values of things like LOGIN_URL.

 Maybe just a note in the documentation would be good. It took me a while
 to figure out, because I haven't been able to find anything else about
 this online. (I guess that non-`/` script paths are uncommon and reversing
 urls from `manage.py` is also uncommon, so both together are very
 uncommon.)

-- 
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] #16733: pk/id bug in multiple inheritance of concrete classes

[Django]

#16733: pk/id bug in multiple inheritance of concrete classes
-+--
 Reporter:  Leo  |  Owner:  nobody
 Type:  Bug  | Status:  new
Milestone:   |  Component:  Database layer (models, ORM)
  Version:  SVN  |   Severity:  Normal
 Keywords:   |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+--
 If I have two concrete classes A, B and then have a `class C(A,B)` a C
 object's pk and id don't line up.

 The c.pk is a.pk and c.id is b.id. This can create all sorts of problems
 and confusion since you can conventionally use pk and id interchangeably.

-- 
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] #16730: serializing forms which use FilteredSelectMultiple

[Django]

#16730: serializing forms which use FilteredSelectMultiple
-+-
   Reporter: |  Owner:  nobody
  alan.kesselmann@…  | Status:  new
   Type:  Bug|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  1  |
-+-

Comment (by julien):

 Could you clarify what you mean by "user saves selection"? I am a bit
 confused why you need to select things from the destination list.

 This widget is basically to select multiple items from a pool of available
 options (aka the "from" list). Once an item is moved to the destination
 list, then it is considered "selected" in the sense that the user has
 decided to pick that item from the available ones. So here the only
 purpose of selecting items (as in clicking or ctrl-clicking) is to move
 them from one list to the other.

 Your use case seems to involve a third step, i.e. selecting items from the
 pool of already selected items (i.e. already the ones present in the
 destination list) to operate further operations. If that's the case, then
 I'm afraid this is beyond the scope of what was intended for this admin
 widget, and if you've already got an easy workaround to hack some extra
 functionality on top of it then that's great but that would remain your
 own responsibility.

-- 
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] #16732: Unable to have abstract model with unique_together

[Django]

#16732: Unable to have abstract model with unique_together
---+--
 Reporter:  mitar  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Database layer (models, ORM)
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+--
 I have such model definition:

 {{{
 class SlugVersion(models.Model):
 class Meta:
 abstract = True
 unique_together = (('slug', 'version'),)

 slug = models.CharField(db_index=True, max_length=10, editable=False)
 version = models.IntegerField(db_index=True, editable=False)

 class Base(SlugVersion):
 name = models.CharField(max_length=10)

 class Test(Base):
 test = models.IntegerField()
 }}}

 And I am getting:

 {{{
 Error: One or more models did not validate:
 test.test: "unique_together" refers to slug. This is not
 in the same model as the unique_together statement.
 test.test: "unique_together" refers to version. This is not
 in the same model as the unique_together statement.
 }}}

 I see this is as a bug. Why there could not be a table for class `Base`
 with unique constraints on its `slug` and `version` fields, and then 1-1
 relationship with additional table for model `Test` with field `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] #7018: Make ModelForm multiple inheritance possible

[Django]

#7018: Make ModelForm multiple inheritance possible
--+
   Reporter:  bear330 |  Owner:  nobody
   Type:  New feature | Status:  new
  Milestone:  |  Component:  Forms
Version:  SVN |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Design decision needed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+
Changes (by semente):

 * cc: semente+django@… (added)
 * ui_ux:   => 0
 * easy:   => 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] #16730: serializing forms which use FilteredSelectMultiple

[Django]

#16730: serializing forms which use FilteredSelectMultiple
-+-
   Reporter: |  Owner:  nobody
  alan.kesselmann@…  | Status:  new
   Type:  Bug|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  1  |
-+-

Comment (by alan.kesselmann@…):

 The selected items would be appended to previous selection in destination
 list.

 Why im so fond of this widget is that i had to create one such widget for
 myself for one php project. After prototyping our decision was to keep
 items in destination list selected all the time. Simple reason - selecting
 all the items in destination list again just does not make any sense. And
 in case of when the destination list contains more items that fit in
 select area, the scrolling makes selecting those items very very annoying
 for random browser user who usually does not know the ctrl + click and
 shift +  click selecting options.

 So it comes down to comparing those use cases :
 I. User selects items from "from" select(1). User clicks add button(2).
 user saves selection (3)
 II. User selects items from "from" select(1). User clicks add button(2).
 User has to select all the selected items again (i have heard users say -
 why?! i just selected those items in last box, why do i have to select
 them again just to save my selection?) (3). User saves selection (4).

 Case II makes even less sense cause without the jquery form.serialize()
 the widget works exactly as case I.

-- 
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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+-
   Reporter:  pixelcort  |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  1
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-
Changes (by danfairs):

 * cc: dan.fairs@… (removed)


-- 
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] #15367: Improved Auth Password Hashing

[Django]

#15367: Improved Auth Password Hashing
-+-
   Reporter:  poswald|  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.auth
  Milestone:  1.4|   Severity:  Normal
Version:  1.2|   Keywords:  password, hash,
 Resolution: |  hashing, bcrypt, scrypt, pbkdf2,
   Triage Stage:  Design |  sha2, sha1
  decision needed|  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by anonymous):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 cryptacular attempts to address the problem of supporting multiple hash
 functions. The delegating password manager accepts an array of supported
 hash functions, each hashing scheme implements a 'match()' method (does
 the given hash look like that hash function's hash?), and the 'check'
 method accepts a setter to upgrade to the most-preferred hash when someone
 logs in with an older hash. cryptacular includes PBKDF2 and bcrypt.
 https://bitbucket.org/dholth/cryptacular/src/tip/cryptacular/core/__init__.py

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

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

Re: [Django] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+-
   Reporter:  pixelcort  |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  1
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-
Changes (by hha1@…):

 * cc: hha1@… (removed)


-- 
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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+-
   Reporter:  pixelcort  |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  1
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-

Comment (by RaceCondition):

 @tomvons: I'm not in the CC list; I only get the option to add my e-mail
 to the CC, otherwise I wouldn't be asking, would I...

-- 
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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+-
   Reporter:  pixelcort  |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  1
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-
Changes (by tvon):

 * cc: tomvons@… (removed)


Comment:

 @ RaceCondition: removing yourself from the cc list seems to be the only
 way.  Bugzilla at least lets you control what notifications you get, but I
 don't see that feature in this trace setup.

 FWIW, from what I've heard this feature will not be implemented unless
 someone submits a very serious patch, and I imagine you'd hear about that
 through other channels if it were to happen.

-- 
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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+-
   Reporter:  pixelcort  |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  1
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-

Comment (by RaceCondition):

 What do I have to do to stop receiving e-mails about updates to this
 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.

[Django] #16731: startswith and contains doesn't work with F expression

[Django]

#16731: startswith and contains doesn't work with F expression
-+-
 Reporter:  ronnas@… |  Owner:  nobody
 Type:  Bug  | Status:  new
Milestone:   |  Component:  Database layer
  Version:  1.3  |  (models, ORM)
 Keywords:  startswith, F(), |   Severity:  Normal
  wildcards  |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+-
 The expression:
 myTable.objects.filter(field1__startswith=F('field2'))

 rendered to:
 SELECT * FROM `my_table` WHERE `my_table`.`field1` LIKE
 `my_table`.`field2`

 should be:
 SELECT * FROM `my_table` WHERE `my_table`.`field1` LIKE
 CONCAT(`my_table`.`field2`,'%')

-- 
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] #9025: Nested Inline Support in Admin

[Django]

#9025: Nested Inline Support in Admin
-+-
   Reporter:  pixelcort  |  Owner:  nobody
   Type:  New| Status:  new
  feature|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:
 Resolution: |  Has patch:  1
   Triage Stage:  Design |Needs tests:  1
  decision needed|  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  1  |
  UI/UX:  1  |
-+-
Changes (by joeri@…):

 * cc: joeri@… (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] #15198: AuthenticationForm.clean call does not have request set

[Django]

#15198: AuthenticationForm.clean call does not have request set
---+--
   Reporter:  Ciantic  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  contrib.auth
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:
   Triage Stage:  Accepted |  Has patch:  1
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  1|  Easy pickings:  0
  UI/UX:  0|
---+--
Changes (by alej0):

 * cc: alej0varas@… (added)
 * ui_ux:   => 0
 * easy:   => 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] #16693: Unregistering ModelAdmin view and registering it again changing its contents is not realized when invoking it.

[Django]

#16693: Unregistering ModelAdmin view and registering it again changing its
contents is not realized when invoking it.
---+---
   Reporter:  heidar_rafn  |  Owner:  nobody
   Type:  Bug  | Status:  closed
  Milestone:   |  Component:  contrib.admin
Version:  1.3  |   Severity:  Normal
 Resolution:  invalid  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+---

Comment (by heidar_rafn):

 Thanks for the comments. My problem to solve was to allow the user to
 configure the
 {{{ ModelAdmin.list_per_page }}} option, but I obviously did not describe
 it well enough and I did not read the documentation thoroughly enough in
 order to find the easy solution. [[BR]]
 This problem is actually very easy to solve with the documented
 "ModelAdmin.changelist_view(self, request, extra_context=None)" option
 like this:
 {{{
 def changelist_view(self, request, extra_context=None, **kwargs):
 try:
 self.list_per_page =
 int(ConfigParameters.objects.get(name="FLIGHTADMIN_LIST_PER_PAGE").value)
 except:
 self.list_per_page = 5;
 return super(FlightAdmin, self).changelist_view(request,
 extra_context=extra_context)

 }}}

-- 
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] #16730: serializing forms which use FilteredSelectMultiple

[Django]

#16730: serializing forms which use FilteredSelectMultiple
-+-
   Reporter: |  Owner:  nobody
  alan.kesselmann@…  | Status:  new
   Type:  Bug|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution: |  Has patch:  0
   Triage Stage:  Design |Needs tests:  0
  decision needed|  Easy pickings:  1
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  1  |
-+-
Changes (by julien):

 * component:  Forms => contrib.admin


-- 
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] #16730: serializing forms which use FilteredSelectMultiple

[Django]

#16730: serializing forms which use FilteredSelectMultiple
--+
   Reporter:  alan.kesselmann@…   |  Owner:  nobody
   Type:  Bug | Status:  new
  Milestone:  |  Component:  Forms
Version:  1.3 |   Severity:  Normal
 Resolution:  |   Keywords:
   Triage Stage:  Design decision needed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  1
  UI/UX:  1   |
--+
Changes (by julien):

 * stage:  Unreviewed => Design decision needed


Comment:

 I see how this can be annoying in some situations like yours, however the
 case can also be made that keeping the items selected could be confusing
 for the user. What if, for example, some items in the destination list
 were already selected before the move? Would the moved ones be appended to
 the selection or would the prior selection in the destination list be
 cleared before re-selecting only the freshly moved ones?

-- 
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] #16726: Make is_safe decorator for filters

[Django]

#16726: Make is_safe decorator for filters
-+-
   Reporter: |  Owner:  jezdez
  kostia.balitsky@…  | Status:  closed
   Type: |  Component:  Template system
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution:  duplicate  |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by anonymous):

 Replying to [comment:7 jezdez]:
 > .. at least in the sense that both is_safe and needs_autoescape only set
 a flag on the filter functions.
 But they are supposed to do different things, correct?

-- 
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] #16730: serializing forms which use FilteredSelectMultiple

[Django]

#16730: serializing forms which use FilteredSelectMultiple
-+
   Reporter:  alan.kesselmann@…  |  Owner:  nobody
   Type:  Bug| Status:  new
  Milestone: |  Component:  Forms
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  1  |
-+
Changes (by anonymous):

 * needs_better_patch:   => 0
 * ui_ux:  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] #16730: serializing forms which use FilteredSelectMultiple

[Django]

#16730: serializing forms which use FilteredSelectMultiple
---+
 Reporter:  alan.kesselmann@…  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  Forms
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  1
UI/UX:  0  |
---+
 Hello!

 This is minor but annoying problem.

 I use django.contrib.admin.widgets.FilteredSelectMultiple on publicly
 visible page and post forms contents with ajax - gathering data with
 form.serialize(). When doing so i noticed that info from the select widget
 was not sent to server. I followed problem to
 django/contrib/admin/media/js/SelectBox.js and to SelectBox objects render
 method. The problem why jQuery.serialize() does not serialize selects
 contents is simply because those options arent selected after moving from
 one select to another. And they arent selected because SelectBox.render()
 is called after each moving - and after it none of the options have
 selected attribute.

 Like i said - it is not big problem and it has workaround - you have to
 select the options in 2nd select if you want form.serialize() to pick up
 its contents. But when selects contents are many, then this is not easy.
 It would be much easyer if they remained selected after beeing moved from
 one select to another.

 Alan

-- 
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] #16726: Make is_safe decorator for filters

[Django]

#16726: Make is_safe decorator for filters
-+-
   Reporter: |  Owner:  jezdez
  kostia.balitsky@…  | Status:  closed
   Type: |  Component:  Template system
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution:  duplicate  |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by jezdez):

 .. at least in the sense that both is_safe and needs_autoescape only set a
 flag on the filter functions.

-- 
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] #6135: Introduce a short-cut for template filters that has needs_autoescape = True

[Django]

#6135: Introduce a short-cut for template filters that has needs_autoescape = 
True
---+-
   Reporter:  anonymous|  Owner:  nobody
   Type:  New feature  | Status:  new
  Milestone:   |  Component:  Template system
Version:  SVN  |   Severity:  Normal
 Resolution:   |   Keywords:  autoescape
   Triage Stage:  Accepted |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+-
Changes (by jezdez):

 * ui_ux:   => 0
 * easy:   => 0


Comment:

 #16726 was a dupe.

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

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

Re: [Django] #16726: Make is_safe decorator for filters

[Django]

#16726: Make is_safe decorator for filters
-+-
   Reporter: |  Owner:  jezdez
  kostia.balitsky@…  | Status:  closed
   Type: |  Component:  Template system
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution:  duplicate  |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

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


Comment:

 Actually this is a dupe of #6135.

-- 
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] #16726: Make is_safe decorator for filters

[Django]

#16726: Make is_safe decorator for filters
-+-
   Reporter: |  Owner:  jezdez
  kostia.balitsky@…  | Status:  assigned
   Type: |  Component:  Template system
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * status:  new => assigned
 * owner:  nobody => 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] #3378: new template filter to convert datetime from utc to other timezone

[Django]

#3378: new template filter to convert datetime from utc to other timezone
-+-
   Reporter:  arvin  |  Owner:  nobody
   Type: | Status:  closed
  Uncategorized  |  Component:  Template system
  Milestone: |   Severity:  Normal
Version:  SVN|   Keywords:  timezone, utc
 Resolution:  wontfix|  Has patch:  1
   Triage Stage:  Design |Needs tests:  1
  decision needed|  Easy pickings:  0
Needs documentation:  1  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 This should be resolved by #2626.

-- 
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] #16726: Make is_safe decorator for filters

[Django]

#16726: Make is_safe decorator for filters
-+-
   Reporter: |  Owner:  nobody
  kostia.balitsky@…  | Status:  new
   Type: |  Component:  Template system
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by anonymous):

 Replying to [comment:2 russellm]:
 > I'd much rather see a separate @is_safe decorator, rather than a single-
 purpose @safe_filter.
 It's not a big deal to implement both of them :)

-- 
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] #16726: Make is_safe decorator for filters

[Django]

#16726: Make is_safe decorator for filters
-+-
   Reporter: |  Owner:  nobody
  kostia.balitsky@…  | Status:  new
   Type: |  Component:  Template system
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by jezdez):

 Sounds good to me, too.

-- 
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] #16726: Make is_safe decorator for filters

[Django]

#16726: Make is_safe decorator for filters
-+-
   Reporter: |  Owner:  nobody
  kostia.balitsky@…  | Status:  new
   Type: |  Component:  Template system
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-

Comment (by russellm):

 I'd much rather see a separate @is_safe decorator, rather than a single-
 purpose @safe_filter.

-- 
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] #16729: inconsistency between doc and code for oracle DB backend

[Django]

#16729: inconsistency between doc and code for oracle DB backend
-+-
   Reporter: |  Owner:  nobody
  simon.cruanes.2007@…   | Status:  new
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:  oracle doc option
   Triage Stage:  Ready for  |  Has patch:  1
  checkin|Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by julien):

 * 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] #16726: Make is_safe decorator for filters

[Django]

#16726: Make is_safe decorator for filters
-+-
   Reporter: |  Owner:  nobody
  kostia.balitsky@…  | Status:  new
   Type: |  Component:  Template system
  Cleanup/optimization   |   Severity:  Normal
  Milestone: |   Keywords:
Version:  SVN|  Has patch:  0
 Resolution: |Needs tests:  0
   Triage Stage:  Accepted   |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by jezdez):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.2 => SVN
 * needs_docs:   => 0
 * type:  New feature => Cleanup/optimization
 * 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] #16729: inconsistency between doc and code for oracle DB backend

[Django]

#16729: inconsistency between doc and code for oracle DB backend
-+-
   Reporter: |  Owner:  nobody
  simon.cruanes.2007@…   | Status:  new
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:  oracle doc option
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-

Comment (by aaugustin):

 This was a typo in my patch for #16478 that was committed last week in
 r16646.

-- 
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] r16713 - django/trunk/django/contrib/localflavor/si

[noreply]

Author: jezdez
Date: 2011-08-30 05:11:09 -0700 (Tue, 30 Aug 2011)
New Revision: 16713

Modified:
   django/trunk/django/contrib/localflavor/si/si_postalcodes.py
Log:
Fixed indentation introduced in r16706.

Modified: django/trunk/django/contrib/localflavor/si/si_postalcodes.py
===
--- django/trunk/django/contrib/localflavor/si/si_postalcodes.py
2011-08-30 12:09:45 UTC (rev 16712)
+++ django/trunk/django/contrib/localflavor/si/si_postalcodes.py
2011-08-30 12:11:09 UTC (rev 16713)
@@ -1,468 +1,469 @@
 # *-* coding: utf-8 *-*
 
 SI_POSTALCODES = [
- (1000, u'Ljubljana'),
- (1215, u'Medvode'),
- (1216, u'Smlednik'),
- (1217, u'Vodice'),
- (1218, u'Komenda'),
- (1219, u'Laze v Tuhinju'),
- (1221, u'Motnik'),
- (1222, u'Trojane'),
- (1223, u'Blagovica'),
- (1225, u'Lukovica'),
- (1230, u'Dom\u017eale'),
- (1233, u'Dob'),
- (1234, u'Menge\u0161'),
- (1235, u'Radomlje'),
- (1236, u'Trzin'),
- (1241, u'Kamnik'),
- (1242, u'Stahovica'),
- (1251, u'Morav\u010de'),
- (1252, u'Va\u010de'),
- (1262, u'Dol pri Ljubljani'),
- (1270, u'Litija'),
- (1272, u'Pol\u0161nik'),
- (1273, u'Dole pri Litiji'),
- (1274, u'Gabrovka'),
- (1275, u'\u0160martno pri Litiji'),
- (1276, u'Primskovo'),
- (1281, u'Kresnice'),
- (1282, u'Sava'),
- (1290, u'Grosuplje'),
- (1291, u'\u0160kofljica'),
- (1292, u'Ig'),
- (1293, u'\u0160marje - Sap'),
- (1294, u'Vi\u0161nja Gora'),
- (1295, u'Ivan\u010dna Gorica'),
- (1296, u'\u0160entvid pri Sti\u010dni'),
- (1301, u'Krka'),
- (1303, u'Zagradec'),
- (1310, u'Ribnica'),
- (1311, u'Turjak'),
- (1312, u'Videm - Dobrepolje'),
- (1313, u'Struge'),
- (1314, u'Rob'),
- (1315, u'Velike La\u0161\u010de'),
- (1316, u'Ortnek'),
- (1317, u'Sodra\u017eica'),
- (1318, u'Lo\u0161ki Potok'),
- (1319, u'Draga'),
- (1330, u'Ko\u010devje'),
- (1331, u'Dolenja vas'),
- (1332, u'Stara Cerkev'),
- (1336, u'Kostel'),
- (1337, u'Osilnica'),
- (1338, u'Ko\u010devska Reka'),
- (1351, u'Brezovica pri Ljubljani'),
- (1352, u'Preserje'),
- (1353, u'Borovnica'),
- (1354, u'Horjul'),
- (1355, u'Polhov Gradec'),
- (1356, u'Dobrova'),
- (1357, u'Notranje Gorice'),
- (1358, u'Log pri Brezovici'),
- (1360, u'Vrhnika'),
- (1370, u'Logatec'),
- (1372, u'Hotedr\u0161ica'),
- (1373, u'Rovte'),
- (1380, u'Cerknica'),
- (1381, u'Rakek'),
- (1382, u'Begunje pri Cerknici'),
- (1384, u'Grahovo'),
- (1385, u'Nova vas'),
- (1386, u'Stari trg pri Lo\u017eu'),
- (1410, u'Zagorje ob Savi'),
- (1411, u'Izlake'),
- (1412, u'Kisovec'),
- (1413, u'\u010cem\u0161enik'),
- (1414, u'Podkum'),
- (1420, u'Trbovlje'),
- (1423, u'Dobovec'),
- (1430, u'Hrastnik'),
- (1431, u'Dol pri Hrastniku'),
- (1432, u'Zidani Most'),
- (1433, u'Rade\u010de'),
- (1434, u'Loka pri Zidanem Mostu'),
- (2000, u'Maribor'),
- (2201, u'Zgornja Kungota'),
- (2204, u'Miklav\u017e na Dravskem polju'),
- (2205, u'Star\u0161e'),
- (2206, u'Marjeta na Dravskem polju'),
- (2208, u'Pohorje'),
- (2211, u'Pesnica pri Mariboru'),
- (2212, u'\u0160entilj v Slovenskih goricah'),
- (2213, u'Zgornja Velka'),
- (2214, u'Sladki vrh'),
- (2215, u'Cer\u0161ak'),
- (2221, u'Jarenina'),
- (, u'Jakobski Dol'),
- (2223, u'Jurovski Dol'),
- (2229, u'Male\u010dnik'),
- (2230, u'Lenart v Slovenskih goricah'),
- (2231, u'Pernica'),
- (2232, u'Voli\u010dina'),
- (2233, u'Sveta Ana v Slovenskih goricah'),
- (2234, u'Benedikt'),
- (2235, u'Sveta Trojica v Slovenskih goricah'),
- (2236, u'Cerkvenjak'),
- (2241, u'Spodnji Duplek'),
- (2242, u'Zgornja Korena'),
- (2250, u'Ptuj'),
- (2252, u'Dornava'),
- (2253, u'Destrnik'),
- (2254, u'Trnovska vas'),
- (2255, u'Vitomarci'),
- (2256, u'Jur\u0161inci'),
- (2257, u'Polen\u0161ak'),
- (2258, u'Sveti Toma\u017e'),
- (2259, u'Ivanjkovci'),
- (2270, u'Ormo\u017e'),
- (2272, u'Gori\u0161nica'),
- (2273, u'Podgorci'),
- (2274, u'Velika Nedelja'),
- (2275, u'Miklav\u017e pri Ormo\u017eu'),
- (2276, u'Kog'),
- (2277, u'Sredi\u0161\u010de ob Dravi'),
- (2281, u'Markovci'),
- (2282, u'Cirkulane'),
- (2283, u'Zavr\u010d'),
- (2284, u'Videm pri Ptuju'),
- (2285, u'Zgornji Leskovec'),
- (2286, u'Podlehnik'),
- (2287, u'\u017detale'),
- (2288, u'Hajdina'),
- (2289, u'Stoperce'),
- (2310, u'Slovenska Bistrica'),
- (2311, u'Ho\u010de'),
- (2312, u'Orehova vas'),
- (2313, u'Fram'),
- (2314, u'Zgornja Polskava'),
- (2315, u'\u0160martno na Pohorju'),
- (2316, u'Zgornja Lo\u017enica'),
- (2317, u'Oplotnica'),
- (2318, u'Laporje'),
- (2319, u'Polj\u010dane'),
- (2321, u'Makole'),
- (2322, u'Maj\u0161perk'),
- (2323, u'Ptujska Gora'),
- (2324, u'Lovrenc na Dravskem polju'),
- (2325, u'Kidri\u010devo'),
- (2326, u'Cirkovce'),
- (2327, u'Ra\u010de'),
- (2331, u'Pragersko'),
- (2341, u'Limbu\u0161'),
- (2342, u'Ru\u0161e'),
- (2343, u'Fala'),
- (2344, u'Lovrenc na Pohorju'),
- (2345, u'Bistrica ob Dravi'),
- (2351, u'Kamnica'),
- (2352, u'Selnica ob Dravi'),
- (2353, u'Sv. Duh na Ostrem Vrhu'),
- (2354, u'Bresternica'),
- (2360, u'Radlje ob Dravi'),
- (2361, u'O\u017ebalt'),
- (2362, u'Kapla'),
- (2363, 

Re: [Django] #16717: Add optional [as VARNAME] to trans template tag

[Django]

#16717: Add optional [as VARNAME] to trans template tag
-+-
   Reporter:  jezdez |  Owner:  nobody
   Type:  New| Status:  closed
  feature|  Component:
  Milestone: |  Internationalization
Version:  SVN|   Severity:  Normal
 Resolution:  fixed  |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
Changes (by jezdez):

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


Comment:

 In [16712]:
 {{{
 #!CommitTicketReference repository="" revision="16712"
 Fixed #16717 -- Added ability to store result of trans template tag in
 context variable.
 }}}

-- 
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] r16712 - in django/trunk: django/templatetags docs/releases docs/topics/i18n tests/regressiontests/templates

[noreply]

Author: jezdez
Date: 2011-08-30 05:09:45 -0700 (Tue, 30 Aug 2011)
New Revision: 16712

Modified:
   django/trunk/django/templatetags/i18n.py
   django/trunk/docs/releases/1.4.txt
   django/trunk/docs/topics/i18n/internationalization.txt
   django/trunk/tests/regressiontests/templates/tests.py
Log:
Fixed #16717 -- Added ability to store result of trans template tag in context 
variable.

Modified: django/trunk/django/templatetags/i18n.py
===
--- django/trunk/django/templatetags/i18n.py2011-08-30 08:14:35 UTC (rev 
16711)
+++ django/trunk/django/templatetags/i18n.py2011-08-30 12:09:45 UTC (rev 
16712)
@@ -70,8 +70,9 @@
 
 
 class TranslateNode(Node):
-def __init__(self, filter_expression, noop):
+def __init__(self, filter_expression, noop, asvar=None):
 self.noop = noop
+self.asvar = asvar
 self.filter_expression = filter_expression
 if isinstance(self.filter_expression.var, basestring):
 self.filter_expression.var = Variable(u"'%s'" % 
self.filter_expression.var)
@@ -79,7 +80,12 @@
 def render(self, context):
 self.filter_expression.var.translate = not self.noop
 output = self.filter_expression.resolve(context)
-return _render_value_in_context(output, context)
+value = _render_value_in_context(output, context)
+if self.asvar:
+context[self.asvar] = value
+return ''
+else:
+return value
 
 
 class BlockTranslateNode(Node):
@@ -296,16 +302,21 @@
 elif value[-1] == "'":
 value = '"%s"' % value[1:-1].replace('"','\\"')
 
-if self.more():
-if self.tag() == 'noop':
+noop = False
+asvar = None
+
+while self.more():
+tag = self.tag()
+if tag == 'noop':
 noop = True
+elif tag == 'as':
+asvar = self.tag()
 else:
-raise TemplateSyntaxError("only option for 'trans' is 
'noop'")
-else:
-noop = False
-return (value, noop)
-value, noop = TranslateParser(token.contents).top()
-return TranslateNode(parser.compile_filter(value), noop)
+raise TemplateSyntaxError(
+"only options for 'trans' are 'noop' and 'as VAR.")
+return (value, noop, asvar)
+value, noop, asvar = TranslateParser(token.contents).top()
+return TranslateNode(parser.compile_filter(value), noop, asvar)
 
 @register.tag("blocktrans")
 def do_block_translate(parser, token):

Modified: django/trunk/docs/releases/1.4.txt
===
--- django/trunk/docs/releases/1.4.txt  2011-08-30 08:14:35 UTC (rev 16711)
+++ django/trunk/docs/releases/1.4.txt  2011-08-30 12:09:45 UTC (rev 16712)
@@ -283,6 +283,10 @@
   about :ref:`the 403 (HTTP Forbidden) view` for more
   information.
 
+* The :ttag:`trans` template tag now takes an optional ``as`` argument to
+  be able to retrieve a translation string without displaying it but setting
+  a template context variable instead.
+
 .. _backwards-incompatible-changes-1.4:
 
 Backwards incompatible changes in 1.4

Modified: django/trunk/docs/topics/i18n/internationalization.txt
===
--- django/trunk/docs/topics/i18n/internationalization.txt  2011-08-30 
08:14:35 UTC (rev 16711)
+++ django/trunk/docs/topics/i18n/internationalization.txt  2011-08-30 
12:09:45 UTC (rev 16712)
@@ -451,6 +451,32 @@
 %}``. If your translations require strings with variables (placeholders), use
 ``{% blocktrans %}`` instead.
 
+.. versionchanged:: 1.4
+
+If you'd like to retrieve a translated string without displaying it, you can
+use the following syntax::
+
+{% trans "This is the title" as the_title %}
+
+{{ the_title }}
+
+
+In practice you'll use this to get strings that are used in multiple places
+or should be used as arguments for other template tags or filters::
+
+{% trans "starting point" as start %}
+{% trans "end point" as end %}
+{% trans "La Grande Boucle" as race %}
+
+
+  {{ race }}
+
+
+{% for stage in tour_stages %}
+{% cycle start end %}: {{ stage }}{% if forloop.counter|divisibleby:2 
%}{% else %}, {% endif %}
+{% endfor %}
+
+
 .. templatetag:: blocktrans
 
 ``blocktrans`` template tag

Modified: django/trunk/tests/regressiontests/templates/tests.py
===
--- django/trunk/tests/regressiontests/templates/tests.py   2011-08-30 
08:14:35 UTC (rev 16711)
+++ django/trunk/tests/regressiontests/templates/tests.py   2011-08-30 
12:09:45 UTC (rev 16712)
@@ -1294,6 +1294,12 @@
 # blocktrans handling of variables which are not in the context.
  

Re: [Django] #16729: inconsistency between doc and code for oracle DB backend

[Django]

#16729: inconsistency between doc and code for oracle DB backend
-+-
   Reporter: |  Owner:  nobody
  simon.cruanes.2007@…   | Status:  new
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:  oracle doc option
   Triage Stage:  Accepted   |  Has patch:  1
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
Changes (by aaugustin):

 * has_patch:  0 => 1
 * 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] #16729: inconsistency between doc and code for oracle DB backend (was: inconsitency between doc and code for oracle DB backend)

[Django]

#16729: inconsistency between doc and code for oracle DB backend
-+-
   Reporter: |  Owner:  nobody
  simon.cruanes.2007@…   | Status:  new
   Type:  Bug|  Component:  Database layer
  Milestone: |  (models, ORM)
Version:  1.3|   Severity:  Normal
 Resolution: |   Keywords:  oracle doc option
   Triage Stage: |  Has patch:  0
  Unreviewed |Needs tests:  0
Needs documentation:  0  |  Easy pickings:  1
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by simon.cruanes.2007@…):

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


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

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

[Django] #16729: inconsitency between doc and code for oracle DB backend

[Django]

#16729: inconsitency between doc and code for oracle DB backend
+--
 Reporter:  |  Owner:  nobody
  simon.cruanes.2007@…  | Status:  new
 Type:  Bug |  Component:  Database layer (models, ORM)
Milestone:  |   Severity:  Normal
  Version:  1.3 |   Triage Stage:  Unreviewed
 Keywords:  oracle doc  |  Easy pickings:  1
  option|
Has patch:  0   |
UI/UX:  0   |
+--
 According to the doc for the oracle DB backend, at
 https://docs.djangoproject.com/en/dev/ref/settings/?from=olddocs#test-
 create-user
 the option to prevent a user from being created during tests is
 TEST_CREATE_USER.

 However, this option has no effect since the code at
 
https://code.djangoproject.com/browser/django/trunk/django/db/backends/oracle/creation.py#L219
 uses 'TEST_USER_CREATE' instead of 'TEST_CREATE_USER'.

 This is an inconsistency between code and doc, imho it should be enough to
 update the 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] #16728: Registering custom Admin class for User model breaks changing passwords

[Django]

#16728: Registering custom Admin class for User model breaks changing passwords
-+-
   Reporter: |  Owner:  nobody
  django.bigfudge@…  | Status:  closed
   Type:  Bug|  Component:  contrib.admin
  Milestone: |   Severity:  Normal
Version:  1.3|   Keywords:
 Resolution:  invalid|  Has patch:  0
   Triage Stage: |Needs tests:  0
  Unreviewed |  Easy pickings:  0
Needs documentation:  0  |
Patch needs improvement:  0  |
  UI/UX:  0  |
-+-
Changes (by aaugustin):

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


Old description:

> I am doing this:
>
> class UserProfileInline(admin.StackedInline):
> model = UserProfile
>

> class UserAdmin(admin.ModelAdmin):
> save_on_top = True
> inlines = [UserProfileInline]
>
> admin.site.unregister(User)
> admin.site.register(User, UserAdmin)
>
> To allow me to edit UserProfiles inline with Users. However, doing this
> seems to break the password reset feature within django admin (not the
> user-facing password reset – the one on the User model itself which
> allows and administrator to set a user's password manually. The error is:
>
> user object with primary key u'3/password' does not exist.

New description:

 I am doing this:

 {{{
 class UserProfileInline(admin.StackedInline):
 model = UserProfile


 class UserAdmin(admin.ModelAdmin):
 save_on_top = True
 inlines = [UserProfileInline]

 admin.site.unregister(User)
 admin.site.register(User, UserAdmin)
 }}}

 To allow me to edit UserProfiles inline with Users. However, doing this
 seems to break the password reset feature within django admin (not the
 user-facing password reset – the one on the User model itself which allows
 and administrator to set a user's password manually. The error is:

 user object with primary key u'3/password' does not exist.

--

Comment:

 Indeed, your code doesn't work. You may have more luck if you subclass
 `django.contrib.auth.admin.UserAdmin` (I haven't tested).

 Anyway, that isn't a bug in Django. Could you use the django-users mailing
 list or the #django IRC channel for this kind of requests? Trac is the
 place for reporting bugs, it isn't a support forum. 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.

[Django] #16728: Registering custom Admin class for User model breaks changing passwords

[Django]

#16728: Registering custom Admin class for User model breaks changing passwords
---+---
 Reporter:  django.bigfudge@…  |  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
UI/UX:  0  |
---+---
 I am doing this:

 class UserProfileInline(admin.StackedInline):
 model = UserProfile


 class UserAdmin(admin.ModelAdmin):
 save_on_top = True
 inlines = [UserProfileInline]

 admin.site.unregister(User)
 admin.site.register(User, UserAdmin)

 To allow me to edit UserProfiles inline with Users. However, doing this
 seems to break the password reset feature within django admin (not the
 user-facing password reset – the one on the User model itself which allows
 and administrator to set a user's password manually. The error is:

 user object with primary key u'3/password' does not exist.

-- 
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] #16727: contrib.contenttypes.views.shortcut error

[Django]

#16727: contrib.contenttypes.views.shortcut error
---+--
 Reporter:  anonymous  |  Owner:  nobody
 Type:  Bug| Status:  new
Milestone: |  Component:  contrib.contenttypes
  Version:  1.3|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+--
 There is a problem during absurl processing:

 {{{#!python
 absurl = obj.get_absolute_url()
 if absurl.startswith('http://') or absurl.startswith('https://'):
 return http.HttpResponseRedirect(absurl)
 else:
 ...
 }}}

 So, if get_absolute_url returns '//sub.example.com/entry.html' shortcut
 view will return something like
 'http://example.com//sub.example.com/entry.html'

 This problem was founded with help of django_hosts application. Author of
 this app decided to return urls without 'http:' or 'https:' prefix. Here
 is the explanation:
  The double slash at the beginning of the href is an easy way to not
 have to worry about which scheme (http or https) is used. Your browser
 will automatically choose the currently used scheme. If you're on
 https://mysite.com/ a link with an href of //mysite.com/about/ would
 actually point to https://mysite.com/about/. For more information see the
 The protocol-relative URL article by Paul Irish or the appropriate section
 in RFC 3986.

 I think the better way is urlparse lib using to decide on the url kind.

-- 
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] #16726: Make is_safe decorator for filters

[Django]

#16726: Make is_safe decorator for filters
---+-
 Reporter:  kostia.balitsky@…  |  Owner:  nobody
 Type:  New feature| Status:  new
Milestone: |  Component:  Template system
  Version:  1.2|   Severity:  Normal
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+-
 Why not turn boring process of coding

 {{{
 @register.filter('amazing')
 def amazing(value):
 # Not doing anything unsafe ;)
 ...
 return new_value
 amazing.is_safe = True
 }}}

 into something more interesting like


 {{{
 @register.safe_filter('amazing')
 def amazing(value):
 # Not doing anything unsafe ;)
 ...
 return new_value
 }}}

 ?

-- 
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] #7717: python now() and javascript now-button in admin not the same

[Django]

#7717: python now() and javascript now-button in admin not the same
--+---
   Reporter:  mikaelm |  Owner:  nobody
   Type:  Uncategorized   | Status:  closed
  Milestone:  |  Component:  contrib.admin
Version:  newforms-admin  |   Severity:  Normal
 Resolution:  invalid |   Keywords:  now_button
   Triage Stage:  Unreviewed  |  Has patch:  0
Needs documentation:  0   |Needs tests:  0
Patch needs improvement:  0   |  Easy pickings:  0
  UI/UX:  0   |
--+---
Changes (by aaugustin):

 * ui_ux:   => 0
 * type:   => Uncategorized
 * severity:   => Normal
 * easy:   => 0


Comment:

 The same idea was accepted in #14253, and that ticket describes a
 solution.

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

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

[Changeset] r16711 - in django/trunk/docs: faq releases

[noreply]

Author: idangazit
Date: 2011-08-30 01:14:35 -0700 (Tue, 30 Aug 2011)
New Revision: 16711

Modified:
   django/trunk/docs/faq/admin.txt
   django/trunk/docs/releases/1.4.txt
Log:
Added admin browser support policy note.

Modified: django/trunk/docs/faq/admin.txt
===
--- django/trunk/docs/faq/admin.txt 2011-08-29 23:01:25 UTC (rev 16710)
+++ django/trunk/docs/faq/admin.txt 2011-08-30 08:14:35 UTC (rev 16711)
@@ -94,3 +94,15 @@
 like to make should be possible by editing the stylesheet. We've got a
 :doc:`guide to the CSS used in the admin ` to get you 
started.
 
+What browsers are supported for using the admin?
+
+
+The admin provides a fully-functional experience to `YUI's A-grade`_ browsers,
+with the notable exception of IE6, which is not supported.
+
+There *may* be minor stylistic differences between supported browsers—for
+example, some browsers may not support rounded corners. These are considered
+acceptable variations in rendering.
+
+.. _YUI's A-grade: http://yuilibrary.com/yui/docs/tutorials/gbs/ 
+

Modified: django/trunk/docs/releases/1.4.txt
===
--- django/trunk/docs/releases/1.4.txt  2011-08-29 23:01:25 UTC (rev 16710)
+++ django/trunk/docs/releases/1.4.txt  2011-08-30 08:14:35 UTC (rev 16711)
@@ -57,10 +57,27 @@
 
 We've switched the admin and other bundled templates to use the HTML5
 doctype. While Django will be careful in its use of HTML5 features, to maintain
-compatibility with old browsers, this change means that you can use any HTML5
+compatibility with older browsers, this change means that you can use any HTML5
 features you need in admin pages without having to lose HTML validity or
 override the provided templates to change the doctype.
 
+Supported browsers for the admin
+
+
+Django hasn't had a clear policy on which browsers are supported for using the
+admin app. Django's new policy formalizes existing practices: `YUI's A-grade`_
+browsers should provide a fully-functional admin experience, with the notable
+exception of IE6, which is no longer supported.
+
+Released over ten years ago, IE6 imposes many limitations on modern web
+development. The practical implications of this policy are that contributors
+are free to improve the admin without consideration for these limitations.
+
+This new policy **has no impact** on development outside of the admin. Users of
+Django are free to develop webapps compatible with any range of browsers.
+
+.. _YUI's A-grade: http://yuilibrary.com/yui/docs/tutorials/gbs/
+
 List filters in admin interface
 ~~~
 

-- 
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] #16725: Error in example code from per-view cache docs

[Django]

#16725: Error in example code from per-view cache docs
--+---
 Reporter:  BernhardEssl  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Milestone:|  Component:  Documentation
  Version:  SVN   |   Severity:  Normal
 Keywords:|   Triage Stage:  Unreviewed
Has patch:  0 |  Easy pickings:  0
UI/UX:  0 |
--+---
 https://docs.djangoproject.com/en/dev/topics/cache/#specifying-per-view-
 cache-in-the-urlconf

 The second URL pattern is wrong.


 {{{
 (r'^foo/(\d{1,2})/$', cache_page(60 * 15)(my_view)),
 }}}

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