Hi! you could have stayed on IRC, I answered you. PYPYLOG is a pretty generic logging infrastructure that gives you access to a whole bunch of information. It depends very much what you want to achieve with it.
A simple thing to try to get started is looking at the JIT summary like this: PYPYLOG=jit-summary:- pypy yourprogram.py the syntax of the value of the env variable is: category:output_target the category is a comma-separated list of categories you are interested in, in this case jit-summary. after the colon : you can either give a filename, or "-" for stdout. That means the above will print some summary statistics about what the JIT did after your program finishes. That's a good starting point. For further info, let's talk on IRC or reply to the mail which specific things you are interested in. Cheers, CF On 22.03.22 10:28, Aksam Lwanga wrote:
Hey. am confused about the debugging variable for PYPYLOG, have set its value, am trying to run the benchmark so that I can get some insights on how to use it in the future, however when I compile my file it doesn't show me the output file, do I need to set any other thing apart from the PYPYLOG environment variable, Which commands ensures that have run pypy to ensure that debugging is enabled?, any assistance is highly appreciated. _______________________________________________ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: cfb...@gmx.de
_______________________________________________ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com
