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

Re: [RFC PATCH 0/4] git-p4: python 3 compatability

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Nov 28, 2019, 12:54 UTC
Message-ID
<nycvar.QRO.7.76.6.1911281352130.31080@tvgsbejvaqbjf.bet>
In-Reply-To
<20191128012807.3103-1-yang.zhao@skyboxlabs.com>
Hi,
On Wed, 27 Nov 2019, Yang Zhao wrote:
Show 5 quoted lines
> This patchset the necessary changes to have git-p4 run under python 3.
>
> I'm submitting this as an RFC as the changes are not exhaustive. I do not have
> p4d available, and therefore cannot run the tests locally. I have made
> best-effort attempts to test the changes against a repo I do have read access to.

How about opening a PR at https://github.com/git/git? This will run our Travis and Azure Pipelines builds, and I am sure that you can add a debug-only patch to force-use Python3 on the Perforce tests (and if I were you, I would also restrict the run to those tests by editing `.travis.yml` and `azure-pipelines.yml`, both of which files should be easy enough to understand without additional documentation).

Ciao, Johannes

Previous: Elijah Newren
Message 7 of 7 in “git-p4: python 3 compatability”
  1. 0/4 git-p4: python 3 compatabilityYang Zhao, Nov 28, 2019
  2. 2/4 git-p4: properly encode/decode communication with git for python 3Yang Zhao, Nov 28, 2019
  3. 1/4 git-p4: decode response from p4 to str for python3Yang Zhao, Nov 28, 2019
  4. 3/4 git-p4: open .gitp4-usercache.txt in text modeYang Zhao, Nov 28, 2019
  5. 4/4 git-p4: use utf-8 encoding for file paths throughoutYang Zhao, Nov 28, 2019
  6. Elijah NewrenNov 28, 2019
  7. Johannes SchindelinNov 28, 2019

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.