I've got the same problem that Mark had in May: Metakit's build process
results in Mk4py.dylib, which Python doesn't recognize as a module it can
load. John Abel said that he had a workaround and I even found in the
archives where he asked the same question. But it seems that in both cases,
the workaround was sent off-list.
If someone would share a clue here, I'd be very grateful. It might be best
to send it to the list, for posterity.
Regards,
Matt
_____________________________________________
Metakit mailing list - [email protected]
http://www.equi4.com/mailman/listinfo/metakit
