Re: [Django] #13376: Messages should have an "expire" flag

[Django]

#13376: Messages should have an "expire" flag
--+---
 Reporter:  ryanshow@…|Owner:  Andy Miller
 Type:  New feature   |   Status:  assigned
Component:  contrib.messages  |  Version:  1.2-beta
 Severity:  Normal|   Resolution:
 Keywords:  messages, expire  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  1
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+---
Changes (by Andy Miller):

 * owner:  (none) => Andy Miller
 * 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/01070190280c58ff-2f7116a2-9858-437d-a470-e548659b0fa0-00%40eu-central-1.amazonses.com.

Re: [Django] #35528: Add EmailMultiAlternatives.body_contains() to aid email test assertions (was: Added "body_contains" method to "EmailMultiAlternatives")

[Django]

#35528: Add EmailMultiAlternatives.body_contains() to aid email test assertions
-+
 Reporter:  Ron  |Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Mail)  |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  email| Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+
Changes (by Sarah Boyce):

 * has_patch:  0 => 1
 * stage:  Unreviewed => Accepted
 * summary:  Added "body_contains" method to "EmailMultiAlternatives" =>
 Add EmailMultiAlternatives.body_contains() to aid email test
 assertions

-- 
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/0107019026d8fd47-046a549f-17a1-47a0-8eac-1422a0802560-00%40eu-central-1.amazonses.com.

Re: [Django] #35505: Add a template block to the admin for extension by third party apps

[Django]

#35505: Add a template block to the admin for extension by third party apps
-+-
 Reporter:  Tom Carrick  |Owner:  Stefan
 |  Ivic
 Type:  New feature  |   Status:  assigned
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

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

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107019026c9c66d-7308082a-3919-4bbb-9f4d-2e0c426f9e14-00%40eu-central-1.amazonses.com.

[Django] #35528: Added "body_contains" method to "EmailMultiAlternatives"

[Django]

#35528: Added "body_contains" method to "EmailMultiAlternatives"
---+
   Reporter:  Ron  |  Owner:  nobody
   Type:  New feature  | Status:  new
  Component:  Core (Mail)  |Version:  dev
   Severity:  Normal   |   Keywords:  email
   Triage Stage:  Unreviewed   |  Has patch:  0
Needs documentation:  0|Needs tests:  0
Patch needs improvement:  0|  Easy pickings:  0
  UI/UX:  0|
---+
 Currently, it's very hard and tedious to assert the content of an email
 object. Therefore, we want to add a method "body_contains()" to
 "EmailMultiAlternatives" to check a search string in all available text-
 based alternatives (content parts, like HTML).

 This method can then be easily asserted in any given unit-test.

 There's a forum discussion going on about this topic:
 https://forum.djangoproject.com/t/improve-email-unit-testing/32044/1

 I've already created a PR for a suggetion:
 https://github.com/django/django/pull/18278/files
-- 
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/0107019026bfb159-379ae5b0-ab83-4d50-8534-7781488b8049-00%40eu-central-1.amazonses.com.

Re: [Django] #25306: Allow a limit_choices_to callable to accept the current model instance

[Django]

#25306: Allow a limit_choices_to callable to accept the current model instance
--+
 Reporter:  Miles Hutson  |Owner:  nobody
 Type:  New feature   |   Status:  new
Component:  Forms |  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 Sven R. Kunze):

 Also came across this issue recently.


 A bunch of StackOverflow questions could be solved a lot easier when the
 current instance would be available in ```limit_choices_to```:

 https://stackoverflow.com/questions/tagged/limit-choices-to?tab=Active
 https://stackoverflow.com/questions/39593577/how-to-get-instance-of-
 entity-in-limit-choices-to-django
 https://stackoverflow.com/questions/232435/how-do-i-restrict-foreign-keys-
 choices-to-related-objects-only-in-django
 https://stackoverflow.com/questions/47774013/django-limit-choices-to-to-
 current-objects-id
 https://stackoverflow.com/questions/28901089/use-field-value-in-limit-
 choices-to-in-django

 Having a db model solution would make the proposed work-arounds
 obsolete/easier (especially they usually only work for a single form or
 admin/inline). Also maintaining a single place of the choice restriction
 is better also in terms of security (hidden/filtered choices due to
 perms).

 I would imagine two possible some solutions:

 - one using an optional ```request=None, obj=None``` parameters to the
 callable (backwards compatible)
 - one using some special ```InstanceRef()``` object in a Q object
 (analogously to ```OuterRef("pk")```

 Personally, I would prefer the first solution because it's much more
 flexible and permission-wise the Request object is sometimes needed to
 realize more complex filtering.

 @Simon nice lib 
-- 
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/0107019026858c9c-61d136d3-c9a0-4e71-b060-18d2914ffc4d-00%40eu-central-1.amazonses.com.

Re: [Django] #35497: Long email address causes crash when generating a message

[Django]

#35497: Long email address causes crash when generating a message
-+-
 Reporter:  Alexandru Chirila|Owner:  Clinton
 |  Christian
 Type:  Bug  |   Status:  assigned
Component:  Core (Mail)  |  Version:  5.0
 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 Sarah Boyce):

 * cc: Florian Apolloner (added)
 * needs_better_patch:  0 => 1

Comment:

 #31784 discussed and went against the idea updating the line length to 998
 and so we would need to revisit that discussion if we are to accept the
 current PR.
 From what I see, the arguments in #31784 still stand and this is not the
 approach to resolve this 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107019026519567-23b73f37-a35a-4a36-8b9c-727e90d7680b-00%40eu-central-1.amazonses.com.

Re: [Django] #35520: ModelAdmin uses incorrect database in change and delete views

[Django]

#35520: ModelAdmin uses incorrect database in change and delete views
---+---
 Reporter:  Jake Howard|Owner:  Jake Howard
 Type:  Bug|   Status:  assigned
Component:  contrib.admin  |  Version:  dev
 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 Sarah Boyce):

 * needs_better_patch:  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/010701902610c71c-f043909c-3464-4164-90a4-517f2d403897-00%40eu-central-1.amazonses.com.

Re: [Django] #35269: GeneratedFields can't be defined on RelatedFields

[Django]

#35269: GeneratedFields can't be defined on RelatedFields
-+-
 Reporter:  Perrine L.   |Owner:  nobody
 Type:  New feature  |   Status:  closed
Component:  Database layer   |  Version:  5.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:  invalid
 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 Marco Glauser):

 We ran into the same issue. We tried to switch the responsible user of a
 task depending on some simple business logic that could be evaluated by
 the GeneratedField.

 The ForeignObject approach is working for us.

 For anyone stumbling on this discussion later on, we observed a caching
 issue with ForeignObject. The cache of the field doesn't get refreshed
 when `refresh_from_db` gets called.
 We had to explicitly override `refresh_from_db` on the Task model

 {{{
 def refresh_from_db(self, using=None, fields=None):
 super(Task, self).refresh_from_db(using=using, fields=fields)
 responsible_user_field = self._meta.get_field("responsible_user")
 if responsible_user_field.is_cached(self):
responsible_user_field.delete_cached_value(self)
 }}}
-- 
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/0107019025d07946-de482054-8847-45c6-b499-f6de6a44b916-00%40eu-central-1.amazonses.com.

Re: [Django] #35483: ModelMultipleChoiceField with CharField key throws ValueError if data contains NUL (0x00) characters

[Django]

#35483: ModelMultipleChoiceField with CharField key throws ValueError if data
contains NUL (0x00) characters
-+-
 Reporter:  Jennifer Richards|Owner:  lotvall
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  4.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  ModelMultipleChoiceField null nul  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Comment (by Sarah Boyce <42296566+sarahboyce@…>):

 In [changeset:"b8983dcf57b46a4391891cecdfc856c9c1c8d363" b8983dc]:
 {{{#!CommitTicketReference repository=""
 revision="b8983dcf57b46a4391891cecdfc856c9c1c8d363"
 [5.1.x] Fixed #35483 -- Added NUL (0x00) character validation to
 ModelChoiceFields.

 Applied the ProhibitNullCharactersValidator to ModelChoiceField and
 ModelMultipleChoiceField.

 Co-authored-by: Viktor Paripás 
 Co-authored-by: Vasyl Dizhak 
 Co-authored-by: Arthur Vasconcelos 

 Backport of 38ad710aba885ad26944ff5708ce1a02a446d2d3 from main.
 }}}
-- 
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/0107019025b8df89-d125cb23-4930-4915-8397-41061381c87b-00%40eu-central-1.amazonses.com.

Re: [Django] #35483: ModelMultipleChoiceField with CharField key throws ValueError if data contains NUL (0x00) characters

[Django]

#35483: ModelMultipleChoiceField with CharField key throws ValueError if data
contains NUL (0x00) characters
-+-
 Reporter:  Jennifer Richards|Owner:  lotvall
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  4.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  ModelMultipleChoiceField null nul  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce <42296566+sarahboyce@…>):

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

Comment:

 In [changeset:"38ad710aba885ad26944ff5708ce1a02a446d2d3" 38ad710]:
 {{{#!CommitTicketReference repository=""
 revision="38ad710aba885ad26944ff5708ce1a02a446d2d3"
 Fixed #35483 -- Added NUL (0x00) character validation to
 ModelChoiceFields.

 Applied the ProhibitNullCharactersValidator to ModelChoiceField and
 ModelMultipleChoiceField.

 Co-authored-by: Viktor Paripás 
 Co-authored-by: Vasyl Dizhak 
 Co-authored-by: Arthur Vasconcelos 
 }}}
-- 
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/0107019025b585b3-938d815e-b0d3-493e-93ea-f37698cfec70-00%40eu-central-1.amazonses.com.

Re: [Django] #35502: In the tutorial we have two mysite directories, and we often see users confused by that.

[Django]

#35502: In the tutorial we have two mysite directories, and we often see users
confused by that.
--+
 Reporter:  Meta Petric   |Owner:  tabiva
 Type:  Cleanup/optimization  |   Status:  closed
Component:  Documentation |  Version:  dev
 Severity:  Normal|   Resolution:  wontfix
 Keywords:  tutorial  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Sarah Boyce):

 * needs_better_patch:  0 => 1
 * resolution:   => wontfix
 * status:  assigned => closed

Comment:

 Having read through the changes, I am no longer convinced this is the best
 way forward as `django-admin startproject mysite` is the simplist version
 of running the `startproject` command and having this documented in the
 intro tutorial has some benefits. This makes me think that a wider
 discussion is needed. If you wish to progress this change, please discuss
 it on the [https://forum.djangoproject.com/c/internals/5 forum] also to
 confirm where exactly beginners get confused as maybe this isn't the right
 way to fix it.

 tabvia please note that you your PR is missing some file header updates
 for the code snippets in the tutorial.
-- 
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/0107019025a8c54b-1173a3b2-cc32-462e-9971-8815467c0fa7-00%40eu-central-1.amazonses.com.

Re: [Django] #35103: UniqueConstraint message does not use violation_error_message

[Django]

#35103: UniqueConstraint message does not use violation_error_message
-+-
 Reporter:  Gerben Morsink   |Owner:  Gerben
 Type:   |  Morsink
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  5.1
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  UniqueConstraint,| Triage Stage:  Accepted
  violation_error_message|
Has patch:  1|  Needs documentation:  0
  Needs tests:  1|  Patch needs improvement:  1
Easy pickings:  1|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * 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/0107019025973761-e43746a8-67bd-4519-a813-36498f9efcc0-00%40eu-central-1.amazonses.com.

Re: [Django] #35404: Admin fieldset multiple flexbox regressions

[Django]

#35404: Admin fieldset multiple flexbox regressions
-+-
 Reporter:  minusf   |Owner:  Vaarun
 |  Sinha
 Type:  Bug  |   Status:  assigned
Component:  contrib.admin|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:  css admin fieldset   | Triage Stage:  Accepted
  accessibility  |
Has patch:  0|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  1
-+-
Changes (by Vaarun Sinha):

 * owner:  nobody => Vaarun Sinha
 * 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/0107019025669ee3-cc1d04e1-66eb-4e32-939d-c6071531e5eb-00%40eu-central-1.amazonses.com.

Re: [Django] #35483: ModelMultipleChoiceField with CharField key throws ValueError if data contains NUL (0x00) characters

[Django]

#35483: ModelMultipleChoiceField with CharField key throws ValueError if data
contains NUL (0x00) characters
-+-
 Reporter:  Jennifer Richards|Owner:  lotvall
 Type:  Bug  |   Status:  assigned
Component:  Forms|  Version:  4.2
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
  ModelMultipleChoiceField null nul  |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * stage:  Accepted => Ready for checkin

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701902559abfb-f5c6a7ea-0dab-4aac-ad76-de9bc49dfbf9-00%40eu-central-1.amazonses.com.

Re: [Django] #34846: Add "Copy" button to the code snippets in docs.

[Django]

#34846: Add "Copy" button to the code snippets in docs.
-+-
 Reporter:  rushabhTt|Owner:  Mubeen F.
 Type:   |   Status:  assigned
  Cleanup/optimization   |
Component:  Documentation|  Version:  4.2
 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 Sarah Boyce):

 * needs_better_patch:  0 => 1

Comment:

 Investigation is required as to whether this shouldn't be solved in
 
[https://github.com/django/djangoproject.com/blob/main/djangoproject/static/js/mod/clippify.js
 djangoproject.com] as is the current 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701902540e526-b39e9b0c-1e54-4e04-9238-3942c771ecab-00%40eu-central-1.amazonses.com.

Re: [Django] #35306: Improve documentation for the various date format settings

[Django]

#35306: Improve documentation for the various date format settings
-+-
 Reporter:  Richard  |Owner:  Lufafa
 Type:   |  Joshua
  Cleanup/optimization   |   Status:  assigned
Component:   |  Version:  5.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  LANGUAGE_CODE,   | Triage Stage:  Accepted
  DATE_FORMAT|
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * needs_better_patch:  0 => 1

Comment:

 Adding the link from #35470 is required
-- 
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/010701902536343d-39527fe1-1783-444e-bc42-8c756eed977a-00%40eu-central-1.amazonses.com.

Re: [Django] #35441: Context autoescape parameter is not documented

[Django]

#35441: Context autoescape parameter is not documented
-+-
 Reporter:  Roman Donchenko  |Owner:  John
 Type:   |  Higgins
  Cleanup/optimization   |   Status:  assigned
Component:  Template system  |  Version:  5.0
 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 Sarah Boyce):

 * needs_better_patch:  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/010701902533d01d-ced44cc6-1565-4954-bdf9-e5e41518a003-00%40eu-central-1.amazonses.com.

Re: [Django] #12978: Support in syndication framework for CSS stylesheet links

[Django]

#12978: Support in syndication framework for CSS stylesheet links
-+-
 Reporter:  intrepidweb  |Owner:  Baptiste
 |  Mispelon
 Type:  New feature  |   Status:  assigned
Component:  contrib.syndication  |  Version:  1.1
 Severity:  Normal   |   Resolution:
 Keywords:  syndication css  | Triage Stage:  Ready for
  stylesheets|  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Sarah Boyce):

 * stage:  Accepted => Ready for checkin

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/010701902509a5c5-20bdb8c2-e165-41af-95fa-d50aace61626-00%40eu-central-1.amazonses.com.