Skip to content

Conversation

@fchapoton
Copy link
Contributor

This is trying to fix our broken CI, where pyright complains about the type of PariError.

📝 Checklist

  • The title is concise, informative, and self-explanatory.
  • The description explains in detail what this PR is about.

@github-actions
Copy link

github-actions bot commented Nov 3, 2023

Documentation preview for this PR (built with commit 76196ad; changes) is ready! 🎉

@fchapoton fchapoton requested a review from tobiasdiez November 3, 2023 15:13
Copy link
Contributor

@tobiasdiez tobiasdiez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for taking the initiative. Your fix works and looks good to me (Thus marking it as blocker).

However, it reverts the changes of #36271 so I'm not sure if @mkoeppe is happy with it.

@mkoeppe
Copy link
Contributor

mkoeppe commented Nov 3, 2023

It's fine for now, I'll find a solution that is compatible with pyright in #35095, where this change was cherry-picked from.

@vbraun vbraun merged commit 4533ffb into sagemath:develop Nov 5, 2023
@fchapoton fchapoton deleted the fix_pyright_ci branch November 5, 2023 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants