[Django] #33664: Timezones with hyphens in name fail in Extract() functions.

2022-04-26 Thread Django 
#33664: Timezones with hyphens in name fail in Extract() functions.
-+-
   Reporter:  Doug   |  Owner:  nobody
  Franklin   |
   Type: | Status:  new
  Uncategorized  |
  Component: |Version:  3.2
  Uncategorized  |   Keywords:  timezone extract
   Severity:  Normal |  hyphen
   Triage Stage: |  Has patch:  0
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 {{{
 local_tz = pytz.timezone(""Asia/Ust-Nera")
 models = Model.objects.annotate(
 created_at_month=ExtractMonth('created_at', tzinfo=local_tz)
 )
 }}}

 When evaluating the queryset it fails with:


 {{{
 DataError: time zone "Asia/Ust+Nera" not recognized
 }}}

 The "+" in "Asia/Ust+Nera" is suspicious.I have confirmed this fails with
 other timezones with hyphens, such as "America/Port-au-Prince".

 I have also confirmed my postgresql DB supports these timezones:

 {{{
 SELECT
 name,
 abbrev,
 utc_offset,
 is_dst
 FROM pg_timezone_names
 WHERE name !~ 'posix'
 ORDER BY name asc;
 }}}
 {{{
 ```
 Asia/Ust-Nera| +10| 10:00:00   | f
 ...
 America/Port-au-Prince   | EDT| -04:00:00  | t
 ```
 }}}

-- 
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/010701806953a330-a84ec518-9f78-4c9b-ab9d-ff17028d2b98-00%40eu-central-1.amazonses.com.

[Django] #33663: Timezones with hyphens in name fail in Extract() functions.

2022-04-26 Thread Django 
#33663: Timezones with hyphens in name fail in Extract() functions.
-+
   Reporter:  spetoolio  |  Owner:  nobody
   Type:  Uncategorized  | Status:  new
  Component:  Uncategorized  |Version:  4.0
   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  |
-+
 {{{
 local_tz = pytz.timezone(""Asia/Ust-Nera")
 Model.objects.annotate(
 created_at_month=ExtractMonth('created_at', tzinfo=local_tz)
 )
 }}}

 Fails with:


 {{{
 DataError: time zone "Asia/Ust+Nera" not recognized
 }}}

 I have confirmed this fails with other timezones with hyphens, such as
 "America/Port-au-Prince".

 I have also confirmed my postgresql DB supports these timezones:

 {{{
 SELECT
 name,
 abbrev,
 utc_offset,
 is_dst
 FROM pg_timezone_names
 WHERE name !~ 'posix'
 ORDER BY name asc;
 }}}

-- 
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/0107018069509d48-73175806-54b6-4522-a8fe-f6521dda2f97-00%40eu-central-1.amazonses.com.

Re: [Django] #29854: Altering the primary key targeted by several foreign keys incorrectly alters the foreign key's NULL attribute on MySQL (was: Altering the primary key targeted by several foreign k

2022-04-26 Thread Django 
#29854: Altering the primary key targeted by several foreign keys incorrectly
alters the foreign key's NULL attribute on MySQL
-+-
 Reporter:  Rick Yang|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Migrations   |  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  MySQL, Migration,| Triage Stage:  Accepted
  Altering primary key,  |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Collin Anderson):

 * cc: Collin Anderson (added)
 * has_patch:  0 => 1


Comment:

 I'm just confirming this is still an issue on mysql and that Baptiste's
 "quick workaround" above (sorting the fields) worked for me. I don't know
 what the proper solution should be, but it might be worth committing the
 workaround.

 In my particular case, I'm trying to migrate from an auto-created `id =
 AutoField(primary_key=True)` field to `id =
 models.CharField(max_length=15, primary_key=True)`, and there's a
 `ForeignKey(MyModel, null=True)` that was getting `NOT NULL`, likely
 because there are also some `ForeignKey(MyModel, null=False)` fields
 referencing this model, and they're getting mixed up.

 I think this one's complicated enough that I don't think I'm able to
 create a minimal test case, but here's a patch without any tests that
 fixes it for me:

 https://github.com/django/django/pull/15635

-- 
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/01070180672516d3-0abdf1d9-0dc8-4ecd-acfe-ea25164a919b-00%40eu-central-1.amazonses.com.

Re: [Django] #33646: Adding async interface to QuerySet.

2022-04-26 Thread Django 
#33646: Adding async interface to QuerySet.
-+-
 Reporter:  Mariusz Felisiak |Owner:  Andrew
 |  Godwin
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  4.0
  (models, ORM)  |
 Severity:  Normal   |   Resolution:
 Keywords:  async| 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):

 * 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/010701806724548e-da432681-95ce-428f-a606-38eee528b872-00%40eu-central-1.amazonses.com.

Re: [Django] #33647: bulk_update silently truncating values for size limited fields

2022-04-26 Thread Django 
#33647: bulk_update silently truncating values for size limited fields
-+-
 Reporter:  jerch|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (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 jerch):

 Replying to [comment:9 Carlton Gibson]:

 > ... I'm not sure the 11 days since you opened the ticket is that much
 for folks to come to a view. If your workaround is preforming well for
 you, that's good input. Otherwise you may need a little patience, though I
 see some input on the mailing list... 

 Well this ticket here is only loosely related and much younger (found the
 issue while doing some bulk_update tests). Ah whatever, will just wait on
 the mailing list input...

-- 
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/0107018066dbb531-fc484410-caf3-40a8-b0bf-99477791fbd6-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
--+
 Reporter:  mpachas   |Owner:  mpachas
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  date, template, i18n  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Description changed by mpachas:

Old description:

> DATE_FORMAT, DATETIME_FORMAT and MONTH_DAY_FORMAT strings in Catalan
> language are wrong because it uses always the preposition "de" between
> the day number and the month name but it is wrong when the month name
> starts with vowel like abril (April), agost (August) or octubre
> (October). In that case it should be d'abril, d'agost or d'octubre.
>
> I think that alt.month Month translations were created to help in this
> kind of situations (https://github.com/django/django/commit/2478f8588e)
> so this issue can be solved by a combination of a Catalan formats.py
> patch (django/conf/locale/ca/formats.py) and changing that translations
> (via Transifex).
>
> Actual:
> DATE_FORMAT = r"j \d\e F \d\e Y"
>
> msgid "January"
> msgstr "gener"
>
> msgid "April"
> msgstr "abril"
>
> {item.date | date} output -> 25 de gener de 2007
> {item.date | date} output -> 4 de abril de 2014---> THIS IS WRONG
>
> Proposal:
>
> DATE_FORMAT = r"j E \d\e Y" # E placeholder: alt. month translations for
> special cases.
>
> msgctxt "alt. month"
> msgid "January"
> msgstr "de gener"
>
> msgctxt "alt. month"
> msgid "April"
> msgstr "d'abril"
>
> {item.date | date} output -> 25 de gener de 2007
> {item.date | date} output -> 4 d'abril de 2014
>
> I'm trying to reach Catalan Transifex Team to add those strings, I think
> .po/.mo files won't follow the usual pull request way, but they must be
> changed before this file gets patched.
>
> Alternative month representation is available since this
> https://code.djangoproject.com/ticket/12309#no1

New description:

 DATE_FORMAT, DATETIME_FORMAT and MONTH_DAY_FORMAT strings in Catalan
 language are wrong because it uses always the preposition "de" between the
 day number and the month name but it is wrong when the month name starts
 with vowel like abril (April), agost (August) or octubre (October). In
 that case it should be d'abril, d'agost or d'octubre.

 I think that alt.month Month translations were created to help in this
 kind of situations (https://github.com/django/django/commit/2478f8588e) so
 this issue can be solved by a combination of a Catalan formats.py patch
 (django/conf/locale/ca/formats.py) and changing that translations (via
 Transifex).

 Actual:
 DATE_FORMAT = r"j \d\e F \d\e Y"

 msgid "January"
 msgstr "gener"

 msgid "April"
 msgstr "abril"

 {item.date | date} output -> 25 de gener de 2007
 {item.date | date} output -> 4 de abril de 2014---> THIS IS WRONG

 Proposal:

 DATE_FORMAT = r"j E \d\e Y" # E placeholder: alt. month translations for
 special cases.

 msgctxt "alt. month"
 msgid "January"
 msgstr "de gener"

 msgctxt "alt. month"
 msgid "April"
 msgstr "d'abril"

 {item.date | date} output -> 25 de gener de 2007
 {item.date | date} output -> 4 d'abril de 2014

 I'm trying to reach Catalan Transifex Team to add those strings, I think
 .po/.mo files won't follow the usual pull request way, but they must be
 changed before this file gets patched.

 Alternative month representation is available since this
 https://code.djangoproject.com/ticket/12309#no1

 Patch: https://github.com/django/django/pull/15634

--

-- 
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/01070180667c7106-81191f50-2783-45e9-8458-f3a7011bd453-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
--+
 Reporter:  mpachas   |Owner:  mpachas
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  date, template, i18n  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by mpachas):

 Replying to [comment:5 Carlton Gibson]:
 > Replying to [comment:4 mpachas]:
 >
 > Yes, I would open it anyway: it's easier to work with PRs than patch
 files (if only that we're already there, and seeing it in our list…)
 > Thanks
 PR available at https://github.com/django/django/pull/15634, I've just get
 in touch with aaloy as Transifex coordinator for Django translations in
 Catalan.

-- 
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/01070180667a842e-04d5ce93-2cc0-451a-9298-ad9f064b0220-00%40eu-central-1.amazonses.com.

[Django] #33662: Choose witch items are to be display per language in Sitemap

2022-04-26 Thread Django 
#33662: Choose witch items are to be display per language in Sitemap
-+-
   Reporter:  roxanebellot   |  Owner:  nobody
   Type:  New feature| Status:  new
  Component:  Uncategorized  |Version:  4.0
   Severity:  Normal |   Keywords:  sitemap
   Triage Stage:  Unreviewed |  Has patch:  0
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  0
  UI/UX:  0  |
-+-
 The current implementation of Sitemap is : if we use i18n, then we display
 a cartesian product between some items and some languages.

 There is no way to use the provided i18n automation if we want to display
 some items depending on the language (for instance non-translated blog
 articles).

 I precise in my case, urls are translated, so given a language the url may
 not exist or raise an error.

-- 
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/010701806663faea-56b8bf71-3769-45d9-8737-53ad5e563275-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
--+
 Reporter:  mpachas   |Owner:  mpachas
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  date, template, i18n  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Description changed by mpachas:

Old description:

> DATE_FORMAT, DATETIME_FORMAT and MONTH_DAY_FORMAT strings in Catalan
> language are wrong because it uses always the preposition "de" between
> the day number and the month name but it is wrong when the month name
> starts with vowel like abril (April), agost (August) or octubre
> (October). In that case it should be d'abril, d'agost or d'octubre.
>
> I think that alt.month Month translations were created to help in this
> kind of situations (https://github.com/django/django/commit/2478f8588e)
> so this issue can be solved by a combination of a Catalan formats.py
> patch (django/conf/locale/ca/formats.py) and changing that translations
> (via Transifex).
>
> Actual:
> DATE_FORMAT = r"j \d\e F \d\e Y"
>
> msgid "January"
> msgstr "enero"
>
> msgid "April"
> msgstr "abril"
>
> {item.date | date} output -> 25 de enero de 2007
> {item.date | date} output -> 4 de abril de 2014---> THIS IS WRONG
>
> Proposal:
>
> DATE_FORMAT = r"j E \d\e Y" # E placeholder: alt. month translations for
> special cases.
>
> msgctxt "alt. month"
> msgid "January"
> msgstr "de enero"
>
> msgctxt "alt. month"
> msgid "April"
> msgstr "d'abril"
>
> {item.date | date} output -> 25 de enero de 2007
> {item.date | date} output -> 4 d'abril de 2014
>
> I'm trying to reach Catalan Transifex Team to add those strings, I think
> .po/.mo files won't follow the usual pull request way, but they must be
> changed before this file gets patched.
>
> Alternative month representation is available since this
> https://code.djangoproject.com/ticket/12309#no1

New description:

 DATE_FORMAT, DATETIME_FORMAT and MONTH_DAY_FORMAT strings in Catalan
 language are wrong because it uses always the preposition "de" between the
 day number and the month name but it is wrong when the month name starts
 with vowel like abril (April), agost (August) or octubre (October). In
 that case it should be d'abril, d'agost or d'octubre.

 I think that alt.month Month translations were created to help in this
 kind of situations (https://github.com/django/django/commit/2478f8588e) so
 this issue can be solved by a combination of a Catalan formats.py patch
 (django/conf/locale/ca/formats.py) and changing that translations (via
 Transifex).

 Actual:
 DATE_FORMAT = r"j \d\e F \d\e Y"

 msgid "January"
 msgstr "gener"

 msgid "April"
 msgstr "abril"

 {item.date | date} output -> 25 de gener de 2007
 {item.date | date} output -> 4 de abril de 2014---> THIS IS WRONG

 Proposal:

 DATE_FORMAT = r"j E \d\e Y" # E placeholder: alt. month translations for
 special cases.

 msgctxt "alt. month"
 msgid "January"
 msgstr "de gener"

 msgctxt "alt. month"
 msgid "April"
 msgstr "d'abril"

 {item.date | date} output -> 25 de gener de 2007
 {item.date | date} output -> 4 d'abril de 2014

 I'm trying to reach Catalan Transifex Team to add those strings, I think
 .po/.mo files won't follow the usual pull request way, but they must be
 changed before this file gets patched.

 Alternative month representation is available since this
 https://code.djangoproject.com/ticket/12309#no1

--

-- 
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/01070180664d435f-248fc34b-0773-401c-a9de-00d389eb00a0-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
--+
 Reporter:  mpachas   |Owner:  mpachas
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  date, template, i18n  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by Carlton Gibson):

 Replying to [comment:4 mpachas]:

 Yes, I would open it anyway: it's easier to work with PRs than patch files
 (if only that we're already there, and seeing it in our list…)
 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/01070180663a8a7f-568433d0-7098-4f57-a6da-3c096003e695-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
--+
 Reporter:  mpachas   |Owner:  mpachas
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  date, template, i18n  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+

Comment (by mpachas):

 Replying to [comment:3 Carlton Gibson]:

 I will open a PR as soon as we update django.po and django.mo for Catalan.
 Otherwise, if the PR gets merged without the translations update then
 DATE_FORMAT, DATETIME_FORMAT and MONTH_DAY_FORMAT will show an incomplete
 format for all months instead of a wrong format for 3 months.

 If you think I should open it anyway, please tell me. 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/0107018066313102-d51817ab-2c5c-4e05-99a7-8e97e5a2b375-00%40eu-central-1.amazonses.com.

Re: [Django] #33647: bulk_update silently truncating values for size limited fields

2022-04-26 Thread Django 
#33647: bulk_update silently truncating values for size limited fields
-+-
 Reporter:  jerch|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (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 Carlton Gibson):

 Hi Jörg.

 > ...giving ppl early feedback helps to keep them engaged, and lowers the
 risk of time consuming dead end implementations (time on both ends, the
 implementer and the reviewers/maintainers), esp. when the bigger picture
 needs to be addressed (API changes, bigger codebase changes involved at
 several places)

 Sure. I'm not sure the 11 days since you opened the ticket is that much
 for folks to come to a view. If your workaround is preforming well for
 you, that's good input. Otherwise you may need a little patience, though I
 see some input on the mailing list... 

 > ...if the separated issue tracker in trac...

 That's out of scope for this one I'm afraid . (There are mailing list
 discussions about it, but it's not trivial, not least because of the
 history in Trac... — As I say out of scope for 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/01070180661dfc0e-c9626843-f77a-4840-bc55-d77d1259f101-00%40eu-central-1.amazonses.com.

Re: [Django] #33543: Depracate passing False to OrderBy's nulls_first and nulls_last.

2022-04-26 Thread Django 
#33543: Depracate passing False to OrderBy's nulls_first and nulls_last.
-+-
 Reporter:  Gordon Wrigley   |Owner:
 Type:   |  AllenJonathan
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (models, ORM)  |
 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 Mariusz Felisiak):

 * needs_better_patch:  0 => 1
 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/15632 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/010701806610d22d-7cf72a9f-6ad2-4d9e-a5e5-8168a83722df-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
--+
 Reporter:  mpachas   |Owner:  mpachas
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  date, template, i18n  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Carlton Gibson):

 * cc: Carlton Gibson (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/010701806609ffbd-0728d4f9-b5d1-4625-b033-2c643b126802-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
--+
 Reporter:  mpachas   |Owner:  mpachas
 Type:  Bug   |   Status:  assigned
Component:  Internationalization  |  Version:  4.0
 Severity:  Normal|   Resolution:
 Keywords:  date, template, i18n  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  1 |UI/UX:  0
--+
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 Hi, thanks for the report.

 >… it is wrong when the month name starts with vowel like abril (April),
 agost (August) or octubre (October). In that case it should be d'abril,
 d'agost or d'octubre.

 Yep, OK.

 Let's accept; without reviewing fully, your explanation that we need to
 update the formats sounds likely.

 Are you able to open a PR on GitHub with your patch?
 https://github.com/django/django/pulls

 Moltes gràcies!

-- 
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/0107018065ffda81-3c4f911f-6543-43be-95e6-45231becfce6-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
-+-
 Reporter:  mpachas  |Owner:  mpachas
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  4.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  date, template,  | Triage Stage:
  i18n   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mpachas):

 * Attachment "patch.diff" added.

 patch with .diff extension

-- 
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/0107018065f0c2a9-f74c6b98-4223-4f2d-a392-bf161c81bbfa-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
-+-
 Reporter:  mpachas  |Owner:  mpachas
 Type:  Bug  |   Status:  assigned
Component:   |  Version:  4.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  date, template,  | Triage Stage:
  i18n   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mpachas):

 * owner:  nobody => mpachas
 * 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/0107018065ef9ea2-a846af9f-aa77-4579-80cb-b846bf43abda-00%40eu-central-1.amazonses.com.

Re: [Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
-+-
 Reporter:  mpachas  |Owner:  nobody
 Type:  Bug  |   Status:  new
Component:   |  Version:  4.0
  Internationalization   |
 Severity:  Normal   |   Resolution:
 Keywords:  date, template,  | Triage Stage:
  i18n   |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  1|UI/UX:  0
-+-
Changes (by mpachas):

 * Attachment "patch.patch" added.

 patch file for formats.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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/0107018065e67ab9-e70195d7-0db1-41e2-9b13-231b9f1eea11-00%40eu-central-1.amazonses.com.

[Django] #33661: Fix Catalan formats.py to use alt.month

2022-04-26 Thread Django 
#33661: Fix Catalan formats.py to use alt.month
-+-
   Reporter:  mpachas|  Owner:  nobody
   Type:  Bug| Status:  new
  Component: |Version:  4.0
  Internationalization   |   Keywords:  date, template,
   Severity:  Normal |  i18n
   Triage Stage: |  Has patch:  1
  Unreviewed |
Needs documentation:  0  |Needs tests:  0
Patch needs improvement:  0  |  Easy pickings:  1
  UI/UX:  0  |
-+-
 DATE_FORMAT, DATETIME_FORMAT and MONTH_DAY_FORMAT strings in Catalan
 language are wrong because it uses always the preposition "de" between the
 day number and the month name but it is wrong when the month name starts
 with vowel like abril (April), agost (August) or octubre (October). In
 that case it should be d'abril, d'agost or d'octubre.

 I think that alt.month Month translations were created to help in this
 kind of situations (https://github.com/django/django/commit/2478f8588e) so
 this issue can be solved by a combination of a Catalan formats.py patch
 (django/conf/locale/ca/formats.py) and changing that translations (via
 Transifex).

 Actual:
 DATE_FORMAT = r"j \d\e F \d\e Y"

 msgid "January"
 msgstr "enero"

 msgid "April"
 msgstr "abril"

 {item.date | date} output -> 25 de enero de 2007
 {item.date | date} output -> 4 de abril de 2014---> THIS IS WRONG

 Proposal:

 DATE_FORMAT = r"j E \d\e Y" # E placeholder: alt. month translations for
 special cases.

 msgctxt "alt. month"
 msgid "January"
 msgstr "de enero"

 msgctxt "alt. month"
 msgid "April"
 msgstr "d'abril"

 {item.date | date} output -> 25 de enero de 2007
 {item.date | date} output -> 4 d'abril de 2014

 I'm trying to reach Catalan Transifex Team to add those strings, I think
 .po/.mo files won't follow the usual pull request way, but they must be
 changed before this file gets patched.

 Alternative month representation is available since this
 https://code.djangoproject.com/ticket/12309#no1

-- 
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/0107018065e56842-b72f5a5f-77ed-4460-8621-4f44c3e60a3b-00%40eu-central-1.amazonses.com.

Re: [Django] #21183: Filter block on the right covers information in admin

2022-04-26 Thread Django 
#21183: Filter block on the right covers information in admin
-+-
 Reporter:  Vlada Macek  |Owner:  (none)
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:  wontfix
 Keywords:  admin, filter,   | Triage Stage:
  collapse   |  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
 * needs_better_patch:  1 => 0
 * has_patch:  1 => 0
 * ui_ux:  1 => 0
 * resolution:   => wontfix
 * stage:  Accepted => Unreviewed


Comment:

 Closing as "wontfix". #27471 has been implemented and we don't need both
 options.

 Marcelo, thanks for the reminder.

-- 
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/0107018065893f72-90d21d89-86c0-4b9c-a02d-0eee221e13ca-00%40eu-central-1.amazonses.com.

Re: [Django] #21183: Filter block on the right covers information in admin

2022-04-26 Thread Django 
#21183: Filter block on the right covers information in admin
-+-
 Reporter:  Vlada Macek  |Owner:  (none)
 Type:  New feature  |   Status:  new
Component:  contrib.admin|  Version:  dev
 Severity:  Normal   |   Resolution:
 Keywords:  admin, filter,   | Triage Stage:  Accepted
  collapse   |
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  1
Easy pickings:  0|UI/UX:  1
-+-

Comment (by Marcelo Galigniana):

 Should this ticket be closed due ticket
 https://code.djangoproject.com/ticket/27471 was merged?

 I'm asking because of the
 [https://code.djangoproject.com/ticket/27471#comment:5 Mariusz Felisiak's
 comment]

-- 
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/010701806583f937-b8297885-05b3-45f0-9eba-63581ace32ee-00%40eu-central-1.amazonses.com.

Re: [Django] #27471: Make admin's list_filter choices collapsable

2022-04-26 Thread Django 
#27471: Make admin's list_filter choices collapsable
-+-
 Reporter:  Greg McCoy   |Owner:  Marcelo
 |  Galigniana
 Type:  New feature  |   Status:  closed
Component:  contrib.admin|  Version:  1.10
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  filter admin | Triage Stage:  Ready for
  collaspe   |  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:"27aa7035f57f0db30b6632e4274e18b430906799" 27aa7035]:
 {{{
 #!CommitTicketReference repository=""
 revision="27aa7035f57f0db30b6632e4274e18b430906799"
 Fixed #27471 -- Made admin's filter choices collapsable.
 }}}

-- 
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/01070180652cb48a-330a0783-a2c8-4a6a-86bc-9d840f38d057-00%40eu-central-1.amazonses.com.

Re: [Django] #33647: bulk_update silently truncating values for size limited fields

2022-04-26 Thread Django 
#33647: bulk_update silently truncating values for size limited fields
-+-
 Reporter:  jerch|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (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 jerch):

 Hey Carlton,

 thanks for the headsup. I didnt meant to sound like a drama queen, sorry
 if it came that way. Also I am not eager to push my ideas through at any
 price, since I could be totally on the wrong track, simply for reasons
 I've overlooked. So it is more about getting feedback at all, whether
 things go into the right direction or not.

 What I've learned from >20ys OSS contributions - giving ppl early feedback
 helps to keep them engaged, and lowers the risk of time consuming dead end
 implementations (time on both ends, the implementer and the
 reviewers/maintainers), esp. when the bigger picture needs to be addressed
 (API changes, bigger codebase changes involved at several places). I know
 that django is a very big codebase with lots of legacy, which imho makes
 it even harder for someone from outside to get involved. This for sure is
 a balancing act to maintain. Ofc slow pace is not a bad thing - in fact I
 like django for not buying every shiny new idea in town, as it gives very
 solid development experience (using django myself since version 0.8).
 At this point I wonder if the separated issue tracker in trac vs. repo in
 github might be part of a communication/transfer issue? (At least for me
 as maintainer of several projects github/gitlab made conceptual
 discussions and overall communications alot easier than back in
 SVN/mailing list times...)

 I hope I did not derail this issue too much. :)

-- 
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/01070180651c2fa4-0626f7b0-e7bb-45d2-8c8f-71b76d1f31b9-00%40eu-central-1.amazonses.com.

Re: [Django] #29799: Allow registration and unregistration of lookups per field instances.

2022-04-26 Thread Django 
#29799: Allow registration and unregistration of lookups per field instances.
-+-
 Reporter:  Simon Charette   |Owner:  Can
 |  Sarıgöl
 Type:  New feature  |   Status:  assigned
Component:  Database layer   |  Version:  dev
  (models, ORM)  |
 Severity:  Normal   |   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 Himanshu Balasamanta):

 * cc: Himanshu Balasamanta (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/0107018064f8a8dd-1228abec-56d0-4c32-89ab-e566541662a6-00%40eu-central-1.amazonses.com.

Re: [Django] #33543: Depracate passing False to OrderBy's nulls_first and nulls_last.

2022-04-26 Thread Django 
#33543: Depracate passing False to OrderBy's nulls_first and nulls_last.
-+-
 Reporter:  Gordon Wrigley   |Owner:
 Type:   |  AllenJonathan
  Cleanup/optimization   |   Status:  assigned
Component:  Database layer   |  Version:  3.2
  (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 AllenJonathan):

 * owner:  nobody => AllenJonathan
 * 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/0107018064d2c69b-5feb17de-944f-4a07-95dc-7093c19f1e5b-00%40eu-central-1.amazonses.com.

Re: [Django] #33658: Document the "blank" argument of forms.ModelChoiceField.

2022-04-26 Thread Django 
#33658: Document the "blank" argument of forms.ModelChoiceField.
-+-
 Reporter:  Carsten Fuchs|Owner:  Alokik
 Type:   |  Roy
  Cleanup/optimization   |   Status:  assigned
Component:  Documentation|  Version:  4.0
 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
-+-

Comment (by Carsten Fuchs):

 Thanks Alokik Roy for anticipating and taking 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/01070180649df6ee-97a5162f-e5b1-463a-bcff-94298c1ad372-00%40eu-central-1.amazonses.com.

Re: [Django] #33656: RangeWidget crashes for RangeFields for lists/tuples in default.

2022-04-26 Thread Django 
#33656: RangeWidget crashes for RangeFields for lists/tuples in default.
-+-
 Reporter:  Li Yun   |Owner:  Li Yun
 Type:  Bug  |   Status:  closed
Component:  contrib.postgres |  Version:  3.2
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
  MultiWidget,RangeWidget,psycopg2   |  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:"37602e49484a88867f40e9498f86c49c2d1c5d7c" 37602e49]:
 {{{
 #!CommitTicketReference repository=""
 revision="37602e49484a88867f40e9498f86c49c2d1c5d7c"
 Fixed #33656 -- Fixed MultiWidget crash when compressed value is a tuple.
 }}}

-- 
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/01070180649d1acc-e35cf000-f2a8-4776-bee1-547f42cb3521-00%40eu-central-1.amazonses.com.

Re: [Django] #33647: bulk_update silently truncating values for size limited fields

2022-04-26 Thread Django 
#33647: bulk_update silently truncating values for size limited fields
-+-
 Reporter:  jerch|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Database layer   |  Version:  4.0
  (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 Carlton Gibson):

 [https://groups.google.com/g/django-
 developers/c/jIGj1KKuaDM/m/4EiKPV5XAgAJ Link to the mailing list thread]

 Hi Jörg — thanks for the input here. Sorry you're feeling frustrated.

 > Could it be that no one is actually interested in a revamped bulk_update
 implementation in django? Or is django development known to have a very
 slow pace / being in maintenance mode mostly?

 So there's three points there:

 * I suspect it's not **lots** of people who are directly vested, but there
 are a number of regular contributors to the ORM (Simon included) and I'd
 imagine this is a topic of interest, but, as you've already pointed out in
 your mailing list post, there are several tradeoffs to consider, and it'll
 need some thought. Folks have limit bandwidth: that doesn't entail no
 interest. I hope that's clear.
 * Django **does** have a slow pace. That's OK. After 16+ years, that's
 proven to be one of its strengths. It's a big project, with a lot of
 surface area, and (again) folks have limited bandwidth. It's one reason
 why third-party packages, such as the one you've done, are a good way to
 go, as they allow a faster pace, and a sandbox to work on issues.
 * Despite the slow pace, Django is in anything but maintenance mode: you
 need only look at the release notes over the last few major releases to
 see that new features are constantly being worked on and delivered. If you
 zoom-out from any particular issue, I contest, the development pace is
 actually quite rapid for a project of Django's size and maturity (despite
 being "slow" on the surface.)

 We're currently heads-down working towards the feature freeze for Django
 4.1 — there is no chance (really) of this getting addressed for that. That
 leaves a realistic opportunity to discuss it for Django 4.2, and if you're
 keen, and the technical questions can be resolved, there's no reason it
 couldn't get in for that. If we miss that, then the next one... — Again
 zooming out, it soon fades that it took x-cycles to get any particular
 feature work completed.

 Looking at the timestamps on the discussion here, not much time has passed
 between comments. I'd suggest a little patience, and working on the third-
 party implementation to resolve any outstanding issues in that time. If
 it's **ready™** following up on the mailing list thread may be appropriate
 to let folks know they can give it a try.

 I hope that all makes sense, and helps anchor expectations.
 [https://www.commitstrip.com/en/2014/05/07/the-truth-behind-open-source-
 apps/ There's a nice comic here which I always try to keep in mind].

 Kind Regards,

 Carlton

-- 
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/01070180649706a1-bab49e31-7fc3-40cd-bf5d-6d4f0304c409-00%40eu-central-1.amazonses.com.