Le vendredi 26 août 2016, Antoine Pitrou <solip...@pitrou.net> a écrit :
> On Fri, 26 Aug 2016 00:07:53 +0200 > Victor Stinner <victor.stin...@gmail.com <javascript:;>> > wrote: > > > > By the way, I don't know if it's worth it to have a "pyperformance" > > command line tool. You can already use "python3 -m performance ..." > > syntax. But you have to recall the Python version used to install the > > module. "python2 -m performance ..." doesn't work if you only > > installed performance for Python 3! > > Also, you may have several Python 3s installed (the system 3.4, a > custom 3.4, a custom 3.5, a custom 3.6...) so a CLI script is much > easier to use. Yeah right. Thanks for helping me to take a decision on that. For example, I don't want to install performance in PyPy system directory. FYI performance _is_ installed for each tested Python, but in a dedicated virtual environment which is isolated from the system to get a more reliable testing environment. For example, the number of .pth files installed on the system has an impact on startup time. Having a controlled venv avoids the random number of .pth files. Victor
_______________________________________________ Speed mailing list Speed@python.org https://mail.python.org/mailman/listinfo/speed
