Grokinstallation corrupts when editing source remotely over AFP

[jhsware]

If I edit a source file on my production server remotely over an AFP-connection the project is corrupted (I use Textmate). The only solution is to reinstall a new grokproject and copy the source files etc, but it is a royal...

Solution (Martijn and PvW:

If so, I suspect the problem can be fixed in scan.py, in the method 'getSubModuleInfos'.
There's a for loop there:
 for entry in sorted(os.listdir(directory)):
if you add as the first line in that loop the following:
  if entry.startswith('.'):
      continue
that might fix matters. Should be safe enough to add this to Martian, as Python modules aren't supposed to start with a dot.
In fact, module names have to start with an alphabetic character or an underscore, so we can expand this rule to the following:

  if not entry[0].isalpha() and entry[0] != '_':
      continue

PvW: Yup, including a test with some of those MacOSX generated resource fork files :).

I guess we could even expand this to testing with a regular expression whether it's a valid Python module name at all...

PvW: Not such a bad idea.

[Martijn Faassen (faassen)]

Did you try out the fix I suggested?

[jhsware (sebastian-urbantalk)]

I only tried the second one, but it worked perfectly! I just wanted to
file a bug so it isn't forgotten.

Mvh Sebastian
08-410 280 41
0707- 577 858

17 jun 2008 kl. 14.23 skrev Martijn Faassen:

> Did you try out the fix I suggested?
>
> --
> Grokinstallation corrupts when editing source remotely over AFP
> https://bugs.launchpad.net/bugs/240607
> You received this bug notification because you are a direct subscriber
> of the bug.