date:20151117

Re: [Django] #25770: authenticate and login can not write cookie 'sessionid'

2015-11-17 Thread Django

#25770: authenticate and login can not write cookie 'sessionid'
-+-
 Reporter:  mrgaolei |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  contrib.auth |  Version:  1.8
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  authenticate login   | Triage Stage:
  session|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mrgaolei):

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


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

Re: [Django] #25770: authenticate and login can not write cookie 'sessionid'

2015-11-17 Thread Django

#25770: authenticate and login can not write cookie 'sessionid'
-+-
 Reporter:  mrgaolei |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.auth |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:  authenticate login   | Triage Stage:
  session|  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by mrgaolei):

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


Comment:

 Is my fault!
 I don't return any HttpResponse, so the status of HTTP is not 2xx or 3xx,
 so any session operation are rollback.

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

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

2015-11-17 Thread Django

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 georgemarshall):

 The CI server seems to have crashed out, needs to be rerun.

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

[Django] #25770: authenticate and login can not write cookie 'sessionid'

2015-11-17 Thread Django

#25770: authenticate and login can not write cookie 'sessionid'
--+
 Reporter:  mrgaolei  |  Owner:  nobody
 Type:  Bug   | Status:  new
Component:  contrib.auth  |Version:  1.8
 Severity:  Normal|   Keywords:  authenticate login session
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 If I use 'django.contrib.auth.urls' login, everything are OK, cookie
 'sessionid' writes to Browser.

 But, when I login Manually, like:

 {{{
 from django.contrib.auth import authenticate, login, logout
 def some_view(request):
 user = authenticate(username="mrgaolei", password="123456")
 if user is not None:
 login(request, user)
 }}}

 No any exceptions, but user not loginged, and no cookie 'sessionid' writes
 to Browser.
 My settings.py is generated by manage.py startproject.

 I tried capture login status like:

 {{{
 from django.contrib.auth import authenticate, login, logout
 def some_view(request):
 print request.user.is_authenticated()
 user = authenticate(username="mrgaolei", password="123456")
 if user is not None:
 login(request, user)
 print request.user.is_authenticated()
 }}}

 When I refresh this url, terminal output:
 {{{
 False
 True
 }}}

 It seems the 'login' method writes the 'sessionid` cookie expire only 1
 second.
 Is this a bug? Or my fault?

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

Re: [Django] #25321: Make it clear that django.db.backends.schema messages (which can propogate to django.db.backends) don't include 'duration'

2015-11-17 Thread Django

#25321: Make it clear that django.db.backends.schema messages (which can 
propogate
to django.db.backends) don't include 'duration'
--+
 Reporter:  netpositive36 |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:  logging, db   | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by timgraham):

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


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

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

Re: [Django] #25104: Documentation assumes that there's a httpd.conf

2015-11-17 Thread Django

#25104: Documentation assumes that there's a httpd.conf
--+
 Reporter:  ChristianKleineidam   |Owner:
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  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:  1 |UI/UX:  0
--+
Changes (by timgraham):

 * owner:  slick666 =>
 * 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/077.b8b93a2c01df43167d35203b43ffca8c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

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

2015-11-17 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:  1
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timgraham):

 * needs_better_patch:  0 => 1
 * stage:  Ready for checkin => Accepted


Comment:

 Left comments for improvement.

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

Re: [Django] #25356: startapp template mustn't encourage using default_app_config

2015-11-17 Thread Django

#25356: startapp template mustn't encourage using default_app_config
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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:"6258e163352690faf20bfc92c12468316d1a47ae" 6258e163]:
 {{{
 #!CommitTicketReference repository=""
 revision="6258e163352690faf20bfc92c12468316d1a47ae"
 Refs #24971, #25356 -- Clarified how apps.py works in 1.9 release notes.
 }}}

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

Re: [Django] #25356: startapp template mustn't encourage using default_app_config

2015-11-17 Thread Django

#25356: startapp template mustn't encourage using default_app_config
-+-
 Reporter:  aaugustin|Owner:  aaugustin
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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:"7bbfc43e34c1909b8edfc8e3188c35447cffef15" 7bbfc43e]:
 {{{
 #!CommitTicketReference repository=""
 revision="7bbfc43e34c1909b8edfc8e3188c35447cffef15"
 [1.9.x] Refs #24971, #25356 -- Clarified how apps.py works in 1.9 release
 notes.

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

Re: [Django] #24971: Make startapp generate an apps.py

2015-11-17 Thread Django

#24971: Make startapp generate an apps.py
-+-
 Reporter:  timgraham|Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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:"7bbfc43e34c1909b8edfc8e3188c35447cffef15" 7bbfc43e]:
 {{{
 #!CommitTicketReference repository=""
 revision="7bbfc43e34c1909b8edfc8e3188c35447cffef15"
 [1.9.x] Refs #24971, #25356 -- Clarified how apps.py works in 1.9 release
 notes.

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

Re: [Django] #24971: Make startapp generate an apps.py

2015-11-17 Thread Django

#24971: Make startapp generate an apps.py
-+-
 Reporter:  timgraham|Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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:"6258e163352690faf20bfc92c12468316d1a47ae" 6258e163]:
 {{{
 #!CommitTicketReference repository=""
 revision="6258e163352690faf20bfc92c12468316d1a47ae"
 Refs #24971, #25356 -- Clarified how apps.py works in 1.9 release notes.
 }}}

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

Re: [Django] #25768: Cast Variable, and provide multiplication

2015-11-17 Thread Django

#25768: Cast Variable, and provide multiplication
+--
 Reporter:  BenLiyanage |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Uncategorized   |  Version:  1.8
 Severity:  Normal  |   Resolution:
 Keywords:  QuerySet.extra  | 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):

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


Comment:

 I think `Cast` is covered by #24932.

 I think Django already supports
 [https://docs.djangoproject.com/en/stable/ref/models/expressions
 /#supported-arithmetic multiplication in F expressions]. Does that work
 for your case?

 For future reference, please keep a ticket limited to 1 request.

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

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

Re: [Django] #25769: Update utils.version.get_version() for new release candidate naming scheme

2015-11-17 Thread Django

#25769: Update utils.version.get_version() for new release candidate naming 
scheme
--+
 Reporter:  timgraham |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Utilities |  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):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/5676 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/067.a06ad7a28a72cc682abde5830f4741e7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25766: adding javascript "this.disabled" invalidate ManyToManyField

2015-11-17 Thread Django

#25766: adding javascript "this.disabled" invalidate ManyToManyField
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.7
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by timgraham):

 I think this is covered by #16730.

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

Re: [Django] #25766: adding javascript "this.disabled" invalidate ManyToManyField

2015-11-17 Thread Django

#25766: adding javascript "this.disabled" invalidate ManyToManyField
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.7
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by liwee):

 I added the javascript to prevent multiple button clicks; Whilst
 submitting credit card details for payment, some sites disable the submit
 button to prevent multiple payments, I am just trying to mimic that
 behaviour.

 If you comment {{{filter_horizontal = ('qn',)}}} and try again, saving
 will not cause a problem. Originally, I had the impression that it was a
 problem with ManyToManyField because I was able to save other fields
 without a problem.

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

[Django] #25769: Update utils.version.get_version() for new release candidate naming scheme

2015-11-17 Thread Django

#25769: Update utils.version.get_version() for new release candidate naming 
scheme
+
   Reporter:  timgraham |  Owner:  nobody
   Type:  Cleanup/optimization  | Status:  new
  Component:  Utilities |Version:  master
   Severity:  Normal|   Keywords:
   Triage Stage:  Accepted  |  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 For release candidate versions, setuptools 8.0+ generates filenames like
 "Django-1.9rc1.tar.gz" instead "Django-1.9c1.tar.gz" ('rc' instead of
 'c').

 PEP 386 has been superseded by PEP 440 which recommends “rc” because
 almost everyone was using “rc” and not “c”.

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

Re: [Django] #25526: Document how to output color from custom management commands

2015-11-17 Thread Django

#25526: Document how to output color from custom management commands
--+
 Reporter:  bmispelon |Owner:  elenaoat
 Type:  Cleanup/optimization  |   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:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"a9f1ea32750be33385d7ba014f9ed63d6ee695d6" a9f1ea32]:
 {{{
 #!CommitTicketReference repository=""
 revision="a9f1ea32750be33385d7ba014f9ed63d6ee695d6"
 [1.8.x] Fixed #25526 -- Documented how to output colored text in custom
 management commands.

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

Re: [Django] #25526: Document how to output color from custom management commands

2015-11-17 Thread Django

#25526: Document how to output color from custom management commands
--+
 Reporter:  bmispelon |Owner:  elenaoat
 Type:  Cleanup/optimization  |   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:  1
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Tim Graham ):

 In [changeset:"43da3179a46c9000532a46674424923d98f5434b" 43da3179]:
 {{{
 #!CommitTicketReference repository=""
 revision="43da3179a46c9000532a46674424923d98f5434b"
 [1.9.x] Fixed #25526 -- Documented how to output colored text in custom
 management commands.

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

Re: [Django] #25526: Document how to output color from custom management commands

2015-11-17 Thread Django

#25526: Document how to output color from custom management commands
--+
 Reporter:  bmispelon |Owner:  elenaoat
 Type:  Cleanup/optimization  |   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:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"d26207d56cab21e3767121d53ebaddbbfc78a4ce" d26207d]:
 {{{
 #!CommitTicketReference repository=""
 revision="d26207d56cab21e3767121d53ebaddbbfc78a4ce"
 Fixed #25526 -- Documented how to output colored text in custom management
 commands.
 }}}

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

[Django] #25768: Cast Variable, and provide multiplication

2015-11-17 Thread Django

#25768: Cast Variable, and provide multiplication
---+
 Reporter:  BenLiyanage|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:  QuerySet.extra
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 Hey,

 I'm trying to do an orm query and have run into two scenarios where I
 believe I need to use extra.  The two scenarios are:

 == Type Casting

 Casting a column to an int. Specifically, I have a boolean column that I
 need to do something like this:

 select column::int

 == Multiplication

 I need to multiply a column by a constant, or another column.
 Specifically the column from the previous cast.

 select new_column * -1
 select column1 * column2

 == Full Select Example

 Ultimately I need to combine the above two like this:

 select bool_column::int * -1 * another_int_column

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

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

Re: [Django] #25682: Audit bare except clauses

2015-11-17 Thread Django

#25682: Audit bare except clauses
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Other) |  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:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"0a2d3b7387b815b4e5d5f3c026f8409fd2a7ff70" 0a2d3b7]:
 {{{
 #!CommitTicketReference repository=""
 revision="0a2d3b7387b815b4e5d5f3c026f8409fd2a7ff70"
 Fixed #25682 -- Removed bare except clauses.
 }}}

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

Re: [Django] #25695: csrf_failure view should take a template parameter

2015-11-17 Thread Django

#25695: csrf_failure view should take a template parameter
-+-
 Reporter:  raphaelm |Owner:  raphaelm
 Type:  New feature  |   Status:  closed
Component:  Uncategorized|  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:"16945f0e9c57aeabadb6f2e2f150a2687455be40" 16945f0e]:
 {{{
 #!CommitTicketReference repository=""
 revision="16945f0e9c57aeabadb6f2e2f150a2687455be40"
 Fixed #25695 -- Added template_name parameter to csrf_failure() view.
 }}}

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

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

Re: [Django] #11313: list_editable fields don't support 'save' in multiuser environment

2015-11-17 Thread Django

#11313: list_editable fields don't support 'save' in multiuser environment
+
 Reporter:  margieroginski  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.1-beta
 Severity:  Normal  |   Resolution:
 Keywords:  model formsets  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+

Comment (by timgraham):

 I suspect so, but you could try your test on Django 1.7 to see if it fails
 there as patjlm indicated he could reproduce the issue there.

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

Re: [Django] #11313: list_editable fields don't support 'save' in multiuser environment

2015-11-17 Thread Django

#11313: list_editable fields don't support 'save' in multiuser environment
+
 Reporter:  margieroginski  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.1-beta
 Severity:  Normal  |   Resolution:
 Keywords:  model formsets  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  1
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+
Changes (by benred42):

 * cc: benred42@… (added)


Comment:

 Is this issue still present in 1.8?  I was attempting to write a test for
 the issue and could not reproduce the issue as stated in the 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/072.4998bf0bfe4944e4039da0fedefcd45d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25621: AlterField to ForeignKey reverse migration doesn't drop the constraint

2015-11-17 Thread Django

#25621: AlterField to ForeignKey reverse migration doesn't drop the constraint
+--
 Reporter:  mgedmin |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  1.8
 Severity:  Normal  |   Resolution:  needsinfo
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by timgraham):

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


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

Re: [Django] #25758: Date filter doesn't use internationalization when USE_L10N is True

2015-11-17 Thread Django

#25758: Date filter doesn't use internationalization when USE_L10N is True
-+-
 Reporter:  AliLozano|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
  date,format,internationalization   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 I'll accept the ticket since no tests fail if that line from the pull
 request is removed (same with `if arg is None: arg = settings.TIME_FORMAT`
 in the time filter, but we still need a test to show what this fixes.

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

Re: [Django] #25682: Audit bare except clauses

2015-11-17 Thread Django

#25682: Audit bare except clauses
-+-
 Reporter:  aaugustin|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Other) |  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.ff89dbbf8698b41fb81acd2e6a8ec5cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25736: Define management commands via function

2015-11-17 Thread Django

#25736: Define management commands via function
-+-
 Reporter:  olethanh |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  1
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Please reopen if you can start a discussion and get a consensus to add
 this. 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/066.5c115e0aaeb3b83c9fc8e8a6371f16f2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25756: ArrayField does not work with FileField

2015-11-17 Thread Django

#25756: ArrayField does not work with FileField
--+
 Reporter:  adongy|Owner:
 Type:  Bug   |   Status:  new
Component:  contrib.postgres  |  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):

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


Comment:

 I'm not sure to what extent we can fix this, but if not, we can document
 the limitation or try to add a helpful error message indicating that it's
 unsupported.

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

Re: [Django] #25731: Remove choices from ether instance or method attribute in Select widget

2015-11-17 Thread Django

#25731: Remove choices from ether instance or method attribute in Select widget
-+-
 Reporter:  codingjoe|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Forms|  Version:  1.8
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

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


Comment:

 Please reopen if you can provide a patch, otherwise I'm not sure how to
 proceed with 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/067.ff852e46afc6468dff5797ea988aab79%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24971: Make startapp generate an apps.py

2015-11-17 Thread Django

#24971: Make startapp generate an apps.py
-+-
 Reporter:  timgraham|Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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 jamesbeith):

 Yeah I think so. Especially if using `default_app_config` is discouraged,
 I wasn't aware of this.

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

Re: [Django] #25763: Django missing repr friendly formatting of request

2015-11-17 Thread Django

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

Comment:

I think you should be able to write a custom logging handler similar to
`AdminEmailHandler` which uses `record.request` to format the request data
any way you like. This might be something we'd consider for inclusion in
Django itself, although since no one has complained until seven months
after the release of Django 1.8, I guess it's not a popular use case. Feel
free to raise the issue on the DevelopersMailingList if you feel my
analysis is off-base. 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/068.64c3fb36ba9e03f2d05005c20c1731ae%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24971: Make startapp generate an apps.py

2015-11-17 Thread Django

#24971: Make startapp generate an apps.py
-+-
 Reporter:  timgraham|Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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 timgraham):

 That said, how about [https://github.com/django/django/pull/5675 a small
 enhancement] to the 1.9 release notes to clarify the expected behavior?

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

Re: [Django] #24971: Make startapp generate an apps.py

2015-11-17 Thread Django

#24971: Make startapp generate an apps.py
-+-
 Reporter:  timgraham|Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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 timgraham):

 That's intentional, see #25356.

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

Re: [Django] #24971: Make startapp generate an apps.py

2015-11-17 Thread Django

#24971: Make startapp generate an apps.py
-+-
 Reporter:  timgraham|Owner:
 |  MounirMesselmeni
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  master
  commands)  |
 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 jamesbeith):

 I just tested this with Django 1.9rc1 and the `default_app_config`
 statement was not added to the `__init__.py` file, the file was blank.

 I noticed this first in my own project but also in a blank test project.

 '''Steps'''

 - Created a new Python 3.4 virtualenv
 - Installed Django 1.9rc1 via pip
 - Ran `django-admin startproject mysite`
 - Ran `python manage.py startapp polls` from within the project

 '''Expected Behaviour'''

 - An `apps.py` file is created with appropriate content
 - An `__init__.py` file is created with appropriate `default_app_config`
 statement

 '''Actual Behaviour'''

 - An `apps.py` file is created with appropriate content
 - An `__init__.py` file is created but '''no''' `default_app_config`
 statement is included, the file is blank

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

Re: [Django] #25767: integer_field_ranges are incorrect for MySQL backend

2015-11-17 Thread Django

#25767: integer_field_ranges are incorrect for MySQL backend
-+-
 Reporter:  georgemarshall   |Owner:
 |  georgemarshall
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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
 * has_patch:  0 => 1


Comment:

 Tests aren't passing on the [https://github.com/django/django/pull/5674
 pull request] and I left some comments for improvement.

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

Re: [Django] #25710: Clarify the docs about what INTERNAL_IPS does

2015-11-17 Thread Django

#25710: Clarify the docs about what INTERNAL_IPS does
-+-
 Reporter:  knbk |Owner:
 Type:   |  alexmorozov
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"361038ee03b3b8513470990fc1851a51f56ecd6c" 361038ee]:
 {{{
 #!CommitTicketReference repository=""
 revision="361038ee03b3b8513470990fc1851a51f56ecd6c"
 [1.9.x] Fixed #25710 -- Clarified the docs about what INTERNAL_IPS does.

 Backport of 5abed864ee1cd31a0b920768b4abe85b26b43a4d from master
 }}}

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

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

Re: [Django] #25710: Clarify the docs about what INTERNAL_IPS does

2015-11-17 Thread Django

#25710: Clarify the docs about what INTERNAL_IPS does
-+-
 Reporter:  knbk |Owner:
 Type:   |  alexmorozov
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"b4aa38d106e903a21773d3486885fd8d2fa8a660" b4aa38d]:
 {{{
 #!CommitTicketReference repository=""
 revision="b4aa38d106e903a21773d3486885fd8d2fa8a660"
 [1.8.x] Fixed #25710 -- Clarified the docs about what INTERNAL_IPS does.

 Backport of 5abed864ee1cd31a0b920768b4abe85b26b43a4d from master
 }}}

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

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

Re: [Django] #25710: Clarify the docs about what INTERNAL_IPS does

2015-11-17 Thread Django

#25710: Clarify the docs about what INTERNAL_IPS does
-+-
 Reporter:  knbk |Owner:
 Type:   |  alexmorozov
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"5abed864ee1cd31a0b920768b4abe85b26b43a4d" 5abed86]:
 {{{
 #!CommitTicketReference repository=""
 revision="5abed864ee1cd31a0b920768b4abe85b26b43a4d"
 Fixed #25710 -- Clarified the docs about what INTERNAL_IPS does.
 }}}

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

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

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

2015-11-17 Thread Django

#24324: Crashes when project path or path to Django install contains a non-ascii
character
-+-
 Reporter:  notsqrt  |Owner:  timgraham
 Type:  Bug  |   Status:  closed
Component:  Core (Management |  Version:  1.8
  commands)  |
 Severity:  Release blocker  |   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 timgraham):

 * status:  new => closed
 * version:  1.8alpha1 => 1.8
 * resolution:   => fixed


Comment:

 The issue reported in this ticket is fixed in Django 1.8. Please open a
 new bug with steps to reproduce if you are encountering a different issue.
 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/065.457a472e6715929c4acdfa9fab1d9cff%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24324: Crashes when project path or path to Django install contains a non-ascii character

2015-11-17 Thread Django

#24324: Crashes when project path or path to Django install contains a non-ascii
character
-+-
 Reporter:  notsqrt  |Owner:  timgraham
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  1.8alpha1
  commands)  |
 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 kissgyorgy):

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


Comment:

 I don't think the solution to the problem should be "Just don't use
 nonascii characters in path names".
 I'm not totally sure, but I suppose the problem is the `unicode_literals`
 future import.

 See Armin's opinion here: https://github.com/PythonCharmers/python-
 future/issues/22

 I got a traceback like this:
 {{{
 a = '/var/lib/jenkins/jobs/K\xc3\xa1rtyarendel\xc5\x91/workspace/orders'
 p = ('management.py',)
 path =
 '/var/lib/jenkins/jobs/K\xc3\xa1rtyarendel\xc5\x91/workspace/orders'
 b = 'management.py'

 def join(a, *p):
 """Join two or more pathname components, inserting '/' as needed.
 If any component is an absolute path, all previous path components
 will be discarded.  An empty last part will result in a path that
 ends with a separator."""
 path = a
 for b in p:
 if b.startswith('/'):
 path = b
 elif path == '' or path.endswith('/'):
 path +=  b
 else:
 >   path += '/' + b
 E   UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3
 in position 23: ordinal not in range(128)

 /usr/lib64/python2.7/posixpath.py:80: UnicodeDecodeError
 }}}

 As far as I understand ``os.path.join`` can't handle unicode inputs, but
 when you use the `unicode_literals`, everything will be unicode.

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

Re: [Django] #25766: adding javascript "this.disabled" invalidate ManyToManyField

2015-11-17 Thread Django

#25766: adding javascript "this.disabled" invalidate ManyToManyField
---+--
 Reporter:  liwee  |Owner:  nobody
 Type:  Bug|   Status:  closed
Component:  contrib.admin  |  Version:  1.7
 Severity:  Normal |   Resolution:  needsinfo
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--
Changes (by timgraham):

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


Comment:

 It's not clear to me how or why this is a bug in Django. It seems to me
 that `onClick="this.disabled=true; this.form.submit();"` is something that
 you or a third-party package you are using 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/063.fc2c32e701b39e1f7bb6ee90d9b2956c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #12128: Remove restrictive 30 character limit from username of AuthenticationForm.

2015-11-17 Thread Django

#12128: Remove restrictive 30 character limit from username of 
AuthenticationForm.
---+--
 Reporter:  SmileyChris|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.1
 Severity:  Normal |   Resolution:  fixed
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+--
Changes (by timgraham):

 * resolution:  wontfix => fixed


Comment:

 The `AuthenticationForm` `max_length` was increased to 254 characters in
 bfcda7781a886ab2b7b41937c0f49c088f58a3d7 (Django 1.5) (#19130).

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

Re: [Django] #12128: Remove restrictive 30 character limit from username of AuthenticationForm.

2015-11-17 Thread Django

#12128: Remove restrictive 30 character limit from username of 
AuthenticationForm.
---+--
 Reporter:  SmileyChris|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.1
 Severity:  Normal |   Resolution:  wontfix
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  1  |UI/UX:  1
---+--
Changes (by nehemiahjacob):

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

Re: [Django] #12128: Remove restrictive 30 character limit from username of AuthenticationForm.

2015-11-17 Thread Django

#12128: Remove restrictive 30 character limit from username of 
AuthenticationForm.
---+--
 Reporter:  SmileyChris|Owner:  nobody
 Type:  Uncategorized  |   Status:  closed
Component:  contrib.auth   |  Version:  1.1
 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 nehemiahjacob):

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


Comment:

 This 'wontfix' decision was taken nearly 6 years ago. Will there be a
 consideration to reopen this? Because I wish to use subclass AbstractUser
 model and impose email address as username. In this decade email addresses
 easily reach 30+ characters.

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

Re: [Django] #25762: Optimize numberformat.format

2015-11-17 Thread Django

Comment (by jaap3):

By the way, while refactoring this code I was wondering if supporting
NUMBER_GROUPING other than 3 is even useful. None of the locales shipped
with Django define anything other than 3, and the other related
configuration options (THOUSAND_SEPARATOR and USE_THOUSAND_SEPARATOR) all
refer to grouping by 3 anyway.

It would also be nice if number formatting on strings was deprecated. It
seems that Django already tries to call it with numbers in the places it's
used, and there's no real check if the strings that are passed into the
function are even number like.

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

46 matches

Mail list logo