I am actually not at all interested in support for Python 2.4 (or 2.5 or
2.6). My real objective is for StGit to support Python 2.7 and 3.x
out of the same code base. But experience indicates that old Python
versions die hard. So as an intermediate goal, I want to establish a
final version of StGit that supports legacy Python 2.x versions so that
we can make the breaking changes required to simultaneously support
Python 2.7 and 3.x.

Some idioms have snuck in that break support for Python 2.4 (and
probably 2.5). Also, PyPy 5.6 (implementing Python 2.7) was broken due
to a subtle StGit bug along with a subtle difference between CPython and
PyPy semantics concerning builtin functions.

These patches enable full support of PyPy and restore basic Python 2.4
compatibility, although not all tests pass with Python 2.4 and I have
not deep-dived the remaining problems. The following tests still fail
with Python 2.4:

   t1000-branch-create.sh
   t1800-import.sh
   t1900-mail.sh
   t3300-edit.sh
   t4100-publish.sh

Peter Grayson (4):
  Repair support for Python 2.4
  Python 2.4 compatibility for test.py
  Repair custom any() and all() implementations
  Add classifiers and download_url to setup.py

 setup.py                 | 21 +++++++++++-
 stgit/lib/git.py         |  4 ++-
 stgit/lib/transaction.py |  2 +-
 stgit/utils.py           |  9 ++++--
 t/test.py                | 84 ++++++++++++++++++++++++++++++++----------------
 5 files changed, 87 insertions(+), 33 deletions(-)

_______________________________________________
stgit-users mailing list
[email protected]
https://mail.gna.org/listinfo/stgit-users

Reply via email to