Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fixed DeprecationWarning #739

Merged
merged 12 commits into from
Aug 1, 2023

Conversation

uri-rodberg
Copy link
Contributor

fixed DeprecationWarning

Fixes #727

@codecov
Copy link

codecov bot commented Aug 1, 2023

Codecov Report

Merging #739 (2a8b071) into master (eb2420d) will not change coverage.
Report is 2 commits behind head on master.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #739   +/-   ##
=======================================
  Coverage   74.11%   74.11%           
=======================================
  Files          30       30           
  Lines        1700     1700           
=======================================
  Hits         1260     1260           
  Misses        440      440           
Files Changed Coverage Δ
sorl/__init__.py 100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@uri-rodberg
Copy link
Contributor Author

Can you please review this PR?

@uri-rodberg uri-rodberg merged commit c7b4531 into jazzband:master Aug 1, 2023
28 checks passed
@claudep
Copy link
Contributor

claudep commented Aug 1, 2023

It's not very nice to merge such pull requests and pollute the master git history with 12 commits to only change one file. Please next time, at least squash the commits when merging, as long as the individual commits do not make sense to figure by themselves in the main history.

@uri-rodberg
Copy link
Contributor Author

It's not very nice to merge such pull requests and pollute the master git history with 12 commits to only change one file. Please next time, at least squash the commits when merging, as long as the individual commits do not make sense to figure by themselves in the main history.

OK, next time. Let me know if you want to revert this time.

@claudep
Copy link
Contributor

claudep commented Aug 1, 2023

No need to revert, just take care in the future. Ideally, each commit in a good git history should pass the test suite. It's not just nit-picking, it has a real value when for example you want to git bisect a repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DeprecationWarning from setuptools 67.5.0 and above
4 participants