Switch to ruff

[alifbe]

• Use ruff for code linting and formatting close Use ruff for code formatting/linting #429
• Update contributing documentation
• Remove sphinx pin

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (2a8cfa8) 98.77% compared to head (29e9a3e) 98.80%.

❗ Current head 29e9a3e differs from pull request most recent head 846350c. Consider uploading reports for the commit 846350c to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #430      +/-   ##
==========================================
+ Coverage   98.77%   98.80%   +0.02%     
==========================================
  Files          17       17              
  Lines        2701     2682      -19     
==========================================
- Hits         2668     2650      -18     
+ Misses         33       32       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mferrera]

I'm a bit concerned about performance implications of removing inplace=True from the dataframes. Maybe @berland should comment about this (he may also object to removing pylint stuff)

[alifbe]

I'm a bit concerned about performance implications of removing inplace=True from the dataframes. Maybe @berland should comment about this (he may also object to removing pylint stuff)

I didn't know that ruff doesn't replace pylint 😊

It seems like there are quite a few issues in main branch found by pylint. Instead of putting it back here, I am thinking to solve it in another PR. Created issue #431

[mferrera]

For what it's worth, I think pylint is typically used to get a sense of some code quality or improvements rather than making sure code satisfies all of its conditions. You'll almost never see pylint included in linting CI workflows for that reason. It's a good barometer but not necessarily a bar to meet.