Hi Kevin,
Yes tabnanny does complain about line 38. It does belong to the
__init__ function just as line 42 does. Generally when you define a
method everything between one def and the next belong to the same
function (unless its a local function or something). Obviously your
editor is not set to 8 space tabs which is the normal assumption by
the python interpreter so thats why it doesnt complain.
Its true that its probably bad to have tabs and spaces mixed, but you
should also set your tab to 8 spaces in your editor.
Michael.
On Fri, Jan 16, 2009 at 3:51 PM, kevin thompson
<kevin.david.thompson(a)gmail.com> wrote:
I was just looking over the code for the
FileAddressSpace class and I didn't
understand something. I jumped into the IRC room and asked the question,
but nobody was home.
I'm not sure what I'm missing here, but something doesn't seem right to me.
When I look at the __init__ function, it seems like the whitespace is all
messed up. For example, lines 37 and 40 are indented with 8 spaces, but
lines 38 and 39 are indented with tabs. Line 42 doesn't even appear to be
part of the __init__ function. I would think that python would throw an
error about this, but it doesn't seem to mind. What am I missing?
Kevin
_______________________________________________
Vol-dev mailing list
Vol-dev(a)volatilityfoundation.org
http://lists.volatilityfoundation.org/mailman/listinfo/vol-dev