I see. Thank you very much!
Cheers,
Jessica
On Tuesday, April 10, 2018 at 5:59:20 PM UTC-4, Brenton Cleeland wrote:
>
> Hi Jessica (& team!),
>
> My immediate thought is that those rows are errors. They should be ignored
> and not included in any list added to Django :)
>
> On 11 April 2018 at 0
I agree with you, but at some point, we could combine solid annotated core
with a cut off for non annotated code? Otherwise, this will end up being a
loop.
On Wednesday, 11 April 2018 17:16:21 UTC+3, dmoisset wrote:
>
>
>
> On 11 April 2018 at 11:21, Andreas Galazis > wrote:
>
>> To me one appr
On 11 April 2018 at 11:21, Andreas Galazis wrote:
> To me one approach would be to put a cut off for any merged code /PR
> start inlining type hints/annotations for all new code. This seems to
> simple to be a solution but at the end of the day as code gets updated even
> bigger part of the codeb
To me one approach would be to put a cut off for any merged code /PR start
inlining type hints/annotations for all new code. This seems to simple to
be a solution but at the end of the day as code gets updated even
bigger part of the codebase will have type hints. The question is whether
parti
Right. I just use python manage.py…
I just checked python3 manage.py and it doesn’t work.
From: collinmander...@gmail.com [mailto:collinmander...@gmail.com] On Behalf Of
Collin Anderson
Sent: Wednesday, April 11, 2018 7:46 AM
To: django-developers@googlegroups.com
Subject: Re: Shouldn't manage.p
but python3 manage.py doesn't work on windows, right?
On Tue, Apr 10, 2018 at 10:17 PM, Josh Smeaton
wrote:
> As a datapoint, I've seen roughly 1 person per week in #django IRC
> confused about specific startup exceptions due to them using python 2
> rather than python 3 on Django >= 2.0. Unsur
