idlesign
Rutracker direct proxies patch
Added proxy parameters into several RuTrackerTracker (and deeper) methods. It might be useful in the case of proxy usage exactly in a specific RuTracker requests. Tunnel functionality is not affected (can be used both simultaneously).
Pull Request Test Coverage Report for Build 125
- 7 of 11 (63.64%) changed or added relevant lines in 3 files are covered.
- No unchanged relevant lines lost coverage.
- Overall coverage decreased (-0.02%) to 62.776%
| Changes Missing Coverage | Covered Lines | Changed/Added Lines | % |
|---|---|---|---|
| torrt/utils.py | 3 | 4 | 75.0% |
| torrt/trackers/rutracker.py | 2 | 5 | 40.0% |
| <!-- | Total: | 7 | 11 |
| Totals | |
|---|---|
| Change from base Build 124: | -0.02% |
| Covered Lines: | 968 |
| Relevant Lines: | 1542 |
💛 - Coveralls
Thank you.
Before we proceed, can you elaborate on why do you want to apply proxies exclusively to rutracker, but not for others, what's the usecase?
Just because I use only RuTracker :) I use some parts of torrt in my custom scenarios where sometimes it needs to switch proxy "on the fly" for better load distribution among proxies. I think it's not difficult to patch all of methods, but I inspected only calls I used and didn't look into other parts of code.
I think it's not difficult to patch all of methods, but I inspected only calls I used and didn't look into other parts of code.
Ok, let's introduce it. You'd need to ensure CLI configuration of rutracker won't fail, though.