I consider it wrong to not add "from __future__ import division" to Python 2 code that is to be migrated. Yes, it changes behavior where integer division is required, but then I can use // to signal integer division where required. Skipping the import statement will only come back to hurt when switching over to Python 3!
![[TH] FS vs BME - VCT Ascension Pacific - Lower Bracket Final](http://i.ytimg.com/vi/wnygqsR2Fig/mqdefault.jpg)
if uwsgi.opt.get('optimize_mem') == b'True' ahhhhh!!!!!
One line to save your program 30% memory
I consider it wrong to not add "from __future__ import division" to Python 2 code that is to be migrated. Yes, it changes behavior where integer division is required, but then I can use // to signal integer division where required. Skipping the import statement will only come back to hurt when switching over to Python 3!
Awesome talk!
great presentation! I couldn't find the slides in either of the links thought.
www.slideshare.net/LisaGuo4/pycon2017-instagram-keynote?qid=31592668-9f41-40b7-b6fd-45ef17b0a5a7&v=&b=&from_search=1
wow, python 3.6, you guys use 2to3 tools ?
They are using python-modernize, which based on 2to3 but more powerful.
活捉一只知乎工程师。
Great talk, love seeing Django at scale
I feel like the guy's big dream is getting a job in the PR department