- 
                Notifications
    You must be signed in to change notification settings 
- Fork 706
chore: drop support for Python 3.10 and add support for Python 3.13 #7935
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
Conversation
| Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@            Coverage Diff             @@
##           master    #7935      +/-   ##
==========================================
- Coverage   99.69%   99.68%   -0.01%     
==========================================
  Files         543      543              
  Lines       55964    55964              
==========================================
- Hits        55791    55790       -1     
- Misses        173      174       +1     ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
 | 
add stories for pylint tracking
| Should we update the required tests now? | 
| 
 Yes, or we can do it after it merges? | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
| 
 We can do it after, but then branch would require force merge by admin | 
| Just wondering if we could get this PR merged? It's a blocker for the FTQC. Thanks @andrijapau | 
| 
 Yes, just waiting on #7996 (review) to merge in order to free up CI to merge this PR. | 
As the name suggests 😄 .
Side effects to note,
pylintwas bumped to latest (3.3.7) in order to be compatible with3.11. Since the minimum supported version (3.0.0) had false negatives / positives which were subsequently fixed in later versions it makes sense to skip to latest. Some errors needed to get suppressed at thepylintrclevel as there were too many to tackle at once (or require discussion liketoo-many-positional-arguments.blackandisortto latest.[sc-95555]
[sc-91391]