git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v2] INSTALL: git-p4 doesn't support Python 3

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 20, 2013, 18:54 UTC
Message-ID
<7vwqv7lm6b.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130120110620.GJ31172@serenity.lan>
John Keeping <john@keeping.me.uk> writes:
> git-p4 supports Python 2.6 and later versions of Python 2.  Since Python
> 2.8 will never exist [1], it is most concise to just list the supported
> versions.

Thanks; Eric's patch recently updated git-p4.py to require 2.4 I think. Shouldn't it also be updated?

Show 25 quoted lines
>
> [1] http://www.python.org/dev/peps/pep-0404/
>
> Signed-off-by: John Keeping <john@keeping.me.uk>
> Acked-by: Pete Wyckoff <pw@padd.com>
> ---
> Since v1:
>  - Fixed a typo in the commit message.
>
>  INSTALL | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/INSTALL b/INSTALL
> index 28f34bd..c456d1c 100644
> --- a/INSTALL
> +++ b/INSTALL
> @@ -131,7 +131,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.6 or later is needed to use the git-p4
> +	- Python version 2.6 or 2.7 is needed to use the git-p4
>  	  interface to Perforce.
>  
>   - Some platform specific issues are dealt with Makefile rules,
Previous: John KeepingNext: John Keeping
Message 2 of 5 in “INSTALL: git-p4 doesn't support Python 3”
  1. INSTALL: git-p4 doesn't support Python 3John Keeping, Jan 20, 2013
  2. Junio C HamanoJan 20, 2013
  3. John KeepingJan 20, 2013
  4. Junio C HamanoJan 20, 2013
  5. Brandon CaseyJan 20, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.