Re: [Django] #34077: Make BoundField renderable.

[Django]

#34077: Make BoundField renderable.
-+
 Reporter:  David Smith  |Owner:  skidipap
 Type:  New feature  |   Status:  assigned
Component:  Forms|  Version:  4.1
 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 skidipap):

 * owner:  nobody => skidipap
 * 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/0107018400ebc13e-c936bb7d-0505-4804-b31a-732378b2e756-00%40eu-central-1.amazonses.com.

Re: [Django] #34110: Add InMemoryStorage

[Django]

#34110: Add InMemoryStorage
-+-
 Reporter:  Josh |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  File |  Version:  dev
  uploads/storage|
 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 skidipap):

 * owner:  skidipap => (none)
 * status:  assigned => new


-- 
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/0107018400e20094-3155b46f-1080-46d2-a651-0c44f8dca3a0-00%40eu-central-1.amazonses.com.

Re: [Django] #34110: Add InMemoryStorage

[Django]

#34110: Add InMemoryStorage
-+-
 Reporter:  Josh |Owner:  skidipap
 Type:  New feature  |   Status:  assigned
Component:  File |  Version:  dev
  uploads/storage|
 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 skidipap):

 * owner:  nobody => skidipap
 * 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/0107018400e1860f-e70bdd0b-e163-4980-bd7d-1b29bd3cd422-00%40eu-central-1.amazonses.com.

Re: [Django] #29942: viewsource links to contrib.auth.forms not appearing

[Django]

#29942: viewsource links to contrib.auth.forms not appearing
---+--
 Reporter:  Yemar Nevets   |Owner:  Felix Hein
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  2.1
 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 Zach Borboa):

 * cc: Zach Borboa (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/010701840099a626-ab0bd8cb-2636-4b44-bf67-f5f19ab1b2b7-00%40eu-central-1.amazonses.com.

Re: [Django] #6148: Add generic support for database schemas

[Django]

#6148: Add generic support for database schemas
-+-
 Reporter:  Ian Kelly|Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  oracle postgresql| Triage Stage:  Accepted
  mysql schemas  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  0
-+-

Comment (by Simon Charette):

 As pointed out by a kind attendee at DjangoConUS 2022 we might have to
 revive [https://github.com/django/django/pull/6162/ Anssi's PR] sooner
 than later to support installs against PostgresSQL 15+.

 From [https://www.postgresql.org/docs/release/15.0/ PostgresSQL 15.0
 release notes]

 > Remove `PUBLIC` creation permission on the public schema (Noah Misch)
 >
 > The new default is one of the secure schema usage patterns that Section
 5.9.6 has recommended since the security release for CVE-2018-1058. The
 change applies to new database clusters and to newly-created databases in
 existing clusters. Upgrading a cluster or restoring a database dump will
 preserve public's existing permissions.
 >
 > For existing databases, especially those having multiple users, consider
 revoking `CREATE` permission on the public schema to adopt this new
 default. For new databases having no need to defend against insider
 threats, granting `CREATE` permission will yield the behavior of prior
 releases.

 If your project was created on PostgreSQL < 15 you should not run into any
 issues even when upgrading but for projects created on a fresh 15+ install
 you might have to issue a `GRANT CREATE ON SCHEMA public TO
 $your_django_user` until support for `DATABASES['SCHEMA']` is 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/01070184004a34d2-9e17aaa7-d54d-40b2-aac9-2b0c8a6f48ba-00%40eu-central-1.amazonses.com.

Re: [Django] #33662: Choose which items are displayed per language in Sitemap

[Django]

#33662: Choose which items are displayed per language in Sitemap
--+
 Reporter:  roxanebellot  |Owner:  roxanebellot
 Type:  New feature   |   Status:  assigned
Component:  contrib.sitemaps  |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  sitemap   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by roxanebellot):

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


Comment:

 Sorry for the delay, I did not at all see any of your comments sooner !

 I have in my project a model Article which could be summed up in four
 fields (url_en, url_fr, content_en and content_fr). Some of these article
 are only written in one language. With no content, the page is empty. Even
 if it exists, I don't want this empty page to be in my sitemap.

 My idea was to add a method in Sitemap to return a boolean indicating
 whether the item should be displayed in the sitemap given a language.
 I made a first draft for a patch
 
([https://github.com/django/django/compare/main...roxanebellot:django:ticket_33662]).
 I wait for a green light on the feature before submitting it as a PR.

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/01070184000747b6-048576ca-d076-490a-a95a-8a2a054c6b1d-00%40eu-central-1.amazonses.com.