xasm 1.2.0__tar.gz → 1.2.1__tar.gz

{xasm-1.2.0 → xasm-1.2.1}/.editorconfig

@@ -1,4 +1,4 @@
-# THis is an EditorConfig file
+# This is an EditorConfig file
 # https://EditorConfig.org
 
 root = true

{xasm-1.2.0 → xasm-1.2.1}/.gitignore

@@ -2,8 +2,11 @@
 *~
 /.cache
 /.eggs
+/.idea
+/.mypy_cache
 /.pytest_cache
 /.python-version
+/ChangeLog-spell-corrected
 /README.html
 /build
 /dist

xasm-1.2.1/.pre-commit-config.yaml

@@ -0,0 +1,22 @@
+default_language_version:
+  python: python
+repos:
+-   repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v4.5.0
+    hooks:
+    - id: check-merge-conflict
+    - id: debug-statements
+      stages: [pre-commit]
+    - id: end-of-file-fixer
+      stages: [pre-commit]
+# -   repo: https://github.com/pycqa/isort
+#     rev: 5.13.2
+#     hooks:
+#       - id: isort
+#         stages: [pre-commit]
+-   repo: https://github.com/psf/black
+    rev: 23.12.1
+    hooks:
+    - id: black
+      language_version: python3
+      stages: [pre-commit]

{xasm-1.2.0 → xasm-1.2.1}/ChangeLog

@@ -1,8 +1,262 @@
+2025-10-13  rocky <rb@dusytfeet.com>
+
+	* xasm/version.py: Get ready for release 1.2.1
+
+2025-10-13  rocky <rb@dusytfeet.com>
+
+	* README.rst, admin-tools/install-all-3.6-3.10.sh,
+	admin-tools/install-all-newest.sh,
+	admin-tools/make-dist-3.6-3.10.sh: Better package testing
+
+2025-10-13  rocky <rb@dusytfeet.com>
+
+	* admin-tools/install-all-3.8-3.10.sh,
+	admin-tools/install-all-newest.sh,
+	admin-tools/make-dist-3.8-3.10.sh,
+	admin-tools/pyenv-3.6-3.10-versions: Packaging, yet again
+
+2025-10-13  rocky <rb@dusytfeet.com>
+
+	* Makefile, admin-tools/merge-for-3.6.sh: Ever changing "standards"
+
+2025-10-13  rocky <rb@dusytfeet.com>
+
+	* admin-tools/check-newest-versions.sh: Correct admin scripts
+
+2025-10-13  rocky <rb@dusytfeet.com>
+
+	* README.rst, admin-tools/make-dist-newest.sh, pyproject.toml,
+	setup.py: Packaging
+
+2025-10-13  rocky <rb@dusytfeet.com>
+
+	* admin-tools/check-3.6-3.10-versions.sh,
+	admin-tools/check-newest-versions.sh,
+	admin-tools/checkout_common.sh,
+	admin-tools/install-all-3.8-3.10.sh,
+	admin-tools/install-all-newest.sh,
+	admin-tools/make-dist-3.8-3.10.sh, admin-tools/make-dist-newest.sh,
+	admin-tools/merge-for-3.6.sh, admin-tools/pyenv-3.6-3.10-versions,
+	admin-tools/pyenv-newest-versions, admin-tools/setup-master.sh,
+	admin-tools/setup-python-3.6.sh, admin-tools/test-versions.sh: Admin
+	crap
+
+2025-10-13  rocky <rb@dusytfeet.com>
+
+	* .github/workflows/{osx.yml => macos.yml},
+	.github/workflows/ubuntu.yml, .pre-commit-config.yaml,
+	requirements.txt, xasm/assemble.py: Misc fixes
+
+2025-06-21  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: Correct bug respecing create_code API Fixes #24
+
+2025-02-18  rocky <rb@dusytfeet.com>
+
+	* requirements.txt: Make dependabot happy
+
+2024-12-24  rocky <rb@dusytfeet.com>
+
+	* .pre-commit-config.yaml, requirements.txt: Make dependabot happy
+
+2024-09-10  rocky <rb@dusytfeet.com>
+
+	* requirements.txt: Silenced dependabot
+
+2024-07-03  rocky <rb@dusytfeet.com>
+
+	* .github/ISSUE_TEMPLATE/bug-report.md,
+	.github/ISSUE_TEMPLATE/config.yml,
+	.github/ISSUE_TEMPLATE/feature-request.md, HOW-TO-USE.rst,
+	README.rst: Correct spelling typos
+
+2024-07-02  rocky <rb@dusytfeet.com>
+
+	* HOW-TO-USE.rst, README.rst: Update README.rst
+
+2024-07-02  rocky <rb@dusytfeet.com>
+
+	* HOW-TO-USE.rst, xasm/assemble.py, xasm/pyc_convert.py: More
+	explicit comments and ...  add ## comments, and document better module and method information
+
+2024-06-23  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py, xasm/pyc_convert.py: bug fixes...  * decode_linotab() -> decode_lineno_tab_old to make it clear that
+	  this routine works for version before 3.10 * last instruction can be RERAISE or RASE_VARARGS in addition to   RETURN_VALUE * Avoid using asm.code.to_native() for now, since there are bugs
+
+2024-06-23  R. Bernstein <rocky@users.noreply.github.com>
+
+	* HOW-TO-USE.rst: Update HOW-TO-USE.rst Spell check and update information
+
+2024-06-23  R. Bernstein <rocky@users.noreply.github.com>
+
+	* HOW-TO-USE.rst: Update HOW-TO-USE.rst
+
+2024-06-23  R. Bernstein <rocky@users.noreply.github.com>
+
+	* HOW-TO-USE.rst: Update HOW-TO-USE.rst
+
+2024-06-23  R. Bernstein <rocky@users.noreply.github.com>
+
+	* HOW-TO-USE.rst: Update HOW-TO-USE.rst
+
+2024-06-15  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: Misc tweaks and bug fixes...  * Handle numeric labels better * Adjust field name co_linetable for 3.10+ * Warn if duplicate line number seen and < 3.10
+
+2024-06-04  rocky <rb@dusytfeet.com>
+
+	* .github/workflows/osx.yml, .github/workflows/ubuntu.yml,
+	.github/workflows/windows.yml: CI - need latest xdis for testing
+
+2024-06-04  rocky <rb@dusytfeet.com>
+
+	* pytest/test_assemble.py, xasm/assemble.py: Go over EXTENDED_ARG
+	creation in bytecode
+
+2024-06-03  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: remove unused import
+
+2024-06-03  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py, xasm/xasm_cli.py: Compute EXTENDED_ARG better;
+	fix a typo
+
+2024-06-03  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: Improve offset label handling and ..  ignore EXTENDED_ARG
+
+2024-06-03  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: Fix two misfeatures...  1. If Python bytecode is not set, complain and exit 2. Detect and handle line numbers on instructions
+
+2024-05-26  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: Check that operand values are in range
+
+2024-05-26  rocky <rb@dusytfeet.com>
+
+	* xasm/write_pyc.py, xasm/xasm_cli.py: Track and report errors in
+	return code better
+
+2024-05-26  rocky <rb@dusytfeet.com>
+
+	* .editorconfig: Typo
+
+2024-05-26  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: Tweak missing return value error
+
+2024-05-26  rocky <rb@dusytfeet.com>
+
+	* pytest/test_write_pyc.py: Skip a pytest on windows CI
+
+2024-05-26  rocky <rb@dusytfeet.com>
+
+	* .github/workflows/windows.yml, __pkginfo__.py, requirements.txt,
+	setup.py: Another attempt to get CI actions working
+
+2024-05-26  rocky <rb@dusytfeet.com>
+
+	* .github/workflows/osx.yml, .github/workflows/ubuntu.yml,
+	.github/workflows/windows.yml: Try Workflows actions
+
+2024-05-26  rocky <rb@dusytfeet.com>
+
+	* test/TODO.md: Add a TODO
+
+2024-05-26  rocky <rb@dusytfeet.com>
+
+	* test/tasm-3.10-bad.pyasm, test/tasm-3.10.pyasm, xasm/assemble.py:
+	Add a check for last instruction being a "return"
+
+2024-05-22  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: Offset in 3.10+ need to be divided by two
+
+2024-05-20  rocky <rb@dusytfeet.com>
+
+	* xasm/xasm_cli.py: Tweak asm file path
+
+2024-02-20  rocky <rb@dusytfeet.com>
+
+	* requirements.txt: Keep dependabot happy
+
+2024-01-10  rocky <rb@dusytfeet.com>
+
+	* requirements.txt: Bump cryptography to silence Depedabot
+
+2024-01-10  rocky <rb@dusytfeet.com>
+
+	* .pre-commit-config.yaml, xasm/assemble.py, xasm/pyc_convert.py,
+	xasm/xasm_cli.py: convert % to f-strings
+
+2024-01-09  rocky <rb@dusytfeet.com>
+
+	* pytest/test_write_pyc.py, requirements.txt: Update requirements as
+	recommended by dependabot Also comment out a test where xdis marshal is broken.
+
+2023-12-17  R. Bernstein <rocky@users.noreply.github.com>
+
+	* : Merge pull request #21 from rocky/lint Some lint found
+
+2023-10-23  rocky <rb@dustyfeet.com>
+
+	* .gitignore, __pkginfo__.py, requirements.txt, xasm/.gitignore,
+	xasm/assemble.py, xasm/pyc_convert.py, xasm/xasm_cli.py: Misc lint
+
+2023-09-18  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: version -> version_tuple fixes
+
+2023-09-18  rocky <rb@dusytfeet.com>
+
+	* .gitignore, admin-tools/pyenv-newest-versions,
+	admin-tools/setup-master.sh, test/.gitignore: Bump testing versions
+
+2022-12-02  rocky <rb@dustyfeet.com>
+
+	* xasm/assemble.py: Pycharm lint
+
+2022-12-02  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: Add a more detailed assert message...  about the header.
+
+2022-12-02  rocky <rb@dusytfeet.com>
+
+	* xasm/version.py: Bump version to development version
+
+2022-10-17  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py, xasm/write_pyc.py: Remove debug statement.  Fixes #17 Also, add msg when we can't dump a code object
+
+2022-08-22  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py, xasm/write_pyc.py: Fix a couple of small bugs
+
+2022-06-16  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: Detect native code objects in constants
+
+2022-04-02  R. Bernstein <rocky@users.noreply.github.com>
+
+	* : Merge pull request #15 from
+	Svenskithesource/Svenskithesource-patch-2 Fix empty append call
+
+2022-03-05  R. Bernstein <rocky@users.noreply.github.com>
+
+	* : Merge pull request #13 from Svenskithesource/patch-1 Typo
+
+2021-12-04  rocky <rb@dusytfeet.com>
+
+	* xasm/assemble.py: wrong variable python_version -> version Fixes #11
+
 2021-11-07  rocky <rb@dusytfeet.com>
 
 	* ChangeLog, NEWS.md, admin-tools/check-versions.sh,
-	admin-tools/pyenv-versions, xasm/version.py: Get ready for release
-	1.2.0
+	admin-tools/make-dist.sh, admin-tools/pyenv-versions, setup.cfg,
+	xasm/version.py: Get ready for release 1.2.0
 
 2021-11-07  rocky <rocky@dusytfeet.com>
 
@@ -10,7 +264,7 @@
 
 2021-11-07  rocky <rocky@dusytfeet.com>
 
-	* admin-tools/pyenv-versions, admin-tools/setup-master.sh: 
+	* admin-tools/pyenv-versions, admin-tools/setup-master.sh:
 	Administrivia
 
 2021-11-05  rocky <rocky@dusytfeet.com>
@@ -62,7 +316,7 @@
 
 	* ChangeLog, NEWS.md, __pkginfo__.py,
 	admin-tools/how-to-make-a-release.md, admin-tools/pyenv-versions,
-	setup.py, xasm/__init__.py, xasm/pyc_convert.py, xasm/version.py: 
+	setup.py, xasm/__init__.py, xasm/pyc_convert.py, xasm/version.py:
 	Get ready for release 1.1.1
 
 2020-07-02  rocky <rocky@gnu.org>
@@ -129,7 +383,7 @@
 	* Makefile, __pkginfo__.py, admin-tools/how-to-make-a-release.md,
 	admin-tools/pyenv-versions, pytest/.gitignore,
 	pytest/test_write_pyc.py, test/test_all.py, xasm/.gitignore,
-	xasm/assemble.py, xasm/misc.py, xasm/write_pyc.py, xasm/xasm_cli.py: 
+	xasm/assemble.py, xasm/misc.py, xasm/write_pyc.py, xasm/xasm_cli.py:
 	Revise for new xdis. Add Better write_pyc() fn
 
 2019-11-06  rocky <rb@dustyfeet.com>
@@ -463,7 +717,7 @@
 2017-07-04  rocky <rb@dustyfeet.com>
 
 	* test/gcd-2.7.pyasm, xasm/assemble.py: More proper label handling All non-int labels are absolute Labels as an operand don't and shouldn't have the trailing ':'.
-	pydisasm doen't add that Start moving toward xdis enhanced ability to work with Python code
+	pydisasm doesn't add that. Start moving toward xdis's enhanced ability to work with Python code
 	more interchangeably between Python 2 and 3.
 
 2017-07-03  rocky <rb@dustyfeet.com>
@@ -547,4 +801,3 @@
 2017-06-26  rocky <rb@dustyfeet.com>
 
 	* Assembler first step
-

{xasm-1.2.0 → xasm-1.2.1}/HOW-TO-USE.rst

@@ -1,5 +1,5 @@
 Introduction
-*************
+============
 
 Welcome back to the wonderful times world of SEGV's (from the Python interpreter)!
 
@@ -11,7 +11,7 @@ skeletal. Then use ``pydisasm --xasm`` to convert to the Python source
 code assembler format. From this then modify the results and run
 ``pyc-xasm``.
 
-In normal python disassembly code (and in the bytecode file), the main
+In normal Python disassembly code (and in the bytecode file), the main
 function appears first; it contains constants which contain code to
 other functions and so on. In Python disassembly these are linearized
 so that from top down you have a topological sort of the dependencies.
@@ -30,22 +30,39 @@ instructions. Another reason why using ``pydisasm --xasm`` is
 preferable right now.
 
 Format of assembly file
------------------------
+=======================
 
-Again, easiest to consult the ``pydiasm --xasm`` output ``.pyasm``-file that is 
-produced. Even easier, just to look in the test directory_ for files that end 
+Again, easiest to consult the ``pydisasm --xasm`` output ``.pyasm``-file that is
+produced. Even easier, just to look in the test directory_ for files that end
 with ``.pyasm``.
 
-In general, lines that start with "#" in column one are comments or code or function 
-objects other than bytecode instructions.
+Lines that start with '##" are comments.
+
+Examples::
+
+    ## This line is a comment
+    ## Method Name:       GameSheet
 
-Necessary fields that are in Python code object and function objects
-are here. These include stuff like the Python "magic" number which
-determines which Python bytecode opcodes to use and which Python
-interpreter can be used to run the resulting program.
+Lines that start with ``#``" in column one are used to indicate a code
+or function object that is not a bytecode instructions. However this
+is only true if the rest of the line matches one of the code of
+function objects mentioned below. If instead the the rest of a line
+does not match a function or code object, it line too will be
+treated tacitly as a comment.
 
 Module-level info
------------------
+------------------
+
+
+The only necessary mdoule-level inforamation that is needed is the
+Python "magic" number which determines which Python bytecode opcodes
+to use and which Python interpreter can be used to run the resulting
+program.
+
+Optional information includes:
+
+* Timestamp of code
+* Source code size module 2**32 or a SIP hash
 
 Here is an example of the module-level information:
 
@@ -53,16 +70,27 @@ Here is an example of the module-level information:
 
    # Python bytecode 2.2 (60717)
    # Timestamp in code: 1499156389 (2017-07-04 04:19:49)
+   # Source code size mod 2**32: 577 bytes
 
-The bytecode is necessary. However the timestamp is not. In Python 3
-there is also a size modulo 2**32 that is recorded.
+Again, the bytecode number is necessary. However the timestamp is not. In Python 3
+there is also a size modulo 2**32 that is recorded, and in later Python this can be a
+SIP hash.
 
 ::
 
-   # Source code size mod 2**32: 577 bytes
 
 Method-level info
-.................
+------------------
+
+Method-level information starts with ``#`` in column one. Here is some
+method-level information:
+
+* The method name of the code object (``Method Name``)
+* Number of local variables used in module or function (``Number of locals``)
+* A filename where the file (``Filename``)
+* Maximum Stack Size needed to run code (``Stack Size``)
+* Code flags which indicate properties of the code (``Flags``)
+* Fine number for the first line of the code (``First Line``)
 
 Here is an example:
 
@@ -72,9 +100,10 @@ Here is an example:
    # Filename: exec
    # Argument count: 2
    # Kw-only arguments: 0
-   # Number of locals: 2 # Stack size: 3
+   # Number of locals: 2
+   # Stack size: 3
    # Flags: 0x00000043 (NOFREE | NEWLOCALS | OPTIMIZED)
-   # First Line: 11 
+   # First Line: 11
    # Constants:
    # 0: ' GCD. We assume positive numbers'
    # 1: 0
@@ -95,7 +124,7 @@ Here is an example:
 
 Some of these can be omitted and default values will be used. For the
 lists like Constants, Names, and so on, those can be omitted too. But
-if they are, the instruction section can't refer to those values by list index value. (List index value is however used in the actual bytecode.)b
+if they are, the instruction section can't refer to those values by list index value. (List index value is however used in the actual bytecode.)
 
 Although we haven't gotten to the exact format of instructions, what
 the last sentence means is that
@@ -104,14 +133,14 @@ the last sentence means is that
 
    LOAD_CONST 3
 
-would be invalid if the size of the constant array is less than 4, or `constant[3]` wasn't defined by adding it to the `Constants` section. However when you put a value in parenthesis, that indicate a value rather than an index into a list. 
+would be invalid if the size of the constant array is less than 4, or `constant[3]` wasn't defined by adding it to the `Constants` section. However when you put a value in parenthesis, that indicate a value rather than an index into a list.
 So you could instead write:
 
 ::
 
    LOAD_CONST (1)
 
-which in this case does the same thing since `1 = constant[3]`. If the value 1 does not appear anywhere in the constants list, the assember would append the value 1 to the end of the list of the constants list. When writing the final bytecode file an appropriate constant index will be inserted into that instruction. 
+which in this case does the same thing since `1 = constant[3]`. If the value 1 does not appear anywhere in the constants list, the assembler would append the value 1 to the end of the list of the constants list. When writing the final bytecode file an appropriate constant index will be inserted into that instruction.
 
 Line Numbers and Labels
 -----------------------
@@ -126,14 +155,14 @@ example
        LOAD_CONST ('this is line 66')
 
 The ``LOAD_CONST`` instruction will be noted as being on line 66. Note
-that Python requires that line numbers don't decrease as the a
+that Python before version 3.10 requires that line numbers don't decrease as the a
 method increases in bytecode offset. Also note that there can be white
 space before the line number; the number doesn't have to be in
 column 1.
 
 Labels are like line numbers in that they have a colon suffix on the
 line and must be the first thing on a line. However The first
-character of a label _can't_ be a number: that's how we distinguish
+character of a label *cannot* be a number: that's how we distinguish
 between line numbers and labels. Here is a label:
 
 ::
@@ -151,7 +180,7 @@ Instructions
 -------------
 
 The module level bytecode line determines what Python opcodes are
-exceptable and how operands are interpreted.
+acceptable and how operands are interpreted.
 
 Instructions come after the other module or function information that starts with `#` and
 is shown above.
@@ -161,8 +190,19 @@ module field which would start with a #. And it is not a line number
 or label listed in the last section. We've seen examples of
 instructions above.
 
-Instructions start with an opcode and will have an operand depending
-on whether the opcode requires one or not. However as we've seen above
+Operation name
+...............
+
+Instructions start with an opcode name like ``LOAD_CONST``. The specific opcode names used depends on the Python version you are using.
+So make sure to consult the "opcodes" section of the "dis" module documentation for the version of Python listed at the top of the metadata section.
+
+
+Operand
+........
+
+
+An instruction may also have an operand depending
+on whether the opcode requires one or not. However as we've seen above,
 the operands can take a couple of forms. The operand can be a number
 which represents a bytecode offset, or an index into one of the method
 lists like the Constants, or Names list. I don't recommend though that
@@ -175,13 +215,15 @@ parenthesis. For example:
 ::
 
     LOAD_CONST (3)    # loads number 3
-    LOAD_CONST 3      # load Constants[3] 
+    LOAD_CONST 3      # load Constants[3]
     JUMP_ABSOLUTE 10  # Jumps to offset 10
     JUMP_ABSOLUTE L10 # Jumps to label L10
     LOAD_CONSTANT (('load_entry_point',)) # Same as: tuple('load_entry_point')
 
 Instructions can also have additional stuff after the operand and that is ignored.
 
+Internally operand values are integers or indexes in some table. When an index value is more than 255 (the largest value that fits in a single byte), an ``EXTENDED_OPERAND`` instruction is added automatically.
+
 Cool Stuff
 ----------
 
@@ -196,20 +238,9 @@ doesn't have to be the same as the Python interpreter that runs
 TODO
 -----
 
-Possibly we should figure out when to put in ``EXTENDED_ARGS``
-instructions. And for now, even though you put in ``EXTENDED_ARGS``,
-the operand that follows may have the value folded into it. For
-example in Python 3.6 where an operand can be at most 255, of you
-wanted to jump relative 259 bytes you'd write:
-
-::
-
-   EXTENDED_ARG 1  # Needed because below offset is greater than 255 away
-   JUMP_FORWARD 259  # Should really be 3 (= 259 - 256)
-
 We should have a better API to generate instructions from inside
 Python. This is pretty straightforward to do.
 
-I've not put much in the way of error checking and error reporting.
+There is some error checking of consistency of the input file, but more  error checking is desirable.
 
 .. _directory: https://github.com/rocky/python-xasm/tree/master/test

{xasm-1.2.0 → xasm-1.2.1}/Makefile

@@ -11,8 +11,8 @@ check: test
 
 #: Run tests
 test:
-	py.test pytest
-	py.test test/test_all.py
+	pytest pytest
+	pytest test/test_all.py
 
 clean:
 	cd test && make clean
@@ -27,3 +27,4 @@ rmChangeLog:
 #: Create a ChangeLog from git via git log and git2cl
 ChangeLog: rmChangeLog
 	git log --pretty --numstat --summary | $(GIT2CL) >$@
+	patch ChangeLog < ChangeLog-spell-corrected.diff

xasm-1.2.1/NEWS.md

@@ -0,0 +1,44 @@
+1.2.1 2025-10-13
+----------------
+
+* Repackage for Python 3.11 and poetry. I can't describe what thrill it gives me to have to do this every few years.
+* Correct bug respecting `create_code` API Fixes #24
+* More explicit comments. Add some `##` comments. Document module and method information better.
+* `decode_linotab()` is now `decode_lineno_tab_old` to make it clear that this routine works for version before 3.10.
+* Avoid using `asm.code.to_native()` for now, since there are bugs.
+* Handle numeric labels better.
+* Adjust field name `co_linetable` for bytecode after 3.10.
+* Warn if duplicate line numbers seen and the assembler is before bytecode for 3.10
+* Improve `EXTENDED_ARG` handling and creation.
+* If Python bytecode is not set, complain and exit.
+* Detect and handle line numbers on instructions
+* Add a check for last instruction being either a `RETURN_VALUE`, or `RERAISE`, or `RAISE_VARARGS`
+* Offsets in bytecode for 3.10 need to be divided by two
+* Lint code a little
+
+1.2.0 2021-11-07
+----------------
+
+* Adjust to use xdis 6.0.3 or later
+* start adding `.READ` directive
+
+1.1.1 2020-10-27
+----------------
+
+- Fix bugs in cross-assembly bytecode writing
+- Detect PyPy.
+- Add SIP hash field. Fixes #4
+
+1.1.0 2020-04-24
+----------------
+
+- Fix bugs in writing 3.7 and 3.8 pyc
+- Require newer xdis to get fixes to 3.8 pyc marshaling
+
+
+1.0.0 2019-10-19
+----------------
+
+- Go over docs.
+- Require newer xdis to get early bytecodes bytecodes: 1.0, 1.1, 1.2, and 1.6.
+- More sensitive to network ordering