rht

The `batch_run` defaulting to 1 CPU has a major impact on the tutorial simplification for Windows, and so can't be reverted easily if you want a release without breaking changes.

Alternative interpretation: https://0ver.org/. In this sense 0.10.0, is still a major release.

Nice catch. I forgot the existence of #1333 (I thought I was missing a breaking change, but couldn't pinpoint it). > First of all we never stated we use semver....

> The semver specification is specifically about API compatibility and this does not break API compatibility. The default value of an argument being changed in a public function in https://github.com/projectmesa/mesa/blob/c2103830cd9054bdb5437a712e1add1e474daf95/mesa/batchrunner.py#L39....

I have also stated my other reason to go 1.0.0, i.e. because of how people expect a version bump should happen in their requirements.txt when they do `~= 0.9`.

That PR is merged into [projectmesa:base_ci_cache_experiment](https://github.com/projectmesa/mesa/tree/base_ci_cache_experiment), not the main branch, and so can be ignored.

Check if your model's `self.running` (https://github.com/projectmesa/mesa/blob/main/mesa/model.py#L32) remains `True`. If it is `False`, the model is no longer running.

This is based on @dmnfarrell 's awesome [blog post](https://dmnfarrell.github.io/bioinformatics/abm-mesa-python).

```jsx ``` Yes, this is more readable. We could approximate it using vanilla JS's backticks, but it's not semantic. Regarding with using React, I assume that you want to use...

> Display the server inline, which I never managed to do reliable. This problem is documented in https://github.com/projectmesa/mesa/discussions/1259.