Skip to content
Snippets Groups Projects
  1. Mar 03, 2022
  2. Nov 06, 2020
    • Gregory Szorc's avatar
      global: use python3 in shebangs · c102b704
      Gregory Szorc authored
      Python 3 is the future. We want Python scripts to be using Python 3
      by default.
      
      This change updates all `#!/usr/bin/env python` shebangs to use
      `python3`.
      
      Does this mean all scripts use or require Python 3: no.
      
      In the test environment, the `PATH` environment variable in tests is
      updated to guarantee that the Python executable used to run
      run-tests.py is used. Since test scripts all now use
      `#!/usr/bin/env python3`, we had to update this code to install
      a `python3` symlink instead of `python`.
      
      It is possible there are some random scripts now executed with the
      incorrect Python interpreter in some contexts. However, I would argue
      that this was a pre-existing bug: we should almost always be executing
      new Python processes using the `sys.executable` from the originating
      Python script, as `python` or `python3` won't guarantee we'll use the
      same interpreter.
      
      Differential Revision: https://phab.mercurial-scm.org/D9273
      c102b704
  3. Nov 16, 2019
  4. Feb 21, 2019
  5. Aug 22, 2018
    • Katsunori FUJIWARA's avatar
      i18n: merge i18n comments of translatable texts correctly · d0e8933d
      Katsunori FUJIWARA authored
      Before this patch, i18n comments of translatable texts are lost at
      creation of hg.pot file, if:
      
        - same translatable text appears multiple times,
        - the 1st appearance does not have i18n comment, and
        - any of rest has it
      
      For example, previous patch for filemerge.py adds translatable texts
      with i18n comments, but these comments are lost, because:
      
        - automatically added texts in docstring of internal merge tools are
          picked up earlier than these translatable texts, because of
          location in filemerge.py
      
        - but docstring has no i18n comment
      
      This patch makes addentry() of posplit merge i18n comments of later
      translatable texts, in order to keep them at creation of hg.pot.
      d0e8933d
  6. May 12, 2016
  7. Feb 11, 2016
    • Katsunori FUJIWARA's avatar
      i18n: calculate correct line number in source of messages to be translated · a1924bc6
      Katsunori FUJIWARA authored
      Before this patch, line number in source of the message to be
      translated is wrong in hg.pot, if corresponded message is placed after
      ".. DIRECTIVE::", because number of lines related to such directive
      isn't added to variable "delta", which holds number of untranslated
      lines in given text.
      
      This patch always adds "2" to "delta", because text block is split
      into translation units by "\n\n".
      a1924bc6
  8. Feb 03, 2014
  9. Nov 17, 2013
  10. Feb 03, 2014
  11. Jun 17, 2010
Loading