Py65

-------------------------

------------------

- Fixed a bug with character input that would cause characters to be
dropped when pasting in larger amounts of text. This makes it possible
to paste programs into EhBASIC and Taliforth. Patch by SamCoVT.

- Fixed interactive assembly on Python 3.

- Fixed regular expression warnings on Python 3.12.

- The ``fill`` command in the monitor now shows an error message if an
address or value is out of range.

- Added ``irq()`` and ``nmi()`` methods to the ``MPU`` class, so that
interrupts can be simulated. Patch by Irmen de Jong.

- The ``MPU`` class constructor now accepts ``None`` for the initial PC, which
will cause it to read the address from the reset vector on ``reset()``.

- The ``py65`` package is no longer a namespace package.

- Fixed assembly and disassembly of 65C02 instruction $64 (``STZ $12``).
Patch by Patrick Surry.

- Removed use of the ``asyncore`` module deprecated in Python 3.10.

------------------

- The ``Monitor`` class now allows the default memory to be supplied in
the constructor. Patch by Irmen de Jong.

- Fixed a bug where setting the MPU via ``py65mon`` command line arguments
would have no effect. Reported by Michael A. Morris, patch by Ed Spittles.

- The ``itoa()`` function in ``conversions.py`` now raises an error when an
unsupported base is given. Patch by Scot W. Stevenson.

- The unused hexdump loader utility has been removed.

------------------

- Fixed a bug where the ordering of ``py65mon`` command line arguments
produced different results. Arguments can now be specified in any
order. Patch by Mario Keller.

- Added new ``--input`` and ``--output`` arguments to ``py65mon`` that
allow the addresses of the ``getc`` and ``putc`` handlers to be
changed. Patch by Mario Keller.

- Fixed a 65C02 bug where the TSB and TRB instructions did not set
the Z flag correctly. Thanks to Kris Kennaway for reporting it.

-----------------

- Released as a universal wheel.

-----------------

- Added a workaround to $F001 output to catch encoding errors and
display a "?" instead of crashing. This condition can occur if
the 6502 program sends bytes to $F001 that aren't compatible with
the terminal's character encoding.