Get ready for release 1.4.0

Author: rocky

ChangeLog-spell-corrected.diff

@@ -1,3 +1,12 @@
+1.4.0 2025-07-26
+================
+
+* Adjust for changes in the Python 3.13 for debugging, and breakage caused by Python 3.13 and its packaging system.
+* Environment variable `TREPAN_PYGMENTS_STYLE` now influences the default style used. This is useful in when going from a shell using Pygments goes into the debugger. In particular, the Mathics3 debugger and ``mathicsscript`` work this way.
+* Add set/show disasmflavor to set disassembly style. "Disasmflavor" is the name `gdb` uses.
+* Improve `run_eval()` based on use.
+* Go over docs, and README.rst
+
 1.3.1 2025-01-16
 ================
 

NEWS.md

@@ -10,7 +10,7 @@ Abstract
 This is a gdb-like debugger for Python. It is a rewrite of *pdb* from
 the ground up. I was disappointed with the flakiness, imprecision, and
 poor quality of coding, modularity, and level of documentation when I
-first looked at *pdb*. 
+first looked at *pdb*.
 
 *pdb* has gotten better since then. But a complete debugger is way more complex than what you'd expect from
 a Standard Python module; it requires a larger set of supporting packages than is found in the Standard Python library.
@@ -108,7 +108,7 @@ GNU Readline is not just a simple static list but varies depending on
 the context. For example, for frame-changing commands that take
 optional numbers, the list of *valid numbers* is considered.
 
-In time (and perhaps with some volunteers), ``prompt_toolkit will be as good as GNU Readline completion.
+In time (and perhaps with some volunteers), ``prompt_toolkit`` will be as good as GNU Readline completion.
 
 Terminal Handling
 -----------------

README.rst

@@ -0,0 +1,56 @@
+#!/bin/bash
+PACKAGE=trepan3k
+
+# FIXME put some of the below in a common routine
+function finish {
+  cd $make_dist_311_owd
+}
+
+make_trepan_dist_36_owd=$(pwd)
+trap finish EXIT
+
+cd $(dirname ${BASH_SOURCE[0]})
+
+if ! source ./pyenv-3.11-versions ; then
+    exit $?
+fi
+if ! source ./setup-python-3.11.sh ; then
+    exit $?
+fi
+
+. ./setup-python-3.11.sh
+
+cd ..
+source trepan/version.py
+if [[ ! -n $__version__ ]]; then
+    echo "You need to set __version__ first"
+    exit 1
+fi
+echo $__version__
+
+for pyversion in $PYVERSIONS; do
+    echo --- $pyversion ---
+    if [[ ${pyversion:0:4} == "pypy" ]] ; then
+	echo "$pyversion - PyPy does not get special packaging"
+	continue
+    fi
+    if ! pyenv local $pyversion ; then
+	exit $?
+    fi
+    # pip bdist_egg create too-general wheels. So
+    # we narrow that by moving the generated wheel.
+
+    # Pick out first two number of version, e.g. 3.5.1 -> 35
+    first_two=$(echo $pyversion | cut -d'.' -f 1-2 | sed -e 's/\.//')
+    rm -fr build
+    python setup.py bdist_egg bdist_wheel
+    mv -v dist/${PACKAGE}-$__version__-{py2.py3,$first_two}-none-any.whl
+done
+
+python ./setup.py sdist
+tarball=dist/${PACKAGE}-${__version__}.tar.gz
+
+if [[ -f $tarball ]]; then
+    mv -v $tarball dist/${PACKAGE}_11-${__version__}.tar.gz
+fi
+finish

admin-tools/make-dist-3.11.sh

@@ -34,7 +34,7 @@ for pyversion in $PYVERSIONS; do
     rm -fr build
     # We can't use a universal wheel because depdencies on the decompiler changes
     # for 3.7 and 3.8
-    python setup.py bdist_egg bdist_wheel
+    python wheel .
     if [[ $first_two =~ py* ]]; then
 	if [[ $first_two =~ pypy* ]]; then
 	    # For PyPy, remove the what is after the dash, e.g. pypy37-none-any.whl instead of pypy37-7-none-any.whl

admin-tools/make-dist-newest.sh

@@ -4,8 +4,8 @@ Debugger Command Syntax
 =======================
 
 Command names and arguments are separated with spaces like POSIX shell
-syntax. Parentheses around the arguments and commas between them are
-not used. If the first non-blank character of a line starts with ``#``,
+syntax. Parenthesis around the arguments and commas between them are
+not used. If the first non-blank character of a line starts with `#`,
 the command is ignored.
 
 Commands are split at wherever ``;;`` appears. This process disregards
@@ -21,7 +21,7 @@ Resolving a command name involves possibly 4 steps. Some steps may be
 omitted depending on early success or some debugger settings:
 
 1. The leading token is first looked up in the macro table. If it is in the table, the expansion replaces the current command and
-possibly other commands pushed onto a command queue. Run `help macros` for
+possibly other commands pushed onto a command queue. See `help macros` for
 help on how to define macros, and `info macro` for current macro
 definitions.
 
@@ -39,9 +39,9 @@ program at the point it is stopped. However, this is done only if
 
 If :ref:`auto eval <set_autoeval>` is not set on, or if running the Python statement produces an error, we display an error message that the entered string is "undefined".
 
-If you want a python-, ipython-, or bpython-like shell
-command-processing, it's possible to go into a Python shell with the
-corresponding command. It is also possible to arrange to go into a Python shell every time you enter the debugger.
+If you want python-, ipython-, or bpython-like shell
+command-processing, it's possible to go into a ``python`` shell with the
+corresponding command. It is also possible to arrange to go into a ``python`` shell every time you enter the debugger.
 
 .. seealso::
 

docs/syntax/command.rst

@@ -13,7 +13,7 @@ An address range is in one of the following forms:
 
 A *location* is described elsewhere. *first* and *last* can also be
 linespecs but they also may be a number or address (bytecode
-offset). And finally *last* can be an (line number) offset.
+offset). And finally *last* can be a (line number) offset.
 
 A number is just a decimal number. An offset is a number prefaced with "+" and
 indicates the number to increment the line number found in *first*.
@@ -23,7 +23,7 @@ Examples
 
 ::
 
-  *5                 # start from bytecode offset 5 of current file
+  *5                   # start from bytecode offset 5 of the current file
   *5 ,                 # Same as above.
   foo.py:*5            # start from bytecode offset 5 of file foo.py
 

trepan/processor/command/help/arange.rst

@@ -21,32 +21,32 @@ Resolving a command name involves possibly 4 steps. Some steps may be
 omitted depending on early success or some debugger settings:
 
 1. The leading token is first looked up in the macro table. If it is in
-the table, the expansion is replaces the current command and possibly
+the table, the expansion replaces the current command and possibly
 other commands pushed onto a command queue. See `help macros` for
 help on how to define macros, and `info macro` for current macro
 definitions.
 
-2. The leading token is next looked up in the debugger alias table and
+2. The leading token is next looked up in the debugger alias table, and
 the name may be substituted there. See "help alias" for how to define
 aliases, and "show alias" for the current list of aliases.
 
-3. After the above, The leading token is looked up a table of debugger
+3. After the above, the leading token is looked up in a table of debugger
 commands. If an exact match is found, the command name and arguments
 are dispatched to that command.
 
 4. If after all of the above, we still don't find a command, the line
 may be evaluated as a Python statement in the current context of the
-program at the point it is stopped. However this is done only if
+program at the point it is stopped. However, this is done only if
 "auto evaluation" is on.  It is on by default.
 
 If `auto eval` is not set on, or if running the Python statement
 produces an error, we display an error message that the entered string
 is "undefined".
 
 If you want python-, ipython- or bpython-like shell
-command-processing, it's possible to go into an python shell with the
-corresponding command. It is also possible to arrange going into an
-python shell every time you enter the debugger.
+command-processing, it's possible to go into a ``python`` shell with the
+corresponding command. It is also possible to arrange going into a
+``python`` shell every time you enter the debugger.
 
 See also:
 ---------

trepan/processor/command/help/command.rst

@@ -5,4 +5,4 @@
 # debugger version number.
 
 # fmt: off
-__version__="1.3.2.dev0"  # noqa
+__version__="1.4.0"  # noqa