4 ms·
Largely because nobody has ever found Python to be dog slow. Put your unoptimized Python into production, you'll be fine.
by geofft 5y ago
Largely because nobody has ever found Python to be dog slow. Put your unoptimized Python into production, you'll be fine.
- gpderetta 5y agoWe run pylint as part of our build, including as a prerequisite of merging a branch into master. Our codebase is well over 1M lines of C++. We have about 100k lines of python. Running pylint takes the same order of magnitude of time (half as much IIRC) as running a full optimizing build + linking of the C++ code base. We run pylint over all cores, while we run the C++ build only on a subset of cores on the build machine. I would call that dog slow, unless you think python is not the appropriate language write pylint. And no, it is not fine.
- IshKebab 5y agoDropbox is the biggest user of Python that I know of, and they went as far as writing their own JIT compiler before giving up and switching to faster languages.