Re: [Django] #27396: Docs: send POST request on base.html does not mention {{ csrf_toeken }}

2016-10-27 Thread Django
#27396: Docs: send POST request on base.html does not mention {{ csrf_toeken }}
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 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 Ramin Farajpour Cami):

 Replying to [comment:2 Ramin Farajpour Cami]:
 > Replying to [comment:1 Aymeric Augustin]:
 > > It's unclear to me how declaring this `` tag causes the CSRF
 token to be added to AJAX requests.
 > >
 > > Are you using JavaScript code to extract it from there and add it to
 AJAX requests?
 > >
 > > Or is this a behavior of `` tags that I'm not familiar with?
 > >
 > > If the latter, is it a standardized behavior across browsers? Can you
 provide a like to documentation or compatibility tables?
 >
 > Hi ,
 >
 > please look this ,
 >
 > http://api.rubyonrails.org/classes/ActionView/Helpers/CsrfHelper.html
 >
 > 1 - go to http://www.bugjoo.ir/ first if you use chrome plz press
 (ctrl+shift+n)
 > 2- you see render error
 > 3- please sniff request AJAX (session/current)
 >
 > you see like this,
 >
 > {{{
 >
 
Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
 > Accept-Encoding:gzip, deflate, sdch
 > Accept-Language:en-US,en;q=0.8
 > Cache-Control:no-cache
 > Connection:keep-alive
 > Cookie:__cfduid=d1b7d99024046b0a11e455b195c55783e1477636721
 > Host:www.bugjoo.ir
 > Pragma:no-cache
 > Upgrade-Insecure-Requests:1
 > User-Agent:Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36
 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36
 > }}}
 >
 > there isn't `csrf_token` on cookie,

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


Re: [Django] #27396: Docs: send POST request on base.html does not mention {{ csrf_toeken }}

2016-10-27 Thread Django
#27396: Docs: send POST request on base.html does not mention {{ csrf_toeken }}
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 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 Ramin Farajpour Cami):

 Replying to [comment:1 Aymeric Augustin]:
 > It's unclear to me how declaring this `` tag causes the CSRF token
 to be added to AJAX requests.
 >
 > Are you using JavaScript code to extract it from there and add it to
 AJAX requests?
 >
 > Or is this a behavior of `` tags that I'm not familiar with?
 >
 > If the latter, is it a standardized behavior across browsers? Can you
 provide a like to documentation or compatibility tables?

 Hi ,

 please look this ,

 http://api.rubyonrails.org/classes/ActionView/Helpers/CsrfHelper.html

 1 - go to http://www.bugjoo.ir/ first if you chrome plz press (ctrl+F5)
 2- you see render error
 3- please sniff request AJAX (session/current)

 you see like this,

 {{{
 
Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
 Accept-Encoding:gzip, deflate, sdch
 Accept-Language:en-US,en;q=0.8
 Cache-Control:no-cache
 Connection:keep-alive
 Cookie:__cfduid=d1b7d99024046b0a11e455b195c55783e1477636721
 Host:www.bugjoo.ir
 Pragma:no-cache
 Upgrade-Insecure-Requests:1
 User-Agent:Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML,
 like Gecko) Chrome/54.0.2840.71 Safari/537.36
 }}}

 there isn't `csrf_token` on cookie,

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


Re: [Django] #27396: Docs: send POST request on base.html does not mention {{ csrf_toeken }}

2016-10-27 Thread Django
#27396: Docs: send POST request on base.html does not mention {{ csrf_toeken }}
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.10
 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 Aymeric Augustin):

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


Comment:

 It's unclear to me how declaring this `` tag causes the CSRF token
 to be added to AJAX requests.

 Are you using JavaScript code to extract it from there and add it to AJAX
 requests?

 Or is this a behavior of `` tags that I'm not familiar with?

 If the latter, is it a standardized behavior across browsers? Can you
 provide a like to documentation or compatibility tables?

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


[Django] #27396: Docs: send POST request on base.html does not mention {{ csrf_toeken }}

2016-10-27 Thread Django
#27396: Docs: send POST request on base.html does not mention {{ csrf_toeken }}
--+
 Reporter:  Ramin Farajpour Cami  |  Owner:  nobody
 Type:  Cleanup/optimization  | Status:  new
Component:  Documentation |Version:  1.10
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hi,

 Have a look at the section "AJAX " in this documentation page:

 https://docs.djangoproject.com/en/1.10/ref/csrf/#ajax

 It does not mention the highly relevantcsrf_toeken  on meta tag  on
 base.html I think it should.

 {{{
 
 }}}

 many case there is use AJAX on root path `http://127.0.0.1` this action

 urls.py:

 {{{
 url(r'^$', Index , name='Index'),
 }}}

 base.html


 {{{
 
 
 
 
 {% block title %}My amazing site{% endblock %}
 

 
 
 {% block sidebar %}
 
 Home
 Blog
 
 {% endblock %}
 

 
 {% block content %}{% endblock %}
 
 
 
 }}}

 index.html

 {{{
 {% extends "base.html" %}

 {% block title %}{{ section.title }}{% endblock %}

 {% block content %}
 {{ section.title }}

 {% endblock %}
 }}}

 now when action index return render , now if users use AJAX on base.html
 (for example : check session permission on use javascript on page
 base.html ) howevery this page nothing cookie set csrf_token for send to
 server side ,

 there is 2 way :
 1 - use {% csrf_token %}  , this create input tag on base.html (this is
 not good )
 2 - use meta tag (``)

 i use 2 , and work it great ,

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


Re: [Django] #27373: Incorrect message on 404 debug page for an empty request path

2016-10-27 Thread Django
#27373: Incorrect message on 404 debug page for an empty request path
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Error reporting  |  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:"c7f86d3eec84aeff83fc01f12990edb329ec2c4d" c7f86d3e]:
 {{{
 #!CommitTicketReference repository=""
 revision="c7f86d3eec84aeff83fc01f12990edb329ec2c4d"
 Fixed #27373 -- Corrected 404 debug page message for an empty request
 path.
 }}}

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


[Django] #27395: Django sitemap and i18n

2016-10-27 Thread Django
#27395: Django sitemap and i18n
--+
 Reporter:  Hovi  |  Owner:  nobody
 Type:  New feature   | Status:  new
Component:  contrib.sitemaps  |Version:  1.10
 Severity:  Normal|   Keywords:
 Triage Stage:  Unreviewed|  Has patch:  0
Easy pickings:  0 |  UI/UX:  0
--+
 Hello,

 django sitemap supports i18n field, that enables generating language-aware
 sitemaps, here is doc:
 
https://docs.djangoproject.com/en/1.10/ref/contrib/sitemaps/#django.contrib.sitemaps.Sitemap.i18n

 Problem is, that it generates them just as each url separately with no
 relations. One of google recommendations is to mark same content in
 different languages using sitemap with xhtml:link element:
 https://support.google.com/webmasters/answer/189077

 Would be cool to add possibility to generate these tags.

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


Re: [Django] #21412: Django message framework called with None

2016-10-27 Thread Django
#21412: Django message framework called with None
-+-
 Reporter:  merb |Owner:  Denis
 |  Cornehl
 Type:  Bug  |   Status:  closed
Component:  contrib.messages |  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  messages | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham):

 Please open a new ticket rather than commenting on a closed one. 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/062.ae925e7abac7b477c223cc7a709f0543%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #21412: Django message framework called with None

2016-10-27 Thread Django
#21412: Django message framework called with None
-+-
 Reporter:  merb |Owner:  Denis
 |  Cornehl
 Type:  Bug  |   Status:  closed
Component:  contrib.messages |  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  messages | Triage Stage:  Ready for
 |  checkin
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Chris Portela):

 I am also using Django Rest Framework and came here to second Raffaele's
 proposal here.

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

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


Re: [Django] #27373: Incorrect message on 404 debug page for an empty request path

2016-10-27 Thread Django
#27373: Incorrect message on 404 debug page for an empty request path
-+-
 Reporter:  felixxm  |Owner:  felixxm
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Error reporting  |  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 Tim Graham):

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


Re: [Django] #26578: validate_ipv4_address (and probably other validators) accept non-ASCII digits

2016-10-27 Thread Django
#26578: validate_ipv4_address (and probably other validators) accept non-ASCII
digits
-+-
 Reporter:  Martin Dickopp   |Owner:  Iacopo
 |  Spalletti
 Type:  Bug  |   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 Tim Graham):

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


Comment:

 The [https://github.com/django/django/pull/7435 PR] could use a few more
 tests.

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

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


Re: [Django] #27394: template "floatformat" tag throws ValueError for big numbers in Python 3

2016-10-27 Thread Django
#27394: template "floatformat" tag throws ValueError for big numbers in Python 3
-+
 Reporter:  mateuszf |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  floatformat python3  | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by felixxm):

 * has_patch:  0 => 1


Comment:

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


Re: [Django] #27393: Admin: input boxes on password reset forms are not aligned

2016-10-27 Thread Django
#27393: Admin: input boxes on password reset forms are not aligned
--+
 Reporter:  Michiel Beijen|Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  contrib.admin |  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:  1
--+
Changes (by Tim Graham):

 * type:  Bug => Cleanup/optimization
 * stage:  Unreviewed => Accepted


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

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


Re: [Django] #27358: Add a system check for FileField upload_to starting with a slash

2016-10-27 Thread Django
#27358: Add a system check for FileField upload_to starting with a slash
--+
 Reporter:  Tim Graham|Owner:  Frank
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (System checks)  |  Version:  1.10
 Severity:  Normal|   Resolution:
 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):

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


Comment:

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


Re: [Django] #27394: template "floatformat" tag throws ValueError for big numbers in Python 3

2016-10-27 Thread Django
#27394: template "floatformat" tag throws ValueError for big numbers in Python 3
-+
 Reporter:  mateuszf |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  floatformat python3  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by felixxm):

 Replying to [comment:1 Tim Graham]:
 > A regression test is attached, though it doesn't work on Python 2
 either, returning the original value rather than the formatted version.

 I attached correct regression test. Previous was little bit wrong because

   -1.323297138040798e+35 =  -1.323297138040798 * 10^35 =
 -1323297138040798

 PR in progress.

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


Re: [Django] #27394: template "floatformat" tag throws ValueError for big numbers in Python 3

2016-10-27 Thread Django
#27394: template "floatformat" tag throws ValueError for big numbers in Python 3
-+
 Reporter:  mateuszf |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  floatformat python3  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by felixxm):

 * Attachment "27394-test.2.diff" added.

 Test

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


Re: [Django] #27394: template "floatformat" tag throws ValueError for big numbers in Python 3

2016-10-27 Thread Django
#27394: template "floatformat" tag throws ValueError for big numbers in Python 3
-+
 Reporter:  mateuszf |Owner:  felixxm
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  floatformat python3  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by felixxm):

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


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


Re: [Django] #27394: template "floatformat" tag throws ValueError for big numbers in Python 3

2016-10-27 Thread Django
#27394: template "floatformat" tag throws ValueError for big numbers in Python 3
-+
 Reporter:  mateuszf |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Template system  |Version:  1.10
 Severity:  Normal   | Resolution:
 Keywords:  floatformat python3  |   Triage Stage:  Unreviewed
Has patch:  0|  Easy pickings:  0
UI/UX:  0|
-+
Changes (by Tim Graham):

 * Attachment "27394-test.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.18baa4b737c7912448468cb96ce05dee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #27394: template "floatformat" tag throws ValueError for big numbers in Python 3

2016-10-27 Thread Django
#27394: template "floatformat" tag throws ValueError for big numbers in Python 3
-+
 Reporter:  mateuszf |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:  floatformat python3  | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham):

 * needs_better_patch:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 A regression test is attached, though it doesn't work on Python 2 either,
 returning the original value rather than the formatted version.

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

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


Re: [Django] #27392: Remove "Tests that", "Ensures that", etc. from test docstings

2016-10-27 Thread Django
#27392: Remove "Tests that", "Ensures that", etc. from test docstings
-+-
 Reporter:  Tim Graham   |Owner:  Mahendra
 Type:   |  Yadav
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham):

 Another phrasing to remove is "Checks that" / "Check that".

 A [https://github.com/django/django/pull/7439 PR] is started by za.

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


[Django] #27394: template "floatformat" tag throws ValueError for big numbers in Python 3

2016-10-27 Thread Django
#27394: template "floatformat" tag throws ValueError for big numbers in Python 3
-+-
 Reporter:  mateuszf |  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Template system  |Version:  1.10
 Severity:  Normal   |   Keywords:  floatformat python3
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 I'm porting application from Python 2 to Python 3.
 We receive and display floating point values from external system. They
 may be big values.

 Following example works on Python 2 with Django 1.10.2 but throws
 "ValueError: valid range for prec is [1, MAX_PREC]" on Python 3 with the
 same Django version.


 {{{
 def my_view(request):
 return render(request, my_template.html', {
 'value':-1.323297138040798e+35 })
 }}}

 {{{
 {{ value|floatformat:2 }}
 }}}

 We have separate custom tag for displaying values in scientific format but
 how am I supposed to check if value will be printed in scientific format
 before printing it in template ? This was working automatically in 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/051.f97f34e1b8c67d16dfd19cb04293f8fd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Django] #27327: Simplify time zone handling by making pytz a required dependency

2016-10-27 Thread Django
#27327: Simplify time zone handling by making pytz a required dependency
-+-
 Reporter:  Tim Graham   |Owner:  Tim
 Type:   |  Graham
  Cleanup/optimization   |   Status:  closed
Component:  Utilities|  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:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"414ad25b090a63eaaf297b1164c8f7d814a710a2" 414ad25b]:
 {{{
 #!CommitTicketReference repository=""
 revision="414ad25b090a63eaaf297b1164c8f7d814a710a2"
 Fixed #27327 -- Simplified time zone handling by requiring pytz.
 }}}

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


Re: [Django] #27328: return `Set-Cookie` if sessionid= None value

2016-10-27 Thread Django
#27328: return `Set-Cookie` if sessionid=  None value
-+-
 Reporter:  Ramin Farajpour  |Owner:  nobody
  Cami   |
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  contrib.sessions |  Version:  1.10
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham):

 What would be a purpose of manipulating the sessionid in JavaScript like
 that? I'm not familiar with the "virtual cookies" concept in your earlier
 comment.

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


Re: [Django] #27392: Remove "Tests that", "Ensures that", etc. from test docstings

2016-10-27 Thread Django
#27392: Remove "Tests that", "Ensures that", etc. from test docstings
-+-
 Reporter:  Tim Graham   |Owner:  Mahendra
 Type:   |  Yadav
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  master
 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 Mahendra Yadav):

 * owner:  za => Mahendra Yadav


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


Re: [Django] #25684: Runserver doesn't use `LOGGING` configuration

2016-10-27 Thread Django
#25684: Runserver doesn't use `LOGGING` configuration
-+-
 Reporter:  Flavio Curella   |Owner:  Flavio
 |  Curella
 Type:  New feature  |   Status:  closed
Component:  Error reporting  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  runserver logging| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by jonathan-golorry):

 I'm not really sure what's going on so I don't want to open a ticket
 myself, but I'm consistently getting Mark's "Logged from file basehttp.py"
 error with DjangoRestFramework when closing a tab of the browsable API
 while it's uploading a file.

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


Re: [Django] #27392: Remove "Tests that", "Ensures that", etc. from test docstings

2016-10-27 Thread Django
#27392: Remove "Tests that", "Ensures that", etc. from test docstings
--+
 Reporter:  Tim Graham|Owner:  za
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Documentation |  Version:  master
 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 za):

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


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