##// END OF EJS Templates
mercurial: implement import hook for handling C/Python modules...
mercurial: implement import hook for handling C/Python modules There are a handful of modules that have both pure Python and C extension implementations. Currently, setup.py copies files from mercurial/pure/*.py to mercurial/ during the install process if C extensions are not available. This way, "import mercurial.X" will work whether C extensions are available or not. This approach has a few drawbacks. First, there aren't run-time checks verifying the C extensions are loaded when they should be. This could lead to accidental use of the slower pure Python modules. Second, the C extensions aren't compatible with PyPy and running Mercurial with PyPy requires installing Mercurial - you can't run ./hg from a source checkout. This makes developing while running PyPy somewhat difficult. This patch implements a PEP-302 import hook for finding and loading the modules with both C and Python implementations. When a module with dual implementations is requested for import, its import is handled by our import hook. The importer has a mechanism that controls what types of modules we allow to load. We call this loading behavior the "module load policy." There are 3 settings: * Only load C extensions * Only load pure Python * Try to load C and fall back to Python An environment variable allows overriding this policy at run time. This is mainly useful for developers and for performing actions against the source checkout (such as installing), which require overriding the default (strict) policy about requiring C extensions. The default mode for now is to allow both. This isn't proper and is technically backwards incompatible. However, it is necessary to implement a sane patch series that doesn't break the world during future bisections. The behavior will be corrected in future patch. We choose the main mercurial/__init__.py module for this code out of necessity: in a future world, if the custom module importer isn't registered, we'll fail to find/import certain modules when running from a pure installation. Without the magical import-time side-effects, *any* importer of mercurial.* modules would be required to call a function to register our importer. I'm not a fan of import time side effects and I initially attempted to do this. However, I was foiled by our own test harness, which has numerous `python` invoked scripts that "import mercurial" and fail because the importer isn't registered. Realizing this problem is probably present in random Python scripts that have been written over the years, I decided that sacrificing purity for backwards compatibility is necessary. Plus, if you are programming Python, "import" should probably "just work." It's worth noting that now that we have a custom module loader, it would be possible to hook up demand module proxies at this level instead of replacing __import__. We leave this work for another time, if it's even desired. This patch breaks importing in environments where Mercurial modules are loaded from a zip file (such as py2exe distributions). This will be addressed in a subsequent patch.

File last commit:

r23742:3a4d8a6c default
r27220:4374d819 default
Show More
revsets.txt
134 lines | 3.7 KiB | text/plain | TextLexer
Martin Geisler
help: new revsets topic...
r11382 Mercurial supports a functional language for selecting a set of
revisions.
The language supports a number of predicates which are joined by infix
operators. Parenthesis can be used for grouping.
Matt Mackall
revset: simplify help not about quoting
r15962 Identifiers such as branch names may need quoting with single or
double quotes if they contain characters like ``-`` or if they match
one of the predefined predicates.
Brodie Rao
revset: support raw string literals...
r12408
Special characters can be used in quoted identifiers by escaping them,
e.g., ``\n`` is interpreted as a newline. To prevent them from being
interpreted, strings can be prefixed with ``r``, e.g. ``r'...'``.
Martin Geisler
help: new revsets topic...
r11382
There is a single prefix operator:
``not x``
Changesets not in x. Short form is ``! x``.
These are the supported infix operators:
``x::y``
A DAG range, meaning all changesets that are descendants of x and
ancestors of y, including x and y themselves. If the first endpoint
is left out, this is equivalent to ``ancestors(y)``, if the second
Julian Cowley
revset: fix spelling typo
r11450 is left out it is equivalent to ``descendants(x)``.
Martin Geisler
help: new revsets topic...
r11382
An alternative syntax is ``x..y``.
``x:y``
All changesets with revision numbers between x and y, both
inclusive. Either endpoint can be left out, they default to 0 and
tip.
``x and y``
The intersection of changesets in x and y. Short form is ``x & y``.
``x or y``
The union of changesets in x and y. There are two alternative short
forms: ``x | y`` and ``x + y``.
``x - y``
Changesets in x but not in y.
Wagner Bruna
help/revsets: clean up whitespace between paragraphs
r14692
Kevin Gessner
revset: add ^ and ~ operators from parentrevspec extension...
r14070 ``x^n``
The nth parent of x, n == 0, 1, or 2.
For n == 0, x; for n == 1, the first parent of each changeset in x;
for n == 2, the second parent of changeset in x.
``x~n``
The nth first ancestor of x; ``x~0`` is x; ``x~3`` is ``x^^^``.
There is a single postfix operator:
``x^``
Equivalent to ``x^1``, the first parent of each changeset in x.
Martin Geisler
help: new revsets topic...
r11382
The following predicates are supported:
Patrick Mezard
revsets: generate predicate help dynamically
r12821 .. predicatesmarker
Martin Geisler
help: new revsets topic...
r11382
Alexander Solovyov
revset aliases
r14098 New predicates (known as "aliases") can be defined, using any combination of
existing predicates or other aliases. An alias definition looks like::
<alias> = <definition>
Wagner Bruna
help/revsets: revset aliases can be defined on any config file
r14693 in the ``revsetalias`` section of a Mercurial configuration file. Arguments
of the form `$1`, `$2`, etc. are substituted from the alias into the
definition.
Alexander Solovyov
revset aliases
r14098
For example,
::
[revsetalias]
h = heads()
d($1) = sort($1, date)
rs($1, $2) = reverse(sort($1, $2))
defines three aliases, ``h``, ``d``, and ``rs``. ``rs(0:tip, author)`` is
exactly equivalent to ``reverse(sort(0:tip, author))``.
FUJIWARA Katsunori
revset: introduce new operator "##" to concatenate strings/symbols at runtime...
r23742 An infix operator ``##`` can concatenate strings and identifiers into
one string. For example::
[revsetalias]
issue($1) = grep(r'\bissue[ :]?' ## $1 ## r'\b|\bbug\(' ## $1 ## r'\)')
``issue(1234)`` is equivalent to ``grep(r'\bissue[ :]?1234\b|\bbug\(1234\)')``
in this case. This matches against all of "issue 1234", "issue:1234",
"issue1234" and "bug(1234)".
All other prefix, infix and postfix operators have lower priority than
``##``. For example, ``$1 ## $2~2`` is equivalent to ``($1 ## $2)~2``.
Martin Geisler
help: new revsets topic...
r11382 Command line equivalents for :hg:`log`::
-f -> ::.
-d x -> date(x)
-k x -> keyword(x)
-m -> merge()
-u x -> user(x)
-b x -> branch(x)
-P x -> !::x
-l x -> limit(expr, x)
Brodie Rao
revsets: add descriptions for sample queries in the help
r12659 Some sample queries:
- Changesets on the default branch::
Mads Kiilerich
help: use Windows cmd compatible quoting in revset help
r12808 hg log -r "branch(default)"
Brodie Rao
revsets: add descriptions for sample queries in the help
r12659
- Changesets on the default branch since tag 1.5 (excluding merges)::
Mads Kiilerich
help: use Windows cmd compatible quoting in revset help
r12808 hg log -r "branch(default) and 1.5:: and not merge()"
Martin Geisler
help: new revsets topic...
r11382
Brodie Rao
revsets: add a sample query to the help for getting active branches
r12660 - Open branch heads::
Mads Kiilerich
help: use Windows cmd compatible quoting in revset help
r12808 hg log -r "head() and not closed()"
Brodie Rao
revsets: add a sample query to the help for getting active branches
r12660
Brodie Rao
revsets: add descriptions for sample queries in the help
r12659 - Changesets between tags 1.3 and 1.5 mentioning "bug" that affect
Martin Geisler
revsets: fix stray * in help topic
r12667 ``hgext/*``::
Brodie Rao
revsets: add descriptions for sample queries in the help
r12659
Mads Kiilerich
help: use Windows cmd compatible quoting in revset help
r12808 hg log -r "1.3::1.5 and keyword(bug) and file('hgext/*')"
Brodie Rao
revsets: add descriptions for sample queries in the help
r12659
Idan Kamara
help/revset: fix grammar
r13937 - Changesets committed in May 2008, sorted by user::
Brodie Rao
revsets: add descriptions for sample queries in the help
r12659
Mads Kiilerich
help: use Windows cmd compatible quoting in revset help
r12808 hg log -r "sort(date('May 2008'), user)"
Brodie Rao
revsets: add descriptions for sample queries in the help
r12659
- Changesets mentioning "bug" or "issue" that are not in a tagged
release::
FUJIWARA Katsunori
doc: use "tag" revset predicate instead of "tagged" for example in help...
r18469 hg log -r "(keyword(bug) or keyword(issue)) and not ancestors(tag())"