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

RE: [PATCH v4 00/22] git-p4: Various code tidy-ups

From
Joel Holdsworth <jholdsworth@nvidia.com>
Date
Apr 5, 2022, 12:04 UTC
Message-ID
<BL0PR12MB4849BAE614E63BBB0B77EC29C8E49@BL0PR12MB4849.namprd12.prod.outlook.com>
In-Reply-To
<CAPMMpohm74nVbi-dR=YOLoT+CbPiHGuVo35EoufKGKHP9Urexg@mail.gmail.com>
Show 6 quoted lines
> So, an initial test suggests that a recent version of git-p4 at least doesn't fail in
> the same way under python3, in the face of at least some of these encoding
> issues. I don't know yet whether failures will occur in other places, nor
> whether the not-failing behavior is better, worse or the same as I had under
> python2, but it seems plausible that I won't be filing any test_expect_failure
> tests after all, and will instead say "yay, python3 ftw!"
That would be fabulous.
I myself have a repository that has a variety of such issues. A common case is CP-1252 Smart Quote characters produced on Windows which are incompatible with UTF-8, without explicit conversion.
However, a lot of these problems can be avoided by simply avoiding conversion to text in the first place. In many cases the incoming data doesn't need to be converted and can be passed around as binary. I'm slowly working toward this goal, and once this patch-set it merged I have a couple of other decoding patches in the pipeline. If you have any other failure cases, please do submit them as test cases, or bug reports at least.
I would prefer the script to discard Python 2 support, but even if the consensus is to retain it, Python 3 forces us to address these issues which is a great step in the right direction.
Joel
Previous: Tao KlerksNext: Tao Klerks
Message 29 of 31 in “git-p4: Various code tidy-ups”
  1. 00/22 git-p4: Various code tidy-upsJoel Holdsworth, Feb 10, 2022
  2. 01/22 git-p4: add blank lines between functions and class definitionsJoel Holdsworth, Feb 10, 2022
  3. 02/22 git-p4: remove unneeded semicolons from statementsJoel Holdsworth, Feb 10, 2022
  4. 03/22 git-p4: indent with 4-spacesJoel Holdsworth, Feb 10, 2022
  5. 05/22 git-p4: convert descriptive class and function comments into docstringsJoel Holdsworth, Feb 10, 2022
  6. 04/22 git-p4: improve consistency of docstring formattingJoel Holdsworth, Feb 10, 2022
  7. 06/22 git-p4: remove commented codeJoel Holdsworth, Feb 10, 2022
  8. 07/22 git-p4: sort and de-duplcate pylint disable listJoel Holdsworth, Feb 10, 2022
  9. 09/22 git-p4: remove spaces around default argumentsJoel Holdsworth, Feb 10, 2022
  10. 08/22 git-p4: remove padding from lists, tuples and function argumentsJoel Holdsworth, Feb 10, 2022
  11. 10/22 git-p4: removed brackets when assigning multiple return valuesJoel Holdsworth, Feb 10, 2022
  12. 12/22 git-p4: remove extraneous spaces before function argumentsJoel Holdsworth, Feb 10, 2022
  13. 11/22 git-p4: place a single space after every commaJoel Holdsworth, Feb 10, 2022
  14. 13/22 git-p4: remove redundant backslash-continuations inside bracketsJoel Holdsworth, Feb 10, 2022
  15. 14/22 git-p4: remove spaces between dictionary keys and colonsJoel Holdsworth, Feb 10, 2022
  16. 15/22 git-p4: ensure every comment has a single #Joel Holdsworth, Feb 10, 2022
  17. 16/22 git-p4: ensure there is a single space around all operatorsJoel Holdsworth, Feb 10, 2022
  18. 17/22 git-p4: normalize indentation of lines in conditionalsJoel Holdsworth, Feb 10, 2022
  19. 19/22 git-p4: only seperate code blocks by a single empty lineJoel Holdsworth, Feb 10, 2022
  20. 20/22 git-p4: move inline comments to line aboveJoel Holdsworth, Feb 10, 2022
  21. 22/22 git-p4: sort importsJoel Holdsworth, Feb 10, 2022
  22. 18/22 git-p4: compare to singletons with "is" and "is not"Joel Holdsworth, Feb 10, 2022
  23. 21/22 git-p4: seperate multiple statements onto seperate linesJoel Holdsworth, Feb 10, 2022
  24. Tao KlerksApr 2, 2022
  25. Tao KlerksApr 2, 2022
  26. Joel HoldsworthApr 4, 2022
  27. Tao KlerksApr 5, 2022
  28. Tao KlerksApr 5, 2022
  29. Joel HoldsworthApr 5, 2022
  30. Tao KlerksApr 5, 2022
  31. Tao KlerksApr 11, 2022

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.