Closed studioj closed 2 years ago
should i remove the 2.7 part? I see you disabled the build (but maybe thats because it was failing
The 2.7 removal was mostly because of the official Python abandonment of 2.7, so it makes sense to no longer worry too much about it. I think we can remove 2.7 now.
shoudl be ready to merge
From a quick look, it seems the Travis tests are failing because of the new crypto modules written in Rust. I'll need to add a Rust compiler to the config.
@rbanffy one remaining :-)
@rbanffy i dont know how important that dist: bionic was => but removing it made it work
Stale pull request message
I think this is still a valid PR @rbanffy I reopened.
Agreed. If there is a need for this, we need to reassess.
❌ Merging this PR will decrease code quality in the affected files by 1.25%.
Quality metrics | Before | After | Change |
---|---|---|---|
Complexity | 0.44 ⭐ | 0.50 ⭐ | 0.06 👎 |
Method Length | 30.95 ⭐ | 37.38 ⭐ | 6.43 👎 |
Working memory | 5.22 ⭐ | 5.30 ⭐ | 0.08 👎 |
Quality | 89.23% ⭐ | 87.98% ⭐ | -1.25% 👎 |
Other metrics | Before | After | Change |
---|---|---|---|
Lines | 138 | 174 | 36 |
Changed files | Quality Before | Quality After | Quality Change |
---|---|---|---|
tests/test_pip_chill.py | 89.23% ⭐ | 87.98% ⭐ | -1.25% 👎 |
Here are some functions in these files that still need a tune-up:
File | Function | Complexity | Length | Working Memory | Quality | Recommendation |
---|
The emojis denote the absolute quality of the code:
The 👍 and 👎 indicate whether the quality has improved or gotten worse with this pull request.
Please see our documentation here for details on how these metrics are calculated.
We are actively working on this report - lots more documentation and extra metrics to come!
Help us improve this quality report!
Explain reassess please. :) Can I do something? Or do you asume the project complete?
Stale pull request message
as requested PR for having tests runnable on windows and having the 2.7 build pass