For PyOxidizer, we'll need to read the default configs using the
resources module. This prepares for putting that call in rcutil.
Details
Details
- Reviewers
- None
- Group Reviewers
hg-reviewers
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
Comment Actions
The patch seems functionally correct. But I have a question about whether this is the desired approach. See inline comment.
mercurial/rcutil.py | ||
---|---|---|
102 | Do you think it would be better to change the return type to expose a resource type, which the caller can resolve accordingly? Or maybe do away with leaving it up to the caller to open and read paths? It just feels weird for some I/O to be performed in this function while some I/O is deferred to the caller. But I don't have this code paged in, so maybe my comment is off base. |
Do you think it would be better to change the return type to expose a resource type, which the caller can resolve accordingly? Or maybe do away with leaving it up to the caller to open and read paths? It just feels weird for some I/O to be performed in this function while some I/O is deferred to the caller.
But I don't have this code paged in, so maybe my comment is off base.