I did not kept the numbers
Active Repositories
Active Repositories
- rNRWHG narrowhg
- 369 Commits
- ·
- Restricted Project
- Jan 26 2018, 6:48 PM
- Mercurial
Recent Activity
Recent Activity
Yesterday
Yesterday
acezar updated the diff for D8872: rhg: make output of `files` relative to the current directory and the root.
acezar updated the diff for D8868: rhg: add a `Files` `Command` to prepare the `rhg files` subcommand.
acezar updated the diff for D8864: rhg: Do not return error when when we really mean ok in commands.
acezar updated the diff for D8861: hg-core: make parse_dirstate return references rather than update hashmaps.
acezar retitled D8867: rhg: simplify `FindRootError` handling from rhg: simply `FindRootError` handling to rhg: simplify `FindRootError` handling.
martinvonz updated the diff for D8858: packaging: include templates with their package as key in package_data.
Mon, Aug 3
Mon, Aug 3
Having thought about this a bit more, I think using the importlib.resources high-level APIs are better. i.e. this series as-is is fine.
martinvonz updated the diff for D8858: packaging: include templates with their package as key in package_data.
Added signature for changeset 7fc3c5fbc65f
Added tag 5.5 for changeset 7fc3c5fbc65f
pulkit committed rHG7fc3c5fbc65f: mergestate: fix BC breakage introduced because of removal of a merge record.
mergestate: fix BC breakage introduced because of removal of a merge record
Maybe add an example with | head for completeness?
Alphare added a comment to D8872: rhg: make output of `files` relative to the current directory and the root.
To reviewers: this was my changeset, I'm not sure how authorship is attributed but I... accept the revision of course.
In D8854#132358, @indygreg wrote:OMG. When I reviewed this, I thought your assertion that resources.open_binary('mercurial.templates', 'coal/map') is not valid was wrong because the low-level resource reader on the meta path importer does allow relative paths! However, it appears that the open_binary() helper functions limit this! This is yet another example of wonky behavior in these resources APIs. FWIW I've brought many of these to the attention of the core Python people at https://bugs.python.org/issue36128 and https://gitlab.com/python-devs/importlib_resources/-/issues/58 (and a few other places that I can't find the links to).
Typo in the title: s/simply/simplify/
@acezar Do you remember the kind of performance difference we had when adding this? I think it would be interesting to add it to the commit message.
To add to this change, it's also entirely possible that we may never need the trait altogether.