-
Notifications
You must be signed in to change notification settings - Fork 179
Sync pyproject with mesa #268
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
Sync pyproject with mesa #268
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
# Conflicts: # examples/boltzmann_wealth_model_network/boltzmann_wealth_model_network/model.py # examples/boltzmann_wealth_model_network/boltzmann_wealth_model_network/server.py # examples/color_patches/color_patches/model.py
@derkweijers thank you for the contribution. Can you rebase and squash? And also fix the checks. |
I spoke too soon. It looks like #271 fixes the ruff errors. |
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.
Thanks @derkweijers!
This PR syncs parts of the
pyproject.toml
from the Mesa repo to this mesa-examples repo. It also updates some project/contact info.The PR is a bit tricky since it introduces new Ruff rules. For example, upper-case variables are discouraged. Sometimes it makes sense though (for example if it's part of a formula). I've added ignore flags where applicable and fixed the other cases.
Furthermore, Ruff rule B008 was triggered a couple of times. That's fixed in this PR as well, but I would appreciate opinions on how it's solved.
I've opted out of the Docstrings rule since that might be an entire PR on its own.