Replies: 3 comments 3 replies
-
We should start to deprecate Edit: not necessary anymore after #1546 |
Beta Was this translation helpful? Give feedback.
0 replies
-
Since those changes are already in the main branch, would that mean the next release will be major one (2.0) instead of a minor one (1.2)? |
Beta Was this translation helpful? Give feedback.
2 replies
-
I believe this is one, yes? #1524 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm compiling a list of breaking changes we should do for Mesa 2.0.
SingleGrid.position_agent(agent, x, y)
should be deprecated in favor ofplace_agent
andmove_to_empty
.position_agent
is error-prone. E.g. A bug has existed in the Schelling example for a very long time, where the number of agents in the scheduler does not match the number of agents in the grid. This is only discovered recently and fixed in fix: position_agent: Enforce type of x and y #1509.Grid.get_neighborhood
must raise an error when position is out of bound, where currently it silently returns an empty list Make Grid.get_neighborhood faster #1476 (comment). PR: Raise exception when pos is out of bounds in Grid.get_neighborhood #1524get_neighbors
inNetworkGrid
is more equivalent toget_neighborhood
in the other grid classes. Implementget_neighbors
andget_neighborhood
that are consistent with other grid classes, as stated in breaking: NetworkGrid: modify get_neighbors and create get_neighborhood #1542Debatable:
model.grid
tomodel.space
examples: Rename model.grid to model.space #1344Beta Was this translation helpful? Give feedback.
All reactions