##// END OF EJS Templates
rust-pyo3: implementation of LazyAncestors...
rust-pyo3: implementation of LazyAncestors There is a difference in the implementaion of `__contains__` between PyO3 and rust-cpython: if the specified signature in Rust code is for a precise type (e.g., `PyRevision`) rust-cpython would automatically convert the potential resulting `TypeError` into `Ok(false)`, whereas PyO3 let it bubble up. Hence we treat the case manually and add it to the common test. In Mercurial Python code, `None in` for a `LazyAncestors` object can really happens, namely in this lambda from `discover._postprocessobsolete`: ``` ispushed = lambda n: torev(n) in futurecommon ``` This lambda can get called with `n` such that `torev(n)` is `False` (seen in `test-bookmarks-push-pull.t`).

File last commit:

r50731:3d7bf111 stable
r53430:6b694bdf default
Show More
requirements-macos.txt.in
22 lines | 545 B | text/plain | TextLexer
/ contrib / packaging / requirements-macos.txt.in
# Declare macOS-specific requirements for generating
# the compiled (frozen) set of requirements in
# ./requirements-macos.txt.
# If run on Windows, it may be necessary to run dos2unix
# on the output file to replace any CRLF newlines with LF.
# TODO: dulwich, pygit2, and pytest-vcr are flagged as being
# incompatible with in-memory resources. Maybe there's a
# way to bundle just them externally.
docutils
#dulwich
# Needed by the release note tooling
fuzzywuzzy
keyring
#pygit2
pygments
# Needed by the phabricator tests
#pytest-vcr