I wrote this code for a Python job interview (last minute).I was told I would have the code reviewed. It didn't happen!Please could you review this and get back to me on what I could have done better etc. Any help would be most appreciated.

#TODO:#1) show needs to cater for new cell object#2) new region array instead of imgarray (region array = dictionary type thing, region(object, with colour value), then list all cells by reference), new objection, has new region with colour, look for all regions with colour X change to Y, should then change ref value in cell (hack to region), then re-render (i.e. new show method)

#Changed the way cell is; now, 3dim array. Layers needed. Region will have colour still and each object created will be part of a new region.#created diagram to sort it out what to do#removed new layer (3d array). Have id for region now.

Coding layout conventions: Thanks! Normally it would look ok. I'm not sure what happened to the code rendering in this. Anyway, in Notepad++ in Python viewing mode, I think it's slightly easier to read. I do agree to the 'readable' code convention, but I disagree with convention nazism (Godwin's law). I've spotted a couple of things I could do with rearrangement with the code to make it slightly more concise, but from my coding experience (10 years), I've seen a lot worse.Conclusion: I agree that the code shown here is difficult to read (no fault of anyone's, but my own; should have reviewed before submit). I wave the flag of 'I give up' and go on my merry way.

Thank you for your help, I appreciate any guidance, and this hit the spot.