You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Python 3.10/3.11, the old DYNAMIC_EXECUTION_PROFILE and DXPAIRS macros were replaced with Py_STATS macro. The sys.getdxp() function is no longer used with Tools/scripts/analyze_dxp.py. Now if Python is built with ./configure --enable-pystats, statistics on opcodes are written into the /tmp/py_stats/ directory and these files can be analyzed with Tools/scripts/summarize_stats.py.
I propose to remove sys.getdxp() and Tools/scripts/analyze_dxp.py.
The text was updated successfully, but these errors were encountered:
Remove the sys.getdxp() function and the Tools/scripts/analyze_dxp.py
script. DXP stands for "dynamic execution pairs". They were related
to DYNAMIC_EXECUTION_PROFILE and DXPAIRS macros which have been
removed in Python 3.11. Python can now be built with "./configure
--enable-pystats" to gather statistics on Python opcodes.
In Python 3.10/3.11, the old DYNAMIC_EXECUTION_PROFILE and DXPAIRS macros were replaced with Py_STATS macro. The sys.getdxp() function is no longer used with Tools/scripts/analyze_dxp.py. Now if Python is built with
./configure --enable-pystats
, statistics on opcodes are written into the/tmp/py_stats/
directory and these files can be analyzed withTools/scripts/summarize_stats.py
.I propose to remove sys.getdxp() and Tools/scripts/analyze_dxp.py.
The text was updated successfully, but these errors were encountered: