[Grok-dev] What's stopping five.grok from using "new" martian

[Martin Aspeli]

Hi,

I'm a little sick of this happening:

  - I create a grokked module foo.py and add a component registration 
(e.g. a view) and start up Zope

  - I decide to rename foo.py to bar.py

  - Grok chokes with a configuration conflict, because foo.pyc is lying 
around, and contains the same registration

AFAIR, non-grokking of pyc files has landed in martian, but isn't usable 
in five.grok and/or the version of grokcore.* it uses.

Can anyone remember what the status is? I'd like to get this fixed.

Martin

-- 
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book