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

Martijn Faassen faassen at startifact.com
Fri Nov 21 03:03:41 EST 2008

Fernando Correa Neto wrote:
> Hey,
> On Thu, Nov 20, 2008 at 2:10 PM, Lennart Regebro <regebro at gmail.com> wrote:
>> 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 main point is that the scan module needs more control on what it
> groks. It is so greedy that it was grokking even hidden files created
> by a samba share.

+1 on a patch that fixes this. We've had a discussion earlier this year. 
I'm fine with something heavy duty which just ignores *.py files that 
start with a period (.), as those are really not files you'd like to 
see. If there are other things like editor droppings we should be 
ignoring, let's please ignore them too.



More information about the Grok-dev mailing list