date:20160215

Re: [Django] #26221: reusable-apps doc should include polls.migrations in setup.py packages

2016-02-15 Thread Django

#26221: reusable-apps doc should include polls.migrations in setup.py packages
---+
 Reporter:  tubaman|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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:"ca1f4390c432ba69898219a0f7d50c09b3a75781" ca1f439]:
 {{{
 #!CommitTicketReference repository=""
 revision="ca1f4390c432ba69898219a0f7d50c09b3a75781"
 [1.9.x] Fixed #26221 -- Used find_packages() in reusable apps tutorial.

 Otherwise the migrations package won't be included in the tarball.

 Backport of 11af73eaeb4371ded68460c1591abd6aefa57a90 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/065.879619cc0bd5ce6bbd6c86f813c4a07e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26221: reusable-apps doc should include polls.migrations in setup.py packages

2016-02-15 Thread Django

#26221: reusable-apps doc should include polls.migrations in setup.py packages
---+
 Reporter:  tubaman|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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:"4aab1d4bb36ff036eead142a4c76c01659d5954d" 4aab1d4b]:
 {{{
 #!CommitTicketReference repository=""
 revision="4aab1d4bb36ff036eead142a4c76c01659d5954d"
 [1.8.x] Fixed #26221 -- Used find_packages() in reusable apps tutorial.

 Otherwise the migrations package won't be included in the tarball.

 Backport of 11af73eaeb4371ded68460c1591abd6aefa57a90 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/065.ded1a5b88bfd60e286566f7b846ebc7e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26221: reusable-apps doc should include polls.migrations in setup.py packages

2016-02-15 Thread Django

#26221: reusable-apps doc should include polls.migrations in setup.py packages
---+
 Reporter:  tubaman|Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Documentation  |  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
---+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"11af73eaeb4371ded68460c1591abd6aefa57a90" 11af73e]:
 {{{
 #!CommitTicketReference repository=""
 revision="11af73eaeb4371ded68460c1591abd6aefa57a90"
 Fixed #26221 -- Used find_packages() in reusable apps tutorial.

 Otherwise the migrations package won't be included in the tarball.
 }}}

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

Re: [Django] #26214: Better error message for RuntimeError: populate() isn't reentrant

2016-02-15 Thread Django

#26214: Better error message for RuntimeError: populate() isn't reentrant
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  1.9
 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:

 The rationale makes sense to me.

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

Re: [Django] #26107: Add an option to int_list_validator to allow negative integers

2016-02-15 Thread Django

#26107: Add an option to int_list_validator to allow negative integers
+
 Reporter:  cooperjbrandon  |Owner:  akki
 Type:  New feature |   Status:  assigned
Component:  Core (Other)|  Version:  1.9
 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 timgraham):

 * needs_better_patch:  1 => 0


Comment:

 Don't forget to ticket the appropriate flags so the ticket appears in the
 [https://dashboard.djangoproject.com "Patches needing review" queue].

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

Re: [Django] #26107: Add an option to int_list_validator to allow negative integers

2016-02-15 Thread Django

#26107: Add an option to int_list_validator to allow negative integers
+
 Reporter:  cooperjbrandon  |Owner:  akki
 Type:  New feature |   Status:  assigned
Component:  Core (Other)|  Version:  1.9
 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 akki):

 PR: https://github.com/django/django/pull/6148

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

Re: [Django] #23833: Add a management command to drop all tables

2016-02-15 Thread Django

#23833: Add a management command to drop all tables
-+-
 Reporter:  MattBlack85  |Owner:
 |  MattBlack85
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   |  worksforme
 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 thenewguy):

 I tried this but it doesn't work with non-reversable migrations... raise
 Migration.IrreversibleError("Operation %s in %s is not reversible" %
 (operation, self))

 It would be handy to be able to clear a database even when the migrations
 cannot be reversed

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

Re: [Django] #26107: Add an option to int_list_validator to allow negative integers

2016-02-15 Thread Django

#26107: Add an option to int_list_validator to allow negative integers
+
 Reporter:  cooperjbrandon  |Owner:  akki
 Type:  New feature |   Status:  assigned
Component:  Core (Other)|  Version:  1.9
 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 akki):

 * owner:  nobody => akki
 * status:  new => assigned


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

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

Re: [Django] #24727: ClearableFileInput masks useful exceptions in is_initial()

2016-02-15 Thread Django

#24727: ClearableFileInput masks useful exceptions in is_initial()
-+-
 Reporter:  bluezio  |Owner:
 Type:   |  berkerpeksag
  Cleanup/optimization   |   Status:  closed
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   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 Berker Peksag ):

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


Comment:

 In [changeset:"043383e3f31955c493517cb5b12dd538c02f5246" 043383e3]:
 {{{
 #!CommitTicketReference repository=""
 revision="043383e3f31955c493517cb5b12dd538c02f5246"
 Fixed #24727 -- Prevented ClearableFileInput from masking exceptions on
 Python 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/065.31444203e4b58eecddb4161425c20055%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26214: Better error message for RuntimeError: populate() isn't reentrant

2016-02-15 Thread Django

#26214: Better error message for RuntimeError: populate() isn't reentrant
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  1.9
 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 aaugustin):

 I understand the reasoning behind this suggestion, but in my experience,
 trying to be smart with error handling often backfires, and my gut feeling
 is that this is too magical.

 Besides Python 3's exception chaining solves the problem entirely... Let's
 say that my motivation for doing something is non-existent, given that I
 don't plan to ever use Python 2 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/065.b93d5309c3f9b1c6ccc59006b3875908%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25759: Add **kwargs to as_sql method of Expressions

2016-02-15 Thread Django

#25759: Add **kwargs to as_sql method of Expressions
-+-
 Reporter:  jarshwah |Owner:
 |  kaifeldhoff
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  master
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  expressions  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by kaifeldhoff):

 * has_patch:  0 => 1


Comment:

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

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

Re: [Django] #26215: FloatRangeField/IntegerRangeField with None as a range boundary doesn't round trip in serialization

2016-02-15 Thread Django

#26215: FloatRangeField/IntegerRangeField with None as a range boundary doesn't
round trip in serialization
-+-
 Reporter:  bukin242 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  1.9
 Severity:  Normal   |   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):

 For the records, this might be a regression introduced by #24937.

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

Re: [Django] #25735: Add test tagging to Django test runner

2016-02-15 Thread Django

#25735: Add test tagging to Django test runner
---+
 Reporter:  carljm |Owner:  mrbox
 Type:  New feature|   Status:  assigned
Component:  Testing framework  |  Version:  1.8
 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 timgraham):

 * needs_better_patch:  1 => 0


Comment:

 [https://github.com/django/django/pull/6138 Updated PR]

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

Re: [Django] #26215: FloatRangeField/IntegerRangeField with None as a range boundary doesn't round trip in serialization

2016-02-15 Thread Django

#26215: FloatRangeField/IntegerRangeField with None as a range boundary doesn't
round trip in serialization
-+-
 Reporter:  bukin242 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.postgres |  Version:  1.9
 Severity:  Normal   |   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


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

Re: [Django] #26219: Cannot filter by DecimalField in RawQuery

2016-02-15 Thread Django

#26219: Cannot filter by DecimalField in RawQuery
-+-
 Reporter:  jirek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  DecimalField | Triage Stage:  Accepted
  RawQuery   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by charettes):

 * easy:  0 => 1


Comment:

 Marking as ''easy picking'' since a test can easily be written from 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/063.2d929ed4d48c268647890cc90b24ce65%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26223: Squashing migrations with preserve_default=False keeps the default

2016-02-15 Thread Django

#26223: Squashing migrations with preserve_default=False keeps the default
+
 Reporter:  bartekwojcicki  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 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


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

Re: [Django] #26215: FloatRangeField/IntegerRangeField with None as a range boundary doesn't round trip in serialization

2016-02-15 Thread Django

#26215: FloatRangeField/IntegerRangeField with None as a range boundary doesn't
round trip in serialization
--+
 Reporter:  bukin242  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 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 claudep):

 * needs_better_patch:  1 => 0


Comment:

 On [https://github.com/django/django/pull/6145 that PR], I fixed the
 problem by changing the serialization in the first place (outputting
 `null` instead of `'None'` from `RangeField.value_to_string`).

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

Re: [Django] #26214: Better error message for RuntimeError: populate() isn't reentrant

2016-02-15 Thread Django

#26214: Better error message for RuntimeError: populate() isn't reentrant
-+-
 Reporter:  guettli  |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  Version:  1.9
 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 timgraham):

 * owner:   => nobody
 * cc: aaugustin (added)
 * component:  Error reporting => Core (Other)
 * type:  Uncategorized => Cleanup/optimization


Comment:

 I'm not sure. Aymeric, what's your opinion?

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

Re: [Django] #26220: Allow SingleObjectTemplateResponseMixin to get a template_name from form_class if it's a ModelForm (was: CBV: Finding template_name from form_class if it's a ModelForm)

2016-02-15 Thread Django

#26220: Allow SingleObjectTemplateResponseMixin to get a template_name from
form_class if it's a ModelForm
---+
 Reporter:  nim65s |Owner:  nobody
 Type:  New feature|   Status:  new
Component:  Generic views  |  Version:  1.9
 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 timgraham):

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


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

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

Re: [Django] #26217: Docs for WeekArchiveView are misleading about %W

2016-02-15 Thread Django

#26217: Docs for WeekArchiveView are misleading about %W
---+
 Reporter:  konk   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  1.9
 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_docs:   => 0
 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Would be great if you could submit a patch since you apparently understand
 the 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/066.12a42444a7892503b47f849e01f9f9e9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26215: FloatRangeField/IntegerRangeField with None as a range boundary doesn't round trip in serialization (was: if dumpdata FloatRangeField and IntegerRangeField values = "None" and pos

2016-02-15 Thread Django

#26215: FloatRangeField/IntegerRangeField with None as a range boundary doesn't
round trip in serialization
--+
 Reporter:  bukin242  |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  Version:  1.9
 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 timgraham):

 * needs_better_patch:  0 => 1
 * component:  Database layer (models, ORM) => contrib.postgres
 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted


Old description:

> 1. FloatRangeField db data == None
> 2. ./manage dumpdata
> 3. ./manage loaddata
>
> Conversion problem. accept string u'None' to float type
>
> Track:
>   File "/local/lib/python2.7/site-
> packages/django/db/models/fields/__init__.py", line 1803, in to_python
> params={'value': value},
>
> Decision:
>
> {{{
>
> def to_python(self, value):
> if value == u'None':
> return None
> elif value is None:
> return value
> try:
> return float(value)
> except (TypeError, ValueError):
> raise exceptions.ValidationError(
> self.error_messages['invalid'],
> code='invalid',
> params={'value': value},
> )
> }}}
>
> And IntegerField too
>
> Source data dump example:
>
> {{{
> {"upper": "None", "lower":
> "1.45", "bounds": "[)"}
> }}}

New description:

 1. FloatRangeField db data == None
 2. ./manage dumpdata
 3. ./manage loaddata

 Conversion problem. accept string u'None' to float type

 Traceback:
 {{{
   File "/local/lib/python2.7/site-
 packages/django/db/models/fields/__init__.py", line 1803, in to_python
 params={'value': value},
 }}}
 Decision:

 {{{

 def to_python(self, value):
 if value == u'None':
 return None
 elif value is None:
 return value
 try:
 return float(value)
 except (TypeError, ValueError):
 raise exceptions.ValidationError(
 self.error_messages['invalid'],
 code='invalid',
 params={'value': value},
 )
 }}}

 And IntegerField too

 Source data dump example:

 {{{
 {"upper": "None", "lower":
 "1.45", "bounds": "[)"}
 }}}

--

Comment:

 I've understood the problem now and attached a test. Not sure if the
 proposed fix is correct.

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

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

Re: [Django] #26215: if dumpdata FloatRangeField and IntegerRangeField values = "None" and post loaddata is ValidationError

2016-02-15 Thread Django

#26215: if dumpdata FloatRangeField and IntegerRangeField values = "None" and 
post
loaddata is ValidationError
-+-
 Reporter:  bukin242 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 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 timgraham):

 * Attachment "26215-test2.diff" 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.5629991349b7d60f3e6f4a3e46fced66%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #26215: if dumpdata FloatRangeField and IntegerRangeField values = "None" and post loaddata is ValidationError

2016-02-15 Thread Django

#26215: if dumpdata FloatRangeField and IntegerRangeField values = "None" and 
post
loaddata is ValidationError
-+-
 Reporter:  bukin242 |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 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 timgraham):

 * Attachment "26215-test2.diff" 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.f62a88a603be548eb5f5f22376979fd1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24727: ClearableFileInput masks useful exceptions in is_initial()

2016-02-15 Thread Django

#24727: ClearableFileInput masks useful exceptions in is_initial()
-+-
 Reporter:  bluezio  |Owner:
 Type:   |  berkerpeksag
  Cleanup/optimization   |   Status:  assigned
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   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


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

Re: [Django] #26212: Forms' FileField is not pickleable

2016-02-15 Thread Django

#26212: Forms' FileField is not pickleable
-+-
 Reporter:  koterpillar  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.9
 Severity:  Normal   |   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:"180d4cbfe64f261ecb96bc15047c95c3b008fe4b" 180d4cb]:
 {{{
 #!CommitTicketReference repository=""
 revision="180d4cbfe64f261ecb96bc15047c95c3b008fe4b"
 [1.8.x] Fixed #26212 -- Made forms.FileField and translation.lazy_number()
 picklable.

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

Re: [Django] #26212: Forms' FileField is not pickleable

2016-02-15 Thread Django

#26212: Forms' FileField is not pickleable
-+-
 Reporter:  koterpillar  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.9
 Severity:  Normal   |   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:"765e6c411c11e6288f67c6782c919931eb114273" 765e6c4]:
 {{{
 #!CommitTicketReference repository=""
 revision="765e6c411c11e6288f67c6782c919931eb114273"
 [1.9.x] Fixed #26212 -- Made forms.FileField and translation.lazy_number()
 picklable.

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

Re: [Django] #26212: Forms' FileField is not pickleable

2016-02-15 Thread Django

#26212: Forms' FileField is not pickleable
-+-
 Reporter:  koterpillar  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.9
 Severity:  Normal   |   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:"b59f963ad2a49322725b20fac71661bd49643443" b59f963]:
 {{{
 #!CommitTicketReference repository=""
 revision="b59f963ad2a49322725b20fac71661bd49643443"
 Fixed #26212 -- Made forms.FileField and translation.lazy_number()
 picklable.
 }}}

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

Re: [Django] #23832: Storage API should provide a timezone aware approach

2016-02-15 Thread Django

#23832: Storage API should provide a timezone aware approach
--+
 Reporter:  jaylett   |Owner:  jaylett
 Type:  New feature   |   Status:  assigned
Component:  File uploads/storage  |  Version:  master
 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 timgraham):

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

Re: [Django] #26222: In migrating older project, after pip upgrade of Django to 1.9.2, Gunicorn crashes on failure to find validation

2016-02-15 Thread Django

#26222: In migrating older project, after pip upgrade of Django to 1.9.2, 
Gunicorn
crashes on failure to find validation
-+-
 Reporter:  JonathanHayward  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  upgrade, | Triage Stage:
  validation, gunicorn   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 "`run_gunicorn`, `gunicorn_django` and `gunicorn_paster` are now
 completely deprecated and will be removed in the next release. Use the
 `gunicorn` command instead."

 http://docs.gunicorn.org/en/stable/2014-news.html#deprecations

 I'll follow up with a pull request to actually remove it.

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

Re: [Django] #26224: Tutorial Part 5 (Testing) Generates app_label error

2016-02-15 Thread Django

#26224: Tutorial Part 5 (Testing) Generates app_label error
-+--
 Reporter:  EricBLivingston  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  worksforme
 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:   => worksforme


Comment:

 The tutorial works for me (and everyone else who's completed it since 1.9
 was released). It looks like you made a mistake somewhere and this isn't
 the place to get help debugging that. Of course, if you get help and find
 that there is actually some problem, then by all means reopen the ticket
 and let us know what the problem is.

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

Re: [Django] #26222: In migrating older project, after pip upgrade of Django to 1.9.2, Gunicorn crashes on failure to find validation

2016-02-15 Thread Django

#26222: In migrating older project, after pip upgrade of Django to 1.9.2, 
Gunicorn
crashes on failure to find validation
-+-
 Reporter:  JonathanHayward  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  upgrade, | Triage Stage:
  validation, gunicorn   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by JonathanHayward):

 I don't know what the problem is, but:

 root@localhost:~# pip install gunicorn
 Requirement already satisfied (use --upgrade to upgrade): gunicorn in
 /usr/local/lib/python2.7/dist-packages
 root@localhost:~# pip install --upgrade gunicorn
 Requirement already up-to-date: gunicorn in /usr/local/lib/python2.7/dist-
 packages

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

Re: [Django] #26224: Tutorial Part 5 (Testing) Generates app_label error

2016-02-15 Thread Django

#26224: Tutorial Part 5 (Testing) Generates app_label error
-+--
 Reporter:  EricBLivingston  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  worksforme
 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 EricBLivingston):

 Why was this closed? There's something missing in the tutorial, that
 prevents the tests from running correctly. I read that 1.9 introduces some
 restraints or requirements related to this app binding issue. Perhaps the
 tutorial has not been updated from 1.8 to accommodate that new
 requirement.

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

Re: [Django] #26224: Tutorial Part 5 (Testing) Generates app_label error

2016-02-15 Thread Django

#26224: Tutorial Part 5 (Testing) Generates app_label error
-+--
 Reporter:  EricBLivingston  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Documentation|  Version:  1.9
 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 EricBLivingston):

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


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

Re: [Django] #26224: Tutorial Part 5 (Testing) Generates app_label error

2016-02-15 Thread Django

#26224: Tutorial Part 5 (Testing) Generates app_label error
-+--
 Reporter:  EricBLivingston  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  1.9
 Severity:  Normal   |   Resolution:  worksforme
 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
 * needs_docs:   => 0
 * resolution:   => worksforme
 * needs_tests:   => 0
 * needs_better_patch:   => 0


Comment:

 Please see TicketClosingReasons/UseSupportChannels for ways to get help,
 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/073.38b96ce4f4db8a647b135e1a593c2a98%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[Django] #26224: Tutorial Part 5 (Testing) Generates app_label error

2016-02-15 Thread Django

#26224: Tutorial Part 5 (Testing) Generates app_label error
-+
 Reporter:  EricBLivingston  |  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Documentation|Version:  1.9
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 I have been walking through the Tutorial for Django, and upon reaching
 part 5 and introducing the first test case, I get this output (the
 directory I put the tutorial in is called 'demo')

 `RuntimeError: Model class demo.polls.models.Question doesn't declare an
 explicit app_label and isn't in an application in INSTALLED_APPS.`

 I tried adding a Meta section to the Question model, after doing some
 poking around in the docs.

 {{{
 #!python
 class Question(models.Model):
 question_text = models.CharField(max_length=200)
 pub_date = models.DateTimeField('date published')

 class Meta:
 app_label='polls'
 }}}

 But then I get this:

 `RuntimeError: Conflicting 'question' models in application 'polls':
  and .`

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

Re: [Django] #25409: Allow url and groups of urls to be easily tagged and selected

2016-02-15 Thread Django

#25409: Allow url and groups of urls to be easily tagged and selected
-+-
 Reporter:  atul-bhouraskar  |Owner:  atul-
 |  bhouraskar
 Type:  New feature  |   Status:  assigned
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Someday/Maybe
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by timgraham):

 [https://groups.google.com/d/topic/django-
 developers/Y6pJyqOmllA/discussion django-dev discussion].

 [https://github.com/django/django/pull/6141 PR] for another proposal:
 `url(r'^$', include('suburl'), wrap=[wrap1, wrap2])`.

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

Re: [Django] #25304: Allow management commands to check if database migrations are applied

2016-02-15 Thread Django

#25304: Allow management commands to check if database migrations are applied
-+-
 Reporter:  mlorant  |Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 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:"1ac7fdcd136bbb7ae5476cb54f670be20178c4e2" 1ac7fdcd]:
 {{{
 #!CommitTicketReference repository=""
 revision="1ac7fdcd136bbb7ae5476cb54f670be20178c4e2"
 Refs #25304 -- Added assertion for Command.requires_migrations_checks
 default.
 }}}

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

Re: [Django] #26126: Transient failure of requests.tests.RequestsTests.test_max_age_expiration

2016-02-15 Thread Django

#26126: Transient failure of 
requests.tests.RequestsTests.test_max_age_expiration
-+-
 Reporter:  charettes|Owner:
 Type:   |  berkerpeksag
  Cleanup/optimization   |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   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:"33b5bb79308c26615f55dc5eef85deb25f741ce2" 33b5bb79]:
 {{{
 #!CommitTicketReference repository=""
 revision="33b5bb79308c26615f55dc5eef85deb25f741ce2"
 [1.9.x] Fixed #26126 -- Fixed transient failure of test_max_age_expiration

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

Re: [Django] #26126: Transient failure of requests.tests.RequestsTests.test_max_age_expiration

2016-02-15 Thread Django

#26126: Transient failure of 
requests.tests.RequestsTests.test_max_age_expiration
-+-
 Reporter:  charettes|Owner:
 Type:   |  berkerpeksag
  Cleanup/optimization   |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   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:"927f43ea3add3cf92856c447bb021b59b22603df" 927f43ea]:
 {{{
 #!CommitTicketReference repository=""
 revision="927f43ea3add3cf92856c447bb021b59b22603df"
 [1.8.x] Fixed #26126 -- Fixed transient failure of test_max_age_expiration

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

Re: [Django] #26126: Transient failure of requests.tests.RequestsTests.test_max_age_expiration

2016-02-15 Thread Django

#26126: Transient failure of 
requests.tests.RequestsTests.test_max_age_expiration
-+-
 Reporter:  charettes|Owner:
 Type:   |  berkerpeksag
  Cleanup/optimization   |   Status:  closed
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"b17a9150a0c3a132e82b53755ede62a45f897875" b17a9150]:
 {{{
 #!CommitTicketReference repository=""
 revision="b17a9150a0c3a132e82b53755ede62a45f897875"
 Fixed #26126 -- Fixed transient failure of test_max_age_expiration
 }}}

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

Re: [Django] #26193: urlize doesn't handle extra punctuation after the link properly

2016-02-15 Thread Django

#26193: urlize doesn't handle extra punctuation after the link properly
---+-
 Reporter:  lsemel |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  Utilities  |  Version:  1.8
 Severity:  Normal |   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:"dec334cb66b3ee59cb82e1bb99a584aa0b9fbbd5" dec334c]:
 {{{
 #!CommitTicketReference repository=""
 revision="dec334cb66b3ee59cb82e1bb99a584aa0b9fbbd5"
 Fixed #26193 -- Made urlize() trim multiple trailing punctuation.
 }}}

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

Re: [Django] #26223: Squashing migrations with preserve_default=False keeps the default

2016-02-15 Thread Django

#26223: Squashing migrations with preserve_default=False keeps the default
+--
 Reporter:  bartekwojcicki  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  Migrations  |  Version:  1.8
 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 bartekwojcicki):

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


Old description:

> I have a migration with AlterField with default value provided and
> preserve_default=False. When I squash it, I got a CreateModel operation
> with default value for this field set.
>
> Steps to reproduce:
> 1. Create a model, make migrations.
> {{{
> #!div style="font-size: 80%"
>   {{{#!python
> class FooBar(models.Model):
> pass
>   }}}
> }}}
>
> 2. Add field without default,  make migrations, provide a one-off
> default.
> {{{
> #!div style="font-size: 80%"
>   {{{#!python
> class FooBar(models.Model):
> foo = models.TextField()
>   }}}
> }}}
>
> 3. Squash migrations.
> Squashed migrations keeps the default in CreateModel operation.
> {{{
> #!div style="font-size: 80%"
>   {{{#!python
> operations = [
> migrations.CreateModel(
> name='FooBar',
> fields=[
> ('id', models.AutoField(auto_created=True,
> primary_key=True, serialize=False, verbose_name='ID')),
> ('foo', models.TextField(default='bar')),
> ],
> ),
> ]
>   }}}
> }}}
>
> Running makemigrations again creates a migration with AlterField,
> removing the default
> {{{
> #!div style="font-size: 80%"
>   {{{#!python
> operations = [
> migrations.AlterField(
> model_name='foobar',
> name='foo',
> field=models.TextField(),
> ),
> ]
>   }}}
> }}}

New description:

 I have a migration with AlterField with default value provided and
 preserve_default=False. When I squash it, I got a CreateModel operation
 with default value for this field set.

 Steps to reproduce:
 1. Create a model, make migrations.
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 class FooBar(models.Model):
 pass
   }}}
 }}}

 2. Add field without default, make migrations, provide a one-off default.
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 class FooBar(models.Model):
 foo = models.TextField()
   }}}
 }}}

 3. Squash migrations.
 Squashed migration keeps the default in CreateModel operation.
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 operations = [
 migrations.CreateModel(
 name='FooBar',
 fields=[
 ('id', models.AutoField(auto_created=True,
 primary_key=True, serialize=False, verbose_name='ID')),
 ('foo', models.TextField(default='bar')),
 ],
 ),
 ]
   }}}
 }}}

 Running makemigrations again creates a migration with AlterField, removing
 the default.
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 operations = [
 migrations.AlterField(
 model_name='foobar',
 name='foo',
 field=models.TextField(),
 ),
 ]
   }}}
 }}}

--

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

[Django] #26223: Squashing migrations with preserve_default=False keeps the default

2016-02-15 Thread Django

#26223: Squashing migrations with preserve_default=False keeps the default
+
 Reporter:  bartekwojcicki  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  Migrations  |Version:  1.8
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 I have a migration with AlterField with default value provided and
 preserve_default=False. When I squash it, I got a CreateModel operation
 with default value for this field set.

 Steps to reproduce:
 1. Create a model, make migrations.
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 class FooBar(models.Model):
 pass
   }}}
 }}}

 2. Add field without default,  make migrations, provide a one-off default.
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 class FooBar(models.Model):
 foo = models.TextField()
   }}}
 }}}

 3. Squash migrations.
 Squashed migrations keeps the default in CreateModel operation.
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 operations = [
 migrations.CreateModel(
 name='FooBar',
 fields=[
 ('id', models.AutoField(auto_created=True,
 primary_key=True, serialize=False, verbose_name='ID')),
 ('foo', models.TextField(default='bar')),
 ],
 ),
 ]
   }}}
 }}}

 Running makemigrations again creates a migration with AlterField, removing
 the default
 {{{
 #!div style="font-size: 80%"
   {{{#!python
 operations = [
 migrations.AlterField(
 model_name='foobar',
 name='foo',
 field=models.TextField(),
 ),
 ]
   }}}
 }}}

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

Re: [Django] #26126: Transient failure of requests.tests.RequestsTests.test_max_age_expiration

2016-02-15 Thread Django

#26126: Transient failure of 
requests.tests.RequestsTests.test_max_age_expiration
-+-
 Reporter:  charettes|Owner:
 Type:   |  berkerpeksag
  Cleanup/optimization   |   Status:  assigned
Component:  Testing framework|  Version:  master
 Severity:  Normal   |   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


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

Re: [Django] #26219: Cannot filter by DecimalField in RawQuery

2016-02-15 Thread Django

#26219: Cannot filter by DecimalField in RawQuery
-+-
 Reporter:  jirek|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.9
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  DecimalField | Triage Stage:  Accepted
  RawQuery   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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

Re: [Django] #26222: In migrating older project, after pip upgrade of Django to 1.9.2, Gunicorn crashes on failure to find validation

2016-02-15 Thread Django

#26222: In migrating older project, after pip upgrade of Django to 1.9.2, 
Gunicorn
crashes on failure to find validation
-+-
 Reporter:  JonathanHayward  |Owner:  nobody
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.9
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  upgrade, | Triage Stage:
  validation, gunicorn   |  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
 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * resolution:   => invalid


Old description:

> 0
> down vote
> favorite
> I have an old Django project that I haven't kept up, and now I'd like to
> make necessary changes to work with current versions of Django and
> related software. I'm not sure what to make of the current error; it
> appears to me that it doesn't have something under the django.core
> umbrella, but my Django 1.9.2 installation is up to date:
>
> [2016-02-14 17:23:10 +] [4605] [ERROR] Exception in worker process:
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/dist-packages/gunicorn/arbiter.py", line
> 515, in spawn_worker
> worker.init_process()
>   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
> line 122, in init_process
> self.load_wsgi()
>   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
> line 130, in load_wsgi
> self.wsgi = self.app.wsgi()
>   File "/usr/local/lib/python2.7/dist-packages/gunicorn/app/base.py",
> line 67, in wsgi
> self.callable = self.load()
>   File "/usr/local/lib/python2.7/dist-
> packages/gunicorn/app/djangoapp.py", line 141, in load
> mod = util.import_module("gunicorn.app.django_wsgi")
>   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
> import_module
> __import__(name)
>   File "/usr/local/lib/python2.7/dist-
> packages/gunicorn/app/django_wsgi.py", line 21, in
> from django.core.management.validation import get_validation_errors
> ImportError: No module named validation
> Traceback (most recent call last):
>   File "/usr/local/lib/python2.7/dist-packages/gunicorn/arbiter.py", line
> 515, in spawn_worker
> worker.init_process()
>   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
> line 122, in init_process
> self.load_wsgi()
>   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
> line 130, in load_wsgi
> self.wsgi = self.app.wsgi()
>   File "/usr/local/lib/python2.7/dist-packages/gunicorn/app/base.py",
> line 67, in wsgi
> self.callable = self.load()
>   File "/usr/local/lib/python2.7/dist-
> packages/gunicorn/app/djangoapp.py", line 141, in load
> mod = util.import_module("gunicorn.app.django_wsgi")
>   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
> import_module
> __import__(name)
>   File "/usr/local/lib/python2.7/dist-
> packages/gunicorn/app/django_wsgi.py", line 21, in
> from django.core.management.validation import get_validation_errors
> ImportError: No module named validation
> [2016-02-14 17:23:10 +] [4605] [INFO] Worker exiting (pid: 4605)
> [2016-02-14 17:23:11 +] [4597] [INFO] Shutting down: Master
> [2016-02-14 17:23:11 +] [4597] [INFO] Reason: Worker failed to boot.
> root@localhost:~/unixytalk# pip install Django==1.9.2
> Requirement already satisfied (use --upgrade to upgrade): Django==1.9.2
> in /usr/local/lib/python2.7/dist-packages

New description:

 I have an old Django project that I haven't kept up, and now I'd like to
 make necessary changes to work with current versions of Django and related
 software. I'm not sure what to make of the current error; it appears to me
 that it doesn't have something under the django.core umbrella, but my
 Django 1.9.2 installation is up to date:
 {{{
 [2016-02-14 17:23:10 +] [4605] [ERROR] Exception in worker process:
 Traceback (most recent call last):
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/arbiter.py", line
 515, in spawn_worker
 worker.init_process()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
 line 122, in init_process
 self.load_wsgi()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
 line 130, in load_wsgi
 self.wsgi = self.app.wsgi()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/app/base.py", line
 67, in wsgi
 self.callable = self.load()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/app/djangoapp.py",
 line 141, in

Re: [Django] #10941: Add a templatetag to generate querystrings

2016-02-15 Thread Django

Comment (by funkybob):

Personally I think it wouldn't hurt to have a helper for the specific case
of altering the page number _only_.

In a prior project we ended up needing 4 different querystring
manipulators [and I'm sure there could have been more].

One would output the original, less any listed keys, plus any specified
keys _overridden_ in value.
One would just add new values.
One would return the original with only the listed keys.
A final just updated the page number.

This still doesn't cover, for instance, when you want to add a second
value to an existing key... or well, given it's a multi-dict, the
options are endless.

So, to reiterate: A _simple_ helper for helping with pagination, which is
a problem almost everyone encounters, would be good.

A general purpose querystring manipulator? Leave that to 3rd parties.

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

[Django] #26222: In migrating older project, after pip upgrade of Django to 1.9.2, Gunicorn crashes on failure to find validation

2016-02-15 Thread Django

#26222: In migrating older project, after pip upgrade of Django to 1.9.2, 
Gunicorn
crashes on failure to find validation
---+---
 Reporter: |  Owner:  nobody
  JonathanHayward  |
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.9
 Severity:  Normal |   Keywords:  upgrade, validation, gunicorn
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+---
 0
 down vote
 favorite
 I have an old Django project that I haven't kept up, and now I'd like to
 make necessary changes to work with current versions of Django and related
 software. I'm not sure what to make of the current error; it appears to me
 that it doesn't have something under the django.core umbrella, but my
 Django 1.9.2 installation is up to date:

 [2016-02-14 17:23:10 +] [4605] [ERROR] Exception in worker process:
 Traceback (most recent call last):
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/arbiter.py", line
 515, in spawn_worker
 worker.init_process()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
 line 122, in init_process
 self.load_wsgi()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
 line 130, in load_wsgi
 self.wsgi = self.app.wsgi()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/app/base.py", line
 67, in wsgi
 self.callable = self.load()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/app/djangoapp.py",
 line 141, in load
 mod = util.import_module("gunicorn.app.django_wsgi")
   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
 import_module
 __import__(name)
   File "/usr/local/lib/python2.7/dist-
 packages/gunicorn/app/django_wsgi.py", line 21, in
 from django.core.management.validation import get_validation_errors
 ImportError: No module named validation
 Traceback (most recent call last):
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/arbiter.py", line
 515, in spawn_worker
 worker.init_process()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
 line 122, in init_process
 self.load_wsgi()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/workers/base.py",
 line 130, in load_wsgi
 self.wsgi = self.app.wsgi()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/app/base.py", line
 67, in wsgi
 self.callable = self.load()
   File "/usr/local/lib/python2.7/dist-packages/gunicorn/app/djangoapp.py",
 line 141, in load
 mod = util.import_module("gunicorn.app.django_wsgi")
   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in
 import_module
 __import__(name)
   File "/usr/local/lib/python2.7/dist-
 packages/gunicorn/app/django_wsgi.py", line 21, in
 from django.core.management.validation import get_validation_errors
 ImportError: No module named validation
 [2016-02-14 17:23:10 +] [4605] [INFO] Worker exiting (pid: 4605)
 [2016-02-14 17:23:11 +] [4597] [INFO] Shutting down: Master
 [2016-02-14 17:23:11 +] [4597] [INFO] Reason: Worker failed to boot.
 root@localhost:~/unixytalk# pip install Django==1.9.2
 Requirement already satisfied (use --upgrade to upgrade): Django==1.9.2 in
 /usr/local/lib/python2.7/dist-packages

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

Re: [Django] #25251: Inconsistent availability of data migrations in TransactionTestCase when using --keepdb

2016-02-15 Thread Django

#25251: Inconsistent availability of data migrations in TransactionTestCase when
using --keepdb
---+
 Reporter:  davidszotten   |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Testing framework  |  Version:  1.8
 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 romgar):

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

Re: [Django] #22268: Document values_list() behavior for ManyToManyField

2016-02-15 Thread Django

#22268: Document values_list() behavior for ManyToManyField
-+-
 Reporter:  k_sze|Owner:
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:  orm, values_list,| Triage Stage:  Accepted
  ManyToManyField|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by psykrsna):

 * owner:  psykrsna =>
 * status:  assigned => new


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

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

50 matches

Mail list logo