On Sat, 11 Nov 2017 07:34:05 +
Brett Cannon wrote:
>
> One problem with that is I don't want e.g. mypy to start spewing out
> warnings while checking my code.
It's rather trivial for mypy (or any other code analysis tool) to turn
warnings off when importing the code under analysis. And sinc
On 11 November 2017 at 17:34, Brett Cannon wrote:
> On Thu, Nov 9, 2017, 17:33 Nathaniel Smith, wrote:
>> Some more ideas to throw out there:
>>
>> - if an envvar CI=true is set, then by default make deprecation warnings
>> into errors. (This is an informal standard that lots of CI systems use.
>
On Fri, Nov 10, 2017 at 11:34 PM, Brett Cannon wrote:
> On Thu, Nov 9, 2017, 17:33 Nathaniel Smith, wrote:
>> - if an envvar CI=true is set, then by default make deprecation warnings
>> into errors. (This is an informal standard that lots of CI systems use.
>> Error instead of "once" because most
Ben, I have a small package which enables one to do:
with MapGetter(my_dictionary):
from my_dictionary import a, b, parameter3
If this interests you, contributions so it can get hardenned for
mainstram acceptance are welcome.
https://github.com/jsbueno/extradict
On 11 November 2017 at 04:26,
Oops, forgot to reply to the list.
On Nov 12, 2017 03:35, "Koos Zevenhoven" wrote:
On Nov 12, 2017 02:12, "Joao S. O. Bueno" wrote:
Ben, I have a small package which enables one to do:
with MapGetter(my_dictionary):
from my_dictionary import a, b, parameter3
If this interests you, contri
On Sat, Nov 11, 2017 at 3:29 PM, Nick Coghlan wrote:
> And given that one of the key benefits of static analysis is that it
> *doesn't* run the code, I'd be surprised if mypy could ever trigger a
> runtime warning in the code under tests :)
>
Actually there are a few cases where mypy *will* gene
On 11 November 2017 at 23:40, Koos Zevenhoven wrote:
> Oops, forgot to reply to the list.
>
>
> On Nov 12, 2017 03:35, "Koos Zevenhoven" wrote:
>
> On Nov 12, 2017 02:12, "Joao S. O. Bueno" wrote:
>
> Ben, I have a small package which enables one to do:
>
> with MapGetter(my_dictionary):
> f
On Fri, Nov 10, 2017 at 11:02 PM, Nick Coghlan wrote:
> On 11 November 2017 at 01:48, Guido van Rossum wrote:
> > I don't mind the long name. Of all the options so far I really only like
> > 'string_annotations' so let's go with that.
>
> +1 from me.
>
I'd like to reverse my stance on this. We
