[Myghty-users] Transitioning to Mako

[Deron M. <der...@gm...>]

I guess I've been out of it, but I just noticed that Myghty is now in
maintenance mode.  I didn't see any announcement, but only
saw it on the website.  There is mention of Mako as a possible future.

I've reviewed the Mako online documentation, and I am really
liking what I see.  It seems to fix most of the inconsistent syntax
that bothered me in Myghty, and appears to just be a cleaner
architecture (I guess that happens when you get a chance to
start over :)

However I'm trying to figure out how I can eventually get off of
Myghty, and there's things that Mako seems to be missing
(probably intentionally ?).  One of my biggest issues is I NEED to
be able to run on top of mod_python.  This is because I have a
lot of "raw" mod_python handlers running at different Apache
request and filter phases (not just the content or "handler" phase).
And my Myghty apps communicate with them via the low-level
req object.  I just don't see how to do that yet.

There's other things as well that I know I need to change
(such as a reliance on the dhandler stuff), but they don't perplex
me as much (yet).

Is there any additional information someplace to describe in
more detail strategies for migrating from Myghty to Mako, or
whatever else might be needed?  There seems to be about a
million different Python+Web projects and very few are documented
in any basic way so that an outsider can even determine what it
is that they "do" before being dumped right into the API docs.

So, is Mako even supposed to be a Myghty successor, or the
key component of one?   And is this the place to ask these
questions, or the Mako mailing lists, or cross-posted?

Deron Meranda