More administrivia

Author: rocky

.github/ISSUE_TEMPLATE/feature-request.md

@@ -14,6 +14,14 @@ include same input and output. -->
 <!-- Add any additional background for the
 feature, for example: user scenarios, or the value of the feature. -->
 
+## Priority
+
+<!-- If this is important for a particular public good state that here.
+     If this is blocking some important activity let us know what activity it blocks.
+
+	 Otherwise, we'll assume this has the lowest priority in addressing.
+	 -->
+
 ## Tests
 <!-- _This section is optional._
 

README.rst

@@ -12,7 +12,6 @@ The successor to decompyle, uncompyle, and uncompyle2.
 
 I gave a talk on this at `BlackHat Asia 2024 <https://youtu.be/H-7ZNrpsV50?si=nOaixgYHr7RbILVS>`_.
 
-
 Introduction
 ------------
 
@@ -41,7 +40,7 @@ and associated with fragments of the source code. This purpose,
 although compatible with the original intention, is yet a little bit
 different.  See this_ for more information.
 
-Python fragment deparsing, given an instruction offset, is useful in 
+Python fragment deparsing, given an instruction offset, is useful in
 showing stack traces and can be incorporated into any program that
 wants to show a location in more detail than just a line number at
 runtime.  This code can also be used when source code information does
@@ -51,7 +50,7 @@ this.
 There were (and still are) several decompyle, uncompyle,
 uncompyle2, uncompyle3 forks around. Many of them come basically from
 the same code base, and (almost?) all of them are no longer actively
-maintained. One was really good at decompiling Python 1.5-2.3, another is really good at Python 2.7, 
+maintained. One was really good at decompiling Python 1.5-2.3, another is really good at Python 2.7,
 but only that. Another handles Python 3.2
 only; another patched that and handled only 3.3.  You get the
 idea. This code pulls all of these forks together and *moves

admin-tools/check-2.4-2.7-versions.sh

@@ -2,9 +2,9 @@
 # Run tests over all Python versions in branch python-2.4-2.7
 set -e
 function finish {
-  cd $owd
+  cd $uncompyle6_check_owd
 }
-owd=$(pwd)
+uncompyle6_check_owd=$(pwd)
 trap finish EXIT
 
 cd $(dirname ${BASH_SOURCE[0]})

admin-tools/check-3.0-3.2-versions.sh

@@ -2,10 +2,10 @@
 # Run tests over all Python versions in branch python-3.0-3.2
 set -e
 function finish {
-  cd $owd
+  cd $uncompyle6_check_owd
 }
 
-owd=$(pwd)
+uncompyle6_check_owd=$(pwd)
 trap finish EXIT
 
 cd $(dirname ${BASH_SOURCE[0]})

admin-tools/check-3.3-3.5-versions.sh

@@ -2,9 +2,9 @@
 # Run tests over all Python versions in branch python-3.3-3.5
 set -e
 function finish {
-  cd $owd
+  cd $uncompyle6_check_owd
 }
-owd=$(pwd)
+uncomphyle6_check_owd=$(pwd)
 trap finish EXIT
 
 cd $(dirname ${BASH_SOURCE[0]})

admin-tools/check-3.6-3.10-versions.sh

@@ -2,16 +2,16 @@
 # Run tests over all Python versions in branch python-3.3-3.5
 set -e
 function finish {
-  cd $owd
+  cd $uncompyle6_check_owd
 }
-owd=$(pwd)
+uncompyle6_check_owd=$(pwd)
 trap finish EXIT
 
 cd $(dirname ${BASH_SOURCE[0]})
-if ! source ./pyenv-3.3-3.5-versions ; then
+if ! source ./pyenv-3.6-3.10-versions ; then
     exit $?
 fi
-if ! source ./setup-python-3.3.sh ; then
+if ! source ./setup-python-3.6.sh ; then
     exit $?
 fi
 

admin-tools/check-newest-versions.sh

@@ -1,10 +1,10 @@
 #!/bin/bash
 function finish {
-  cd $owd
+  cd $uncompyle6_check_owd
 }
 
 # FIXME put some of the below in a common routine
-owd=$(pwd)
+uncompyle6_check_owd=$(pwd)
 trap finish EXIT
 
 cd $(dirname ${BASH_SOURCE[0]})

admin-tools/make-dist-3.6-3.10.sh

@@ -3,11 +3,11 @@ PACKAGE=uncompyle6
 
 # FIXME put some of the below in a common routine
 function finish {
-  cd $uncompyle6_33_make_owd
+  cd $uncompyle6_36_make_owd
 }
 
 cd $(dirname ${BASH_SOURCE[0]})
-uncompyle6_33_make_owd=$(pwd)
+uncompyle6_36_make_owd=$(pwd)
 trap finish EXIT
 
 if ! source ./pyenv-3.6-3.10-versions ; then