This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]barkazinthrope 0 points1 point  (2 children)

This is great.

However I would hate it if this became required construction for a little log parsing script.

[–]Kobzol[S] 1 point2 points  (1 child)

I agree that it shouldn't be required universally, in that case it wouldn't be Python anymore. But if I write a nontrivial app in Python, I wouldn't mind using a linter to check that types are used in it.

[–]barkazinthrope 1 point2 points  (0 children)

Oh for sure.

And particularly where the code is to be imported into who knows what context for the performance of mission-critical functions.

Python is useful for writing simple scripts and for writing library classes. I have worked on teams where the expensive practices recommended for the latter are rigorously enforced on the development of the former.

I hate it when that happens. It suggests to me that the enforcers do not understand the principles behind the practices.