Nice it actually gives "SyntaxError: invalid syntax", but then it affects all th... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		dorianm on Nov 5, 2016 \| parent \| context \| favorite \| on: Be careful about what you dislike Nice it actually gives "SyntaxError: invalid syntax", but then it affects all the imported libraries so I still prefer the per-file way as a transition.

ambivalence on Nov 5, 2016 [–]

__future__ imports are per file. A few posts up you were proposing an interpreter-wide switch. Did you change your mind?

dorianm on Nov 5, 2016 | [–]

Awesome. I think both are great, first doing file-per-file and once it's working switching the global switch is a pretty good transition workflow.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact