Conversation
|
Performance benchmarks:
|
| # Reminder to update mesa-examples if the value below is changed. | ||
| target-version = "py311" | ||
| extend-exclude = ["docs", "build"] | ||
| extend-exclude = ["build"] |
There was a problem hiding this comment.
This addresses the large package size right? How much does it help?
There was a problem hiding this comment.
Do you mean line-length or am I missing something?
This put docs through the ruff linter and formatter, but I also ignored a lot (see per-file-ignores)
To address the line-length across Mesa we need to add to E501 to [tool.ruff.lint] select and if we want to be compliant with pep 8 we would set the line-length to 79. I am trying to figure out why I am still get a discrepancy between the pre-commit on my machine and the pre-commit in github actions.
There was a problem hiding this comment.
Sorry I confused this with another comment, you're right.
Personally I won't worry too much about this.
|
Thanks Tom! @martibosch could you checkout the rendered docs and confirm this resolves your comments? |
|
JOSS Intro Tutorial Fix - update line lengths (to 79) in tutorials - edit intro tutorial per JOSS requests - edit visualization tutorial per JOSS request - update pyproject.toml to autofix code cell lengths - remove pyprojoect.toml spurious assumption about it being taken care of black formatting - add .virtual documents to .gitignore - test_agent was reformatted due to pyproject.toml changes - remove upper left version switcher - update email in pyproject.toml
|
It was added in this PR: If it’s easier, we could also just reverse this commit: 8d1dd13 |
I removed yesterday and it was added to the PR. Every time I mess with the docs its like I have to relearn the whole process. Ohh well maybe this time it will stick. :) |
EwoutH
left a comment
There was a problem hiding this comment.
Sounds good, merge when you’re ready.
Summary
Updates for JOSS paper #2666
Motive
Per request
Implementation
Additional Notes
The line-length is not formatting in pyproject.toml as discussed here what I am confused about is why it is only identifying some issues on my computer (like 1) but lots of issues when the workflow starts.So I will need to dig into this