This is necessary to make rolling releases of new watchman versions across
users.
Details
Details
- Reviewers
- None
- Group Reviewers
hg-reviewers
Diff Detail
Diff Detail
- Repository
- rHG Mercurial
- Lint
Lint Skipped - Unit
Unit Tests Skipped
Event Timeline
Comment Actions
Overall I like the feature. But the class initialization logic is wonky. That's not your fault: you happen to be wading into a mess. Since it looks like there will be a v2 on this series, I'd encourage you to add some inline comments about the __init__ mess at the least, or ideally refactor it so the code is cleaner.
hgext/fsmonitor/pywatchman/__init__.py | ||
---|---|---|
569–573 | Why the nested __init__? Perhaps this initialization code could be cleaned up so we are assigning an instance instead of a class to self.transport? |
hgext/fsmonitor/pywatchman/__init__.py | ||
---|---|---|
569–573 | I see several ways to refactor the code around:
I have a small preference for solution 1). Solution 4) seems the most heavyweight |
Why the nested __init__?
Perhaps this initialization code could be cleaned up so we are assigning an instance instead of a class to self.transport?