[Grok-dev] martian scan "bug" (feature?)

Malthe Borch mborch at gmail.com
Thu Nov 20 11:43:23 EST 2008

Lennart Regebro wrote:
> Well, that's true, but still, if you don't remove the pyc file, python
> will still thing the module is there. It is how python behaves, and
> I'm not at all sure it's a good idea to fight the language. :)

Martian is already if not fighting, then significantly altering its 
behavior, by importing modules automatically.

> True, it's a more significant issue with grok, and would be encoutered
> more often.

It shouldn't be encountered at all; .pyc is for library-code only, not 
code that has Martian-style components. You can hardly argue with that.


More information about the Grok-dev mailing list