Changed distance calculation to treat space as a torus
Uhh changed to use vectors instead of passing around lots of x's and y's
Uh changed to use vectors to store positions and velocities
Merge branch '0.3' into 0.3.vectors

Conflicts:
	cells.py
	main.py
Ugh this is three times slower than without the Vector class but at least its fast with pypy
Fixed main.py that i broke
Nevermind it looks like Dalen's was faster because it didn't use toroidal distance checking and after fixing that both are too slow because cells won't cross the border to eat
Merge branch '0.3.vectors' into 0.4.dalen

Conflicts:
	cells.py
	environment.py
	main.py
	util.py
Merge branch '0.4.dalen' of github.com:NCFDev/cellular into 0.4.dalen
Screw vector.Vector; from vector import Vector has been amended to cells.py
Expressed my joy for vectors!
Fixed the table accidentally printing the task twice
Create lololol
Cells now move based on actual physics and utilizing vectors. Unfortunately, they have yet to determine when to slow down. Code highly unfinished.
Cells now slow down properly , but we've discovered they accelerate SUPERFAST. Like they make sonic the hedgehog look like a ROCK. I'm tired.
Merge branch '0.4.dalen' of github.com:NCFDev/cellular into 0.4.dalen
Vectors possibly working with new physics but too slow to tell. Bottleneck seems to be in distance_to_start_slowing_down.
I think it's fixed, idk. Fixed Vector and changed mass to 1. Also changed distance_to_start_slowing_down to calculate the distance the cell will move if it stops accelerating.
Merge branch '0.4.dalen' into 0.4
Cells.py changed locations from a tuple to point objects. This commit makes changes display.py to work with that new location structure