On Tue, Feb 18, 2020 at 3:31 AM Ram Rachum wrote:
> Hi guys,
>
> Recently I was working with Django's CSRF protection, customizing it to my
> needs, and discussing with co-workers exactly how it works and how it has
> protection against the BREACH attack being used to retrieve the CSRF key.
>
ht
On Fri, Jan 24, 2020 at 2:17 AM Matemática A3K
wrote:
>
>
> On Fri, Jan 10, 2020 at 8:38 PM Matemática A3K
> wrote:
>
>> Trying to recap all the discussion done in the mailing list, Trac and
>> Github:
>>
>> The problem that was originally reported in #3
On Fri, Jan 10, 2020 at 8:38 PM Matemática A3K
wrote:
> Trying to recap all the discussion done in the mailing list, Trac and
> Github:
>
> The problem that was originally reported in #30439 was about mixed plural
> forms in catalogs bundled with Django, which led to brok
://github.com/django/django/pull/12280#issuecomment-571483273).
Does anyone see any rationale, design or implementation problem in the fix?
Any comment is welcomed :)
On Mon, Jan 6, 2020 at 4:17 PM Matemática A3K
wrote:
>
>
> On Fri, Dec 13, 2019 at 1:04 AM Matemática A3K
> wrote:
>
>
On Fri, Dec 13, 2019 at 1:04 AM Matemática A3K
wrote:
>
>
> On Fri, Dec 6, 2019 at 2:14 AM Matemática A3K
> wrote:
>
>>
>>
>> On Thu, Dec 5, 2019 at 4:23 PM Maciek Olko wrote:
>>
>>> Hi,
>>> I am wondering if Django shouldn't use
On Sat, Dec 21, 2019 at 12:51 PM Adam Johnson wrote:
> I just saw Google is expanding their Patch Rewards program for open source
> security improvements:
> https://security.googleblog.com/2019/12/announcing-updates-to-our-patch-rewards.html
>
> They are offering two tiers of rewards - $5,000 or
On Sun, Dec 15, 2019 at 2:54 AM James Bennett wrote:
> Since this discussion seems to be exclusively about how to use Django,
> please take it to the django-users mailing list; the django-developers list
> is not an appropriate place for this topic.
>
I agree :)
> --
> You received this messag
On Sat, Dec 14, 2019 at 9:25 AM Tom Forbes wrote:
> IMO this is outside of the scope of this mailing list. There is no simple
> answer to this problem, nor a general solution. There is however a wealth
> of information on this topic that you can find with a few Google searches.
>
I agree
> If
On Fri, Dec 6, 2019 at 2:14 AM Matemática A3K
wrote:
>
>
> On Thu, Dec 5, 2019 at 4:23 PM Maciek Olko wrote:
>
>> Hi,
>> I am wondering if Django shouldn't use Unicode Plural Rules as standard
>> and promote it for third-party apps. Even if sometimes numbe
On Fri, Dec 6, 2019 at 2:14 AM Matemática A3K
wrote:
>
>
> On Thu, Dec 5, 2019 at 4:23 PM Maciek Olko wrote:
>
>> Hi,
>> I am wondering if Django shouldn't use Unicode Plural Rules as standard
>> and promote it for third-party apps. Even if sometimes numbe
x documentation that
> describes their statement about plural rules and Unicode standard:
> https://docs.transifex.com/localization-tips-workflows/plurals-and-genders#how-pluralized-strings-are-handled-by-transifex
> .
>
> Regards,
> Maciej
>
> czw., 5 gru 2019 o 08:00 Mat
o be inline with the main form.
On Thu, Dec 5, 2019 at 12:10 AM Matemática A3K
wrote:
>
>
> On Wed, Dec 4, 2019 at 2:25 AM Claude Paroz wrote:
>
>> Le mercredi 4 décembre 2019 03:41:51 UTC+1, Matemática A3K a écrit :
>>>
>>> (...)
>>>
>>> But,
On Wed, Dec 4, 2019 at 2:25 AM Claude Paroz wrote:
> Le mercredi 4 décembre 2019 03:41:51 UTC+1, Matemática A3K a écrit :
>>
>> (...)
>>
>> But, then I realized that there is major caveat on this approach, and
>> that is that updates on the plural equation won&#x
ing it "on
merge", because only the default language will be merged "on start", you
will see the warnings later when it is activated.
Any thoughts?
PS: The "makemessages --comply-plurals" needs to assume that the new pfs
were handled by the previous last one to produce t
On Wed, Nov 27, 2019 at 1:40 AM Matemática A3K
wrote:
>
>
> On Tue, Nov 26, 2019 at 12:51 PM Shai Berger wrote:
>
>> On Tue, 26 Nov 2019 12:28:45 +0100
>> Maciek Olko wrote:
>>
>> > It looks like Transifex uses [1] Unicode Language Plural Rules [2].
>&
On Tue, Nov 26, 2019 at 2:18 AM אורי wrote:
>
>
> 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
On Tue, Nov 26, 2019 at 12:51 PM Shai Berger wrote:
> On Tue, 26 Nov 2019 12:28:45 +0100
> Maciek Olko wrote:
>
> > It looks like Transifex uses [1] Unicode Language Plural Rules [2].
> > If they are incorrect for Hebrew, maybe they should be fixed on
> > Unicode side?
> >
>
> Just for the recor
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:
>
>> ,אורי
>> F
,אורי
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 b
lain" Django will have to deal with serialization (
https://docs.djangoproject.com/en/2.2/topics/serialization/) and not much
besides defaulting to DjangoJsonEncoder for the context in CVB and for
functional views (like https://github.com/jsocol/django-jsonview) can be
done - at least that c
On Wed, Nov 20, 2019 at 11:52 PM James Bennett
wrote:
> On Wed, Nov 20, 2019 at 3:44 PM Curtis Maloney
> wrote:
>
>>
>> Yeah, I expected DRF had this "solved" already. From my own
>> experimentation, mapping `cgi.parse_header` over the the "Accept" header
>> value, split by comma, gets a usable
On Tue, Nov 19, 2019 at 9:20 PM Matemática A3K
wrote:
>
>
> On Tue, Nov 19, 2019 at 1:29 PM Jure Erznožnik
> wrote:
>
>> Sorry for barging in like this, but this is actually a problem I have
>> been dealing with quite a bit lately, so:
>>
>> In my work I
to be accounted for too. This may not be
> a problem for core Django as it doesn't have stages.
>
> Again, sorry, but still hoping this helped in some way.
>
LP,
> Jure
>
>
> On 19/11/2019 01:06, Matemática A3K wrote:
>
>
> I agree with Adam that it should be depr
I agree with Adam that it should be deprecated with no replacement.
The content negotiation is something that should be in but not as a
replacement of it, as a general improvement.
I think there shouldn't be a replacement because "is_ajax" asks whether it
came from a ""regular"" browser instead o
> pull-request somewhere to allow line wise comments and suggestions.
>
> @Matematica, good points, I added some comments inline.
>
> On Fri, Nov 8, 2019, 09:42 Matemática A3K
> wrote:
>
>>
>>
>> On Thu, Nov 7, 2019 at 11:31 AM Johannes Hoppe
>> wrote:
10:16 +0900, Tom Forbes , wrote:
>>>>
>>>> Maybe this discussion is slightly off topic, and at the risk of
>>>> derailing things I’d like to put out my view on this.
>>>>
>>>> There is more to it than just “using Github’s computing power”, jus
On Wed, Nov 6, 2019 at 3:51 AM Carlton Gibson
wrote:
> Hey Shai.
>
> On Wednesday, 6 November 2019 08:43:21 UTC+1, Shai Berger wrote:
>>
>>
>> Is there benefit enough in GitHub Actions (over Jenkins) to justify a
>> move from an open-source based solution?
>>
>
> I don't think we have to move awa
27 matches
Mail list logo
