Get ready for release 1.1.2

Author: rocky

CHANGES.rst

@@ -1,6 +1,20 @@
 CHANGES
 =======
 
+1.1.2
+-----
+
+Release 1.1.1 introduced a small bad interaction with Mathics and the
+unicode infix form of ``Function[]``.
+
+In our master table, when there is a unicode operator like there is for "Function",
+(uF4A1), the operator name to be YAML key name.
+
+There is an alternate ASCII Function operator ``&``. And for that we
+used the name Function which precluded using it for the unicode, where
+it is mandiatory. For ASCII operators it isn't necessary, but still
+nice to do when there is no conflict.
+
 1.1.1
 -----
 

mathics_scanner/data/named-characters.yml

@@ -3475,15 +3475,13 @@ FreakedSmiley:
 # IMPORTANT!
 # ----------
 # For the Mathics Parser to work circa 2021...
-# If an operator name like "Function" has unicode associated with it, then
-# the YAML key *has* to be the operator name.
-# This is because we are doing weird Function-name to unicode translation
-# in the parse.
+# If there is a unicode operator, as we have here for "Function", then
+# the YAML key *has* to be the operator name. ("Function" here).
 #
-# The auto-unicode translation might not be a good thing to do.
-#
-# The ASCII-only version of the Function operator therefore has a
-# different (from the operator) YAML key name.
+# There is an ASCII operator "&" for the Function as well, but
+# the YAML name doesn't have to match since there is just ASCII for that.
+# Since we use the name Function as the key here, the YAML name for "&" has
+# to be different, since YAML keys need to be unique.
 Function:
   ascii: "|->"
   has-unicode-inverse: false

mathics_scanner/version.py

@@ -4,4 +4,4 @@
 # This file is suitable for sourcing inside POSIX shell as
 # well as importing into Python. That's why there is no
 # space around "=" below.
-__version__="1.1.2.dev0"  # noqa
+__version__="1.1.2"  # noqa