Boids: Full refactor

[bozcar]

Group 23

[ageorgou]

Very nice, your version clearly shows what each part of the code does, through the method names and their docstrings.

Nice use of typing hints.

As some of the lines (especially when calling methods) are quite long, you could break them down, keeping one argument per line, and using some intermediate variables.
For example:

self.update_vel([(other.velocity['x']-self.velocity['x'])*scaling/number_of_boids, (other.velocity['y']-self.velocity['y'])*scaling/number_of_boids])

could become

self.updat_vel([
    (other.velocity['x']-self.velocity['x'])*scaling/number_of_boids,
    (other.velocity['y']-self.velocity['y'])*scaling/number_of_boids
])

or

x_velocity_diff = (other.velocity['x']-self.velocity['x'])*scaling/number_of_boids
y_velocity_diff = (other.velocity['y']-self.velocity['y'])*scaling/number_of_boids
self.update_vel(x_velocity_diff, y_velocity_diff)

[ageorgou]

I'm guessing this is a typo!

Suggested change

	self.position['x'] += self.velocity['y']
	self.position['x'] += self.velocity['x']

[ageorgou]

This line is quite long, and is repeated in the other method. Perhaps it could be extracted into its own method, such as can_see(self:Boid, other:Boid).