Đoàn Trần Công Danh <congdanhqx@xxxxxxxxx> writes: > Commit 0b4396f068, (git-p4: make python2.7 the oldest supported version, > 2019-12-13) pointed out that git-p4 uses Python 2.7-or-later features > in the code. > > In addition, git-p4 gained enough support for Python 3 from > 6cec21a82f, (git-p4: encode/decode communication with p4 for > python3, 2019-12-13). I am not a Perforce user, so with that in mind, please help me make sure I understand the situation well. The statement "not 3.x, which is not supported by Perforce" is from early 2013, and 6cec21a82f talks about the format of marshalled dict object that comes out of p4 (Perforce) tool that needs to be read in a certain way to be compatible with Python3. Does that mean sometime in these 6 years, Perforce started supporting 3.x? The change to INSTALL just drops the mention of 3.x; do we want to specifically say that any version of 3.x is OK, or is it generally accepted that Python 3.x is "later" than "Python 2.7"? > Let's update our documentation to reflect that fact. Thanks. > diff --git a/INSTALL b/INSTALL > index 9ba33e6a14..8474ad01bf 100644 > --- a/INSTALL > +++ b/INSTALL > @@ -165,8 +165,7 @@ Issues of note: > use English. Under autoconf the configure script will do this > automatically if it can't find libintl on the system. > > - - Python version 2.4 or later (but not 3.x, which is not > - supported by Perforce) is needed to use the git-p4 interface > + - Python version 2.7 or later is needed to use the git-p4 interface > to Perforce.
