date:20120818

Re: [Django] #18792: localflavor for Iranian users

2012-08-18 Thread Django

#18792: localflavor for Iranian users
-+-
 Reporter:  lxsameer |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.localflavor  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  localflavor  | Triage Stage:  Design
Has patch:  0|  decision needed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by angusturner):

 * cc: angusturner (added)
 * stage:  Unreviewed => Design decision needed


Comment:

 Marking as DDN based on ongoing conversation on local flavors here:
 https://groups.google.com/d/topic/django-developers/OiyEGmXTifs/discussion

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #16502: CreateView useless error message when template_name is not specified

2012-08-18 Thread Django

Comment (by bhuztez):

> I don't like the way this patch/pull request works with ModelForms - it
magically extracts a model from a ModelForm, which already needs
discussion as it's new behaviour

Yes, but it is not a new behaviour, the function-based generic view
counterpart did the same magic. I did not know whether or not the design
decision had been changed to not providing a default `template_name`. To
provide a default `template_name`, I don't think there is a much less
magical way , given current ModelForm API.

https://github.com/django/django/blob/stable/1.4.x/django/views/generic/create_update.py#L29

> but even worse it then passes that model out and then makes a brand new
ModelForm out of it - that shouldn't happen.

No, it does not. If `form_class` already exists, it will NOT make a new
`ModelForm` from `model` extracted from that, it will just return
`form_class` you defined. The function-based generic view counterpart did
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 https://groups.google.com/groups/opt_out.

Re: [Django] #6526: Add remove/escape/replace functions to markdown filter

2012-08-18 Thread Django

#6526: Add remove/escape/replace functions to markdown filter
-+-
 Reporter:  taojian  |Owner:  thomaspurchas
 Type:  New feature  |   Status:  assigned
Component:  contrib.markup   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  markup markdown  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by thomaspurchas):

 Replying to [comment:7 lrekucki]:
 > 1. The patch needs unittests to show that it works correctly.
 > 2. It needs documentation. Current docs for {{{markup}}} are not very
 user friendly, but at least the doc string gives you some clue how to use
 it. Updating the docstring is a minimum. Write proper docs for those
 template tags for bonus points :)
 > 3. It needs some more work. My biggest annoyance is
 {{{markdown.HTML_REMOVED_TEXT}}} - I could live with it's content if it
 was translatable, but changing it to something more human-friendly is
 desirable. Also, while there probably are no extensions called "remove",
 "escape"  and "replace" the names are a bit confusing. I propose using
 something like {{{ {{ text|markdown:"safe=replace,more_extensions" }} }}}
 instead.

 lrekucki I have implemented the safe mode setting using {{{ {{
 text|markdown:"safe=replace,more_extensions" }} }}} as you suggested, the
 attached patch also includes some new tests as well.

 Also if you can still remember could you clarify what you mean by:

 > My biggest annoyance is {{{markdown.HTML_REMOVED_TEXT}}} - I could live
 with it's content if it was translatable, but changing it to something
 more human-friendly is desirable.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18793: Duplicate test test_head_no_get in generic_views.base

2012-08-18 Thread Django

#18793: Duplicate test test_head_no_get in generic_views.base
-+-
 Reporter:  void |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Generic views|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Karen Tracey ):

 In [e94584204215413980680525ee19d120b16e70dc]:
 {{{
 #!CommitTicketReference repository=""
 revision="e94584204215413980680525ee19d120b16e70dc"
 Merge pull request #291 from uruz/ticket18793

 Fixed #18793: Removed duplicate test_head_no_get in generic_views.base

 Thanks uruz.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18793: Duplicate test test_head_no_get in generic_views.base

2012-08-18 Thread Django

#18793: Duplicate test test_head_no_get in generic_views.base
-+-
 Reporter:  void |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Generic views|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Alexey Boriskin ):

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


Comment:

 In [f29032eac65c076e54e000966602c35239de15ac]:
 {{{
 #!CommitTicketReference repository=""
 revision="f29032eac65c076e54e000966602c35239de15ac"
 Fixed #18793: Duplicate test test_head_no_get in generic_views.base
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] f29032: Fixed #18793: Duplicate test test_head_no_get in g...

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: f29032eac65c076e54e000966602c35239de15ac
  
https://github.com/django/django/commit/f29032eac65c076e54e000966602c35239de15ac
  Author: Alexey Boriskin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M tests/regressiontests/generic_views/base.py

  Log Message:
  ---
  Fixed #18793: Duplicate test test_head_no_get in generic_views.base


  Commit: e94584204215413980680525ee19d120b16e70dc
  
https://github.com/django/django/commit/e94584204215413980680525ee19d120b16e70dc
  Author: Karen Tracey 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M tests/regressiontests/generic_views/base.py

  Log Message:
  ---
  Merge pull request #291 from uruz/ticket18793

Fixed #18793: Removed duplicate test_head_no_get in generic_views.base

Thanks uruz.


Compare: https://github.com/django/django/compare/e99293250ed9...e94584204215

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #6526: Add remove/escape/replace functions to markdown filter

2012-08-18 Thread Django

#6526: Add remove/escape/replace functions to markdown filter
-+-
 Reporter:  taojian  |Owner:  thomaspurchas
 Type:  New feature  |   Status:  assigned
Component:  contrib.markup   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  markup markdown  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by thomaspurchas):

 * cc: thomaspurchas (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 https://groups.google.com/groups/opt_out.

Re: [Django] #18419: Language code is not correct for Chinese

2012-08-18 Thread Django

#18419: Language code is not correct for Chinese
-+-
 Reporter:  Olli Wang|Owner:  nobody
 |   Status:  new
 Type:  Bug  |  Version:  1.4
Component:   |   Resolution:
  Internationalization   | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  0
 Keywords:  i18n, chinese, zh|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by kitsunde):

 * cc: kitsunde@… (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 https://groups.google.com/groups/opt_out.

Re: [Django] #6526: Add remove/escape/replace functions to markdown filter

2012-08-18 Thread Django

#6526: Add remove/escape/replace functions to markdown filter
-+-
 Reporter:  taojian  |Owner:  thomaspurchas
 Type:  New feature  |   Status:  assigned
Component:  contrib.markup   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  markup markdown  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by thomaspurchas):

 * status:  new => assigned


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #6526: Add remove/escape/replace functions to markdown filter

2012-08-18 Thread Django

#6526: Add remove/escape/replace functions to markdown filter
-+-
 Reporter:  taojian  |Owner:  thomaspurchas
 Type:  New feature  |   Status:  new
Component:  contrib.markup   |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  markup markdown  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by thomaspurchas):

 * owner:  nobody => thomaspurchas
 * status:  reopened => new


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

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

[Django] #18794: When timezone support is enabled, permalinks for DateDetailView are impossible.

2012-08-18 Thread Django

#18794: When timezone support is enabled, permalinks for DateDetailView are
impossible.
---+--
 Reporter:  void   |  Owner:  nobody
 Type:  Bug| Status:  new
Component:  Generic views  |Version:  master
 Severity:  Normal |   Keywords:  timezone, tz
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+--
 With timezone support enabled, permalinks for `DateDetailView` are hard to
 create.

 As clearly stated in docstring of `DateMixin._make_date_lookup_arg`,
 {{{
 When time zone support is enabled, `date` is assumed to be in the
 current time zone, so that displayed items are consistent with the
 URL.
 }}}

 As current time zone is a time zone of the current user, web site should
 generate different urls for different users in order them view same
 content and not 404 page. That's weird: we don't have permalinks anymore.
 User in Moscow may send a link to `DateDetailView` to another user in New
 York, and that user will see 404 page. Or it may be `DayArchiveView`, and
 user in New York will see another set of records.

 I may be not understanding something, as last test in
 `regressiontests.generic_views.dates` even checks for this 404. But what
 is the way I should generate worldwide accessible permalinks?

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18790: Non-ascii characters in password for database settings don't work

2012-08-18 Thread Django

#18790: Non-ascii characters in password for database settings don't work
-+-
 Reporter:  thcourbon@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.4
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  unicode  |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * component:  Core (Management commands) => Database layer (models, ORM)
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Confirmed that the Python 2 psycopg adapter does not support unicode
 password input (OK with Python 3).

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18793: Duplicate test test_head_no_get in generic_views.base

2012-08-18 Thread Django

#18793: Duplicate test test_head_no_get in generic_views.base
-+-
 Reporter:  void |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Generic views|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by void):

 * has_patch:  0 => 1


-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18793: Duplicate test test_head_no_get in generic_views.base

2012-08-18 Thread Django

#18793: Duplicate test test_head_no_get in generic_views.base
-+-
 Reporter:  void |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Generic views|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by void):

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


Comment:

 Pull request [https://github.com/django/django/pull/291]

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #18793: Duplicate test test_head_no_get in generic_views.base

2012-08-18 Thread Django

#18793: Duplicate test test_head_no_get in generic_views.base
--+
 Reporter:  void  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Generic views |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 As subject says, there are two methods with same name test_head_no_get in
 tests/regressiontests/generic_views/base.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 https://groups.google.com/groups/opt_out.

[django/django] e99293: [py3] Fixed slow path through file_move_safe

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e99293250ed9d0ae471faff240bc2e9910a1ec6f
  
https://github.com/django/django/commit/e99293250ed9d0ae471faff240bc2e9910a1ec6f
  Author: Karen Tracey 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/core/files/move.py

  Log Message:
  ---
  [py3] Fixed slow path through file_move_safe

This path is taken on Windows.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18778: ForeignKey to a model with a CharField primary key produces unexpected results for an empty-string PK value

2012-08-18 Thread Django

#18778: ForeignKey to a model with a CharField primary key produces unexpected
results for an empty-string PK value
-+-
 Reporter:  Ubercore |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  invalid
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Ubercore):

 Interesting. This project must have gotten into an odd state with
 migrations. I'll investigate a bit more, but it does look like an invalid
 ticket. 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 https://groups.google.com/groups/opt_out.

Re: [Django] #17209: Dogfood class-based views in contrib.auth

2012-08-18 Thread Django

#17209: Dogfood class-based views in contrib.auth
-+-
 Reporter:  melinath |Owner:  andrews
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  contrib.auth |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  class-based views|  Needs documentation:  0
  admin auth |  Patch needs improvement:  1
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by mjtamlyn):

 * cc: marc.tamlyn@… (added)
 * needs_better_patch:  0 => 1


Comment:

 I've tried bringing the patch up to the current master. Most of the tests
 pass and it seems to be ok, but there's something weird going on with the
 way that the wrapper shim works.

 On discussion with andrewgodwin we've come up with the following changes:

 1) Remove the wrapper shim, and convert all of the keyword arguments to
 kwargs. We can handle `extra_context` by updating the context on the
 `TemplateResponse` object returned from the CBV.

 2) Tests: the new tests should be entirely equivalent to the old tests,
 but also separate. So a new set of urls linked to the cbv views, and
 retest all the expected behaviour. We should then be able to deprecate
 things easily when the time comes.

 3) !Docs/Release notes. The functional views documentation can be removed,
 and we can convert each part of the docs to now document the new, class
 based version.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18792: localflavor for Iranian users

2012-08-18 Thread Django

#18792: localflavor for Iranian users
-+-
 Reporter:  lxsameer |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  contrib.localflavor  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  localflavor  | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by lxsameer):

 * cc: lxsameer@… (added)
 * needs_docs:   => 0
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 I add a module called utils.py under "ir" directory in localflavors. It is
 a borrowed code, but i removed unnecessary codes and make some change in
 it. should i mention the upstream author in the module ?

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #18792: localflavor for Iranian users

2012-08-18 Thread Django

#18792: localflavor for Iranian users
-+-
 Reporter:  lxsameer |  Owner:  nobody
 Type:  New feature  | Status:  new
Component:  contrib.localflavor  |Version:  master
 Severity:  Normal   |   Keywords:  localflavor
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Recently i decide to add some of my local related codes to django, like:
 form and model fields for Jalali calender, National ID Number, phone
 number fields, etc,

 here is my current code:

 https://github.com/lxsameer/django

 I'll do a pull request as soon as my work done.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18791: [py3] Double import of six in django.forms.widgets

2012-08-18 Thread Django

#18791: [py3] Double import of six in django.forms.widgets
-+-
 Reporter:  void |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Python 3 |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Alexey Boriskin ):

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


Comment:

 In [abc4038b0b47e41bb2d75a37944bbb1699806922]:
 {{{
 #!CommitTicketReference repository=""
 revision="abc4038b0b47e41bb2d75a37944bbb1699806922"
 Fixed #18791: [py3] Double import of six in django.forms.widgets
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18791: [py3] Double import of six in django.forms.widgets

2012-08-18 Thread Django

#18791: [py3] Double import of six in django.forms.widgets
-+-
 Reporter:  void |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Python 3 |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Andrew Godwin ):

 In [1758bf76e4a108ef65a6d5d30196b005e4b302e7]:
 {{{
 #!CommitTicketReference repository=""
 revision="1758bf76e4a108ef65a6d5d30196b005e4b302e7"
 Merge pull request #287 from uruz/ticket18791

 Fixed #18791: [py3] Double import of six in django.forms.widgets
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] abc403: Fixed #18791: [py3] Double import of six in django...

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: abc4038b0b47e41bb2d75a37944bbb1699806922
  
https://github.com/django/django/commit/abc4038b0b47e41bb2d75a37944bbb1699806922
  Author: Alexey Boriskin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/forms/widgets.py

  Log Message:
  ---
  Fixed #18791: [py3] Double import of six in django.forms.widgets


  Commit: 1758bf76e4a108ef65a6d5d30196b005e4b302e7
  
https://github.com/django/django/commit/1758bf76e4a108ef65a6d5d30196b005e4b302e7
  Author: Andrew Godwin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/forms/widgets.py

  Log Message:
  ---
  Merge pull request #287 from uruz/ticket18791

Fixed #18791: [py3] Double import of six in django.forms.widgets


Compare: https://github.com/django/django/compare/bf12c663d9c2...1758bf76e4a1

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] e49848: Fixed bug in 212b982 -- Removed duplicate code in ...

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e4984812cd54f7c5f27ccb754fc8ddadcb0693f9
  
https://github.com/django/django/commit/e4984812cd54f7c5f27ccb754fc8ddadcb0693f9
  Author: Marc Tamlyn 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/template/defaultfilters.py

  Log Message:
  ---
  Fixed bug in 212b982 -- Removed duplicate code in removetags


  Commit: bf12c663d9c2e42d62baa9c7212a18ed2fdc1aa3
  
https://github.com/django/django/commit/bf12c663d9c2e42d62baa9c7212a18ed2fdc1aa3
  Author: Andrew Godwin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/template/defaultfilters.py

  Log Message:
  ---
  Merge pull request #289 from mjtamlyn/slugify-real-function

Fixed bug in 212b982 -- Removed duplicate code in removetags


Compare: https://github.com/django/django/compare/5b09fc8ad2b6...bf12c663d9c2

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #16502: CreateView useless error message when template_name is not specified

2012-08-18 Thread Django

#16502: CreateView useless error message when template_name is not specified
-+-
 Reporter:  silverghost3@…   |Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  CreateView "generic  | Triage Stage:  Accepted
  view"  |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by andrewgodwin):

 * needs_better_patch:  0 => 1


Comment:

 I don't like the way this patch/pull request works with ModelForms - it
 magically extracts a model from a ModelForm, which already needs
 discussion as it's new behaviour, but even worse it then passes that model
 out and then makes a brand new ModelForm out of it - that shouldn't
 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 https://groups.google.com/groups/opt_out.

Re: [Django] #3542: Allow month-based date_list on archive_index

2012-08-18 Thread Django

#3542: Allow month-based date_list on archive_index
-+-
 Reporter:  anonymous|Owner:  dtulig
 Type:  New feature  |   Status:  closed
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  date_list month  | Triage Stage:  Accepted
  generic view   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by Andrew Godwin ):

 In [5b09fc8ad2b61331496a7ed2667960ba744c01aa]:
 {{{
 #!CommitTicketReference repository=""
 revision="5b09fc8ad2b61331496a7ed2667960ba744c01aa"
 Merge pull request #288 from mjtamlyn/date-list-period

 Fixed #3542 -- Add support for changing granularity on ArchiveView.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #3542: Allow month-based date_list on archive_index

2012-08-18 Thread Django

#3542: Allow month-based date_list on archive_index
-+-
 Reporter:  anonymous|Owner:  dtulig
 Type:  New feature  |   Status:  closed
Component:  Generic views|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  date_list month  | Triage Stage:  Accepted
  generic view   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Marc Tamlyn ):

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


Comment:

 In [8d5c11caad7f87d14b486a46890782fa0b66bb74]:
 {{{
 #!CommitTicketReference repository=""
 revision="8d5c11caad7f87d14b486a46890782fa0b66bb74"
 Fixed #3542 -- Add support for changing granularity on ArchiveView.

 Resolving the concept from a very old ticket in a more class-based-view
 manner.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 8d5c11: Fixed #3542 -- Add support for changing granularit...

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 8d5c11caad7f87d14b486a46890782fa0b66bb74
  
https://github.com/django/django/commit/8d5c11caad7f87d14b486a46890782fa0b66bb74
  Author: Marc Tamlyn 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/views/generic/dates.py
M docs/ref/class-based-views/generic-date-based.txt
M tests/regressiontests/generic_views/dates.py
M tests/regressiontests/generic_views/urls.py

  Log Message:
  ---
  Fixed #3542 -- Add support for changing granularity on ArchiveView.

Resolving the concept from a very old ticket in a more class-based-view
manner.


  Commit: 5b09fc8ad2b61331496a7ed2667960ba744c01aa
  
https://github.com/django/django/commit/5b09fc8ad2b61331496a7ed2667960ba744c01aa
  Author: Andrew Godwin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/views/generic/dates.py
M docs/ref/class-based-views/generic-date-based.txt
M tests/regressiontests/generic_views/dates.py
M tests/regressiontests/generic_views/urls.py

  Log Message:
  ---
  Merge pull request #288 from mjtamlyn/date-list-period

Fixed #3542 -- Add support for changing granularity on ArchiveView.


Compare: https://github.com/django/django/compare/afc1bd7ab872...5b09fc8ad2b6

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18764: HttpResponse._get_content shouldn't accept non-text types

2012-08-18 Thread Django

#18764: HttpResponse._get_content shouldn't accept non-text types
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:  Bug  |   Status:  new
Component:  HTTP handling|  Version:  master
 Severity:  Release blocker  |   Resolution:
 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 aaugustin):

 * owner:  nobody => aaugustin


Comment:

 Karen, thanks for pointing me to that ticket.

 I'll review that discussion and implement a consistent solution — it isn't
 hard.

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] afc1bd: [py3] Made 212b9826bd Python 3-friendly

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: afc1bd7ab87268b33a8b44b3238f562cdaf2a72f
  
https://github.com/django/django/commit/afc1bd7ab87268b33a8b44b3238f562cdaf2a72f
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/utils/html.py
M django/utils/text.py
M tests/regressiontests/utils/text.py

  Log Message:
  ---
  [py3] Made 212b9826bd Python 3-friendly



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18791: [py3] Double import of six in django.forms.widgets

2012-08-18 Thread Django

#18791: [py3] Double import of six in django.forms.widgets
-+-
 Reporter:  void |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Python 3 |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by void):

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


Comment:

 Pull request: [https://github.com/django/django/pull/287]

-- 
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 https://groups.google.com/groups/opt_out.

[Django] #18791: [py3] Double import of six in django.forms.widgets

2012-08-18 Thread Django

#18791: [py3] Double import of six in django.forms.widgets
--+
 Reporter:  void  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Python 3  |Version:  master
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  1 |  UI/UX:  0
--+
 There is a double import in django.forms.widgets:
 {{{
 from django.utils import six
 from django.utils import datetime_safe, formats
 from django.utils import six
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18776: urlparse do not support reverse_lazy as url arg

2012-08-18 Thread Django

#18776: urlparse do not support reverse_lazy as url arg
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Python 3  |  Version:  master
 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 Aymeric Augustin ):

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


Comment:

 In [de3ad8bb2d14ccf878121b96e6e0359dd8b1f9d5]:
 {{{
 #!CommitTicketReference repository=""
 revision="de3ad8bb2d14ccf878121b96e6e0359dd8b1f9d5"
 [py3] Avoided passing a lazy string to urlparse.

 This causes an exception under Python 3.

 Fixed #18776.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] a120fa: Introduced force_bytes and force_str.

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: a120fac65a17137bc8ac710477478474e3f9973e
  
https://github.com/django/django/commit/a120fac65a17137bc8ac710477478474e3f9973e
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/utils/encoding.py
M docs/ref/utils.txt

  Log Message:
  ---
  Introduced force_bytes and force_str.

This is consistent with the smart_* series of functions and it's going
to be used by the next commit.


  Commit: de3ad8bb2d14ccf878121b96e6e0359dd8b1f9d5
  
https://github.com/django/django/commit/de3ad8bb2d14ccf878121b96e6e0359dd8b1f9d5
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/contrib/auth/decorators.py
M django/contrib/auth/views.py

  Log Message:
  ---
  [py3] Avoided passing a lazy string to urlparse.

This causes an exception under Python 3.

Fixed #18776.


Compare: https://github.com/django/django/compare/f04bb6d798b0...de3ad8bb2d14

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18776: urlparse do not support reverse_lazy as url arg

2012-08-18 Thread Django

#18776: urlparse do not support reverse_lazy as url arg
--+
 Reporter:  claudep   |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Python 3  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by aaugustin):

 Given Claude's decent but unsuccessful efforts toward a "correct" fix, I
 think we should just go for the simplest solution and just break the lazy
 layer before calling urlparse.

 If the same problem crops up somewhere else, we can always revisit this
 decision...

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #14516: Extract methods from removetags and slugify template filters

2012-08-18 Thread Django

#14516: Extract methods from removetags and slugify template filters
-+-
 Reporter:  romainh  |Owner:  ik
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  striptags| Triage Stage:  Accepted
  removetags slugify refactor|  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Andrew Godwin ):

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


Comment:

 In [212b9826bdda5c3c2eb680e6f9c5b046b4172300]:
 {{{
 #!CommitTicketReference repository=""
 revision="212b9826bdda5c3c2eb680e6f9c5b046b4172300"
 Fixed #14516 -- Extract methods from removetags and slugify template
 filters

 Patch by @jphalip updated to apply, documentation and release notes
 added.

 I've documented strip_tags as well as remove_tags as the difference
 between the two wouldn't be immediately obvious.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #16744: Class based view should have the view object in the context

2012-08-18 Thread Django

#16744: Class based view should have the view object in the context
---+
 Reporter:  reinout|Owner:  tobias
 Type:  New feature|   Status:  closed
Component:  Generic views  |  Version:  1.3
 Severity:  Normal |   Resolution:  fixed
 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 Andrew Godwin ):

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


Comment:

 In [58683e9c82d6e7c5fbb7acef79eef9408b776ab0]:
 {{{
 #!CommitTicketReference repository=""
 revision="58683e9c82d6e7c5fbb7acef79eef9408b776ab0"
 Fixed #16744 -- Class based view should have the view object in the
 context

 Updated the most recent patch from @claudep to apply again and updated
 the documentation location.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #17228: params context variable from TemplateView is inconsistent with other get_context_data implementations

2012-08-18 Thread Django

#17228: params context variable from TemplateView is inconsistent with other
get_context_data implementations
--+
 Reporter:  ptone |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Generic views |  Version:  master
 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 Andrew Godwin ):

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


Comment:

 In [f04bb6d798b07aa5e7c1d99d700fa6ddc7d39e62]:
 {{{
 #!CommitTicketReference repository=""
 revision="f04bb6d798b07aa5e7c1d99d700fa6ddc7d39e62"
 Fixed #17228 -- params context variable is inconsistent

 Remove the params variable from the context and just put the variables
 in directly.

 This had not been committed previously as the original pattern was used
 in the functional generic views and we wanted consistency between them,
 but django.views.generic.simple.direct_to_template is now gone so we can
 do it 'right'.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 58683e: Fixed #16744 -- Class based view should have the v...

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 58683e9c82d6e7c5fbb7acef79eef9408b776ab0
  
https://github.com/django/django/commit/58683e9c82d6e7c5fbb7acef79eef9408b776ab0
  Author: Marc Tamlyn 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/views/generic/base.py
M docs/ref/class-based-views/mixins-simple.txt
M docs/ref/templates/api.txt
M docs/releases/1.5.txt
M tests/regressiontests/generic_views/base.py
M tests/regressiontests/generic_views/detail.py
M tests/regressiontests/generic_views/edit.py
M tests/regressiontests/generic_views/list.py

  Log Message:
  ---
  Fixed #16744 -- Class based view should have the view object in the context

Updated the most recent patch from @claudep to apply again and updated
the documentation location.


  Commit: 212b9826bdda5c3c2eb680e6f9c5b046b4172300
  
https://github.com/django/django/commit/212b9826bdda5c3c2eb680e6f9c5b046b4172300
  Author: Marc Tamlyn 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/template/defaultfilters.py
M django/utils/html.py
M django/utils/text.py
M docs/ref/utils.txt
M docs/releases/1.5.txt
M tests/regressiontests/utils/html.py
M tests/regressiontests/utils/text.py

  Log Message:
  ---
  Fixed #14516 -- Extract methods from removetags and slugify template filters

Patch by @jphalip updated to apply, documentation and release notes
added.

I've documented strip_tags as well as remove_tags as the difference
between the two wouldn't be immediately obvious.


  Commit: f04bb6d798b07aa5e7c1d99d700fa6ddc7d39e62
  
https://github.com/django/django/commit/f04bb6d798b07aa5e7c1d99d700fa6ddc7d39e62
  Author: Marc Tamlyn 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/views/generic/base.py
M docs/releases/1.5.txt
M tests/regressiontests/generic_views/base.py

  Log Message:
  ---
  Fixed #17228 -- params context variable is inconsistent

Remove the params variable from the context and just put the variables
in directly.

This had not been committed previously as the original pattern was used
in the functional generic views and we wanted consistency between them,
but django.views.generic.simple.direct_to_template is now gone so we can
do it 'right'.


Compare: https://github.com/django/django/compare/547b18104653...f04bb6d798b0

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 547b18: [py3] Ported django.utils.safestring.

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 547b181046539f548839e42544521503fbe4d821
  
https://github.com/django/django/commit/547b181046539f548839e42544521503fbe4d821
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/db/backends/mysql/base.py
M django/db/backends/postgresql_psycopg2/base.py
M django/db/backends/sqlite3/base.py
M django/utils/encoding.py
M django/utils/safestring.py
M docs/howto/custom-template-tags.txt
M docs/ref/utils.txt
M tests/regressiontests/i18n/tests.py

  Log Message:
  ---
  [py3] Ported django.utils.safestring.

Backwards compatibility aliases were created under Python 2.



-- 
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 https://groups.google.com/groups/opt_out.

[Django] #18790: Non-ascii characters in password for database settings don't work

2012-08-18 Thread Django

#18790: Non-ascii characters in password for database settings don't work
+-
 Reporter:  thcourbon@… |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Core (Management commands)  |Version:  1.4
 Severity:  Normal  |   Keywords:  unicode
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+-
 An UnicodeError is raised when using a password that contains non-ascii
 characters.

 For example the following settings cause an error when I run ./manage.py
 syncdb.
 {{{
 DATABASES = {
 'default': {
 'ENGINE': 'django.db.backends.postgresql_psycopg2',
 'NAME': 'DBName',
 'USER': 'DBUser',
 'PASSWORD': u'je suis français',
 'HOST': 'localhost',
 'PORT': '5432',
 }
 }
 }}}

 To run ./manage.py runserver with an empty project (just update the
 settings) you have to add the magix comment on top of the file :
 # -*- coding: utf-8 -*-

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #16744: Class based view should have the view object in the context

2012-08-18 Thread Django

#16744: Class based view should have the view object in the context
---+
 Reporter:  reinout|Owner:  tobias
 Type:  New feature|   Status:  assigned
Component:  Generic views  |  Version:  1.3
 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 andrewgodwin):

 * needs_better_patch:  0 => 1


Comment:

 Patch no longer applies cleanly, especially the docs part.

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18779: URLValidator can't validate url with ipv6.

2012-08-18 Thread Django

#18779: URLValidator can't validate url with ipv6.
---+
 Reporter:  matwey.kornilov@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Core (Other)   |  Version:  master
 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 Marc Tamlyn ):

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


Comment:

 In [bfa9fc69bf0afae907af0ba3ef2cab8e10a4fa61]:
 {{{
 #!CommitTicketReference repository=""
 revision="bfa9fc69bf0afae907af0ba3ef2cab8e10a4fa61"
 Fixed #18779 -- URLValidator can't validate url with ipv6.

 Validation is reasonably 'soft', as for the ipv4. False positives don't
 matter too much here.
 }}}

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

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

Re: [Django] #18779: URLValidator can't validate url with ipv6.

2012-08-18 Thread Django

#18779: URLValidator can't validate url with ipv6.
---+
 Reporter:  matwey.kornilov@…  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Core (Other)   |  Version:  master
 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
---+

Comment (by Andrew Godwin ):

 In [e41c30801433b30a1805ae8dd2fe79887c6dab0b]:
 {{{
 #!CommitTicketReference repository=""
 revision="e41c30801433b30a1805ae8dd2fe79887c6dab0b"
 Merge pull request #283 from mjtamlyn/ipv6-address-validation

 Fixed #18779 -- URLValidator can't validate url with ipv6.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] bfa9fc: Fixed #18779 -- URLValidator can't validate url wi...

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: bfa9fc69bf0afae907af0ba3ef2cab8e10a4fa61
  
https://github.com/django/django/commit/bfa9fc69bf0afae907af0ba3ef2cab8e10a4fa61
  Author: Marc Tamlyn 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/core/validators.py
M tests/regressiontests/forms/tests/fields.py

  Log Message:
  ---
  Fixed #18779 -- URLValidator can't validate url with ipv6.

Validation is reasonably 'soft', as for the ipv4. False positives don't
matter too much here.


  Commit: e41c30801433b30a1805ae8dd2fe79887c6dab0b
  
https://github.com/django/django/commit/e41c30801433b30a1805ae8dd2fe79887c6dab0b
  Author: Andrew Godwin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/core/validators.py
M tests/regressiontests/forms/tests/fields.py

  Log Message:
  ---
  Merge pull request #283 from mjtamlyn/ipv6-address-validation

Fixed #18779 -- URLValidator can't validate url with ipv6.


Compare: https://github.com/django/django/compare/16ab519f62f4...e41c30801433

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 228441: [py3] Fixed cache tests.

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 2284419a2c7b5da643e53754e3bf82637b52017b
  
https://github.com/django/django/commit/2284419a2c7b5da643e53754e3bf82637b52017b
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/core/cache/backends/db.py

  Log Message:
  ---
  [py3] Fixed cache tests.


  Commit: 85e7a5e140104e7402ba51c313c9e53cb60d96f2
  
https://github.com/django/django/commit/85e7a5e140104e7402ba51c313c9e53cb60d96f2
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/utils/translation/__init__.py
M django/utils/translation/trans_real.py
M tests/regressiontests/i18n/tests.py

  Log Message:
  ---
  [py3] Stopped attempting to translate bytes.

That goes actively against the goal of cleaning string handling.


  Commit: 16ab519f62f4418a8cff143ea92e642ae89bb2cf
  
https://github.com/django/django/commit/16ab519f62f4418a8cff143ea92e642ae89bb2cf
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/core/management/commands/makemessages.py

  Log Message:
  ---
  [py3] Removed gratuitous use of map/lambda

that causes a test failure on Python 3 because map returns an iterator.


Compare: https://github.com/django/django/compare/f34de7dd6eb7...16ab519f62f4

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 527f96: [py3] Fixed formtools tests.

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 527f967ec1e8d463d8f950549d7f5c9b4a4ffc7b
  
https://github.com/django/django/commit/527f967ec1e8d463d8f950549d7f5c9b4a4ffc7b
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/contrib/formtools/tests/__init__.py

  Log Message:
  ---
  [py3] Fixed formtools tests.

Python 3 adds a new pickle protocol. The tests were updated in a way
that makes it easy to add another pickle protocol, should Python gain
one.

Thanks Thomas Pelletier for providing an initial version of this patch.


  Commit: 4c1286cf78d03fb7df03774f5f4beb9756ec29c0
  
https://github.com/django/django/commit/4c1286cf78d03fb7df03774f5f4beb9756ec29c0
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/db/backends/__init__.py
M django/utils/autoreload.py
M django/utils/six.py
M docs/topics/python3.txt

  Log Message:
  ---
  [py3] Added compatibility import of thread/_thread

This commit fixes the auto-reload of the development server.

I should have done that change in ca07fda2.


  Commit: c03cf0b096c241d9b8c83d775355625d2d8a8e86
  
https://github.com/django/django/commit/c03cf0b096c241d9b8c83d775355625d2d8a8e86
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M tests/regressiontests/backends/tests.py

  Log Message:
  ---
  Cleaned up a test slightly.

We should catch all exceptions in the thread to ensure it doesn't die
with an unhandled exception. The type of the exception is already
checked further in the test.


  Commit: f34de7dd6eb7852c272ab2ecc102aa6f06c1d5aa
  
https://github.com/django/django/commit/f34de7dd6eb7852c272ab2ecc102aa6f06c1d5aa
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/db/backends/__init__.py

  Log Message:
  ---
  [py3] Fixed backends tests.


Compare: https://github.com/django/django/compare/0d1653395bc8...f34de7dd6eb7

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18701: Class Based VIew docs about JSONResponseMixin misleading

2012-08-18 Thread Django

#18701: Class Based VIew docs about JSONResponseMixin misleading
-+-
 Reporter:  mbrochh@…|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.4
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  cbv, class based | Triage Stage:  Ready for
  views, docs|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

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


Comment:

 Merged in [0d1653395b].

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] e437dd: Update docs/topics/class-based-views/index.txt

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: e437dd1d6be5fdc3a7acf7abcf97b922e628313b
  
https://github.com/django/django/commit/e437dd1d6be5fdc3a7acf7abcf97b922e628313b
  Author: Preston Holmes 
  Date:   2012-08-17 (Fri, 17 Aug 2012)

  Changed paths:
M docs/topics/class-based-views/index.txt

  Log Message:
  ---
  Update docs/topics/class-based-views/index.txt

View class does not have a render_to_response method - so does not make sense 
for this mixin


  Commit: 0d1653395bc8b88bc6db3fb4d70a09cb6520ae4e
  
https://github.com/django/django/commit/0d1653395bc8b88bc6db3fb4d70a09cb6520ae4e
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M docs/topics/class-based-views/index.txt

  Log Message:
  ---
  Merge pull request #282 from ptone/patch-1

Corrected docs on setup of JSONResponseMixin example


Compare: https://github.com/django/django/compare/1ad05172cb5e...0d1653395bc8

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 6cb76c: [py3] Fixed templates tests.

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 6cb76cb140d8ca9815fc90829b6636eb6e43ac42
  
https://github.com/django/django/commit/6cb76cb140d8ca9815fc90829b6636eb6e43ac42
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M tests/regressiontests/templates/filters.py
M tests/regressiontests/templates/tests.py

  Log Message:
  ---
  [py3] Fixed templates tests.


  Commit: 1ad05172cb5e2fafe85540e2525114843c693955
  
https://github.com/django/django/commit/1ad05172cb5e2fafe85540e2525114843c693955
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M django/core/files/base.py

  Log Message:
  ---
  [py3] Fixed file_storage tests.


Compare: https://github.com/django/django/compare/4da1d0fd65e0...1ad05172cb5e

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18705: Tutorial - URL Template Tag Error

2012-08-18 Thread Django

#18705: Tutorial - URL Template Tag Error
---+--
 Reporter:  max@…  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 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 Aymeric Augustin ):

 In [4da1d0fd65e01abe013e0d5a9174b81c6bbfa677]:
 {{{
 #!CommitTicketReference repository=""
 revision="4da1d0fd65e01abe013e0d5a9174b81c6bbfa677"
 Added a warning about the {% url %} syntax change

 at the point where it bites most beginners.

 Refs #18787, #18762, #18756, #18723, #18705, #18689 and several
 duplicates.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18762: Problem with url in templates

2012-08-18 Thread Django

#18762: Problem with url in templates
---+--
 Reporter:  jendxb@…   |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 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 Aymeric Augustin ):

 In [4da1d0fd65e01abe013e0d5a9174b81c6bbfa677]:
 {{{
 #!CommitTicketReference repository=""
 revision="4da1d0fd65e01abe013e0d5a9174b81c6bbfa677"
 Added a warning about the {% url %} syntax change

 at the point where it bites most beginners.

 Refs #18787, #18762, #18756, #18723, #18705, #18689 and several
 duplicates.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18787: Tutorial code incorrect

2012-08-18 Thread Django

#18787: Tutorial code incorrect
---+--
 Reporter:  Foxpaw |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 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 Aymeric Augustin ):

 In [4da1d0fd65e01abe013e0d5a9174b81c6bbfa677]:
 {{{
 #!CommitTicketReference repository=""
 revision="4da1d0fd65e01abe013e0d5a9174b81c6bbfa677"
 Added a warning about the {% url %} syntax change

 at the point where it bites most beginners.

 Refs #18787, #18762, #18756, #18723, #18705, #18689 and several
 duplicates.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18689: Error in code example

2012-08-18 Thread Django

#18689: Error in code example
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 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 Aymeric Augustin ):

 In [4da1d0fd65e01abe013e0d5a9174b81c6bbfa677]:
 {{{
 #!CommitTicketReference repository=""
 revision="4da1d0fd65e01abe013e0d5a9174b81c6bbfa677"
 Added a warning about the {% url %} syntax change

 at the point where it bites most beginners.

 Refs #18787, #18762, #18756, #18723, #18705, #18689 and several
 duplicates.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18723: Decoupled urls syntax in docs differs from what works on my platform

2012-08-18 Thread Django

#18723: Decoupled urls syntax in docs differs from what works on my platform
--+--
 Reporter:  chris.pagnutti@…  |Owner:  nobody
 Type:  Uncategorized |   Status:  closed
Component:  Documentation |  Version:  1.4
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--

Comment (by Aymeric Augustin ):

 In [4da1d0fd65e01abe013e0d5a9174b81c6bbfa677]:
 {{{
 #!CommitTicketReference repository=""
 revision="4da1d0fd65e01abe013e0d5a9174b81c6bbfa677"
 Added a warning about the {% url %} syntax change

 at the point where it bites most beginners.

 Refs #18787, #18762, #18756, #18723, #18705, #18689 and several
 duplicates.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18756: Tutorial 3 Needs extra funky directive

2012-08-18 Thread Django

#18756: Tutorial 3 Needs extra funky directive
---+--
 Reporter:  anonymous  |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 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 Aymeric Augustin ):

 In [4da1d0fd65e01abe013e0d5a9174b81c6bbfa677]:
 {{{
 #!CommitTicketReference repository=""
 revision="4da1d0fd65e01abe013e0d5a9174b81c6bbfa677"
 Added a warning about the {% url %} syntax change

 at the point where it bites most beginners.

 Refs #18787, #18762, #18756, #18723, #18705, #18689 and several
 duplicates.
 }}}

-- 
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 https://groups.google.com/groups/opt_out.

[django/django] 4da1d0: Added a warning about the {% url %} syntax change

2012-08-18 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 4da1d0fd65e01abe013e0d5a9174b81c6bbfa677
  
https://github.com/django/django/commit/4da1d0fd65e01abe013e0d5a9174b81c6bbfa677
  Author: Aymeric Augustin 
  Date:   2012-08-18 (Sat, 18 Aug 2012)

  Changed paths:
M docs/intro/tutorial03.txt

  Log Message:
  ---
  Added a warning about the {% url %} syntax change

at the point where it bites most beginners.

Refs #18787, #18762, #18756, #18723, #18705, #18689 and several duplicates.



-- 
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 https://groups.google.com/groups/opt_out.

Re: [Django] #18787: Tutorial code incorrect

2012-08-18 Thread Django

#18787: Tutorial code incorrect
---+--
 Reporter:  Foxpaw |Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  Documentation  |  Version:  1.4
 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
---+--
Changes (by aaugustin):

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


Comment:

 You are likely reading the development version documentation while using a
 version of Django <=  1.4.

 The old behaviour of the `url` template tag will be officially deprecated
 in django 1.5 following the deprecation process described
 [https://docs.djangoproject.com/en/dev/releases/1.3/#changes-to-url-and-
 ssi in the Django 1.3 release notes].

 Thanks for reporting anyway.

-- 
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 https://groups.google.com/groups/opt_out.

58 matches

Mail list logo