Re: [Django] #15619: Logout link should be protected

[Django]

#15619: Logout link should be protected
-+-
 Reporter:  Alexey Boriskin  |Owner:  René
 Type:   |  Fleschenberg
  Cleanup/optimization   |   Status:  closed
Component:  contrib.auth |  Version:  dev
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak ):

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


Comment:

 In [changeset:"eb07b5be0ce7c51938ed9b00bae04ebe9a75110c" eb07b5be]:
 {{{
 #!CommitTicketReference repository=""
 revision="eb07b5be0ce7c51938ed9b00bae04ebe9a75110c"
 Fixed #15619 -- Deprecated log out via GET requests.

 Thanks Florian Apolloner for the implementation idea.

 Co-Authored-By: Mariusz Felisiak 
 }}}

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd434fb1a-710e1806-a6b9-4cdd-835c-cd0d11eae613-00%40eu-central-1.amazonses.com.

Re: [Django] #33604: Allow CacheMiddleware.key_prefix to be a callable.

[Django]

#33604: Allow CacheMiddleware.key_prefix to be a callable.
--+
 Reporter:  Alexandru Mărășteanu  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Cache system)   |  Version:  dev
 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 Alexandru Mărășteanu):

 Replying to [comment:3 Mariusz Felisiak]:
 > Tentatively accepted.

 I started writing some tests the other evening so I'll try to open a PR
 later today.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd41c2a3e-96e8b53e-d3d8-4c27-9cc7-eace8d45ffa7-00%40eu-central-1.amazonses.com.

Re: [Django] #33604: Allow CacheMiddleware.key_prefix to be a callable.

[Django]

#33604: Allow CacheMiddleware.key_prefix to be a callable.
--+
 Reporter:  Alexandru Mărășteanu  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Cache system)   |  Version:  dev
 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 Mariusz Felisiak):

 * cc: Tobias Kunze (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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd418f28d-f536b408-d0d7-433a-bfcb-152718ee1de4-00%40eu-central-1.amazonses.com.

Re: [Django] #33604: Allow CacheMiddleware.key_prefix to be a callable. (was: Allow `CacheMiddleware.key_prefix` to be a callable)

[Django]

#33604: Allow CacheMiddleware.key_prefix to be a callable.
--+
 Reporter:  Alexandru Mărășteanu  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Core (Cache system)   |  Version:  dev
 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 Mariusz Felisiak):

 * stage:  Unreviewed => Accepted


Comment:

 Tentatively 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd41843c4-21273c1d-5245-4ed7-a356-a4104b1b8f6d-00%40eu-central-1.amazonses.com.

Re: [Django] #32604: File uploads larger than FILE_UPLOAD_MAX_MEMORY_SIZE get wrong unix group based on setgid

[Django]

#32604: File uploads larger than FILE_UPLOAD_MAX_MEMORY_SIZE get wrong unix 
group
based on setgid
-+-
 Reporter:  Gavin Wahl   |Owner:  Mateo
 Type:   |  Radman
  Cleanup/optimization   |   Status:  assigned
Component:  File |  Version:  3.1
  uploads/storage|
 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 Mateo Radman):

 Hi,
 Is there anything else that needs to be done here?
 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd411055b-3d11c3d2-829c-4b8c-a55b-7ace31a2aa9a-00%40eu-central-1.amazonses.com.

Re: [Django] #33604: Allow `CacheMiddleware.key_prefix` to be a callable

[Django]

#33604: Allow `CacheMiddleware.key_prefix` to be a callable
-+-
 Reporter:  Alexandru|Owner:  nobody
  Mărășteanu |
 Type:  New feature  |   Status:  new
Component:  Core (Cache system)  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Alexandru Mărășteanu):

 Replying to [comment:1 Mariusz Felisiak]:
 > Thanks for the ticket. Dynamic prefixes are not supported, however you
 can use the [https://docs.djangoproject.com/en/stable/topics/cache/#cache-
 key-transformation KEY_FUNCTION] cache setting and changed `key_prefix`
 dynamically. I'm not convinced that we really need another option here.

 The need is to cache dynamically depending on the current request, on
 request properties like the user, or the query params etc. One of my use
 cases is to cache pages for anonymous users only. Another one is to cache
 pages based on some value stored in Redis. Another thing I want to do is
 to force it to skip the cache based on a query param (appending a random
 value is not always possible). Currently I do this with a custom
 middleware which extends the builtin one and simply updates
 `self.key_prefix` at the appropriate times. It seems to me it's a small
 change with great utility.

 The `KEY_FUNCTION` would be useful here if it received the request. But
 allowing a callable `key_prefix` is a lot cheaper than changing the
 signature of `KEY_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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd1a978ff-c6af3e99-6c61-44f6-93ca-7972f3c088c0-00%40eu-central-1.amazonses.com.

Re: [Django] #33604: Allow `CacheMiddleware.key_prefix` to be a callable

[Django]

#33604: Allow `CacheMiddleware.key_prefix` to be a callable
-+-
 Reporter:  Alexandru|Owner:  nobody
  Mărășteanu |
 Type:  New feature  |   Status:  new
Component:  Core (Cache system)  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Mariusz Felisiak):

 Thanks for the ticket. Dynamic prefixes are not supported, however you can
 use the [https://docs.djangoproject.com/en/stable/topics/cache/#cache-key-
 transformation KEY_FUNCTION] cache setting and changed `key_prefix`
 dynamically. I'm not convinced that we really need another option here.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd179ab7f-565c83d7-03a4-4a8b-8248-fda89ef5ea19-00%40eu-central-1.amazonses.com.

[Django] #33604: Allow `CacheMiddleware.key_prefix` to be a callable

[Django]

#33604: Allow `CacheMiddleware.key_prefix` to be a callable
+
   Reporter:  Alexandru Mărășteanu  |  Owner:  nobody
   Type:  New feature   | Status:  new
  Component:  Core (Cache system)   |Version:  dev
   Severity:  Normal|   Keywords:
   Triage Stage:  Unreviewed|  Has patch:  0
Needs documentation:  0 |Needs tests:  0
Patch needs improvement:  0 |  Easy pickings:  0
  UI/UX:  0 |
+
 As discussed in https://groups.google.com/g/django-
 developers/c/UbD1DkV1uPo and https://code.djangoproject.com/ticket/11269
 it would be useful to be able to specify a callable which would allow for
 more dynamic caching. In my case, I need to cache differently depending on
 whether the user is authenticated or not. Another scenario is to cache
 certain pages depending on some timestamp. Other uses cases were mentioned
 in the linked pages.

 There exists https://github.com/peterbe/django-fancy-cache but I was able
 to address this by extending the built-in middleware so I really don't see
 an argument for a 3rd party package.

 I'll try to open a PR for this.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd1657e47-0eff897b-d2fb-430b-861b-bbaf34f2d87a-00%40eu-central-1.amazonses.com.

Re: [Django] #33598: Using multiple FilteredRelation with different filters but for same relation is ignored.

[Django]

#33598: Using multiple FilteredRelation with different filters but for same
relation is ignored.
-+-
 Reporter:  lind-marcus  |Owner:  Mariusz
 |  Felisiak
 Type:  Bug  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Release blocker  |   Resolution:
 Keywords:  FilteredRelation | Triage Stage:  Accepted
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * owner:  nobody => Mariusz Felisiak
 * 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd048bb30-1d3f34e6-d0ee-4dc5-aee2-6bdde7fbbe84-00%40eu-central-1.amazonses.com.

Re: [Django] #33603: Backslashes in template tag arguments are escaped

[Django]

#33603: Backslashes in template tag arguments are escaped
-+-
 Reporter:  bhch |Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Template system  |  Version:  3.2
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * status:  new => closed
 * type:  Bug => Cleanup/optimization
 * resolution:   => wontfix


Comment:

 Thanks for the report, however I don't think Django can do much here, and
 any change would be backward incompatible. Please also take into account
 that it works when `value` is passed directly, e.g.
 {{{
 {% string_replace "My address\r\nwith newline characters" "\r\n"  "," %}
 }}}
 I'd recommend to create a new filter, e.g. `{% replace_newline value %}`,
 pass arguments via context variables, or escape/unescape arguments in
 `string_replace()`.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fd0278906-44cf9fda-8a64-4d51-9d7c-bcfc56095b6a-00%40eu-central-1.amazonses.com.

Re: [Django] #16406: Allow separate access to matches from urlpatterns and extra_context args

[Django]

#16406: Allow separate access to matches from urlpatterns and extra_context args
-+-
 Reporter:  Florian Apolloner|Owner:  Alokik
 Type:   |  Roy
  Cleanup/optimization   |   Status:  assigned
Component:  Core (URLs)  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  resolvers, reverse   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * needs_tests:  0 => 1


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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107017fcf5e9e82-84da85ed-162f-436e-a6c0-ee18142cb502-00%40eu-central-1.amazonses.com.