Re: python-memcached is deprecated, but still used in core Django

[Jure Erznožnik]

I am currently attempting to involve myself more into Django 
development. Have little to no idea how.


This seems to me like an easy pickings and I would be willing to port 
existing code to the new package, if that's okay with the core team.


My expected approach:

1. verify claims

2. take the ticket

3. read up on the contribution guidelines

4. start with master, replace all memcached references with the new 
library, possibly with minimal API impact


5. backport to 2.x, 1.x?

If this sounds remotely what's supposed to be done, let me know, I will 
start working on it.


LP,
Jure

P.S. My planned involvement should ultimately reach around 200 hours of 
yearly investment, should I prove to be useful. All pending verification 
and validation, of course. I don't even know if that's a measurable 
quantity, but right now these are my mid-term plans.




On 25/11/2019 00:45, Adrian Turjak wrote:

A while ago now I opened a ticket that we need to deprecate the
python-memcached backend in Django, and ideally make a new one which
uses Pinterest's pymemcache instead (which is now the most commonly used
one).

This is the ticket:
https://code.djangoproject.com/ticket/29887

But it seems there hasn't been any work on it. Someone assigned
themselves, but nothing beyond that has happened.

At this stage we really need to remove the docs that recommend
python-memcached, and the backend associated with it, and say officially
that only pylibmc is a valid and safe option from the core backends
using Memcached.

Considering how important Memcached is to a lot of projects, this ought
to be a high priority item, with some urgency given that Django core is
sporting support for a now very deprecated and outdated library (Last
released: Dec 16, 2017), with no future, and a clear successor in
pymemcache.

I'm sadly not in a position where I can contribute this myself, but
would be happy to test/review. Are there any willing contributors for
this? Or some people from the Django core team which will tackle this?

Cheers,
Adrian Turjak






--
You received this message because you are subscribed to the Google Groups "Django 
developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/4671b78d-722d-d343-1d1c-7df9826322ec%40gmail.com.

Re: python-memcached is deprecated, but still used in core Django

[Johannes Hoppe]

Do we actually need to deprecate the current backend and create a new one? 
Can't we just rewrite the current backend? Technically changing a 
dependency doesn't require deprecation, does it? It's also a very simply 
update process.

On Monday, November 25, 2019 at 6:46:05 AM UTC+7, Adrian Turjak wrote:
>
> A while ago now I opened a ticket that we need to deprecate the 
> python-memcached backend in Django, and ideally make a new one which 
> uses Pinterest's pymemcache instead (which is now the most commonly used 
> one). 
>
> This is the ticket: 
> https://code.djangoproject.com/ticket/29887 
>
> But it seems there hasn't been any work on it. Someone assigned 
> themselves, but nothing beyond that has happened. 
>
> At this stage we really need to remove the docs that recommend 
> python-memcached, and the backend associated with it, and say officially 
> that only pylibmc is a valid and safe option from the core backends 
> using Memcached. 
>
> Considering how important Memcached is to a lot of projects, this ought 
> to be a high priority item, with some urgency given that Django core is 
> sporting support for a now very deprecated and outdated library (Last 
> released: Dec 16, 2017), with no future, and a clear successor in 
> pymemcache. 
>
> I'm sadly not in a position where I can contribute this myself, but 
> would be happy to test/review. Are there any willing contributors for 
> this? Or some people from the Django core team which will tackle this? 
>
> Cheers, 
> Adrian Turjak 
>
>
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/a5eaf9cc-21aa-4cb8-9d61-9fc8e76e0733%40googlegroups.com.

Re: Fellow Reports - November 2019

[Mariusz Felisiak]

Week ending November 17, 2019.

Released Django 3.0rc1.

*Triaged:*
https://code.djangoproject.com/ticket/30988 - Deprecate the barely 
documented InvalidQuery exception. (accepted)
https://code.djangoproject.com/ticket/30991 - Optional removal of 
transaction and extra get() in get_or_create(). (wontfix)
https://code.djangoproject.com/ticket/30994 - Add support for AsGeoJSON on 
Oracle. (accepted)
https://code.djangoproject.com/ticket/30997 - Deprecate 
HttpRequest.is_ajax. (accepted)
https://code.djangoproject.com/ticket/30989 - Remove not implemented `B` 
time format (Swatch Internet Time). (accepted)
https://code.djangoproject.com/ticket/31000 - Match @import rule and url() 
statement exclude of the css comment during the collectstatic. (duplicate)
https://code.djangoproject.com/ticket/30999 - Typo in custom template tags 
docs. (accepted)
https://code.djangoproject.com/ticket/29097 - Migrations using MySQL fail 
for constraints using composite indexes. (fixed)
https://code.djangoproject.com/ticket/30969 - Add support for query 
expressions as default values. (duplicate)
https://code.djangoproject.com/ticket/31001 - Test failures on SQLite 3.30. 
(duplicate)
https://code.djangoproject.com/ticket/31006 - Document how to escape a 
date/time format character for the |date and |time filters. (accepted)
https://code.djangoproject.com/ticket/31004 - Using FilteredRelation on M2M 
relationship duplicates result rows. (invalid)
https://code.djangoproject.com/ticket/31009 - Test database named just 
"test_". (wontfix)
https://code.djangoproject.com/ticket/31011 - A new template tag for 
ternary operations? (duplicate)
https://code.djangoproject.com/ticket/31014 - Add FromWKB and FromWKT GIS 
functions. (accepted)
https://code.djangoproject.com/ticket/31017 - Search on online Django 
documentation is not working for 2.2 and 3. (invalid)
https://code.djangoproject.com/ticket/31016 - Documentation: MySQL notes: 
utf8. (duplicate)
https://code.djangoproject.com/ticket/31019 - The database backend specific 
checks could be bypassed when using multiple databases. (invalid)
https://code.djangoproject.com/ticket/31022 - Setup GitHub tracking links 
(invalid)
https://code.djangoproject.com/ticket/31021 - Migration doesn't work on 
multi database environment. (worksforme)
https://code.djangoproject.com/ticket/31023 - __second lookup doesn't work 
on Django 2.2.7. (needsinfo)
https://code.djangoproject.com/ticket/31025 - 
HTMLTranslator.highlightlinenothreshold will be removed in Sphinx 3.0. 
(accepted)
https://code.djangoproject.com/ticket/29145 - Allow CIText values to be 
compared as the database would compare them (case-insensitively) (wontfix)

*Reviewed/committed:*
https://github.com/django/django/pull/12074 - Replaced QueryWrapper single 
usage with RawSQL.
https://github.com/django/django/pull/12076 - Fixed #30990 -- Fixed example 
output in 'z' date format docs.
https://github.com/django/django/pull/12092 - Fixed #30989 -- Removed 
unimplemented B time format.
https://github.com/django/django/pull/12073 - Fixed #30988 -- Deprecated 
the InvalidQuery exception class.
https://github.com/django/django/pull/12080 - Fixed #30994 -- Added Oracle 
support for AsGeoJSON GIS function.
https://github.com/django/django/pull/12071 - Expanded API stability docs 
to include our policy of continual improvement.
https://github.com/django/django/pull/11926 - Fixed #30987 -- Added 
models.PositiveBigIntegerField.
https://github.com/django/django/pull/12108 - Fixed #30999 -- Fixed typo in 
docs/howto/custom-template-tags.txt.
https://github.com/django/django/pull/7364 - Fixed #27272 -- Added an 
on_delete RESTRICT handler to allow cascading deletions while protecting 
direct ones.
https://github.com/django/django/pull/12072 - Fixed #30981 -- Fixed admin 
changelist crash when using F() or OrderBy() expressions in 
admin_order_field.
https://github.com/django/django/pull/12096 - Fixed #27164 -- Fixed an 
example of using routers in multiple databases docs.
https://github.com/django/djangoproject.com/pull/960 - Updated 
robots.docs.txt for Django 3.0.
https://github.com/django/django/pull/12062 - Fixed #25388 -- Added an 
option to allow disabling of migrations during test database creation.
https://github.com/django/django/pull/12111 - Fixed #30625 -- Doc'd 
cache.get()/delete() behavior change in Django 2.2.
https://github.com/django/django/pull/12067 - Fixed #30484 -- Added 
conditional expressions support to CheckConstraint.
https://github.com/django/django/pull/12113 - Fixed #30413 -- Fixed test 
database signature on SQLite when test database name is provided.
https://github.com/django/django/pull/12120 - Fixed #31012 -- Reverted 
"Fixed #29056 -- Fixed HTML5 validation of required SelectDateWidget."
https://github.com/django/django/pull/12123 - Fixed #8467 -- Prevented 
crash when adding existent m2m relation with an invalid type.
https://github.com/django/django/pull/12122 - Fixed #9762 -- Made 
DateFormat.r() locale-independ

Django front end usage

[DEEPAK NAILWAL]

Hi All,

I am working on a project and my site is up and running.

Now i want to make my site much presentable as currently it just having 
login, password and forgot password link.

Can you please help me how i can achieve that in short span of time ?


-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/fe5227be-bf1a-4b0d-9f2b-29e782eb8ce4%40googlegroups.com.

Re: Django front end usage

[Adam Johnson]

Hi!

I think you've found the wrong mailing list for this post. This mailing
list is for the development of Django itself, not for support using Django.
This means the discussions of bugs and features in Django itself, rather
than in your code using it. People on this list are unlikely to answer your
support query with their limited time and energy. Read more on the mailing
lists at https://www.djangoproject.com/community/

For support, please use the NEW Django forum at
https://forum.djangoproject.com , django-users mailing list, or IRC #django
on Freenode, or a site like Stack Overflow. There are people out there
willing to help on those channels, but they might not respond if you don't
ask your question well. Stack Overflow's question guide can help you frame
it well: https://stackoverflow.com/help/how-to-ask .

Also if you haven't read it, please take a look at Django's Code of
Conduct: https://www.djangoproject.com/conduct/ . These are our "ground
rules" for working well as a community, and will help you get the most out
of Django and our fantastic community.

Thanks for your understanding,

Adam

On Mon, 25 Nov 2019 at 12:53, DEEPAK NAILWAL 
wrote:

> Hi All,
>
> I am working on a project and my site is up and running.
>
> Now i want to make my site much presentable as currently it just having
> login, password and forgot password link.
>
> Can you please help me how i can achieve that in short span of time ?
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/fe5227be-bf1a-4b0d-9f2b-29e782eb8ce4%40googlegroups.com
> 
> .
>


-- 
Adam

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAMyDDM2%2BmD0my-psKbXiu32t%3D4YiYWocE4Ys7Dz1imj_4dafDw%40mail.gmail.com.

Fellow Reports -- November 2019

[Carlton Gibson]

Hi all. 


Calendar Week 45 -- ending 10 November.


Triaged:

https://code.djangoproject.com/ticket/30964 -- macOS SQLite test failure. 
(needsinfo)
https://code.djangoproject.com/ticket/30963 -- Admin list_editable not 
suitable for multi-user environment. (Someday/Maybe)
https://code.djangoproject.com/ticket/30962 -- GitHub Actions (needsinfo)
https://code.djangoproject.com/ticket/30955 -- Document the different 
behavior of migration historical models while they have abstract base 
classes. (Accepted)
https://code.djangoproject.com/ticket/30961 -- Use proper whitespace in 
CREATE INDEX statements (Accepted)
https://code.djangoproject.com/ticket/30941 -- hasattr(request, 
'_cached_user') check no longer works (Accepted)
https://code.djangoproject.com/ticket/30940 -- Documentation on formsets 
lists incomplete code to detect errors in clean() (Invalid)


Reviewed:

https://github.com/django/django/pull/12046 -- Updated Python license for 
2019.
https://github.com/django/django/pull/12038 -- Clarified that license is 
BSD 3-Clause in package metadata.
https://github.com/django/django/pull/12042 -- Refs #29983 -- Added support 
for using pathlib.Path in all settings.
https://github.com/django/django/pull/12044 -- Ref #30962 -- Added GitHub 
action for static code linters
https://github.com/django/django/pull/12032 -- Adjusted expected exception 
message for Windows.
https://github.com/django/django/pull/12034 -- Harmonized Windows checks in 
tests to a single style.
https://github.com/django/django/pull/12021 -- Refs #29983 -- Added tests 
for FileBasedCache pathlib support.
https://github.com/django/django/pull/12022 -- Refs #29983 -- Added 
pathlib.Path support to the file email backend.
https://github.com/django/django/pull/12024 -- Refs #29983 -- Added test 
for FILE_UPLOAD_TEMP_DIR pathlib support.
https://github.com/django/django/pull/12023 -- Added a link to the file 
email backend from EMAIL_FILE_PATH setting.
https://code.djangoproject.com/ticket/12026 -- Refs #29983 -- Added test 
for FIXTURES_DIRS pathlib support.
https://github.com/django/django/pull/12005 -- Fixed #29983 -- Replaced 
os.path with pathlib.Path.
https://github.com/django/django/pull/12013 -- Fixed #30948 -- Changed 
packaging to use setuptools declarative config in setup.cfg.


Authored:

https://github.com/django/django/pull/12029 -- Doc'd archiving 
historical branches as git tags.




Calendar Week 46 -- ending 17 November.



Preparation for Django 3.0 and other releases. 

Triaged:

https://code.djangoproject.com/ticket/30975 -- Replace get_select_option 
with native select_by_value (Accepted)
https://code.djangoproject.com/ticket/30974 -- Selenium asserts should be 
wait statements (Accepted)
https://code.djangoproject.com/ticket/30973 -- Selenium wait_page_loaded 
waits for wrong page (race condition) (Accepted)


Reviewed:

https://github.com/django/djangosnippets.org/issues/74 -- Increase in spam 
in the past few weeks #74
https://github.com/django/django/pull/12030 -- Fixed #29916 -- Added 
lower_inc, lower_inf, upper_inc, and upper_inf lookups for RangeFields.
https://github.com/django/django/pull/11883 -- Fixed #30759 -- Made 
cache.delete() return whether it succeeded.
https://github.com/django/django/pull/12063 -- Fixed random 
auth_tests.test_tokens.TokenGeneratorTest.test_10265 failures.
https://github.com/django/django/pull/12059 -- Refs #29926 -- Doc'd 
Python 3.8 compatibility in Django 2.2.x.
https://github.com/django/django/pull/12058 -- [2.2.x] Added Python 3.8 
compatibility in Django 2.2.x.
https://github.com/django/django/pull/12057 -- Fixed #30941 -- Reverted 
"Simplified AuthenticationMiddleware a bit."




Calendar Week 47 -- ending 24 November.



Preparation for Django 3.0 and other releases.

Triaged:

https://code.djangoproject.com/ticket/31020 -- Disabled ModelChoiceField 
produces an error in to_python (Duplicate of 30014)
https://code.djangoproject.com/ticket/30998 -- Make it easier to use the 
model instance in ChoiceWidget.create_option() (Accepted)
https://code.djangoproject.com/ticket/31010 -- Add subdomains of localhost 
to ALLOWED_HOSTS in DEBUG mode (needsinfo)
https://code.djangoproject.com/ticket/31012 -- Required SelectDateWidget 
renders invalid HTML (Accepted (Release Blocker))
https://code.djangoproject.com/ticket/31013 -- Remove jQuery dependency 
from SelectBox.js (Accepted)
https://code.djangoproject.com/ticket/31008 -- Incorrect rendering of some 
code blocks in documentation (Accepted)
https://code.djangoproject.com/ticket/30993 -- Class based views and 
syndications are similar, but not exactly the same (needsinfo)
https://code.djangoproject.com/ticket/30964 -- macOS/SQLite test failure 
(needsinfo)
https://code.djangoproject.com/ticket/30995 -- Feature/docs: how should url 
converters decline to match for a named route? (Accepted)


Reviewed:

https://github.com/django/django/pull/12112 -- Simplified 
TemplateDetailView with pathlib.Path.read_text().
https://github.com/djang

Re: python-memcached is deprecated, but still used in core Django

[Adrian Turjak]

That's a tough question. It depends on when and how we do it. A new
backend can potentially be backported to 2.2 (the current safe LTS), but
we can't really update the existing one if people are using it and
expect it to work. Django doesn't actually have any deps for these
libraries, so people have to install them as part of their app deployment.

A new backend, even if mostly a copy of the old one, is the safer
approach and then people need to actively switch to it, and be aware of
it. We then deprecate the old one, and we can backport to 2.2 the new
safe one, and remove the old one in never versions.

On 25/11/19 11:05 pm, Johannes Hoppe wrote:
> Do we actually need to deprecate the current backend and create a new
> one? Can't we just rewrite the current backend? Technically changing a
> dependency doesn't require deprecation, does it? It's also a very
> simply update process.
>
> On Monday, November 25, 2019 at 6:46:05 AM UTC+7, Adrian Turjak wrote:
>
> A while ago now I opened a ticket that we need to deprecate the
> python-memcached backend in Django, and ideally make a new one which
> uses Pinterest's pymemcache instead (which is now the most
> commonly used
> one).
>
> This is the ticket:
> https://code.djangoproject.com/ticket/29887
> 
>
> But it seems there hasn't been any work on it. Someone assigned
> themselves, but nothing beyond that has happened.
>
> At this stage we really need to remove the docs that recommend
> python-memcached, and the backend associated with it, and say
> officially
> that only pylibmc is a valid and safe option from the core backends
> using Memcached.
>
> Considering how important Memcached is to a lot of projects, this
> ought
> to be a high priority item, with some urgency given that Django
> core is
> sporting support for a now very deprecated and outdated library (Last
> released: Dec 16, 2017), with no future, and a clear successor in
> pymemcache.
>
> I'm sadly not in a position where I can contribute this myself, but
> would be happy to test/review. Are there any willing contributors for
> this? Or some people from the Django core team which will tackle
> this?
>
> Cheers,
> Adrian Turjak
>
>
>
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to django-developers+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/a5eaf9cc-21aa-4cb8-9d61-9fc8e76e0733%40googlegroups.com
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/28b2116b-6592-acfc-5726-68764676639f%40catalyst.net.nz.

Re: ngettext_lazy and ngettext

[Matemática A3K]

‪On Mon, Nov 25, 2019 at 6:26 AM ‫אורי‬‎  wrote:‬

> Hi Matemática,
>
> I prefer to keep using Django 2.1 until there is a solution that doesn't
> require so much effort from me when upgrading. I currently don't think we
> need 4 strings (plural forms) in our project's .po files and anyway I don't
> want to change them manually, only if they are changed automatically when I
> upgrade Django. My websites are currently working properly (as far as I
> know) with Django 2.1 and I want to keep it this way.
>
> If a solution is made but applied to Django 3.0 or 3.1, I might decide to
> upgrade directly from 2.1 to 3.0 or 3.1, without using Django 2.2.
>
> אורי
> u...@speedy.net
>
>
אורי,

OK, have in mind that a change of the number of plurals for a language is
kind (if not) of an API change for i18n - now you have to feed a different
input - and should be handled as such. There is no way of modifying your
code on an upgrade by the software distribution (the package).

Did the script that I posted not do the job?



>
> On Mon, Nov 25, 2019 at 1:40 AM Matemática A3K 
> wrote:
>
>> ,אורי‎
>> Follow the instructions here if you want to change the plural form for
>> your django project "temporarily":
>> https://code.djangoproject.com/ticket/30439#comment:17
>>
>> Maintaining several catalogs unmerged can lead to inconsistencies also if
>> you don't keep track of all of them, which can lead to burdens also, i.e.
>> if you translate one string which is already contained in another po with a
>> different plural form, that may be used instead of yours.
>>
>> This is against - I believe, not sure, please someone correct me - the
>> design of gettext on which Django builds upon. Although all .pos have a
>> header with a plural formula, it is assumed that they will be the same for
>> a language, so when merging, only the first one is retained.
>>
>> Supporting multiple catalogs in order to support different plural forms
>> is plausible, it seems to be like an extension to gettext, but it may not
>> fix your problem entirely, because although you may retain the consistency
>> of your pos, some translations will break (Django's) because of the broken
>> formula.
>>
>> One thing is the break by a broken formula, another thing is changing
>> Django's one plural form policy.
>>
>> (JIC, for those interested in the subject and want to catch up - besides
>> reading the ticket -  a gettext catalog plural form contains 2 things: the
>> number of plurals of the language and an equation/formula that decides
>> which one to use for the case. Django uses one "general" gettext catalog
>> per language which is the result of merging several ""subcatalogs"",
>> ""local pos"")
>>
>> The broken formulas introduced can be fixed by a fix in the repo, and/or
>> by changing the syncing scripts with Transifex to do a msgmerge instead.
>> This won't update the plural forms from Django, they will need to be
>> manually updated on the repo - someone will have to check the updated
>> formula and see if it is alright, and it has to be someone knowledgeable
>> about it (I wouldn't be able to discern if the plural form of Slovakian is
>> good or not, besides an evidently broken one from what I learnt), so I
>> think this would rely on the django-i18n committee(?) (I guess this would
>> be more work for them).
>>
>> Another thing is the change of the number of plurals. This will not only
>> imply a change in the plural formula but a change in the entire catalog, as
>> new translations will be needed. This seems something not to be changed
>> unless a mistake was found. If this is changed for convenience, in order to
>> use gettext (and catalog merging), you should ensure that only your
>> catalogs are used. You can give convenience by making your translation
>> utility generate the remaining plurals accordingly so they can be merged
>> with others that contain all the forms.
>>
>> Here is a **shamefull, bad, ugly and dirty** script
>>  that
>> will add the remaining entries to your .po in order to be merged with
>> others that have the total of plurals. Just download it and run
>> "update-po-plurals your.po from=2 to=4 > your_new.po" and it will be
>> converted from two to four (although you will have to adjust manually the
>> header). This way, it will be "merge-able" in every software that uses
>> gettext with all the plurals (
>> https://code.djangoproject.com/ticket/30439#comment:24).
>>
>> The only fix that comes to my mind that will solve this is to give the
>> ability of taking out the locales out from of the django distribution tree
>> to django project tree. This is making a "collectlocale" command that will
>> collect and merge all the .pos distributed in django and put them on
>> settings.LOCALE_ROOT in the project tree. Once this exists, the Django
>> translation module will start using this as the base for merging. You can
>> edit them and VC them in your project. This way n

Re: python-memcached is deprecated, but still used in core Django

[Mariusz Felisiak]

TIcket #29887 doesn't qualify for a backport so if someone prepare a patch 
then we can include it in the Django 3.1. Also, I don't see a strong 
consensus for deprecating python-memcached support. It can found a new 
maintainer in the nearest future.

Best,
Mariusz

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/ce2804d3-8e41-4105-bcd3-0860e26b24e8%40googlegroups.com.

Re: ngettext_lazy and ngettext

[אורי]

On Tue, Nov 26, 2019 at 8:13 AM Matemática A3K 
wrote:

>
>
> ‪On Mon, Nov 25, 2019 at 6:26 AM ‫אורי‬‎  wrote:‬
>
>>
>> אורי,
>
> OK, have in mind that a change of the number of plurals for a language is
> kind (if not) of an API change for i18n - now you have to feed a different
> input - and should be handled as such. There is no way of modifying your
> code on an upgrade by the software distribution (the package).
>
> Did the script that I posted not do the job?
>

No offense, but I didn't try. As a Django user I don't expect Django to
send me to install and run third party scripts that will keep my sites
working when I upgrade Django. I also don't think there is need for 4
plural forms in my .po files. I would like to keep using 2 plural forms as
that makes more sense to me.

I decided to keep using Django 2.1.

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers  (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-developers+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CABD5YeH%3DwqNcWsu5_Lzab39qmcDPY%2BymGD2k-R1mbr%3DEiCvbnQ%40mail.gmail.com.