[Grok-dev] martian scan "bug" (feature?)
Fernando Correa Neto
fcdoth at gmail.com
Thu Nov 20 11:59:06 EST 2008
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.
Even if you were to distribute your code as pyc or pyo, it'd be just a
matter of setting a flag or something so it could explicitly scan for
pyc or pyo.
I don't believe this is desired... otherwise explicitly desired.
More information about the Grok-dev