Part of refactor where we make things more arranged and integrated into single
UpgradeOperation class.
Details
- Reviewers
mharbison72 - Group Reviewers
hg-reviewers - Commits
- rHGaba979b1b90b: upgrade: move `printrequirements()` to UpgradeOperation class
Diff Detail
- Repository
- rHG Mercurial
- Branch
- default
- Lint
No Linters Available - Unit
No Unit Test Coverage
Event Timeline
mercurial/upgrade_utils/actions.py | ||
---|---|---|
574–585 | should we put this into _ attribute to avoid clutting the "public" API of the object ? (and maybe compute them within the print_requirements method? |
mercurial/upgrade_utils/actions.py | ||
---|---|---|
574–585 |
Agreed.
Maybe they can be used at more places, hence leaving them in __init__() for now. |
mercurial/upgrade_utils/actions.py | ||
---|---|---|
574–585 | I am more leaning toward moving them in init when the "maybe" become a certitude. Or do you have actual code using that down the line ? |
should we put this into _ attribute to avoid clutting the "public" API of the object ? (and maybe compute them within the print_requirements method?