I suppose it's just that python implements the white spaces in a very slack way. i.e. the programmer has to have the self discipline to either stick to tab characters or an amount of spaces (in just the same way that programmers have to lay their code out in a tidy way even using ;} systems.) If you're coding for yourself it's probably not an issue but with a project like this you will find that one py file will contain a mixture of tabs and different number of space characters.BlackJack wrote:@paddyg: Why is meaningful indentation an extremely bad and retrograde step?
I would say that on fifty percent of the modifications I have made to the pi3d files I have got an 'unrecognised indent' error. At first I used geany's Document convert tab to spaces however that resulted in a vast amount of work as all the indentation becomes scrambled. Python lets you get away with a first indent of eight spaces then a second indent of two tabs (4 long each) then two tabs and one space then three tabs and five spaces then four tabs and one space. If you look through the pi3d.py code you will find things similar (though not so extreme).