Re: [Django] #25476: bug in array handling hit in get_constraints() for psycopg2?

[Django]

#25476: bug in array handling hit in get_constraints() for psycopg2?
-+-
 Reporter:  heasus   |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  needsinfo
 Keywords:  psycopg2 fetchall| 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):

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


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

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

Re: [Django] #25485: Deprecation notice on GenericRelation is confusing

[Django]

#25485: Deprecation notice on GenericRelation is confusing
--+
 Reporter:  tarkatronic   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:  fixed
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"f79682eaf26c582dadbeec822b845f68029a965c" f79682ea]:
 {{{
 #!CommitTicketReference repository=""
 revision="f79682eaf26c582dadbeec822b845f68029a965c"
 [1.8.x] Fixed #25485 -- Improved deprecation docs for contenttypes
 reorganization.
 }}}

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

Re: [Django] #25466: django.template.loader.LoaderOrigin was removed without proper deprecation

[Django]

#25466: django.template.loader.LoaderOrigin was removed without proper 
deprecation
-+
 Reporter:  tarkatronic  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.9a1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+

Comment (by Tim Graham ):

 In [changeset:"59027a4cae8c5abbd0e9308d95dd6608be9199cd" 59027a4c]:
 {{{
 #!CommitTicketReference repository=""
 revision="59027a4cae8c5abbd0e9308d95dd6608be9199cd"
 [1.9.x] Fixed #25466 -- Added backwards compatibility aliases for
 LoaderOrigin and StringOrigin.

 Thanks Simon Charette for the DeprecationInstanceCheck class.

 Backport of 8d1a001ef6dcbbe8053da05cdb3ec99965b0953f from master
 }}}

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

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

Re: [Django] #25485: Deprecation notice on GenericRelation is confusing

[Django]

#25485: Deprecation notice on GenericRelation is confusing
--+
 Reporter:  tarkatronic   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by tarkatronic):

 Looks good to me, except your new line 529 says "this old location" vs all
 the others saying "the old location". Other than that, it looks much
 better. Thank you!

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

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

Re: [Django] #25466: django.template.loader.LoaderOrigin was removed without proper deprecation

[Django]

#25466: django.template.loader.LoaderOrigin was removed without proper 
deprecation
-+
 Reporter:  tarkatronic  |Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Template system  |  Version:  1.9a1
 Severity:  Release blocker  |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"8d1a001ef6dcbbe8053da05cdb3ec99965b0953f" 8d1a001]:
 {{{
 #!CommitTicketReference repository=""
 revision="8d1a001ef6dcbbe8053da05cdb3ec99965b0953f"
 Fixed #25466 -- Added backwards compatibility aliases for LoaderOrigin and
 StringOrigin.

 Thanks Simon Charette for the DeprecationInstanceCheck class.
 }}}

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

Re: [Django] #25485: Deprecation notice on GenericRelation is confusing

[Django]

#25485: Deprecation notice on GenericRelation is confusing
--+
 Reporter:  tarkatronic   |Owner:  nobody
 Type:  Cleanup/optimization  |   Status:  new
Component:  Documentation |  Version:  1.8
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * has_patch:  0 => 1
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 [https://github.com/django/django/pull/5374 PR] -- does it help? I'm
 reluctant to backport to 1.7 since this causes problems for the translated
 versions of the docs (there isn't a way to update the translations for
 non-stable versions of the docs).

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

[Django] #25485: Deprecation notice on GenericRelation is confusing

[Django]

#25485: Deprecation notice on GenericRelation is confusing
---+
 Reporter:  tarkatronic|  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Documentation  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 In looking up the documentation for GenericRelation, I ran across the
 deprecation notice which looks like:

   class GenericRelation
   Deprecated since version 1.7:
   This class used to be defined in django.contrib.contenttypes.generic.
 Support for importing from this old location will be removed in Django
 1.9.

 This was initially confusing to me for two reasons. To alleviate
 repetition, here's the related conversation from IRC:

   < TheJoey> Is it just me, or is this deprecation notice a bit confusing?
 https://docs.djangoproject.com/en/1.8/ref/contrib/contenttypes/#reverse-
 generic-relations
   < moldy> TheJoey: not to me
   < TheJoey> moldy: It makes it sound to me, at first, like
 GenericRelation itself is deprecated. And then it goes on to say that the
 old location will be removed, but not where the new location is.
   < moldy> TheJoey: i do wish that the reference docs would say "class
 the.import.path.Object" in these headings (the ), but that's a more
 general issue
   < giarc> TheJoey a little... it'd be nice to have the current import
 location mentioned
   < TheJoey> moldy: Or at least showing more import statements in the
 example code
   < TheJoey> Problem is, just looking at this doc, I have no idea where to
 pluck GenericRelation from. Except that I just read something earlier
 today about that particular deprecation, so I already have an idea where
 to look.

 Perhaps this could be stated more along the lines of "This class
 definition was moved from django.contrib.contenttypes.generic to
 django.contrib.contenttypes.fields", or the example below could actually
 show the import.

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

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

Re: [Django] #25376: Replace "sudo pip install" recommendation with virtualenv

[Django]

#25376: Replace "sudo pip install" recommendation with virtualenv
-+-
 Reporter:  timgraham|Owner:  tyagi-
 Type:   |  iiitv
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"f3ce888d3f2b5387d517225d1b70659a32bcc441" f3ce888]:
 {{{
 #!CommitTicketReference repository=""
 revision="f3ce888d3f2b5387d517225d1b70659a32bcc441"
 [1.8.x] Fixed #25376 -- Required virtualenv in installation instructions.

 Thanks Anjul Tyagi for some of the draft text.

 Backport of a523d94b4581ec41c86f5bbaaffdf5bb6b819c2e from master
 }}}

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

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

Re: [Django] #25376: Replace "sudo pip install" recommendation with virtualenv

[Django]

#25376: Replace "sudo pip install" recommendation with virtualenv
-+-
 Reporter:  timgraham|Owner:  tyagi-
 Type:   |  iiitv
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"e21c6f34ded8a2b0a9b5a80ab069eb2e1b15067b" e21c6f34]:
 {{{
 #!CommitTicketReference repository=""
 revision="e21c6f34ded8a2b0a9b5a80ab069eb2e1b15067b"
 [1.9.x] Fixed #25376 -- Required virtualenv in installation instructions.

 Thanks Anjul Tyagi for some of the draft text.

 Backport of a523d94b4581ec41c86f5bbaaffdf5bb6b819c2e from master
 }}}

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

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

Re: [Django] #25376: Replace "sudo pip install" recommendation with virtualenv

[Django]

#25376: Replace "sudo pip install" recommendation with virtualenv
-+-
 Reporter:  timgraham|Owner:  tyagi-
 Type:   |  iiitv
  Cleanup/optimization   |   Status:  closed
Component:  Documentation|  Version:  1.8
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"a523d94b4581ec41c86f5bbaaffdf5bb6b819c2e" a523d94]:
 {{{
 #!CommitTicketReference repository=""
 revision="a523d94b4581ec41c86f5bbaaffdf5bb6b819c2e"
 Fixed #25376 -- Required virtualenv in installation instructions.

 Thanks Anjul Tyagi for some of the draft text.
 }}}

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

Re: [Django] #22384: Deprecate the ability to reverse by dotted path

[Django]

#22384: Deprecate the ability to reverse by dotted path
-+-
 Reporter:  timo |Owner:  timo
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (URLs)  |  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"6348db378a8fef555aba30761857ef161112b499" 6348db37]:
 {{{
 #!CommitTicketReference repository=""
 revision="6348db378a8fef555aba30761857ef161112b499"
 Refs #22384 -- Removed obsolete code for the removal of reversing by
 dotted path.
 }}}

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

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

Re: [Django] #25354: related_query_name doesn't support class/app_label interpolation

[Django]

#25354: related_query_name doesn't support class/app_label interpolation
-+-
 Reporter:  jpulec   |Owner:  jpulec
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 jpulec):

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


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

Re: [Django] #25354: related_query_name doesn't support class/app_label interpolation

[Django]

#25354: related_query_name doesn't support class/app_label interpolation
-+-
 Reporter:  jpulec   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 charettes):

 @jpulec, I don't think this needs to be brought up on django-developers.
 You can go ahead and work on a patch and publish it as PR on Github. See
 our [https://docs.djangoproject.com/en/dev/internals/contributing/
 contributing guidelines].

 From what I can see of the actual implementation of `related_name` linked
 above by Tim a simple similar `if self.remove_field.related_query_name`
 block should do. Feel free to hop on #django-dev and ping `charettes` if
 you need further help.

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

Re: [Django] #25354: related_query_name doesn't support class/app_label interpolation

[Django]

#25354: related_query_name doesn't support class/app_label interpolation
-+-
 Reporter:  jpulec   |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  1.8
  (models, ORM)  |
 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 jpulec):

 I'd be happy to take a crack at it, but I've never contributed before, and
 am not the most familiar with the 'related' internals of django. Is this
 something that should get brought up on django-developers, or would
 starting to work on a patch be the right approach?

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

Re: [Django] #25484: static template tag outputs invalid HTML if storage class's url() returns a URI with '&' characters.

[Django]

#25484: static template tag outputs invalid HTML if storage class's url() 
returns a
URI with '&' characters.
-+
 Reporter:  jneves   |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  contrib.staticfiles  |  Version:  1.8
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * component:  Uncategorized => contrib.staticfiles
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 I think something like this is more correct:
 {{{
 if context.autoescape:
 url = conditional_escape(url)
 }}}
 Could you also add some 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/064.627907b22b933f71b51de27bebbcc87a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #25484: static template tag outputs invalid HTML if storage class's url() returns a URI with '&' characters.

[Django]

#25484: static template tag outputs invalid HTML if storage class's url() 
returns a
URI with '&' characters.
---+
 Reporter:  jneves |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal | Resolution:
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
Changes (by jneves):

 * Attachment "static_escape.2.patch" added.

 Patch to fix the static lack of escape issue (now also covering
 staticfiles)

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

Re: [Django] #25484: static template tag outputs invalid HTML if storage class's url() returns a URI with '&' characters.

[Django]

#25484: static template tag outputs invalid HTML if storage class's url() 
returns a
URI with '&' characters.
---+
 Reporter:  jneves |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal | Resolution:
 Keywords: |   Triage Stage:  Unreviewed
Has patch:  0  |  Easy pickings:  0
UI/UX:  0  |
---+
Changes (by jneves):

 * Attachment "static_escape.patch" added.

 Patch to fix the static lack of escape issue

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

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

Re: [Django] #25203: Document changes to WSGI application loading sequence in 1.7

[Django]

#25203: Document changes to WSGI application loading sequence in 1.7
-+-
 Reporter:  yscumc   |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Documentation|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  wsgi setup   | Triage Stage:  Accepted
  application loading|
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by grahamd):

 Where you need a process level global variable inherited from some key set
 in the Apache configuration, what you are best to do is ensure you are
 running the Django application in a mod_wsgi daemon process group of its
 own (forced to use main interpreter application group), and then base any
 in code decisions on the name of the daemon process group you used in the
 Apache configuration.

 For example, you could even have the name of the Django settings module be
 the name of the daemon process group.

 {{{
 WSGIDaemonProcess mysite.production.settings
 WSGIScriptAlias / /some/path/wsgi.py process-
 group=mysite.production.settings application-group=%{GLOBAL}
 }}}

 In the `wsgi.py` file you can then say:

 {{{
 try:
 import mod_wsgi
 os.environ['DJANGO_SETTINGS_MODULE'] = mod_wsgi.process_group
 except ImportError:
 os.environ.setdefault('DJANGO_SETTINGS_MODULE',
 'mysite.development.settings')
 }}}

 This can be placed before any other module imports as it is dependent on
 information available at import time and not at the time of a request.

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

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

[Django] #25484: static template tag outputs invalid HTML if storage class's url() returns a URI with '&' characters.

[Django]

#25484: static template tag outputs invalid HTML if storage class's url() 
returns a
URI with '&' characters.
---+
 Reporter:  jneves |  Owner:  nobody
 Type:  Uncategorized  | Status:  new
Component:  Uncategorized  |Version:  1.8
 Severity:  Normal |   Keywords:
 Triage Stage:  Unreviewed |  Has patch:  0
Easy pickings:  0  |  UI/UX:  0
---+
 When using a storage class like 'storages.backend.s3.S3BotoStorage' from
 django-storages/django-storages-redux the following template code:

 {{{
 
 }}}

 is rendered as:

 {{{
 https://bucket.region.amazonaws.com:443/css/styles.css?Signature=sm8uyGp12rTST59hSWyTtZz8A&Expires=1443476662&AWSAccessKeyId=AN_AWS_KEY";
 rel="stylesheet" type="text/css" />
 }}}

 when the valid html should be:

 {{{
 https://bucket.region.amazonaws.com:443/css/styles.css?Signature=sm8uyGp12rTST59hSWyTtZz8A&Expires=1443476662&AWSAccessKeyId=AN_AWS_KEY";
 rel="stylesheet" type="text/css" />
 }}}

 This issue is only visible when using a storage that returns URLs with '&'
 characters in the query string.

 Work-around: You get the correct result if you render the above as:

 {{{
 {% static 'css/styles.css' as this_url %}
 
 }}}

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

Re: [Django] #25483: [doc] Using call_command() should pass positional argument as str() instead of int()

[Django]

#25483: [doc] Using call_command() should pass positional argument as str() 
instead
of int()
-+-
 Reporter:  mrkschan |Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  master
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by claudep):

 * needs_better_patch:   => 0
 * component:  Documentation => Core (Management commands)
 * needs_tests:   => 0
 * version:  1.8 => master
 * needs_docs:   => 0
 * type:  Uncategorized => Cleanup/optimization
 * stage:  Unreviewed => Accepted


Comment:

 I think we could force all `args` to text before passing them to
 `parse_args`.

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