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

[Lennart Regebro]

On Thu, Nov 20, 2008 at 15:58, Chris McDonough <chrism at plope.com> wrote:
> Lennart Regebro wrote:
>> Well. this is how python works. You can even distribute only pyc
>> files, if you want.
>
> Yup, but it's not the usual case.

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. :)

> The difference here is that Martian imports everything it finds, whereas in
> normal operations a "stray" pyc might exist but would never be imported or
> otherwise used.

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

-- 
Lennart Regebro: Zope and Plone consulting.
http://www.colliberty.com/
+33 661 58 14 64