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

[Lennart Regebro]

On Wed, Nov 19, 2008 at 14:53, Chris McDonough <chrism at plope.com> wrote:
> When martian scans packages (via the ModuleGrokker), eventually it winds up
> scanning modules that are defined via .pyc and .pyo file representations that do
> not have a corresponding .py source file.  This, at least in my configuration,
> leads to errors because these are typically modules left over after, e.g. a
> module rename, where the "old" .pyc file sticks around even though its source
> file has changed names and has new content.

Well. this is how python works. You can even distribute only pyc
files, if you want.
(We did that with EasyPyblisher for a while in fact).

I don't think Grok should try to circumvent this.

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