date:20140313

Re: [Django] #22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2

2014-03-13 Thread Django

#22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2
-+
 Reporter:  steko|Owner:  bigsassy
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  1
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by bigsassy):

 * needs_docs:  0 => 1


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

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

Re: [Django] #22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2

2014-03-13 Thread Django

#22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2
-+
 Reporter:  steko|Owner:  bigsassy
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Release blocker  |   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 bigsassy):

 * needs_tests:  1 => 0


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

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

[Django] #22270: Explain permissions on proxy models

2014-03-13 Thread Django

#22270: Explain permissions on proxy models
-+-
 Reporter:  gert |  Owner:  nobody
 Type:   | Status:  new
  Cleanup/optimization   |Version:  1.6
Component:  Documentation|   Keywords:  proxy models
 Severity:  Normal   |  permissions
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 The section on Proxy models does not say anything about how system
 permissions are affected.

 There have been known inconsistency issues with this for 5 years now
 ([ticket:11154]).

 Irrespective of the resolution of the inconsistencies I feel it is
 imperative that they are at least mentioned in the documentation. Please
 explain how proxy models and model permissions interact.

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

Re: [Django] #22242: Setting cookie that is too large fails silently

2014-03-13 Thread Django

#22242: Setting cookie that is too large fails silently
-+-
 Reporter:  Euphorbium   |Owner:
   |   Status:  new
 Type:  Bug  |  Version:  1.6
Component:  HTTP handling|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-

Comment (by pirosb3):

 Hi erikr,

 I understand your reasoning perfectly. The compromise of having to check
 the cookie size on every set is too big.
 Should I update the documentation?

 Regards,
 Dan

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

Re: [Django] #21798: Model validation should complain if both `add_now` and `auto_add_now` are specified.

2014-03-13 Thread Django

#21798: Model validation should complain if both `add_now` and `auto_add_now` 
are
specified.
-+-
 Reporter:  charettes|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by PirosB3):

 Hi charettes,

 so you would not take any action, other than warning the user? (you would
 still keep both options enabled?)

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

Re: [Django] #22269: ">

2014-03-13 Thread Django

#22269: ">
-+-
 Reporter:  "> |  src=x onerror=prompt(1)>
 Type:  Uncategorized|   Status:  closed
Component:  Uncategorized|  Version:  1.6
 Severity:  Normal   |   Resolution:  invalid
 Keywords:  "> |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Siecje):

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

Re: [Django] #22234: Special characters in database password are not escaped correctly on Windows platforms

2014-03-13 Thread Django

#22234: Special characters in database password are not escaped correctly on
Windows platforms
-+-
 Reporter:  djangoproject.com@…  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by anubhav9042):

 * cc: anubhav9042@… (added)


Comment:

 If only you could add a test to your PR, we can test the new
 implementation.

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

Re: [Django] #6103: tests/model_forms/tests.py could use some rewriting

2014-03-13 Thread Django

#6103: tests/model_forms/tests.py could use some rewriting
--+
 Reporter:  mtredinnick   |Owner:  claudep
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Forms |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by claudep):

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


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

Re: [Django] #22269: ">

2014-03-13 Thread Django

#22269: ">
-+-
 Reporter:  "> |  src=x onerror=prompt(1)>
 Type:  Uncategorized|   Status:  new
Component:  Uncategorized|  Version:  1.6
 Severity:  Normal   |   Resolution:
 Keywords:  "> |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by " onmouseover=prompt(1)  bad"):

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


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

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

[Django] #22269: ">

2014-03-13 Thread Django

#22269: ">
-+-
 Reporter:  "> |  onerror=prompt(1)>
 Type:  Uncategorized| Status:  new
Component:  Uncategorized|Version:  1.6
 Severity:  Normal   |   Keywords:  ">
Easy pickings:  0|  Has patch:  0
 |  UI/UX:  0
-+-
 ">

 [[Image(">)]]

 [[BR]]



 

 {{{
 [">]


 == "> ==

 ''">''

 }}}

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

Re: [Django] #22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2

2014-03-13 Thread Django

#22001: GeoDjango (contrib.gis) does not create geometry columns in 1.7a2
-+
 Reporter:  steko|Owner:  bigsassy
 Type:  Bug  |   Status:  assigned
Component:  GIS  |  Version:  master
 Severity:  Release blocker  |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by blueyed):

 * cc: django@… (added)


Comment:

 The [https://github.com/django/django/blob/master/docs/howto/custom-model-
 fields.txt#L461 documentation] should probably get verified/clarified:

 > The :meth:`.db_type` method is called by Django when the framework
 > constructs the ``CREATE TABLE`` statements for your application -- that
 is,
 > when you first create your tables. It is also called when constructing a
 > ``WHERE`` clause that includes the model field -- that is, when you
 retrieve data
 > using QuerySet methods like ``get()``, ``filter()``, and ``exclude()``
 and have
 > the model field as an argument. It's not called at any other time, so it
 can afford to
 > execute slightly complex code, such as the ``connection.settings_dict``
 check in
 > the above example.

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

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

Re: [Django] #22260: Custom model field: field.db_type not called for (initial) migration / docs wrong? (DurationField)

2014-03-13 Thread Django

#22260: Custom model field: field.db_type not called for (initial) migration / 
docs
wrong? (DurationField)
+--
 Reporter:  blueyed |Owner:  nobody
 Type:  Bug |   Status:  closed
Component:  Migrations  |  Version:  master
 Severity:  Normal  |   Resolution:  duplicate
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  1   |  Needs documentation:  0
  Needs tests:  1   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by blueyed):

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


Comment:

 The fix for this is now in the pull request for #22001.

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-13 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
-+
 Reporter:  meenzam@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by meenzam@…):

 Then I will suggest to return None from {{{smart_urlquote()}}} in case of
 any exception, then {{{urlize()}}} will not think the string as an url and
 will show text only.
 Also not only path, but also query parameter and fragment should be quoted
 (because they may contain ").

 For query string, we may first {{{parse_qs()}}} and then individually
 encode each key value pairs and remake the query string.
 For fragment, We can do the same as path (unquoting and quoting again).
 Not perfect solution though because some sites store query parameters in
 fragments.

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

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-13 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
-+
 Reporter:  meenzam@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by erikr):

 By which I don't mean that this particular issue should not be fixed
 anymore, in case I was ambiguous - it is definitely a bug.

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

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-13 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
-+
 Reporter:  meenzam@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+

Comment (by erikr):

 The formal description is whatever is documented. However, developers may
 depend on other details of its behaviour, which we should not change if it
 is not necessary.

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

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-13 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
-+
 Reporter:  meenzam@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+
Changes (by meenzam@…):

 * has_patch:  1 => 0


Comment:

 Hmm, yes the commit is wrong, urlize() will not always escape.

 Can you provide the intended behaviour of urlize()? It will then be easier
 to fix when we have a set goal. Currently it is not totally clear what is
 the correct behaviour of urlize() and smart_urlquote().

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

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

Re: [Django] #22184: template_tests relies on leaking state

2014-03-13 Thread Django

#22184: template_tests relies on leaking state
-+---
 Reporter:  aaugustin|Owner:  anubhav9042
 Type:  Bug  |   Status:  assigned
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+---
Changes (by anubhav9042):

 * status:  new => assigned
 * owner:  nobody => anubhav9042
 * cc: anubhav9042@… (added)


Comment:

 problem in TEMPLATE_DIRS.
 Working on the fix.

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

Re: [Django] #21798: Model validation should complain if both `add_now` and `auto_add_now` are specified.

2014-03-13 Thread Django

#21798: Model validation should complain if both `add_now` and `auto_add_now` 
are
specified.
-+-
 Reporter:  charettes|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by charettes):

 By ''warn the user'' I mean adding a field check.

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

Re: [Django] #21798: Model validation should complain if both `add_now` and `auto_add_now` are specified.

2014-03-13 Thread Django

#21798: Model validation should complain if both `add_now` and `auto_add_now` 
are
specified.
-+-
 Reporter:  charettes|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by charettes):

 @erikr, I agree that we allow many silly definition, the combination of
 `auto_now_add` and `default is a good example.

 However I think we should at least warn the user if two of the `add_now`,
 `auto_add_now` and `default` options are defined since the defined
 behavior here is ambiguous.

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

Re: [Django] #22242: Setting cookie that is too large fails silently

2014-03-13 Thread Django

#22242: Setting cookie that is too large fails silently
-+-
 Reporter:  Euphorbium   |Owner:
   |   Status:  new
 Type:  Bug  |  Version:  1.6
Component:  HTTP handling|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by Euphorbium ):

 * owner:  anonymous =>
 * status:  assigned => new
 * easy:  1 => 0


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

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

Re: [Django] #22266: CharField primary keys with underscores are (un)escaped differently in the admin pages

2014-03-13 Thread Django

#22266: CharField primary keys with underscores are (un)escaped differently in 
the
admin pages
+--
 Reporter:  victor.varvariuc@…  |Owner:  nobody
 Type:  Bug |   Status:  new
Component:  contrib.admin   |  Version:  1.6
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Unreviewed
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+--
Changes (by claudep):

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


Comment:

 Might be related to #3

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

Re: [Django] #22242: Setting cookie that is too large fails silently

2014-03-13 Thread Django

Comment (by erikr):

So, a number of things have come up:

* In set_cookie(), there is insufficient information to decide whether or
not the cookie will be too large.
* One way to resolve that is to generate the full cookie in set_cookie(),
or something like that, just to check the length.
* Alternatively, this could be caught when generating the Set-Cookie
headers in the WSGIHandler.
* Regardless of this change, there are other ways to send broken cookies,
like having a path or domain that does not match the current one, or
having many cookies which are individually small enough, but together too
large.

Raising an error from WSGIHandler does not seem like the appropriate
place, and regardless would not even work as expected: as far as I can
see, the 500 handling, which will display the debug page or render the
configured 500 page, etc., is not called if an exception is raised at this
stage - that exception handling happens earlier.

Calculating the full length of the cookie on every set_cookie() call would
work. However, this adds overhead to every cookie ever set, while setting
cookies that are too large seems very exceptional to me. I don't think the
rarity of this issue warrants adding such a performance impact on every
cookie generated by every Django instance. And even in that case, we would
only catch some of the errors made.

All things considered, it seems this is much harder than initially
thought. Considering that, in combination with the rareness of this issue,
and the fact that we can only catch some of these problems, I think it is
not sensible to enforce cookie size in set_cookie(). Amending the
set_cookie() documentation to mention the typical maximum length would
definitely be useful and reasonable.

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

[django/django] 1a2939: [1.6.x] Fixed #22245 -- Avoided widget overwrite i...

2014-03-13 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 1a2939bc26b7077e3196cea9bce52826ec7a6d9d
  
https://github.com/django/django/commit/1a2939bc26b7077e3196cea9bce52826ec7a6d9d
  Author: Claude Paroz 
  Date:   2014-03-13 (Thu, 13 Mar 2014)

  Changed paths:
M django/forms/fields.py
M docs/releases/1.6.3.txt
M tests/forms_tests/tests/test_fields.py

  Log Message:
  ---
  [1.6.x] Fixed #22245 -- Avoided widget overwrite in forms.IntegerField 
subclasses

Thanks Jeroen Pulles for the report and Simon Charette for the review.
Backport of 5a976b4bec7 from master.


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

Re: [Django] #22245: Widget on DecimalField subclass ignored

2014-03-13 Thread Django

#22245: Widget on DecimalField subclass ignored
-+-
 Reporter:  jeroen.pulles@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Claude Paroz ):

 In [changeset:"1a2939bc26b7077e3196cea9bce52826ec7a6d9d"]:
 {{{
 #!CommitTicketReference repository=""
 revision="1a2939bc26b7077e3196cea9bce52826ec7a6d9d"
 [1.6.x] Fixed #22245 -- Avoided widget overwrite in forms.IntegerField
 subclasses

 Thanks Jeroen Pulles for the report and Simon Charette for the review.
 Backport of 5a976b4bec7 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/085.973f092e29fbaefc6165de970024c5f8%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

[django/django] 5a976b: Fixed #22245 -- Avoided widget overwrite in forms....

2014-03-13 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 5a976b4bec79cdb6b75581be6478356fb13fda77
  
https://github.com/django/django/commit/5a976b4bec79cdb6b75581be6478356fb13fda77
  Author: Claude Paroz 
  Date:   2014-03-13 (Thu, 13 Mar 2014)

  Changed paths:
M django/forms/fields.py
M docs/releases/1.6.3.txt
M tests/forms_tests/tests/test_fields.py

  Log Message:
  ---
  Fixed #22245 -- Avoided widget overwrite in forms.IntegerField subclasses

Thanks Jeroen Pulles for the report and Simon Charette for the review.


-- 
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/5321d5b9c271c_342b1071d449845b%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22245: Widget on DecimalField subclass ignored

2014-03-13 Thread Django

#22245: Widget on DecimalField subclass ignored
-+-
 Reporter:  jeroen.pulles@…  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.6
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Claude Paroz ):

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


Comment:

 In [changeset:"5a976b4bec79cdb6b75581be6478356fb13fda77"]:
 {{{
 #!CommitTicketReference repository=""
 revision="5a976b4bec79cdb6b75581be6478356fb13fda77"
 Fixed #22245 -- Avoided widget overwrite in forms.IntegerField subclasses

 Thanks Jeroen Pulles for the report and Simon Charette for the review.
 }}}

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

Re: [Django] #22254: Testing documentation doesn't make it clear that django.setup() needs to be called with setup_test_environment

2014-03-13 Thread Django

#22254: Testing documentation doesn't make it clear that django.setup() needs 
to be
called with setup_test_environment
+---
 Reporter:  peter.landry@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Documentation   |  Version:  1.7-alpha-2
 Severity:  Normal  |   Resolution:
 Keywords:  app-loading | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---

Comment (by peter.landry@…):

 Perhaps it would be better to add instructions or information regarding
 `django.setup()` in
 https://docs.djangoproject.com/en/dev/ref/applications/, then just make a
 reference in the testing docs to it in a warning about using django
 outside of manage.py?

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

Re: [Django] #21693: detaultfilter wordcap converts a string into titlecase but respect the actual uppercase

2014-03-13 Thread Django

#21693: detaultfilter wordcap converts a string into titlecase but respect the
actual uppercase
-+--
 Reporter:  areski   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Template system  |  Version:  1.6
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  filter   | Triage Stage:  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+--
Changes (by timo):

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


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

Re: [Django] #22242: Setting cookie that is too large fails silently

2014-03-13 Thread Django

#22242: Setting cookie that is too large fails silently
-+-
 Reporter:  Euphorbium   |Owner:  anonymous
   |   Status:  assigned
 Type:  Bug  |  Version:  1.6
Component:  HTTP handling|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by PirosB3):

 I had a bigger look at this.

 in Cookie.py, the OutputString is what builds our output.
 http://hg.python.org/cpython/file/2.7/Lib/Cookie.py
 I'll paste it for convenience:
 {{{
   def OutputString(self, attrs=None):
 # Build up our result
 #
 result = []
 RA = result.append

 # First, the key=value pair
 RA("%s=%s" % (self.key, self.coded_value))

 # Now add any defined attributes
 if attrs is None:
 attrs = self._reserved
 items = self.items()
 items.sort()
 for K,V in items:
 if V == "": continue
 if K not in attrs: continue
 if K == "expires" and type(V) == type(1):
 RA("%s=%s" % (self._reserved[K], _getdate(V)))
 elif K == "max-age" and type(V) == type(1):
 RA("%s=%d" % (self._reserved[K], V))
 elif K == "secure":
 RA(str(self._reserved[K]))
 elif K == "httponly":
 RA(str(self._reserved[K]))
 else:
 RA("%s=%s" % (self._reserved[K], V))

 # Return the result
 return _semispacejoin(result)
 }}}

 RCF 6265 says that Cookies are measured by the sum of the length of the
 cookie's name, value, and attributes. So we are interested in the
 {{{result}}} array, which would make it very easy to calculcate the size
 of each cookie. Unfortunately the function returns a string. Does anyone
 see a good way of interacting with this function without having to repeat
 this code in another function?

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

Re: [Django] #21379: class AbstractUser: validators should compile re with Unicode

2014-03-13 Thread Django

#21379: class AbstractUser: validators should compile re with Unicode
--+--
 Reporter:  anonymous |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  contrib.auth  |  Version:  1.5
 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 xelnor):

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


Comment:

 The above regexp doesn't do what it seems to be doing: on Python 2,
 `[\w.@+-]` is equivalent to `[a-zA-Z0-9.@+-]`.
 In Python 3, this will also match all "accented" characters.

 The regexp should be updated for consistency between versions:
 * If the goal is to allow any letter-like char, add `re.UNICODE` to the
 `re.compile` call
 * If it should instead only allow ascii letters, the simplest way would be
 to use the explicit regexp, since the `re.ASCII` flag exists only in Py3.

 Exemple (Python 3):
 {{{
 #!python
 >>> import re
 >>> from django.core import validators
 >>> v = validators.RegexValidator(re.compile('^[\w.@+-]+$'), "Enter a
 valid username.", 'invalid')
 >>> v('foo.bar')
 >>> v('foo bar')
 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/xelnor/dev/venvs/bluesys-tools-py3/lib/python3.3/site-
 packages/django/core/validators.py", line 39, in __call__
 raise ValidationError(self.message, code=self.code)
 django.core.exceptions.ValidationError: ['Enter a valid username.']
 >>> v('jean-rené')
 }}}

 And on Python 2:
 {{{
 #!python
 >>> import re
 >>> from django.core import validators
 >>> v = validators.RegexValidator(re.compile('^[\w.@+-]+$'), "Enter a
 valid username.", 'invalid')
 >>> v('foo.bar')
 >>> v('foo bar')
 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/xelnor/dev/venvs/bluesys-tools/lib/python2.7/site-
 packages/django/core/validators.py", line 39, in __call__
 raise ValidationError(self.message, code=self.code)
 ValidationError: [u'Enter a valid username.']
 >>> v('jean-rené')
 Traceback (most recent call last):
   File "", line 1, in 
   File "/home/xelnor/dev/venvs/bluesys-tools/lib/python2.7/site-
 packages/django/core/validators.py", line 39, in __call__
 raise ValidationError(self.message, code=self.code)
 ValidationError: [u'Enter a valid username.']
 }}}

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

Re: [Django] #22242: Setting cookie that is too large fails silently

2014-03-13 Thread Django

#22242: Setting cookie that is too large fails silently
-+-
 Reporter:  Euphorbium   |Owner:  anonymous
   |   Status:  assigned
 Type:  Bug  |  Version:  1.6
Component:  HTTP handling|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  1|
-+-

Comment (by PirosB3):

 hey guys,

 In core/handlers/wsgi.py
 {{{
 for c in response.cookies.values():
 response_headers.append((str('Set-Cookie'),
 str(c.output(header=''
 }}}

 Couldn't we override django.http.cookie.SimpleCookie.output, and make it
 throw an exception for larger cookies?

 Regards,
 Daniel Pyrathon

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

Re: [Django] #22255: RegexValidator needs support for flags passed to `re.compile` (migrations do not allow for compiled patterns)

2014-03-13 Thread Django

#22255: RegexValidator needs support for flags passed to `re.compile` 
(migrations
do not allow for compiled patterns)
--+
 Reporter:  blueyed   |Owner:  dekomote
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 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 dekomote):

 Updated the patch https://github.com/django/django/pull/2427

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-13 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
-+
 Reporter:  meenzam@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 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 erikr):

 * needs_better_patch:  0 => 1


Comment:

 In that patch however, the conditions are altered: quoting is not
 performed if any exception is raised and caught. This does not appear to
 be part of the tests, so they still all succeed.

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

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

Re: [Django] #22262: Error in Translation Comments Documentation for Templates

2014-03-13 Thread Django

#22262: Error in Translation Comments Documentation for Templates
-+-
 Reporter:  av@… |Owner:  dekomote
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  templates, trans |  Needs documentation:  0
  tags   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by Baptiste Mispelon ):

 In [changeset:"b86ff4ee82b1dddea7179d72ee3368cb8962cbc6"]:
 {{{
 #!CommitTicketReference repository=""
 revision="b86ff4ee82b1dddea7179d72ee3368cb8962cbc6"
 [1.5.x] Fixed #22262 -- Added the correct line in the last example of
 Translator lines

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

Re: [Django] #22262: Error in Translation Comments Documentation for Templates

2014-03-13 Thread Django

#22262: Error in Translation Comments Documentation for Templates
-+-
 Reporter:  av@… |Owner:  dekomote
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  templates, trans |  Needs documentation:  0
  tags   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-

Comment (by Baptiste Mispelon ):

 In [changeset:"141bb90b4c66cca1c4bfafe2a0e5c5777c55c61c"]:
 {{{
 #!CommitTicketReference repository=""
 revision="141bb90b4c66cca1c4bfafe2a0e5c5777c55c61c"
 [1.6.x] Fixed #22262 -- Added the correct line in the last example of
 Translator lines

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

[django/django] b86ff4: [1.5.x] Fixed #22262 -- Added the correct line in ...

2014-03-13 Thread GitHub

  Branch: refs/heads/stable/1.5.x
  Home:   https://github.com/django/django
  Commit: b86ff4ee82b1dddea7179d72ee3368cb8962cbc6
  
https://github.com/django/django/commit/b86ff4ee82b1dddea7179d72ee3368cb8962cbc6
  Author: Dejan Noveski 
  Date:   2014-03-13 (Thu, 13 Mar 2014)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  [1.5.x] Fixed #22262 -- Added the correct line in the last example of 
Translator lines

Backport of 958b511a80c01ac010561c8fefe4548203700fa3 from master.


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

[django/django] 141bb9: [1.6.x] Fixed #22262 -- Added the correct line in ...

2014-03-13 Thread GitHub

  Branch: refs/heads/stable/1.6.x
  Home:   https://github.com/django/django
  Commit: 141bb90b4c66cca1c4bfafe2a0e5c5777c55c61c
  
https://github.com/django/django/commit/141bb90b4c66cca1c4bfafe2a0e5c5777c55c61c
  Author: Dejan Noveski 
  Date:   2014-03-13 (Thu, 13 Mar 2014)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  [1.6.x] Fixed #22262 -- Added the correct line in the last example of 
Translator lines

Backport of 958b511a80c01ac010561c8fefe4548203700fa3 from master.


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

Re: [Django] #22262: Error in Translation Comments Documentation for Templates

2014-03-13 Thread Django

#22262: Error in Translation Comments Documentation for Templates
-+-
 Reporter:  av@… |Owner:  dekomote
 Type:   |   Status:  closed
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:  fixed
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  templates, trans |  Needs documentation:  0
  tags   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by Baptiste Mispelon ):

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


Comment:

 In [changeset:"958b511a80c01ac010561c8fefe4548203700fa3"]:
 {{{
 #!CommitTicketReference repository=""
 revision="958b511a80c01ac010561c8fefe4548203700fa3"
 Fixed #22262 -- Added the correct line in the last example of Translator
 lines
 }}}

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

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

[django/django] 958b51: Fixed #22262 -- Added the correct line in the last...

2014-03-13 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: 958b511a80c01ac010561c8fefe4548203700fa3
  
https://github.com/django/django/commit/958b511a80c01ac010561c8fefe4548203700fa3
  Author: Dejan Noveski 
  Date:   2014-03-13 (Thu, 13 Mar 2014)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  Fixed #22262 -- Added the correct line in the last example of Translator lines


-- 
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/5321af1c6d0ee_23acd0fd40709cb%40hookshot-fe1-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22262: Error in Translation Comments Documentation for Templates

2014-03-13 Thread Django

#22262: Error in Translation Comments Documentation for Templates
-+-
 Reporter:  av@… |Owner:  dekomote
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  templates, trans |  Needs documentation:  0
  tags   |  Patch needs improvement:  0
Has patch:  1|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by dekomote):

 * owner:  nobody => dekomote
 * status:  new => assigned
 * has_patch:  0 => 1


Comment:

 Pull request https://github.com/django/django/pull/2429

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

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-13 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
-+
 Reporter:  meenzam@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  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 meenzam@…):

 * cc: meenzam@… (added)
 * has_patch:  0 => 1


Comment:

 The simple fix will be to unquote and quote only the path of the url, I
 have

 
https://github.com/ienzam/django/commit/692ac89689dd9ddf5895bfaf0181434c5daf81e9

 This passes the current unit 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/075.1e005894e045bda3d6a72bf031d9d946%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21798: Model validation should complain if both `add_now` and `auto_add_now` are specified.

2014-03-13 Thread Django

#21798: Model validation should complain if both `add_now` and `auto_add_now` 
are
specified.
-+-
 Reporter:  charettes|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by PirosB3):

 Hi erikr

 I just read this now, after having done my PR
 (https://github.com/django/django/pull/2428)
 I understand your point, but shouldn't we correct the user in any case? I
 think the fields should do some validation on parameters that are mutually
 exclusive.

 Let me know if we would need this, in any case.

 Regards,
 Dan

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

Re: [Django] #22163: select_for_update should take nowait directly

2014-03-13 Thread Django

#22163: select_for_update should take nowait directly
-+-
 Reporter:  kenny.macdermid@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:   |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by timmartin):

 * cc: timmartin (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/083.4656a4a84e481ffc537c180f78fdef5f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22254: Testing documentation doesn't make it clear that django.setup() needs to be called with setup_test_environment

2014-03-13 Thread Django

#22254: Testing documentation doesn't make it clear that django.setup() needs 
to be
called with setup_test_environment
+---
 Reporter:  peter.landry@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Documentation   |  Version:  1.7-alpha-2
 Severity:  Normal  |   Resolution:
 Keywords:  app-loading | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
Changes (by aaugustin):

 * keywords:   => app-loading


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

Re: [Django] #22268: values_list() on a ManyToManyField returns extra None's when iterated over.

2014-03-13 Thread Django

#22268: values_list() on a ManyToManyField returns extra None's when iterated 
over.
-+-
 Reporter:  k_sze|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  master
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  orm, values_list,|  Needs documentation:  0
  ManyToManyField|  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  0|
-+-
Changes (by bmispelon):

 * version:  1.6 => master
 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 Indeed, there seem to be something going wrong here.
 I tried it out and the bug seems present on older versions too (I tried
 all the way to 1.4).

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

Re: [Django] #22255: RegexValidator needs support for flags passed to `re.compile` (migrations do not allow for compiled patterns)

2014-03-13 Thread Django

#22255: RegexValidator needs support for flags passed to `re.compile` 
(migrations
do not allow for compiled patterns)
--+
 Reporter:  blueyed   |Owner:  dekomote
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 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 dekomote):

 * cc: dekomote (added)
 * has_patch:  0 => 1


Comment:

 Pull request here https://github.com/django/django/pull/2427

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

Re: [Django] #22268: values_list() on a ManyToManyField returns extra None's when iterated over.

2014-03-13 Thread Django

#22268: values_list() on a ManyToManyField returns extra None's when iterated 
over.
-+-
 Reporter:  k_sze|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  1.6
  (models, ORM)  |   Resolution:
 Severity:  Normal   | Triage Stage:
 Keywords:  orm, values_list,|  Unreviewed
  ManyToManyField|  Needs documentation:  0
Has patch:  0|  Patch needs improvement:  0
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by k_sze):

 * needs_better_patch:   => 0
 * type:  Uncategorized => Bug
 * needs_tests:   => 0
 * needs_docs:   => 0


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

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

[Django] #22268: values_list() on a ManyToManyField returns extra None's when iterated over.

2014-03-13 Thread Django

#22268: values_list() on a ManyToManyField returns extra None's when iterated 
over.
-+-
 Reporter:  k_sze|  Owner:  nobody
 Type:  Uncategorized| Status:  new
Component:  Database layer   |Version:  1.6
  (models, ORM)  |   Keywords:  orm, values_list,
 Severity:  Normal   |  ManyToManyField
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+-
 Suppose you have a `schools` app, with these model definitions:

 {{{
 from django.db import models

 class School(models.Model):
 name = models.CharField(unique=True, max_length=255)

 class Class(models.Model):
 school = models.ForeignKey(School)
 name = models.CharField(unique=True, max_length=255)
 students = models.ManyToManyField('Student')

 class Student(models.Model):
 surname = models.CharField(max_length=255)
 given_name = models.CharField(max_length=255)
 }}}

 Now, try this in the Django shell:
 {{{
 $ python manage.py shell

 >>> from schools.models import School, Class, Student

 # Create the school
 >>> concordia = School(name='Concordia University')
 >>> concordia.save()

 # Create the Software Engineering class
 >>> soen = Class(school=concordia, name='Software Engineering')
 >>> soen.save()

 # Create the Computer Engineering class
 >>> coen = Class(school=concordia, name='Computer Engineering')
 >>> coen.save()

 # Create a student
 >>> john_smith = Student(surname='Smith', given_name='John')
 >>> john_smith.save()

 # Add this student into one of the classes
 >>> soen.students.add(john_smith)

 # Now make a query using values_list
 >>> students = Class.objects.values_list('students', flat=True)

 # How many students are there supposed to be in this `students` QuerySet?
 >>> print students.count()
 1

 # What if we iterate over it?
 >>> for s in students:
 >>> print s
 1
 None

 # Wait, what!?
 >>> print len(list(students))
 >>> 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/048.3dfc59286529e29bc35f131df4af81fc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #21798: Model validation should complain if both `add_now` and `auto_add_now` are specified.

2014-03-13 Thread Django

Comment (by erikr):

You are talking about `auto_now` and `auto_now_add`, right? There is no
`auto_add_now`, as far as I know.

Provided that #21785 has resolved the migration issue, what is the actual
need in deprecating this? Looking at the code, I see no reason why it
should be invalid, or how it could cause issues. Yes, it would certainly
be silly to add both `auto_now` and `auto_now_add`to a field, but I there
are tons of silly field definitions that we still allow. For example, we
also allow the combination of `auto_now_add` and `default`.

A different situation would be if defining both would actually break in
some cases, like the issue we resolved in #20484. But with #21785 is
fixed, I see no similar situation here. When defining both, as far as I
know, it behaves correctly and precisely as one would expect. Therefore,
why should we disallow this combination?

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-13 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
-+
 Reporter:  meenzam@…|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Template system  |  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by anonymous):

 This is the commit which introduced unquote
 
https://github.com/django/django/commit/b70c371fc1f18ea0c43b503122df3f311afc7105

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

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

Re: [Django] #21273: Add read only support for Oracle XE to django.contrib.gis

2014-03-13 Thread Django

#21273: Add read only support for Oracle XE to django.contrib.gis
--+
 Reporter:  vinhussey |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  GIS   |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  1
  Needs tests:  1 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by jtiai):

 SDO_GEOMETRY itself has been same for a good while. I do have almost
 working version of read/write support for Oracle XE, as well as 3D support
 for Oracle geometries in general.

 There exists few peculiarities between versions, specially between 10g and
 11g and 3d geometries.

 Currently I think that backend I've been working on is only failing is
 some coordinate transformations.

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

Re: [Django] #22255: RegexValidator needs support for flags passed to `re.compile` (migrations do not allow for compiled patterns)

2014-03-13 Thread Django

#22255: RegexValidator needs support for flags passed to `re.compile` 
(migrations
do not allow for compiled patterns)
--+
 Reporter:  blueyed   |Owner:  dekomote
 Type:  Cleanup/optimization  |   Status:  assigned
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by dekomote):

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


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

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

Re: [Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-13 Thread Django

* needs_better_patch: => 0
* version: 1.5 => master
* needs_tests: => 0
* needs_docs: => 0
* stage: Unreviewed => Accepted

Comment:

It would seem the purpose of its current implementation is that a URL
which is already quoted is not quoted again, but an unquoted URL will be
quoted. The context in which this is applied, is django.utils.html.urlize.
This was added in #9655

(https://github.com/django/django/commit/e3a7bfccbb83712caf0645e4e33f5c03d9dc462b),
although at that time with a little more code than it's current version.

The characters you are expecting to be escaped are currently marked as
safe. Otherwise, even `http://example.com?q=` would already have the URL
encoding applied to it. At first sight, a solution seems to be to make
`smart_urlquote` even smarter, and only consider the currently listed
characters safe if they are not within a URL parameter themselves. I agree
that this is a bug after all.

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

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

Re: [Django] #21798: Model validation should complain if both `add_now` and `auto_add_now` are specified.

2014-03-13 Thread Django

#21798: Model validation should complain if both `add_now` and `auto_add_now` 
are
specified.
-+-
 Reporter:  charettes|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by PirosB3):

 Hi again,

 I think it would be good to warn the user that both parameters cannot be
 used, but also automatically make a decision for him/her (and notify it
 through the warning).
 Does this sound like a reasonable solution?

 The warning could be: "add_now and auto_add_now cannot be both specified,
 add_now has been disabled on this field"

 Please let me know,
 Daniel Pyrathon

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

Re: [Django] #21798: Model validation should complain if both `add_now` and `auto_add_now` are specified.

2014-03-13 Thread Django

#21798: Model validation should complain if both `add_now` and `auto_add_now` 
are
specified.
-+-
 Reporter:  charettes|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-

Comment (by anonymous):

 Hi,

 I am working now to provide a fix for this.

 Regards,
 Daniel Pyrathon

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

[Django] #22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url

2014-03-13 Thread Django

#22267: django.utils.html.smart_urlquote() is incorrectly unquoting the url
-+
 Reporter:  meenzam@…|  Owner:  nobody
 Type:  Bug  | Status:  new
Component:  Template system  |Version:  1.5
 Severity:  Normal   |   Keywords:
 Triage Stage:  Unreviewed   |  Has patch:  0
Easy pickings:  0|  UI/UX:  0
-+
 When we give django.utils.html.smart_urlquote() an url with an already
 embedded query as a query paramater, it is unquoting it which it should
 not do.

 For example,
 {{{
 
smart_urlquote('http://example.com/?q=http%3A%2F%2Fexample.com%2F%3Fx%3D1%26q%3Ddjango')
 }}}
 returns
 'http://example.com/?q=http://example.com/?x=1&q=django'
 which has the query parameters {{{ {'q': ['http://example.com/?x=1',
 'django']} }}}

 where it should have returned the exact url back
 'http://example.com/?q=http%3A%2F%2Fexample.com%2F%3Fx%3D1%26q%3Ddjango'
 which has the query parameters {{{ {'q':
 ['http://example.com/?x=1&q=django']} }}}

 I have written a test here -
 
https://github.com/ienzam/django/blob/master/tests/utils_tests/test_html.py#L203
 {{{
 # Ensure that embedded quoted url does not get unquoted
 self.assertEqual(
 
quote('http://example.com/?q=http%3A%2F%2Fexample.com%2F%3Fx%3D1%26q%3Ddjango'),
 'http://example.com/?q=http%3A%2F%2Fexample.com%2F%3Fx%3D1%26q%3Ddjango')
 }}}

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

Re: [Django] #21798: Model validation should complain if both `add_now` and `auto_add_now` are specified.

2014-03-13 Thread Django

#21798: Model validation should complain if both `add_now` and `auto_add_now` 
are
specified.
-+-
 Reporter:  charettes|Owner:  anonymous
 Type:   |   Status:  assigned
  Cleanup/optimization   |  Version:  master
Component:  Database layer   |   Resolution:
  (models, ORM)  | Triage Stage:  Accepted
 Severity:  Normal   |  Needs documentation:  1
 Keywords:   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  1|
Easy pickings:  1|
-+-
Changes (by PirosB3):

 * owner:  charettes => anonymous
 * status:  new => assigned


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

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

Re: [Django] #21721: Python 3.4 support

2014-03-13 Thread Django

#21721: Python 3.4 support
-+
 Reporter:  mjtamlyn |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Python 3 |  Version:  master
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by mjtamlyn):

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


Comment:

 I can confirm that in python3.4 rc3 there are no test failures. There are
 still warnings from the deprecation of the `imp` module, but that is
 tracked in #21628.

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

Re: [Django] #22256: Crash in find_program when PATH isn't defined

2014-03-13 Thread Django

#22256: Crash in find_program when PATH isn't defined
-+-
 Reporter:  vegitron |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Core (Management |  Version:  master
  commands)  |   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:   |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by bmispelon):

 * needs_docs:   => 0
 * needs_better_patch:   => 1
 * component:  Uncategorized => Core (Management commands)
 * needs_tests:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Left a comment on the pull request regarding the test.

 Once that's fixed, I think this is ready for checkin.

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

[django/django] c8823c: Fixed a grammar error in topics/i18n/translation.

2014-03-13 Thread GitHub

  Branch: refs/heads/master
  Home:   https://github.com/django/django
  Commit: c8823cf481a29e23fe3b9a4ce9f45f6d0b58ea9b
  
https://github.com/django/django/commit/c8823cf481a29e23fe3b9a4ce9f45f6d0b58ea9b
  Author: Iain Dawson 
  Date:   2014-03-13 (Thu, 13 Mar 2014)

  Changed paths:
M docs/topics/i18n/translation.txt

  Log Message:
  ---
  Fixed a grammar error in topics/i18n/translation.

Hooks are quantum; you can not have an amount of them.


-- 
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/532174d3f01c7_256eee1d44751c3%40hookshot-fe2-cp1-prd.iad.github.net.mail.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #22254: Testing documentation doesn't make it clear that django.setup() needs to be called with setup_test_environment

2014-03-13 Thread Django

#22254: Testing documentation doesn't make it clear that django.setup() needs 
to be
called with setup_test_environment
+---
 Reporter:  peter.landry@…  |Owner:  nobody
 Type:  Uncategorized   |   Status:  new
Component:  Documentation   |  Version:  1.7-alpha-2
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  0   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  0
Easy pickings:  0   |UI/UX:  0
+---
Changes (by mjtamlyn):

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


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

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

Re: [Django] #22265: Assurance of consistent behavior of migrations

2014-03-13 Thread Django

#22265: Assurance of consistent behavior of migrations
--+
 Reporter:  aruseni   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
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 erikr):

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


Comment:

 I think this is a valid point - the current text is very strong in its
 assertion, and this may hit some users unexpectedly. I agree we should add
 a sentence to mention the case you describe.

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

[Django] #22266: CharField primary keys with underscores are (un)escaped differently in the admin pages

2014-03-13 Thread Django

#22266: CharField primary keys with underscores are (un)escaped differently in 
the
admin pages
+
 Reporter:  victor.varvariuc@…  |  Owner:  nobody
 Type:  Bug | Status:  new
Component:  contrib.admin   |Version:  1.6
 Severity:  Normal  |   Keywords:
 Triage Stage:  Unreviewed  |  Has patch:  0
Easy pickings:  0   |  UI/UX:  0
+
 Migrated from here: https://code.djangoproject.com/ticket/18381#comment:6

 Although that bug was fixed 2 years ago, related issues seem still present
 in the latest stable Django release 1.6.2.
 CharField primary keys with underscores are (un)escaped differently in the
 admin pages, and when reversing admin URLs with
 django.core.urlresolvers.reverse() or the {% url %} template tag.
 The admin pages add "5F" after the underscore in when rendering URLs, but
 reverse() does not. As a result, links from custom pages into the admin
 break when the object's primary key contains underscores.

 Steps to reproduce:
 - Create a model with "id = models.CharField(max_length=100,
 primary_key=True)" or other similar text primary key field,
 - Register the model to the admin site,
 - Create a model instance with test_123 as the primary key,
 - Visit the admin, and observe admin URLs: they are of the format
 "/admin///test_5F123/"
 - Open the shell, and call reverse('admin:app_model_delete',
 args=['test_123'])
 - The URLs returned are of the format "/admin///test_123/" -
 no 5F
 - As a result, if these links are embedded in pages, they don't work - the
 admin page tries to decode the primary key, expects 5F, and does not find
 the object.

 {{{
 [trains] vic@vic ~/projects/trains (master *) $ ./manage.py shell
 Python 3.3.2+ (default, Oct  9 2013, 14:50:09)

 >>> from django.core.urlresolvers import reverse

 >>> reverse('admin:trains_route_change', args=('test_123',))
 >>> '/trains/route/test_123/'
 }}}

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

Re: [Django] #22262: Error in Translation Comments Documentation for Templates

2014-03-13 Thread Django

#22262: Error in Translation Comments Documentation for Templates
-+-
 Reporter:  av@… |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |  Version:  master
Component:  Documentation|   Resolution:
 Severity:  Normal   | Triage Stage:  Accepted
 Keywords:  templates, trans |  Needs documentation:  0
  tags   |  Patch needs improvement:  0
Has patch:  0|UI/UX:  0
  Needs tests:  0|
Easy pickings:  1|
-+-
Changes (by bmispelon):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * version:  1.6 => master
 * easy:  0 => 1
 * needs_docs:   => 0
 * stage:  Unreviewed => Accepted


Comment:

 Hi,

 Good catch, the actual comment does appear to be missing for the last
 example at https://docs.djangoproject.com/en/dev/topics/i18n/translation
 /#comments-for-translators-in-templates.

 For anyone who'd like to contribute a fix, the file to edit is
 `docs/topics/i18n/translation.txt`.

 Thanks.

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

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

64 matches

Mail list logo