date:20140917

Re: [Django] #23424: Verbatim tag fails to render curly braces

2014-09-17 Thread Django

#23424: Verbatim tag fails to render curly braces
-+-
 Reporter:  stephband|Owner:
 Type:  Bug  |  mountainpaul
Component:  Template system  |   Status:  assigned
 Severity:  Normal   |  Version:  master
 Keywords:  verbatim template|   Resolution:
  tag| Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by shayneoneill):

 Oh wow. I didn't even realise that existed. Thanks! Still I do think that
 allowing multiple verbatim/endverbatim instances on a line would solve a
 lot of headaches.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.28ff2fda15a29c611a9d4d87fd56e1b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23501: remove/add fields programatically in modelform fails in admin

2014-09-17 Thread Django

#23501: remove/add fields programatically in modelform fails in admin
---+
 Reporter:  hadisunyoto|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.7
 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 hadisunyoto):

 I am aware of such methods, what i was trying to do is to push as much
 form control in modelform instead of in the admin. So next time when i
 have time i can build my own admin and reuse modelform without modifying
 the code again

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.81ea33c005eeae82cd2244bdb872a845%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23507: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23507: Clarity: Release Notes regarding initial_data
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  fixtures |  Unreviewed
  intial_data migrations runpython   |  Needs documentation:  0
  runsql |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by timgraham):

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


Comment:

 Duplicate submit of #23512.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.950bc542d8885e12fb27f0862b647b95%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23509: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23509: Clarity: Release Notes regarding initial_data
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  fixtures |  Unreviewed
  intial_data migrations runpython   |  Needs documentation:  0
  runsql |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by timgraham):

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


Comment:

 Duplicate submit of #23512.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7f2ef7d6cb2d04ecb18c5657d946ba79%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23508: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23508: Clarity: Release Notes regarding initial_data
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  fixtures |  Unreviewed
  intial_data migrations runpython   |  Needs documentation:  0
  runsql |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by timgraham):

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


Comment:

 Duplicate submit of #23512.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7c67cb3e13d5fa841f5e3f687e4df273%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23510: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23510: Clarity: Release Notes regarding initial_data
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  fixtures |  Unreviewed
  intial_data migrations runpython   |  Needs documentation:  0
  runsql |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by timgraham):

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


Comment:

 Duplicate submit of #23512.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e085518b9de8ce771f0485f52a29f6d3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23511: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23511: Clarity: Release Notes regarding initial_data
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  duplicate
 Severity:  Normal   | Triage Stage:
 Keywords:  fixtures |  Unreviewed
  intial_data migrations runpython   |  Needs documentation:  0
  runsql |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by timgraham):

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


Comment:

 Duplicate submit of #23512.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.8b54f3da58020f3e02b478f508bd4951%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23512: Make migration docs about initial_data fixtures clearer

2014-09-17 Thread Django

#23512: Make migration docs about initial_data fixtures clearer
--+
 Reporter:  Markush2010   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by timgraham):

 Should also be changed in the 1.7 release notes as described in #23513.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.b9d529501e0347420177ae9a8f454660%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23513: Fixtures/initial_data Clarification in Release Notes for django 1.7

2014-09-17 Thread Django

#23513: Fixtures/initial_data Clarification in Release Notes for django 1.7
-+-
 Reporter:  abhillman|Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:  duplicate
 Keywords:  runpython runsql | Triage Stage:
  documentation migrations   |  Unreviewed
  initial_data   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-
Changes (by timgraham):

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


Comment:

 Since the text is identical, we can make the update part of #23513.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.c23dcaa675c85cde9c1fb8c543b9c051%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23512: Make migration docs about initial_data fixtures clearer

2014-09-17 Thread Django

#23512: Make migration docs about initial_data fixtures clearer
--+
 Reporter:  Markush2010   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * type:  Uncategorized => Cleanup/optimization
 * easy:  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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.afc47f81c48f4683a4eaaf0a536960ff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23512: Make migration docs about initial_data fixtures clearer

2014-09-17 Thread Django

#23512: Make migration docs about initial_data fixtures clearer
---+
Reporter: Markush2010| Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation |Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
---+
From @abhillman on IRC:

When migrations are created in Django 1.7, the fixtures are ignored. This
is a perfectly fine decision, but many users (such as myself) still need
fixture-like functionality. That functionality is provided by RunPython or
RunSQL within a migration. While the release notes correctly indicate that
modifying/creating a migration can replace initial_data, they could be a
little clearer, noting RunPython or RunSQL. For example:

"initial_data fixtures are no longer loaded for apps with migrations; if
you want to load initial data for an app, we suggest you do it in a
migration."

... could become

"initial_data fixtures are no longer loaded for apps with migrations; if
you want to load initial data for an app, we suggest you create a
migration for you application and define a RunPython or RunSQL command in
the operations section of the migration."

That could be immensely helpful for pointing users in the right direction,
especially if they are eager to quickly get django 1.7 up and running...
whilst maintaining fixture-like functionality.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/054.39fa91e3c50470ad0e49583d26f8c1ab%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23513: Fixtures/initial_data Clarification in Release Notes for django 1.7

2014-09-17 Thread Django

#23513: Fixtures/initial_data Clarification in Release Notes for django 1.7
-+-
Reporter: | Owner: nobody
abhillman | Status: new
Type: |Version: 1.7
Uncategorized | Keywords: runpython runsql documentation
Component: | migrations initial_data
Documentation | Has patch: 0
Severity: Normal | UI/UX: 0
Triage Stage: |
Unreviewed |
Easy pickings: 1|
-+-
When migrations are created in Django 1.7, the fixtures are ignored. This
is a perfectly fine decision, but many users (such as myself) still need
fixture-like functionality. That functionality is provided by RunPython or
RunSQL within a migration. While the release notes correctly indicate that
modifying/creating a migration can replace initial_data, they could be a
little clearer, noting RunPython or RunSQL. For example:

"initial_data fixtures are no longer loaded for apps with migrations; if
you want to load initial data for an app, we suggest you do it in a
migration."

... could become

That could be immensely helpful for pointing users in the right direction,
especially if they are eager to quickly get django 1.7 up and running...
whilst maintaining fixture-like functionality.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.fa40e9d4e09ba4384975238b1a5e1e86%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23512: Make migration docs about initial_data fixtures clearer

2014-09-17 Thread Django

#23512: Make migration docs about initial_data fixtures clearer
---+--
 Reporter:  Markush2010|Owner:  nobody
 Type:  Uncategorized  |   Status:  new
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:
 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 Markush2010):

 * cc: info+coding@… (added)
 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.e0f3b32263a649ea371528ce4142ddb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23511: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23511: Clarity: Release Notes regarding initial_data
-+-
Reporter: abhillman| Owner: nobody
Type: | Status: new
Cleanup/optimization |Version: 1.7
Component: Documentation| Keywords: fixtures intial_data
Severity: Normal | migrations runpython runsql
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0| UI/UX: 0
-+-
When migrations are created in Django 1.7, the fixtures are ignored. This
is a perfectly fine decision, but many users (such as myself) still need
fixture-like functionality. That functionality is provided by RunPython or
RunSQL within a migration. While the release notes correctly indicate that
modifying/creating a migration can replace initial_data, they could be a
little clearer, noting RunPython or RunSQL. For example:

"initial_data fixtures are no longer loaded for apps with migrations; if
you want to load initial data for an app, we suggest you do it in a
migration."

... could become

That could be immensely helpful for pointing users in the right direction,
especially if they are eager to quickly get django 1.7 up and running...
whilst maintaining fixture-like functionality.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.34975e88eb953a77cea553993b8a02ea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23510: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23510: Clarity: Release Notes regarding initial_data
-+-
Reporter: abhillman| Owner: nobody
Type: | Status: new
Cleanup/optimization |Version: 1.7
Component: Documentation| Keywords: fixtures intial_data
Severity: Normal | migrations runpython runsql
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1| UI/UX: 0
-+-
When migrations are created in Django 1.7, the fixtures are ignored. This
is a perfectly fine decision, but many users (such as myself) still need
fixture-like functionality. That functionality is provided by RunPython or
RunSQL within a migration. While the release notes correctly indicate that
modifying/creating a migration can replace initial_data, they could be a
little clearer, noting RunPython or RunSQL. For example:

"initial_data fixtures are no longer loaded for apps with migrations; if
you want to load initial data for an app, we suggest you do it in a
migration."

... could become

That could be immensely helpful for pointing users in the right direction,
especially if they are eager to quickly get django 1.7 up and running...
whilst maintaining fixture-like functionality.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.ea7400247724ed36f3724b14955ab5da%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23509: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23509: Clarity: Release Notes regarding initial_data
-+-
Reporter: abhillman| Owner: nobody
Type: | Status: new
Cleanup/optimization |Version: 1.7
Component: Documentation| Keywords: fixtures intial_data
Severity: Normal | migrations runpython runsql
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1| UI/UX: 0
-+-
When migrations are created in Django 1.7, the fixtures are ignored. This
is a perfectly fine decision, but many users (such as myself) still need
fixture-like functionality. That functionality is provided by RunPython or
RunSQL within a migration. While the release notes correctly indicate that
modifying/creating a migration can replace initial_data, they could be a
little clearer, noting RunPython or RunSQL. For example:

"initial_data fixtures are no longer loaded for apps with migrations; if
you want to load initial data for an app, we suggest you do it in a
migration."

... could become

That could be immensely helpful for pointing users in the right direction,
especially if they are eager to quickly get django 1.7 up and running...
whilst maintaining fixture-like functionality.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.0fbd0396077598f6bac12efa310e8d8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23508: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23508: Clarity: Release Notes regarding initial_data
-+-
Reporter: abhillman| Owner: nobody
Type: | Status: new
Cleanup/optimization |Version: 1.7
Component: Documentation| Keywords: fixtures intial_data
Severity: Normal | migrations runpython runsql
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1| UI/UX: 0
-+-
When migrations are created in Django 1.7, the fixtures are ignored. This
is a perfectly fine decision, but many users (such as myself) still need
fixture-like functionality. That functionality is provided by RunPython or
RunSQL within a migration. While the release notes correctly indicate that
modifying/creating a migration can replace initial_data, they could be a
little clearer, noting RunPython or RunSQL. For example:

"initial_data fixtures are no longer loaded for apps with migrations; if
you want to load initial data for an app, we suggest you do it in a
migration."

... could become

That could be immensely helpful for pointing users in the right direction,
especially if they are eager to quickly get django 1.7 up and running...
whilst maintaining fixture-like functionality.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.a43941f8ff14f37de2af9f34dffe35c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23507: Clarity: Release Notes regarding initial_data

2014-09-17 Thread Django

#23507: Clarity: Release Notes regarding initial_data
-+-
Reporter: abhillman| Owner: nobody
Type: | Status: new
Cleanup/optimization |Version: 1.7
Component: Documentation| Keywords: fixtures intial_data
Severity: Normal | migrations runpython runsql
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 1| UI/UX: 0
-+-
When migrations are created in Django 1.7, the fixtures are ignored. This
is a perfectly fine decision, but many users (such as myself) still need
fixture-like functionality. That functionality is provided by RunPython or
RunSQL within a migration. While the release notes correctly indicate that
modifying/creating a migration can replace initial_data, they could be a
little clearer, noting RunPython or RunSQL. For example:

"initial_data fixtures are no longer loaded for apps with migrations; if
you want to load initial data for an app, we suggest you do it in a
migration."

... could become

That could be immensely helpful for pointing users in the right direction,
especially if they are eager to quickly get django 1.7 up and running...
whilst maintaining fixture-like functionality.

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.68dc08e2bde3dbfe2215daf032bcf8b6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23506: How to reference static files outside of the template

2014-09-17 Thread Django

#23506: How to reference static files outside of the template
-+-
 Reporter:  thenewguy|Owner:  nobody
 Type:  Uncategorized|   Status:  new
Component:  contrib.staticfiles  |  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
Has patch:  0|  Unreviewed
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by thenewguy):

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


Comment:

 Something simple like this even:


 {{{
 from django.contrib.staticfiles.templatetags.staticfiles import static as
 _static
 import logging

 logger = logging.getLogger(__name__)

 def static(path):
 try:
 return _static(path)
 except:
 logger.exception('Exception raised looking for static file "%s"' %
 path)
 return u"/missing-file/%s" % path.lstrip("/")
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1d621cda1fbf69da4cb2441b65f84d88%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17656: collectstatic should not require a database

2014-09-17 Thread Django

#17656: collectstatic should not require a database
-+
 Reporter:  jcspray@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  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 carljm):

 I think ideally "fully initialize Django" should not be equivalent to
 "require database connection." But you may be right that this will be
 difficult in practice.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.822dfb1b4dd25363dcced1dd3f535cbc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17656: collectstatic should not require a database

2014-09-17 Thread Django

#17656: collectstatic should not require a database
-+
 Reporter:  jcspray@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  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 timgraham):

 I'd guess this is probably impossible (or at least quite difficult) to
 make possible after the app loading refactor since all management commands
 now fully initialize Django.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/075.0ed88699eb8dc44780b7cab62f3133c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23506: How to reference static files outside of the template

2014-09-17 Thread Django

#23506: How to reference static files outside of the template
-+
 Reporter:  thenewguy|  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  contrib.staticfiles  |Version:  1.7
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 There should be a function like
 `django.contrib.staticfiles.templatetags.staticfiles.static` that is safe
 to use outside of a template.  When it cannot find a static file, it
 should probably be configured to return a url pointing at a view that logs
 the file is missing and returns a 404.

 I just discovered that I took down an environment with one call to
 `static` from `django.contrib.staticfiles.templatetags.staticfiles`.

 {{{

 from django.contrib.staticfiles.templatetags.staticfiles import static

 class FooForm(ModelForm):
 class Media:
 js = (
 static("foo.js"),
 )

 }}}

 `foo.js` didn't get put in place.

 So what is the correct way to reference a static file outside of a
 template keeping something like
 `django.contrib.staticfiles.storage.ManifestStaticFilesStorage` in mind?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.f1966dff716cfd0e8218dbb5827230f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

2014-09-17 Thread Django

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  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 Tim Graham ):

 In [changeset:"d8ee13789b93c8edcf13bf1b20ab9e0098eb81bd"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d8ee13789b93c8edcf13bf1b20ab9e0098eb81bd"
 Avoided a crash on an Oracle GIS test; refs #23504.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.54172695c3b17ce2bf51e5bbd1bd0590%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] d8ee13: Avoided a crash on an Oracle GIS test; refs #23504...

2014-09-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: d8ee13789b93c8edcf13bf1b20ab9e0098eb81bd
  
https://github.com/django/django/commit/d8ee13789b93c8edcf13bf1b20ab9e0098eb81bd
  Author: Tim Graham 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/inspectapp/tests.py

  Log Message:
  ---
  Avoided a crash on an Oracle GIS test; refs #23504.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5419fe9ab62a_56b53fb00303d2a097549%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #17656: collectstatic should not require a database

2014-09-17 Thread Django

#17656: collectstatic should not require a database
-+
 Reporter:  jcspray@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  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
-+
Changes (by MattBlack85):

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


Comment:

 reopening, it seems like it still checks the database. In this case I just
 changed name and password.


 {{{
 Traceback (most recent call last):
   File "manage.py", line 12, in 
 execute_from_command_line(sys.argv)
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 385, in
 execute_from_command_line
 utility.execute()
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/core/management/__init__.py", line 354, in execute
 django.setup()
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/__init__.py", line 21, in setup
 apps.populate(settings.INSTALLED_APPS)
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/apps/registry.py", line 108, in populate
 app_config.import_models(all_models)
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/apps/config.py", line 197, in import_models
 self.models_module = import_module(models_module_name)
   File "/usr/lib64/python2.7/importlib/__init__.py", line 37, in
 import_module
 __import__(name)
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/contrib/auth/models.py", line 40, in 
 class Permission(models.Model):
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/db/models/base.py", line 125, in __new__
 new_class.add_to_class('_meta', Options(meta, **kwargs))
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/db/models/base.py", line 300, in add_to_class
 value.contribute_to_class(cls, name)
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/db/models/options.py", line 166, in contribute_to_class
 self.db_table = truncate_name(self.db_table,
 connection.ops.max_name_length())
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/db/__init__.py", line 40, in __getattr__
 return getattr(connections[DEFAULT_DB_ALIAS], item)
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/db/utils.py", line 243, in __getitem__
 conn = backend.DatabaseWrapper(db, alias)
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/contrib/gis/db/backends/postgis/base.py", line 14, in
 __init__
 self.ops = PostGISOperations(self)
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/contrib/gis/db/backends/postgis/operations.py", line 166,
 in __init__
 if self.spatial_version < (1, 3, 4):
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/utils/functional.py", line 55, in __get__
 res = instance.__dict__[self.func.__name__] = self.func(instance)
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/contrib/gis/db/backends/postgis/operations.py", line 260,
 in spatial_version
 vtup = self.postgis_version_tuple()
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/contrib/gis/db/backends/postgis/operations.py", line 434,
 in postgis_version_tuple
 version = self.postgis_lib_version()
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/contrib/gis/db/backends/postgis/operations.py", line 414,
 in postgis_lib_version
 return self._get_postgis_func('postgis_lib_version')
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/contrib/gis/db/backends/postgis/operations.py", line 404,
 in _get_postgis_func
 with self.connection.temporary_connection() as cursor:
   File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
 return self.gen.next()
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 543, in
 temporary_connection
 cursor = self.cursor()
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 165, in cursor
 cursor = self.make_debug_cursor(self._cursor())
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 138, in _cursor
 self.ensure_connection()
   File "/home/matt/repos/uwncom/lib/python2.7/site-
 packages/django/db/backends/__init__.py", line 133, in ensu

[Django] #23505: unique constraint tracking lost after DropColumn + AddColumn in postgres

2014-09-17 Thread Django

#23505: unique constraint tracking lost after DropColumn + AddColumn in postgres
+-
Reporter: CloudNiner | Owner: nobody
Type: Bug | Status: new
Component: Migrations |Version: 1.7
Severity: Normal | Keywords: unique_together
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
+-
Reproduce:
1. Create model with a multi-column uniqueness constraint in postgres
2. Drop a column in the uniqueness constraint, then readd it with a
different type.
e.g:
{{{#!python
foo = models.IntegerField()
# to
foo = models.CharField(max_length=255)
}}}
3. Attempt to modify the uniqueness constraint and run the subsequent
migration. It fails with 'ValueError: Found wrong number (0) of
constraints for '

This is likely due to django not tracking postgres automatically dropping
the uniqueness constraint when a column is deleted/added.
See 'Description -> DROP COLUMN':
http://www.postgresql.org/docs/9.1/static/sql-altertable.html

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/053.3b9274807fa06959ad17c41018896a9b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23433: Django installs /usr/bin/django-admin and /usr/bin/django-admin.py

2014-09-17 Thread Django

#23433: Django installs /usr/bin/django-admin and /usr/bin/django-admin.py
-+-
 Reporter:  Arfrever |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Packaging|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by aaugustin):

 Yes, the fast track would be to deprecate it in Django 1.8 and remove it
 in Django 2.0.

 However, there's almost no downside to keeping it for a few more years,
 and it will avoid making many tutorials obsolete (for example).

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.7558f06873d61e806f7541d237f70cef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 7fce7f: Skipped some broken tests on Oracle GIS; refs #235...

2014-09-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 7fce7f51eff58b86b97cb797546da57096c0a786
  
https://github.com/django/django/commit/7fce7f51eff58b86b97cb797546da57096c0a786
  Author: Tim Graham 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M django/contrib/gis/tests/geoapp/test_regress.py
M django/contrib/gis/tests/relatedapp/tests.py

  Log Message:
  ---
  Skipped some broken tests on Oracle GIS; refs #23504.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5419e272a6a03_1f7a3fb48d7ef2bc477c5%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

2014-09-17 Thread Django

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  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 Tim Graham ):

 In [changeset:"7fce7f51eff58b86b97cb797546da57096c0a786"]:
 {{{
 #!CommitTicketReference repository=""
 revision="7fce7f51eff58b86b97cb797546da57096c0a786"
 Skipped some broken tests on Oracle GIS; refs #23504.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.e3b53f61a771ab23e3d498ce3e4244dd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23504: Oracle GIS test failures

2014-09-17 Thread Django

#23504: Oracle GIS test failures
---+-
 Reporter:  timgraham  |Owner:  timgraham
 Type:  Bug|   Status:  new
Component:  GIS|  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 timgraham):

 Below are the failures from 89559bcfb096ccc625e0e9ab41e2136fcb32a514
 (right before e9103402c0fa873aea58a6a11dba510cd308cb84#diff-
 54b46d05e1da568b3cc987c423e00c50L253 which broke a bunch more with errors
 like:
 {{{
 ==
 ERROR [0.001s]: test02_select_related
 (django.contrib.gis.tests.relatedapp.tests.RelatedGeoModelTest)
 Testing `select_related` on geographic models (see #7126).
 --
 Traceback (most recent call last):
   File "/home/jenkins/workspace/django-
 
oracle/database/oragis11/python/python2.7/django/contrib/gis/tests/relatedapp/tests.py",
 line 40, in test02_select_related
 self.assertEqual(Point(lon, lat), c.location.point)
   File "/home/jenkins/workspace/django-
 oracle/database/oragis11/python/python2.7/django/db/models/fields/related.py",
 line 565, in __get__
 rel_obj = qs.get()
   File "/home/jenkins/workspace/django-
 oracle/database/oragis11/python/python2.7/django/db/models/query.py", line
 363, in get
 num = len(clone)
   File "/home/jenkins/workspace/django-
 oracle/database/oragis11/python/python2.7/django/db/models/query.py", line
 143, in __len__
 self._fetch_all()
   File "/home/jenkins/workspace/django-
 oracle/database/oragis11/python/python2.7/django/db/models/query.py", line
 977, in _fetch_all
 self._result_cache = list(self.iterator())
   File "/home/jenkins/workspace/django-
 oracle/database/oragis11/python/python2.7/django/db/models/query.py", line
 287, in iterator
 for row in compiler.results_iter():
   File "/home/jenkins/workspace/django-
 oracle/database/oragis11/python/python2.7/django/db/models/sql/compiler.py",
 line 764, in results_iter
 row = self.apply_converters(row, converters)
   File "/home/jenkins/workspace/django-
 oracle/database/oragis11/python/python2.7/django/db/models/sql/compiler.py",
 line 711, in apply_converters
 value = converter(value, self.connection)
   File "/home/jenkins/workspace/django-
 
oracle/database/oragis11/python/python2.7/django/contrib/gis/db/models/fields.py",
 line 202, in from_db_value
 value = Geometry(value)
   File "/home/jenkins/workspace/django-
 oracle/database/oragis11/python/python2.7/django/contrib/gis/geos/geometry.py",
 line 89, in __init__
 raise TypeError('Improper geometry input type: %s' %
 str(type(geo_input)))
 TypeError: Improper geometry input type: 
 }}}
 I guess it's because this logic was lost
 
https://github.com/django/django/commit/e9103402c0fa873aea58a6a11dba510cd308cb84
 #diff-54b46d05e1da568b3cc987c423e00c50L253 on GIS fields.
 {{{
 ==
 ERROR: test13c_count
 (django.contrib.gis.tests.relatedapp.tests.RelatedGeoModelTest)
 Testing `Count` aggregate with `.values()`.  See #15305.
 --
 Traceback (most recent call last):
   File
 "/home/tim/code/django/django/contrib/gis/tests/relatedapp/tests.py", line
 255, in test13c_count
 self.assertEqual(1, len(qs))
   File "/home/tim/code/django/django/db/models/query.py", line 143, in
 __len__
 self._fetch_all()
   File "/home/tim/code/django/django/db/models/query.py", line 977, in
 _fetch_all
 self._result_cache = list(self.iterator())
   File "/home/tim/code/django/django/db/models/query.py", line 1091, in
 iterator
 for row in self.query.get_compiler(self.db).results_iter():
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line 700,
 in results_iter
 for rows in self.execute_sql(MULTI):
   File "/home/tim/code/django/django/db/models/sql/compiler.py", line 786,
 in execute_sql
 cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/backends/utils.py", line 63, in
 execute
 return self.cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/utils.py", line 95, in __exit__
 six.reraise(dj_exc_type, dj_exc_value, traceback)
   File "/home/tim/code/django/django/db/backends/utils.py", line 63, in
 execute
 return self.cursor.execute(sql, params)
   File "/home/tim/code/django/django/db/backends/oracle/base.py", line
 895, in execute
 return self.cursor.execute(query, self._param_generator(params))
 DatabaseErr

Re: [Django] #23446: mysqldb1 is no longer maintained and should not be recommended

2014-09-17 Thread Django

#23446: mysqldb1 is no longer maintained and should not be recommended
-+-
 Reporter:  frewsxcv |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by streeter):

 * cc: django@… (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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.d9216c4c467175fad8c7a16dca978309%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23273: MigrationRecorder does not obey db_router allow_migrate rules

2014-09-17 Thread Django

#23273: MigrationRecorder does not obey db_router allow_migrate rules
+
 Reporter:  froomzy |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7-rc-2
 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 dperetti):

 Another side issue : we cannot just `manage.py migrate someapp` if the
 someapp is a "django <1.7" app without migration : the old syncdb behavior
 is not applied when an application is specified.
 So if want the old apps to sync, I have to just run `manage.py migrate`,
 without argument... which will create unwanted tables when we have
 multiple databases.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.0c7ad621ade29e15d0e657f8638b5ea4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py

2014-09-17 Thread Django

#23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py
-+-
 Reporter:  diek |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by diek):

 You are welcome. It was my pleasure to help. Take care.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.81c43954b6f5098616d276628f5176ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23504: Oracle GIS test failures

2014-09-17 Thread Django

#23504: Oracle GIS test failures
-+---
   Reporter:  timgraham  |  Owner:  timgraham
   Type:  Bug| Status:  new
  Component:  GIS|Version:  master
   Severity:  Normal |   Keywords:
   Triage Stage:  Accepted   |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+---
 As we haven't had this build on Jenkins for a while (ever?), there are
 quite a few test failures that need fixing.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/052.a7fa684901de580d0cceb67d36ba5804%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21648: Deprecate "is_admin_site" option of auth.views.password_reset()

2014-09-17 Thread Django

#21648: Deprecate "is_admin_site" option of auth.views.password_reset()
--+
 Reporter:  brain@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 Thanks for the details. Do you think removing the option isn't acceptable
 then? Any sense whether this sort of setup is common? Would updating your
 site to use the sites framework be too much work?

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.3ee4f0246071f6d377067c6b1a542708%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19544: IntegrityError during Many To Many add()

2014-09-17 Thread Django

#19544: IntegrityError during Many To Many add()
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Someday/Maybe
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by timgraham):

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


Comment:

 Reopening because the ticket was closed anonymously without any detail.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.ae03177d624d38a5a7056ab5c3d39f90%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23433: Django installs /usr/bin/django-admin and /usr/bin/django-admin.py

2014-09-17 Thread Django

#23433: Django installs /usr/bin/django-admin and /usr/bin/django-admin.py
-+-
 Reporter:  Arfrever |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Packaging|   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Someday/Maybe
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by collinanderson):

 If we do remove it, we should officially deprecate it first, 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.5b6f43fa2d702187dc47bf492977408e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23503: renaming model with self-referential ManyToManyField breaks DB schema

2014-09-17 Thread Django

#23503: renaming model with self-referential ManyToManyField breaks DB schema
+--
 Reporter:  sir-sigurd  |Owner:  sir-sigurd
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.7
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by sir-sigurd):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.d7aa7f79aff094e6d651c49d80610dd8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23417: Added/completed zh and zh_CN locale format.py files

2014-09-17 Thread Django

#23417: Added/completed zh and zh_CN locale format.py files
--+
 Reporter:  maltebeckmann |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Translations  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"d4c68c46aacbb151034baa321efe3d104e489e29"]:
 {{{
 #!CommitTicketReference repository=""
 revision="d4c68c46aacbb151034baa321efe3d104e489e29"
 [1.7.x] Fixed #23417 -- Completed locale formats for zh_CN, zh_Hans,
 zh_Hant and zh_TW.

 Backport of 1ac32e76ac from master
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.69f75c505b0561ec66a841a9f7a00448%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 40ce3e: [1.7.x] Overhauled the Welsh formats.py file.

2014-09-17 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 40ce3efda20c4f30de234467c4595e44a65f37fe
  
https://github.com/django/django/commit/40ce3efda20c4f30de234467c4595e44a65f37fe
  Author: Duncan Parkes 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M django/conf/locale/cy/formats.py

  Log Message:
  ---
  [1.7.x] Overhauled the Welsh formats.py file.

Backport of df7187d795 from master


  Commit: d4c68c46aacbb151034baa321efe3d104e489e29
  
https://github.com/django/django/commit/d4c68c46aacbb151034baa321efe3d104e489e29
  Author: Malte Beckmann 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M django/conf/locale/zh_CN/formats.py
M django/conf/locale/zh_Hans/formats.py
M django/conf/locale/zh_Hant/formats.py
M django/conf/locale/zh_TW/formats.py
M docs/releases/1.7.1.txt

  Log Message:
  ---
  [1.7.x] Fixed #23417 -- Completed locale formats for zh_CN, zh_Hans, zh_Hant 
and zh_TW.

Backport of 1ac32e76ac from master


Compare: https://github.com/django/django/compare/fdcef1b86359...d4c68c46aacb

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5419a65015a0f_24873feaef9052bc10143e%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] fc2b8d: Fixed #23495 -- Stopped swallowing real settings i...

2014-09-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: fc2b8ddcc8a0d68dcd333a77314c816469ba96af
  
https://github.com/django/django/commit/fc2b8ddcc8a0d68dcd333a77314c816469ba96af
  Author: Claude Paroz 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M django/conf/__init__.py
M tests/admin_scripts/tests.py

  Log Message:
  ---
  Fixed #23495 -- Stopped swallowing real settings import error

Thanks papaloizouc for the report.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5419a5a944104_48613fb6589c52b8378ad%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23495: ImportError silenced

2014-09-17 Thread Django

#23495: ImportError silenced
-+-
 Reporter:  papaloizouc  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  exceptions, import,  |  checkin
  conf, settings |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"fc2b8ddcc8a0d68dcd333a77314c816469ba96af"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc2b8ddcc8a0d68dcd333a77314c816469ba96af"
 Fixed #23495 -- Stopped swallowing real settings import error

 Thanks papaloizouc for the report.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.043cb263ecd72a7a7b475121b302e42a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 023a3d: Updated release notes for backporting locale addit...

2014-09-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 023a3d99156b458e0a8b0cb039aeca485066be07
  
https://github.com/django/django/commit/023a3d99156b458e0a8b0cb039aeca485066be07
  Author: Tim Graham 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M docs/releases/1.7.1.txt
M docs/releases/1.8.txt

  Log Message:
  ---
  Updated release notes for backporting locale additions; refs #23368 and 
#23417.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5419a50511f11_45e93f96d0d052b8528941%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23368: Overhaule the cy (Welsh) formats.py file.

2014-09-17 Thread Django

#23368: Overhaule the cy (Welsh) formats.py file.
-+-
 Reporter:  duncanparkes |Owner:
 Type:  New feature  |  duncanparkes
Component:   |   Status:  closed
  Internationalization   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  welsh, cy, formats   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"023a3d99156b458e0a8b0cb039aeca485066be07"]:
 {{{
 #!CommitTicketReference repository=""
 revision="023a3d99156b458e0a8b0cb039aeca485066be07"
 Updated release notes for backporting locale additions; refs #23368 and
 #23417.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/070.06a56f02d48883299956650c647ac7b8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23417: Added/completed zh and zh_CN locale format.py files

2014-09-17 Thread Django

#23417: Added/completed zh and zh_CN locale format.py files
--+
 Reporter:  maltebeckmann |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Translations  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"023a3d99156b458e0a8b0cb039aeca485066be07"]:
 {{{
 #!CommitTicketReference repository=""
 revision="023a3d99156b458e0a8b0cb039aeca485066be07"
 Updated release notes for backporting locale additions; refs #23368 and
 #23417.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/071.9ea76af05ee14f36a12034e31e7b04ef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23503: renaming model with self-referential ManyToManyField breaks DB schema

2014-09-17 Thread Django

#23503: renaming model with self-referential ManyToManyField breaks DB schema
+
 Reporter:  sir-sigurd  |  Owner:  sir-sigurd
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.7
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Steps to reproduce:

 * initial `models.py` in `test` app:

 {{{
 from django.db import models

 class Thing(models.Model):

 things = models.ManyToManyField('self')
 }}}

 * do

 {{{
 manage.py makemigrations test
 }}}

 * change model's name:

 {{{
 from django.db import models

 class OtherThing(models.Model):

 things = models.ManyToManyField('self')
 }}}

 * do

 {{{
 manage.py makemigrations test
 manage.py migrate
 }}}

 * in `manage.py shell`:

 {{{
 from test.models import OtherThing;
 OtherThing.things.through.objects.all()
 }}}

 * last line results in:

 {{{
 ) failed:
 django.db.utils.ProgrammingError: ОШИБКА:  колонка
 test_otherthing_things.from_otherthing_id не существует
 LINE 1: SELECT "test_otherthing_things"."id", "test_otherthing_thing...
   ^
 >
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/053.57f73635b68ebab6b70f783898514535%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23501: remove/add fields programatically in modelform fails in admin

2014-09-17 Thread Django

#23501: remove/add fields programatically in modelform fails in admin
---+
 Reporter:  hadisunyoto|Owner:  nobody
 Type:  Bug|   Status:  new
Component:  contrib.admin  |  Version:  1.7
 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
---+
Changes (by timgraham):

 * stage:  Unreviewed => Accepted


Comment:

 I looked into this and I believe you can fix this by using
 
[https://docs.djangoproject.com/en/dev/ref/contrib/admin/#django.contrib.admin.ModelAdmin.get_fields
 ModelAdmin.get_fields()] to exclude the field. It might be easiest to
 simply document that you should use that method and not the `del`
 approach.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.6cba3d2a9ceeeb72b431ea43a5db353d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23065: Migration Error when removing unique constraint

2014-09-17 Thread Django

#23065: Migration Error when removing unique constraint
-+
 Reporter:  anonymous|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  1.7
 Severity:  Release blocker  |   Resolution:
 Keywords:  migrations   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by sir-sigurd):

 * needs_tests:  1 => 0


Comment:

 tests and release notes entry added in the pull request

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7eb269415c2e406d436b94b7d3e3df1e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23332: Change format of test runner output

2014-09-17 Thread Django

#23332: Change format of test runner output
-+-
 Reporter:  googol7  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.5
Component:  Testing framework|   Resolution:  wontfix
 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 googol7):

 created an issue here: http://bugs.python.org/issue22431

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/065.6fe79f4511c6fdb5d33ecc4f4cd1f989%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #19544: IntegrityError during Many To Many add()

2014-09-17 Thread Django

#19544: IntegrityError during Many To Many add()
-+-
 Reporter:  Kronuz   |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.4
Component:  Database layer   |   Resolution:  fixed
  (models, ORM)  | Triage Stage:
 Severity:  Normal   |  Someday/Maybe
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by nihilifer):

 I see that it's set as fixed and closed. That's because this bug cannot be
 reproduced or it was really fixed?
 Asking, because I have the same problem on Django 1.5.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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/064.4cf62f536ae7fd45b36c5117e85ca0ed%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 0eb5cd: Fixed #21775 -- Allowed customization of datafile ...

2014-09-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 0eb5cde9da3252fbdbbb59ae6e421ca04814ad3c
  
https://github.com/django/django/commit/0eb5cde9da3252fbdbbb59ae6e421ca04814ad3c
  Author: Josh Smeaton 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M django/db/backends/oracle/creation.py
M docs/ref/settings.txt
M docs/releases/1.8.txt

  Log Message:
  ---
  Fixed #21775 -- Allowed customization of datafile for Oracle tablespace


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5419932e964fa_11453f88e7d5929c59683%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21775: No facility to specify the datafile of a django test Oracle tablespace

2014-09-17 Thread Django

#21775: No facility to specify the datafile of a django test Oracle tablespace
-+-
 Reporter:  smeatonj |Owner:  alvaro@…
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  oracle   |  Needs documentation:  1
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"0eb5cde9da3252fbdbbb59ae6e421ca04814ad3c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="0eb5cde9da3252fbdbbb59ae6e421ca04814ad3c"
 Fixed #21775 -- Allowed customization of datafile for Oracle tablespace
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/066.aebd28313e4f08b8227c7a844862d83d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21648: Deprecate "is_admin_site" option of auth.views.password_reset()

2014-09-17 Thread Django

#21648: Deprecate "is_admin_site" option of auth.views.password_reset()
--+
 Reporter:  brain@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by googol7):

 No I've got:

 - One Django instance with one settings.py which contains SITE_ID = 1
 - Django CMS installed and INSTALLED_APPS containing django.contrib.sites
 The django CMS pages are only rendered for www.domain.tld
 - Several subomains pointing to the same Django instance. nginx is
 redirecting / to /admin on these subdomains as we only allow login and
 password reset but do not display any django CMS content there:
 abc.domain.tld, def.domain.tld, ghi.domain.tld, jkl.domain.tld
 - In the templates I use a templatetag which returns different
 configurations (CSS, etc.) for the subdomains in use based on the host:
 host = context['request'].get_host()

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.ed06c62e5f850031432b6275d6bae64a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py

2014-09-17 Thread Django

#23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py
-+-
 Reporter:  diek |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"aa1939c1d1e923d98fb00250dee34e00421bcee5"]:
 {{{
 #!CommitTicketReference repository=""
 revision="aa1939c1d1e923d98fb00250dee34e00421bcee5"
 [1.6.x] Fixed #23491 -- Clarified tutorial 3.

 Thanks diek for the suggestion.

 Backport of 54fd84e432 from master
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.2448357ca3d61d4a47a1cb3dd4bdf17f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] aa1939: [1.6.x] Fixed #23491 -- Clarified tutorial 3.

2014-09-17 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: aa1939c1d1e923d98fb00250dee34e00421bcee5
  
https://github.com/django/django/commit/aa1939c1d1e923d98fb00250dee34e00421bcee5
  Author: Tim Graham 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M docs/intro/tutorial03.txt

  Log Message:
  ---
  [1.6.x] Fixed #23491 -- Clarified tutorial 3.

Thanks diek for the suggestion.

Backport of 54fd84e432 from master


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5419821c2e640_47643f81e23232c0908a5%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py

2014-09-17 Thread Django

#23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py
-+-
 Reporter:  diek |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"54fd84e43230bc739160b680c5ba51542e2e6e7d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="54fd84e43230bc739160b680c5ba51542e2e6e7d"
 Fixed #23491 -- Clarified tutorial 3.

 Thanks diek for the suggestion.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.bfa71367807ba2c642f23f4f54c149b3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py

2014-09-17 Thread Django

#23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py
-+-
 Reporter:  diek |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"fdcef1b86359b1c658b58fdfc6bfdebc11f830f6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="fdcef1b86359b1c658b58fdfc6bfdebc11f830f6"
 [1.7.x] Fixed #23491 -- Clarified tutorial 3.

 Thanks diek for the suggestion.

 Backport of 54fd84e432 from master
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.936fd765898bc83a3c22ea16036704bd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] fdcef1: [1.7.x] Fixed #23491 -- Clarified tutorial 3.

2014-09-17 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: fdcef1b86359b1c658b58fdfc6bfdebc11f830f6
  
https://github.com/django/django/commit/fdcef1b86359b1c658b58fdfc6bfdebc11f830f6
  Author: Tim Graham 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M docs/intro/tutorial03.txt

  Log Message:
  ---
  [1.7.x] Fixed #23491 -- Clarified tutorial 3.

Thanks diek for the suggestion.

Backport of 54fd84e432 from master


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/541981dbb15f7_54af3f92c5a0b29c973d1%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 54fd84: Fixed #23491 -- Clarified tutorial 3.

2014-09-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 54fd84e43230bc739160b680c5ba51542e2e6e7d
  
https://github.com/django/django/commit/54fd84e43230bc739160b680c5ba51542e2e6e7d
  Author: Tim Graham 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M docs/intro/tutorial03.txt

  Log Message:
  ---
  Fixed #23491 -- Clarified tutorial 3.

Thanks diek for the suggestion.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/541981be2c8b0_2b2f3fe5828a32a026428%40hookshot-fe4-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21648: Deprecate "is_admin_site" option of auth.views.password_reset()

2014-09-17 Thread Django

#21648: Deprecate "is_admin_site" option of auth.views.password_reset()
--+
 Reporter:  brain@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 Do you have each subdomain setup as a site?

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.ed0758bb43396be159bd2c1876349ca1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #23502: Request for an escape_all filter for non alphanumeric chars with ASCII values less than 256

2014-09-17 Thread Django

#23502: Request for an escape_all filter for non alphanumeric chars with ASCII
values less than 256
-+
Reporter: djbug| Owner: nobody
Type: New feature | Status: new
Component: Utilities|Version: 1.7
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0| UI/UX: 0
-+
If you want to put untrusted data in attributes,

[https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet#RULE_
.232_-
_Attribute_Escape_Before_Inserting_Untrusted_Data_into_HTML_Common_Attributes
OWASP recommends] escaping a lot more characters than what's needed for
escaping untrusted data in HTML elements:

> Except for alphanumeric characters, escape all characters with ASCII
values less than 256 with the &#xHH; format (or a named entity if
available) to prevent switching out of the attribute. The reason this rule
is so broad is that developers frequently leave attributes unquoted.
Properly quoted attributes can only be escaped with the corresponding
quote. Unquoted attributes can be broken out of with many characters,
including [space] % * + , - / ; < = > ^ and |.

The recommendation for Javascript escaping is somewhat similar, except for
using ` \xHH` format instead of `&#xHH;`. This would be a useful addition
to security related utilities.

P.S. Another reference : http://wonko.com/post/html-escaping

--
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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/048.077155590d1be524f818d8f9b0f0066f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21648: Deprecate "is_admin_site" option of auth.views.password_reset()

2014-09-17 Thread Django

#21648: Deprecate "is_admin_site" option of auth.views.password_reset()
--+
 Reporter:  brain@…   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  contrib.auth  |  Version:  master
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by googol7):

 A use case is if you are using django CMS (which relies on
 django.contrib.sites) to host a website on xyz.domain.tld and you have
 several subdomains abc.domain.tld, xyz.domain.tld, etc. which do not use
 django CMS but only provide a (branded) login where users can also click
 the "forgot password" link and in the resulting email the referring URL
 (e.g. xyz.domain.tld) should be used.

 django CMS:

 /cms/models/pagemodel.py
 from django.contrib.sites.models import Site
 site = models.ForeignKey(Site, help_text=_('The site the page is
 accessible at.'), verbose_name=_("site"))

 http://docs.django-cms.org/en/2.4.0/extending_cms/api_references.html
 cms.models.pagemodel.Page
 site (django.contrib.sites.models.Site instance) – Site to put this page
 on

 http://docs.django-
 cms.org/en/latest/getting_started/integrate.html#installing
 Be sure to have 'django.contrib.sites' in INSTALLED_APPS and set SITE_ID
 parameter in your settings: they may be missing from the settings file
 generated by django-admin depending on your Django version and project
 template.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/082.a4d92dd8a28f547f0663b8cbaa53bd94%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23495: ImportError silenced

2014-09-17 Thread Django

#23495: ImportError silenced
-+-
 Reporter:  papaloizouc  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:  exceptions, import,  |  checkin
  conf, settings |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

 * 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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.3f1161c457849971838cd6ae607ee749%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23495: ImportError silenced

2014-09-17 Thread Django

#23495: ImportError silenced
-+-
 Reporter:  papaloizouc  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Core (Other) |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  exceptions, import,  |  Needs documentation:  0
  conf, settings |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by claudep):

 * has_patch:  0 => 1
 * version:  1.6 => master


Comment:

 https://github.com/django/django/pull/3229

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.fc8481c8bc5c983d7160964d83f7a943%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py

2014-09-17 Thread Django

#23491: Django Tutorial 1.7, Pt 3. Adding Index method to views.py
-+-
 Reporter:  diek |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  1.7
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Ready for
 Keywords:   |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Accepted => Ready for checkin


Comment:

 Yes, that's a good compromise.

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.5c957d2fb54b52b149c5b9c10c23a032%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 3132ed: [1.4.x] Fixed #23499 -- Error in built-in template...

2014-09-17 Thread GitHub

  Branch: refs/heads/stable/1.4.x
  Home:   https://github.com/django/django
  Commit: 3132edae41dbb13b924e98e8f0254e847155a050
  
https://github.com/django/django/commit/3132edae41dbb13b924e98e8f0254e847155a050
  Author: Joseph Dougherty 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M docs/ref/templates/builtins.txt

  Log Message:
  ---
  [1.4.x] Fixed #23499 -- Error in built-in template tag "now" documentation

Backport of ab8248361e0a7b4fc7684eaaa5891e16b8562683 from master.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5419380be8ebc_12193fc4c3d4f2c02783%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 9a6624: [1.6.x] Fixed #23499 -- Error in built-in template...

2014-09-17 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 9a66244bd8c8b7202ff51f4aa6069f716ab64317
  
https://github.com/django/django/commit/9a66244bd8c8b7202ff51f4aa6069f716ab64317
  Author: Joseph Dougherty 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M docs/ref/templates/builtins.txt

  Log Message:
  ---
  [1.6.x] Fixed #23499 -- Error in built-in template tag "now" documentation

Backport of ab8248361e0a7b4fc7684eaaa5891e16b8562683 from master.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/541938098b7e0_78493fe6896952bc3707a%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

[django/django] 722516: [1.7.x] Fixed #23499 -- Error in built-in template...

2014-09-17 Thread GitHub

  Branch: refs/heads/stable/1.7.x
  Home:   https://github.com/django/django
  Commit: 722516536e0dd99690ab6df4c27bbceb29df4d5b
  
https://github.com/django/django/commit/722516536e0dd99690ab6df4c27bbceb29df4d5b
  Author: Joseph Dougherty 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M docs/ref/templates/builtins.txt

  Log Message:
  ---
  [1.7.x] Fixed #23499 -- Error in built-in template tag "now" documentation

Backport of ab8248361e0a7b4fc7684eaaa5891e16b8562683 from master.


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/5419380a65aa6_18263f95969bd2bc126570%40hookshot-fe3-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23499: Error in built-in template tag "now" documentation

2014-09-17 Thread Django

#23499: Error in built-in template tag "now" documentation
---+--
 Reporter:  JDougherty |Owner:  JDougherty
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Baptiste Mispelon ):

 In [changeset:"9a66244bd8c8b7202ff51f4aa6069f716ab64317"]:
 {{{
 #!CommitTicketReference repository=""
 revision="9a66244bd8c8b7202ff51f4aa6069f716ab64317"
 [1.6.x] Fixed #23499 -- Error in built-in template tag "now" documentation

 Backport of ab8248361e0a7b4fc7684eaaa5891e16b8562683 from master.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.e0b94cc4c5d9dc407e2b4bdc1c1109b4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23499: Error in built-in template tag "now" documentation

2014-09-17 Thread Django

#23499: Error in built-in template tag "now" documentation
---+--
 Reporter:  JDougherty |Owner:  JDougherty
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Baptiste Mispelon ):

 In [changeset:"722516536e0dd99690ab6df4c27bbceb29df4d5b"]:
 {{{
 #!CommitTicketReference repository=""
 revision="722516536e0dd99690ab6df4c27bbceb29df4d5b"
 [1.7.x] Fixed #23499 -- Error in built-in template tag "now" documentation

 Backport of ab8248361e0a7b4fc7684eaaa5891e16b8562683 from master.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.0ae7eb1bc9f4e21b9ff4b4f70b39ae26%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23499: Error in built-in template tag "now" documentation

2014-09-17 Thread Django

#23499: Error in built-in template tag "now" documentation
---+--
 Reporter:  JDougherty |Owner:  JDougherty
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--

Comment (by Baptiste Mispelon ):

 In [changeset:"3132edae41dbb13b924e98e8f0254e847155a050"]:
 {{{
 #!CommitTicketReference repository=""
 revision="3132edae41dbb13b924e98e8f0254e847155a050"
 [1.4.x] Fixed #23499 -- Error in built-in template tag "now" documentation

 Backport of ab8248361e0a7b4fc7684eaaa5891e16b8562683 from master.
 }}}

--
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 unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.f985950a9b2d2e3e43a07498b7f845fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23499: Error in built-in template tag "now" documentation

2014-09-17 Thread Django

#23499: Error in built-in template tag "now" documentation
---+--
 Reporter:  JDougherty |Owner:  JDougherty
 Type:  Bug|   Status:  closed
Component:  Documentation  |  Version:  1.7
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  0
---+--
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"ab8248361e0a7b4fc7684eaaa5891e16b8562683"]:
 {{{
 #!CommitTicketReference repository=""
 revision="ab8248361e0a7b4fc7684eaaa5891e16b8562683"
 Fixed #23499 -- Error in built-in template tag "now" documentation
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/068.9ece451bf238f31cd0b9ba55b84f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] ab8248: Fixed #23499 -- Error in built-in template tag "no...

2014-09-17 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: ab8248361e0a7b4fc7684eaaa5891e16b8562683
  
https://github.com/django/django/commit/ab8248361e0a7b4fc7684eaaa5891e16b8562683
  Author: Joseph Dougherty 
  Date:   2014-09-17 (Wed, 17 Sep 2014)

  Changed paths:
M docs/ref/templates/builtins.txt

  Log Message:
  ---
  Fixed #23499 -- Error in built-in template tag "now" documentation


-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/541936c42e220_11453f88e7d5929c5880e8%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

73 matches

Mail list logo