On Sun, Aug 21, 2016 at 7:38 AM, Nick Coghlan email@example.com wrote:
On 20 August 2016 at 02:50, Maciej Fijalkowski firstname.lastname@example.org wrote:
Very likely just pyc import time
As one of the import system maintainers, that's a number I consider quite interesting and worth benchmarking :)
It's also one of the key numbers for Linux distro Python usage, since it impacts how responsive the system shell feels to developers and administrators - an end user can't readily tell the difference between "this shell is slow" and "this particular command I am running is using a language interpreter with a long startup time", but an interpreter benchmark suite can.
-- Nick Coghlan | email@example.com | Brisbane, Australia
Fair point, let's have such a benchmark.
Let's not have it called "bzr" though because it gives the wrong impression. The same way unladen swallow added a benchmark and called it "django" while not representing django very well. That said, likely not very many people use bzr, but still, would be good if it's called bzr-pyc or simpler - have a benchmark that imports a whole bunch of pyc from a big project (e.g. pypy :-)