date:20150401

[Django] #24562: Test failure: Pickleability

2015-04-01 Thread Django

#24562: Test failure: Pickleability
---+
   Reporter:  shaib|  Owner:  nobody
   Type:  Bug  | Status:  new
  Component:  Utilities|Version:  1.8
   Severity:  Release blocker  |   Keywords:
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  1
  UI/UX:  0|
---+
 Following the version bump to 1.8.1, we have failures on
 `test_unsupported_unpickle (queryset_pickle.tests.PickleabilityTestCase)`
 and `test_unsupported_unpickle
 (model_regress.test_pickle.ModelPickleTestCase)`. The problem is arguably
 in the test code: Both tests assume that
 `django.utils.version.get_major_version()` returns a `x.y` string, but
 that is only true for .0 minor versions -- and so the tests broke on the
 version bump to 1.8.1.

 I'm not quite sure about the fix --
 `django.utils.version.get_major_version()` looks like a public interface
 but it is not documented as far as I could see; it hasn't changed in a
 long time, but its return value is unintuitive, and I would expect the
 same as the author(s) of these tests.

--
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.88a8c82c6aba5bc94b8829568a57d781%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24561: Allow 'choices'-check to work for callables.

2015-04-01 Thread Django

#24561: Allow 'choices'-check to work for callables.
--+
 Reporter:  EnTeQuAk  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  Core (System checks)  |Version:  1.8
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  1
Easy pickings:  0 |  UI/UX:  0
--+
 Django 1.8 introduced the ability to pass a callable for 'choices' but it
 seems the check-framework was not adapted to this.

 Pull Request: https://github.com/django/django/pull/4434/

--
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/051.fdd2048a0b1ff3f1cbcb631f69c9858c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9739: Admin does not correctly prefill DataTimeField from URL

2015-04-01 Thread Django

#9739: Admin does not correctly prefill DataTimeField from URL
---+
 Reporter:  gilhad |Owner:  RidleyLarsen
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by RidleyLarsen):

 * owner:  dArignac => RidleyLarsen


--
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.c85626db564295b1490c5d4e38358ccb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9739: Admin does not correctly prefill DataTimeField from URL

2015-04-01 Thread Django

#9739: Admin does not correctly prefill DataTimeField from URL
---+
 Reporter:  gilhad |Owner:  dArignac
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+

Comment (by RidleyLarsen):

 Replying to [comment:12 timo]:
 > In any case, the patch needs to be updated to apply cleanly.

 I have attached a patch that applies cleanly and passes testing.

--
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.b32daecb1c6570ac9e0b0eba465e4869%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9739: Admin does not correctly prefill DataTimeField from URL

2015-04-01 Thread Django

#9739: Admin does not correctly prefill DataTimeField from URL
---+
 Reporter:  gilhad |Owner:  dArignac
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  1.0
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by RidleyLarsen):

 * Attachment "patch9739.diff" added.

 patch against a2e56db

--
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.b2a9d3d2bbeefa82e239eeec99efa24f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24554: Optimize migration's state rendering

2015-04-01 Thread Django

#24554: Optimize migration's state rendering
-+-
 Reporter:  ryanahall|Owner:  ryanahall
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"8f987323791181783d3f1ba847ffc0a938ddccdf" 8f987323]:
 {{{
 #!CommitTicketReference repository=""
 revision="8f987323791181783d3f1ba847ffc0a938ddccdf"
 Added Ryan Hall to AUTHORS. Refs #24554
 }}}

--
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.ef53c5c2daa0924938286cd623788011%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24560: createcachetable dry-run mode

2015-04-01 Thread Django

#24560: createcachetable dry-run mode
+
 Reporter:  adamchainz  |  Owner:  nobody
 Type:  Uncategorized   | Status:  new
Component:  Core (Management commands)  |Version:  1.8
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  1
Easy pickings:  0   |  UI/UX:  0
+
 When setting up a table for the DatabaseCache on a project I'm working on,
 I found it would be useful to see the SQL that createcachetable would run
 so it could be customized and stored in a migration. I had to manually
 edit the createcachetable.py file to achieve this, so I've added a proper
 dry-run mode.

--
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.6f1100ca7a7fd60f95eb27472364d94d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20264: URLValidator should allow underscores in local hostname

2015-04-01 Thread Django

#20264: URLValidator should allow underscores in local hostname
--+--
 Reporter:  arthurdebert  |Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  invalid
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by timgraham):

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


Comment:

 Please see TicketClosingReasons/DontReopenTickets, thanks!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.b286e7534c480767422a80b6b4a7ff8f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #20264: URLValidator should allow underscores in local hostname

2015-04-01 Thread Django

#20264: URLValidator should allow underscores in local hostname
--+--
 Reporter:  arthurdebert  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Unreviewed
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+--
Changes (by halayli):

 * status:  closed => new
 * has_patch:  1 => 0
 * resolution:  invalid =>


Comment:

 Since all major browsers support underscores, and DNS allows underscore
 domains, it's bound that when URLValidator is used to validate a user's
 input it will fail unexpectedly from the user's perspective.

 Strictly abiding by the RFC with complete disregard to pragmatism makes no
 sense. The least this highly opinionated class can offer is a strict flag.

--
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.4ce8bec6dd60755b6b9820ac3772b065%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24558: django-admin.py dumpdata should be deterministic for VCS and diff friendliness

2015-04-01 Thread Django

#24558: django-admin.py dumpdata should be deterministic for VCS and diff
friendliness
-+-
 Reporter:  gfairchild   |Owner:  charettes
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

 * needs_tests:  1 => 0


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.75b749cb399adf8b0271a8b86ec099c2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24558: django-admin.py dumpdata should be deterministic for VCS and diff friendliness

2015-04-01 Thread Django

#24558: django-admin.py dumpdata should be deterministic for VCS and diff
friendliness
-+-
 Reporter:  gfairchild   |Owner:  charettes
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by charettes):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.ccb114810b6bfd4ac61f1002b44e1202%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24558: django-admin.py dumpdata should be deterministic for VCS and diff friendliness

2015-04-01 Thread Django

#24558: django-admin.py dumpdata should be deterministic for VCS and diff
friendliness
-+-
 Reporter:  gfairchild   |Owner:  charettes
 Type:  New feature  |   Status:  assigned
Component:  Core (Management |  Version:  master
  commands)  |
 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 charettes):

 * owner:  nobody => charettes
 * status:  new => assigned
 * version:  1.7 => master
 * 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/068.0f1dc7d5025b54fcc34480796cd1533b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

2015-04-01 Thread Django

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
-+-
 Reporter:  pakal|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:   |  Version:  1.8rc1
  Internationalization   |
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

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


--
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/063.f023dc3b2e54afb08f66a16007c2fd02%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

2015-04-01 Thread Django

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
-+-
 Reporter:  pakal|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.8rc1
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"72de42cd401613197902370c812eaf607244d87c" 72de42cd]:
 {{{
 #!CommitTicketReference repository=""
 revision="72de42cd401613197902370c812eaf607244d87c"
 [1.8.x] Refs #24500 -- Avoided locale.getpreferredencoding in makemessages

 Fixes a regression introduced in 53c2cf1e.
 Backport of 3f4e77840 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/063.d559f67f4eac2f5689800b1d763705be%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

2015-04-01 Thread Django

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
-+-
 Reporter:  pakal|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.8rc1
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"3f4e77840249c533b08ef9f1d03d7e3387ed2b4c" 3f4e778]:
 {{{
 #!CommitTicketReference repository=""
 revision="3f4e77840249c533b08ef9f1d03d7e3387ed2b4c"
 Refs #24500 -- Avoided locale.getpreferredencoding in makemessages

 Fixes a regression introduced in 53c2cf1e.
 }}}

--
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/063.3d25b6faef91be45f18b171d8303e772%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

2015-04-01 Thread Django

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
-+-
 Reporter:  pakal|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.8rc1
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by claudep):

 You didn't have a problem before because you have an English locale, and
 the gettext response doesn't include any non-ascii character for you.

--
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/063.58a33377201b10aab3abc6a1be82f0e2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

2015-04-01 Thread Django

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
-+-
 Reporter:  pakal|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  1.8rc1
  Internationalization   |
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * stage:  Accepted => Ready for checkin


Comment:

 Patch works on my Windows. On the other hand, I didn't have a problem
 before this ticket.

--
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/063.83778fe676b48097ddf32028bb88f57e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24538: Rendering a Jinja template with a context containing 'self' fails

2015-04-01 Thread Django

#24538: Rendering a Jinja template with a context containing 'self' fails
-+-
 Reporter:  tim_heap |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8rc1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
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:"5a4f95805f9b4f709cfcac53a453b59bd40a9946" 5a4f9580]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a4f95805f9b4f709cfcac53a453b59bd40a9946"
 [1.8.x] Refs #24538 -- Simplified a test per Aymeric's feedback.

 Backport of a184a99123e4dc4c2a90c20e1604e5d301cd76bf 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/066.29dcb59949525ea53f757ce899deef6c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24555: Wrong content in inclusion templatetags with variable parent template

2015-04-01 Thread Django

Comment (by Tim Graham ):

In [changeset:"5c63c45512eeca1f9c2dbdb0c46cbc7d9c550bdc" 5c63c45]:
{{{
#!CommitTicketReference repository=""
revision="5c63c45512eeca1f9c2dbdb0c46cbc7d9c550bdc"
[1.8.x] Fixed #23441, #24555 -- Improved the behavior of InclusionNode.

This change:

* Makes the InclusionNode cache-safe by removing render-time side effects
to its nodelist.
* Ensures the render_context stack is properly scoped and reset by
updating
the render call to use Template.render rather than Nodelist.render.

Backport of 0808ccce3808235c5b5a56e3f689cec0d4bc0ebf 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/072.c758c3979713e5f0d4815caab0db2141%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23441: Maximum recursion depth exceeded when using custom `inclusion_tag` with recursion in templates and `django.template.loaders.cached.Loader`

2015-04-01 Thread Django

#23441: Maximum recursion depth exceeded when using custom `inclusion_tag` with
recursion in templates and `django.template.loaders.cached.Loader`
-+
Reporter: vstoykov |Owner: nobody
Type: Bug | Status: closed
Component: Template system | Version: 1.7
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1| Needs documentation: 0
Needs tests: 1| Patch needs improvement: 0
Easy pickings: 0|UI/UX: 0
-+

Comment (by Tim Graham ):

This change:

Backport of 0808ccce3808235c5b5a56e3f689cec0d4bc0ebf 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/066.251fa5772f37d331daaeb1d940386b23%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24538: Rendering a Jinja template with a context containing 'self' fails

2015-04-01 Thread Django

#24538: Rendering a Jinja template with a context containing 'self' fails
-+-
 Reporter:  tim_heap |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8rc1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
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:"a184a99123e4dc4c2a90c20e1604e5d301cd76bf" a184a99]:
 {{{
 #!CommitTicketReference repository=""
 revision="a184a99123e4dc4c2a90c20e1604e5d301cd76bf"
 Refs #24538 -- Simplified a test per Aymeric's feedback.
 }}}

--
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.600fa1fb38e5653156368436e0696ef5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24558: django-admin.py dumpdata should be deterministic for VCS and diff friendliness

2015-04-01 Thread Django

#24558: django-admin.py dumpdata should be deterministic for VCS and diff
friendliness
-+-
 Reporter:  gfairchild   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.7
  commands)  |
 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
-+-

Comment (by gfairchild):

 Sure, so here's an example model I have in my `swap` app:

 {{{
 class Term(models.Model):
 term = models.CharField(max_length=255)
 definition = models.TextField()
 reference = models.TextField()
 }}}

 I've attached the output from two consecutive dumps (`./manage.py dumpdata
 swap.Term`).

 You can see that the content of each file is identical. And as you say,
 the objects are indeed sorted by their primary key. The ordering issue is
 with the key-value pairs printed for each object. Each object is just a
 dictionary of keys and values, so there's no ordering maintained.

--
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.d7646789ca2a4f0f4362dbdc523c39af%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24558: django-admin.py dumpdata should be deterministic for VCS and diff friendliness

2015-04-01 Thread Django

#24558: django-admin.py dumpdata should be deterministic for VCS and diff
friendliness
-+-
 Reporter:  gfairchild   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.7
  commands)  |
 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 gfairchild):

 * Attachment "terms2.json" added.

 terms dump 2

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.94bf2557597ea649cd0041d93c6e5fdb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24558: django-admin.py dumpdata should be deterministic for VCS and diff friendliness

2015-04-01 Thread Django

#24558: django-admin.py dumpdata should be deterministic for VCS and diff
friendliness
-+-
 Reporter:  gfairchild   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.7
  commands)  |
 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 gfairchild):

 * Attachment "terms1.json" added.

 terms dump 1

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.8b8250a37f85a22f325c6b47263ef9b1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23441: Maximum recursion depth exceeded when using custom `inclusion_tag` with recursion in templates and `django.template.loaders.cached.Loader`

2015-04-01 Thread Django

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

Comment:

In [changeset:"0808ccce3808235c5b5a56e3f689cec0d4bc0ebf" 0808ccc]:
{{{
#!CommitTicketReference repository=""
revision="0808ccce3808235c5b5a56e3f689cec0d4bc0ebf"
Fixed #23441, #24555 -- Improved the behavior of InclusionNode.

This change:

--
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.3862270375b64eaaf8d17992ac763d9c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24555: Wrong content in inclusion templatetags with variable parent template

2015-04-01 Thread Django

#24555: Wrong content in inclusion templatetags with variable parent template
-+-
 Reporter:  benjaminrigaud   |Owner:  Tim
 |  Graham 
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8rc1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:  templatetags | Triage Stage:  Ready for
  extends block cache|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  new => closed
 * owner:   => Tim Graham 
 * resolution:   => fixed


Comment:

 In [changeset:"0808ccce3808235c5b5a56e3f689cec0d4bc0ebf" 0808ccc]:
 {{{
 #!CommitTicketReference repository=""
 revision="0808ccce3808235c5b5a56e3f689cec0d4bc0ebf"
 Fixed #23441, #24555 -- Improved the behavior of InclusionNode.

 This change:

 * Makes the InclusionNode cache-safe by removing render-time side effects
   to its nodelist.
 * Ensures the render_context stack is properly scoped and reset by
 updating
   the render call to use Template.render rather than Nodelist.render.
 }}}

--
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/072.2d05e2333b56128ac8bcc7096969be5c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

2015-04-01 Thread Django

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
--+
 Reporter:  pakal |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  1.8rc1
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * has_patch:  0 => 1


Comment:

 PR https://github.com/django/django/pull/4425
 `locale.getpreferredencoding(False)` is not usable. For example, it
 returns `ANSI_X3.4-1968` on my system!
 The patch needs to be tested on Windows now.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/063.02424cc573c4bc6b23ac3885877ffe38%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24555: Wrong content in inclusion templatetags with variable parent template

2015-04-01 Thread Django

#24555: Wrong content in inclusion templatetags with variable parent template
-+-
 Reporter:  benjaminrigaud   |Owner:
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8rc1
 Severity:  Release blocker  |   Resolution:
 Keywords:  templatetags | Triage Stage:  Ready for
  extends block cache|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * 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/072.6d9963a44b9ce52b4359384229b66be1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24538: Rendering a Jinja template with a context containing 'self' fails

2015-04-01 Thread Django

#24538: Rendering a Jinja template with a context containing 'self' fails
-+-
 Reporter:  tim_heap |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8rc1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"4ea1909d3c420ba1fbdbf7221cad518d43aef885" 4ea1909]:
 {{{
 #!CommitTicketReference repository=""
 revision="4ea1909d3c420ba1fbdbf7221cad518d43aef885"
 Fixed #24538 -- Allowed self in Jinja context

 Rendering a Jinja template with self in the context threw an error.
 While self is a reserved variable in Jinja, including self in the
 context is not an error, so Django should respect that.
 }}}

--
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.7ff727bdf67cc6671c54db3e3420359a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24538: Rendering a Jinja template with a context containing 'self' fails

2015-04-01 Thread Django

#24538: Rendering a Jinja template with a context containing 'self' fails
-+-
 Reporter:  tim_heap |Owner:  charettes
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.8rc1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
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:"ff8eabc5ccb7af928856910c8af72d84346821e9" ff8eabc]:
 {{{
 #!CommitTicketReference repository=""
 revision="ff8eabc5ccb7af928856910c8af72d84346821e9"
 [1.8.x] Fixed #24538 -- Allowed self in Jinja context

 Rendering a Jinja template with self in the context threw an error.
 While self is a reserved variable in Jinja, including self in the
 context is not an error, so Django should respect that.

 Backport of 4ea1909d3c420ba1fbdbf7221cad518d43aef885 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/066.83e336273f0e886ac66a247997083b3f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24500: Django runtests - 3 tests fail on windows due to encoding troubles

2015-04-01 Thread Django

#24500: Django runtests - 3 tests fail on windows due to encoding troubles
--+
 Reporter:  pakal |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Internationalization  |  Version:  1.8rc1
 Severity:  Release blocker   |   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

 * status:  closed => new
 * severity:  Normal => Release blocker
 * version:  master => 1.8rc1
 * has_patch:  1 => 0
 * resolution:  fixed =>
 * stage:  Ready for checkin => Accepted


Comment:

 Now those tests are failing on my system :-/ I'll try to debug this issue.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/063.03a1e6f57aed8b604324977128d7ba7a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22608: Migrations optimizer slow (due to double working?)

2015-04-01 Thread Django

#22608: Migrations optimizer slow (due to double working?)
--+
 Reporter:  davids|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Migrations|  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 mvantellingen):

 * cc: michaelvantellingen@… (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/064.615b7e1613eca83023ffcb6249ca778f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24555: Wrong content in inclusion templatetags with variable parent template

2015-04-01 Thread Django

#24555: Wrong content in inclusion templatetags with variable parent template
-+-
 Reporter:  benjaminrigaud   |Owner:
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8rc1
 Severity:  Release blocker  |   Resolution:
 Keywords:  templatetags | Triage Stage:  Accepted
  extends block cache|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by prestontimmons):

 * has_patch:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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/072.fed0a320790d8b5e26bed251ab9fb480%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24538: Rendering a Jinja template with a context containing 'self' fails

2015-04-01 Thread Django

#24538: Rendering a Jinja template with a context containing 'self' fails
-+-
 Reporter:  tim_heap |Owner:  charettes
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8rc1
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * has_patch:  0 => 1
 * 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/066.f7bde0c813d27485790ad5ce5b20685b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24543: Add checks / command options for "migrations not applied" and "migrations needed"

2015-04-01 Thread Django

#24543: Add checks / command options for "migrations not applied" and 
"migrations
needed"
-+--
 Reporter:  blueyed  |Owner:
 Type:  New feature  |   Status:  closed
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  wontfix
 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 timgraham):

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


Comment:

 Closing in absence of a clear way to move this ticket forward (also it is
 a little confusing with multiple feature requests, some of which are
 already addressed.)

--
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.fde3479d21ecb0c98208ef9aff3d5e47%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs py2

2015-04-01 Thread Django

#24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs
py2
+
 Reporter:  kezabelle   |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  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 timgraham):

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


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.68807e43af8983a88a4e73ec263ee586%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24553: Pass application list to more admin views

2015-04-01 Thread Django

#24553: Pass application list to more admin views
---+
 Reporter:  rm_|Owner:  nobody
 Type:  New feature|   Status:  new
Component:  contrib.admin  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords:  admin  | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * 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/061.51670a8fc7d7127a2c0db23baf516cde%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24523: django.apps.registry.populate() does not handle failures in app_config.ready()

2015-04-01 Thread Django

#24523: django.apps.registry.populate() does not handle failures in
app_config.ready()
--+
 Reporter:  kalium99  |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Core (Other)  |  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 timgraham):

 * component:  Uncategorized => Core (Other)
 * version:  1.7 => master
 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.9c4c3d6c964e6f3c643b7a451a8ffec7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24554: Optimize migration's state rendering (was: Migrations taking up to an hour to run)

2015-04-01 Thread Django

#24554: Optimize migration's state rendering
-+-
 Reporter:  ryanahall|Owner:  ryanahall
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

--
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.68fe95cfe463d28c2befb54c943d06c5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24554: Migrations taking up to an hour to run

2015-04-01 Thread Django

#24554: Migrations taking up to an hour to run
-+-
 Reporter:  ryanahall|Owner:  ryanahall
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Markus Holtermann ):

 In [changeset:"0c7e2833d9b6f0bbd847d9b9b0eb368611425f7c" 0c7e283]:
 {{{
 #!CommitTicketReference repository=""
 revision="0c7e2833d9b6f0bbd847d9b9b0eb368611425f7c"
 [1.8.x] Fixed #24554 -- Sped up migrations by rendering initial apps when
 they are first needed

 Calling Migration.mutate_state() now also allows to do in_place
 mutations in case an intermediate state is thrown away later.

 Thanks Anssi Kääriäinen for the idea, Ryan Hall for parts of the patch,
 and Claude Paroz and Tim Graham for the review

 Backport of 57dc8dd3fa3c3adf133c522ecadb501d94bacd52 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/067.69fc1c19fca4a6f41c05a3cc849715e6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24554: Migrations taking up to an hour to run

2015-04-01 Thread Django

#24554: Migrations taking up to an hour to run
-+-
 Reporter:  ryanahall|Owner:  ryanahall
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Migrations   |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Markus Holtermann ):

 In [changeset:"2218f7617e6192a706bf7792db34b034765263e2" 2218f761]:
 {{{
 #!CommitTicketReference repository=""
 revision="2218f7617e6192a706bf7792db34b034765263e2"
 [1.8.x] Refs #24554 -- Prevented rendering of unused migrations

 Thanks Claude Paroz and Tim Graham for the review

 Backport of 3e7d9d05ac5efff4e4732c3453c7a8ef502d0ed0 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/067.bbf85e596f3ecb2e959e7425031cd3d9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #18707: Test client doesn't allow testing 500 responses content

2015-04-01 Thread Django

#18707: Test client doesn't allow testing 500 responses content
---+
 Reporter:  ricardokirkner@…   |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Testing framework  |  Version:  1.6
 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 spacediver):

 Hi folks,

 Currently I need to test not even 500 user-facing view, but email sending
 on 500.

 Is there any way to trigger production error handling from within unit
 test with django client (or otherwise from unit test)?

 I strongly hesitate to move this into Selenium integration tests due to
 need of full-fledged email mocking (instead of neat and sweat locmem email
 backend that I may use in unit tests).

 Thanks!

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To 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.3800ddf398f05b5b3b17ac1f60d4b9b9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs py2

2015-04-01 Thread Django

#24559: MigrationLoader.load_disk ImportError handling differs under py3/pypy vs
py2
+
 Reporter:  kezabelle   |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  master
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Currently, within `load_disk`, the following happens:

 {{{
 try:
 module = import_module(module_name)
 except ImportError as e:
 # I hate doing this, but I don't want to squash other
 import errors.
 # Might be better to try a directory check directly.
 if "No module named" in str(e) and MIGRATIONS_MODULE_NAME
 in str(e):
 self.unmigrated_apps.add(app_config.label)
 continue
 raise
 }}}

 However, the
 
[https://github.com/django/django/blob/2832a9b028c267997b2fd3dd0989670d57cdd08f/django/db/migrations/loader.py#L73
 if statement] behaves differently under pypy & python3, because the
 exception string is different.

 Under python2, the following yields
 {{{
 >>> from importlib import import_module
 >>> importlib('test_auth.migrations')
 ImportError: No module named test_auth.migrations
 }}}

 which would hit both parts of the conditional, and end up in
 `self.unmigrated_apps`

 However, under python3.3.3 the exception is:
 {{{
 ImportError: No module named 'test_auth'
 }}}
 and under pypy 2.2.1 (for python 2.7.3) the exception is:
 {{{
 ImportError: No module named test_auth
 }}}
 (same as py3k, sans quotes)

 Neither of these would end up `self.unmigrated_apps` because
 `MIGRATIONS_MODULE_NAME` doesn't appear in the string representation,
 though I suspect `import_module('testauthmigrations')` '''would''' work.

 I originally noticed this because of a [https://travis-ci.org/kezabelle
 /django-typesafetynet/builds/55545694 travis build] for a toy project, so
 it may not be a problem in practice, but it is at least inconsistent.

--
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.53d132b4eb629a819f162cfbdfbf2062%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24558: django-admin.py dumpdata should be deterministic for VCS and diff friendliness

2015-04-01 Thread Django

#24558: django-admin.py dumpdata should be deterministic for VCS and diff
friendliness
-+-
 Reporter:  gfairchild   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  1.7
  commands)  |
 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 claudep):

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


Comment:

 Agreed that deterministic ordering is a desirable goal. Now can you tell
 us what sort of changed ordering are you seeing in your data? It should
 not be with objects themselves, as they are sorted by their primary key.
 Is it an issue with `serializers.sort_dependencies` which gives the model
 ordering?

--
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.d2efef0de99206343b73ea9741657040%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

44 matches

Mail list logo