According to this later blog post (linked from the one you gave, actually),
it is: http://lucumr.pocoo.org/2008/5/31/the-new-ghrml-haml-for-genshi

It may or may not be faster to start with GHRML when developing a new Haml
in Python, but that's not what Brajeshwar was asking. He was asking about
existing Haml implementations in Python, of which there are none that aren't
long-dead.

On Mon, May 3, 2010 at 2:48 PM, dreamcat four <[email protected]> wrote:

> Thats not the right place - look
>
> Blog post:
> http://lucumr.pocoo.org/2008/2/15/ghrml-haml-for-genshi
>
> Comment #8
>
> "The sourecode is part of the pocoo sandbox hg repository: hg clone
> dev.pocoo.org/hg/sandbox"
>
> With minor correction to the URL:
>
> $ hg clone http://dev.pocoo.org/hg/sandbox
>
> Even if not actively maintained, it still seems rather less effort to
> take the existing parser code and to fix it up. Otherwise, im guessing
> it would have to be a case for a python developer (who also know ruby)
> to do a clean port from ruby -> python? That would make most sense
> only if had tried and couldnt rework the ghrml lib.
>
>
> On Mon, May 3, 2010 at 9:41 PM, Nathan Weizenbaum <[email protected]>
> wrote:
> > The GHRML website seems to be down, and last time I checked on it when
> the
> > site was up it seemed to be unmaintained. Looking deeper, the download
> page
> > is still up (http://www.ghrml.org/download/), and the latest package is
> from
> > November 2008. That all says "dead project" to me.
> >
> > On Mon, May 3, 2010 at 5:17 AM, dreamcat four <[email protected]>
> wrote:
> >>
> >> Also,
> >>
> >> You said you did a web search. But like the 3rd result in the list for
> >> "haml python" is GHRML which seems the most appropriate match for your
> >> needs. So why not also mention your reasons for dismissing GHRML over
> >> haml?
> >>
> >> On Mon, May 3, 2010 at 1:00 PM, Nathan Weizenbaum <[email protected]>
> >> wrote:
> >> > The thing about Haml, as opposed to Sass, is that generally when
> you're
> >> > writing Haml templates you want them to integrate with the language
> >> > you're
> >> > writing the backend in. While this could be done via JRuby and Jython,
> >> > you'd
> >> > still need to use Ruby to do the accessing. Many languages have their
> >> > own
> >> > native implementations of Haml, but unfortunately the Python
> >> > implementation
> >> > seems to be long dead.
> >> >
> >> > If you're just generating static pages, you're in a better position.
> >> > There
> >> > are several tools out there that support generating of static sites
> with
> >> > Haml; probably the most widely-used is StaticMatic. This does assume
> >> > some
> >> > degree of Ruby-friendliness, but it's the best I know of for
> generating
> >> > purely static sites.
> >> >
> >> > On Mon, May 3, 2010 at 1:52 AM, Brajeshwar <[email protected]>
> wrote:
> >> >>
> >> >> Hi,
> >> >>
> >> >> I'm sure I'm late to the party but I want to start off with HAML.
> >> >> I've been using and have so far converted 3 of our team and another
> to
> >> >> SASS for all CSS requirements.
> >> >>
> >> >> With Sass, we use Compass and we consider it to be a boon for the
> team.
> >> >> However for HAML, what are the options to use it as a standalone
> >> >> module.
> >> >>
> >> >> We primarily use Python, Clojure and googling around didn't help much
> >> >> on how to integrate HAML into the Python stack.
> >> >> The ideal solution would be something like how Compass does to SASS,
> >> >> the ability to run standalone inside our main app.
> >> >>
> >> >> Any help would be appreciated.
> >> >>
> >> >> Regards,
> >> >> Brajeshwar
> >> >> _____________________
> >> >>
> >> >> --
> >> >> You received this message because you are subscribed to the Google
> >> >> Groups
> >> >> "Haml" group.
> >> >> To post to this group, send email to [email protected].
> >> >> To unsubscribe from this group, send email to
> >> >> [email protected]<haml%[email protected]>
> .
> >> >> For more options, visit this group at
> >> >> http://groups.google.com/group/haml?hl=en.
> >> >>
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google
> >> > Groups
> >> > "Haml" group.
> >> > To post to this group, send email to [email protected].
> >> > To unsubscribe from this group, send email to
> >> > [email protected]<haml%[email protected]>
> .
> >> > For more options, visit this group at
> >> > http://groups.google.com/group/haml?hl=en.
> >> >
> >>
> >> --
> >> You received this message because you are subscribed to the Google
> Groups
> >> "Haml" group.
> >> To post to this group, send email to [email protected].
> >> To unsubscribe from this group, send email to
> >> [email protected] <haml%[email protected]>
> .
> >> For more options, visit this group at
> >> http://groups.google.com/group/haml?hl=en.
> >>
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Haml" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected] <haml%[email protected]>.
> > For more options, visit this group at
> > http://groups.google.com/group/haml?hl=en.
> >
>
> --
> You received this message because you are subscribed to the Google Groups
> "Haml" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected] <haml%[email protected]>.
> For more options, visit this group at
> http://groups.google.com/group/haml?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Haml" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/haml?hl=en.

Reply via email to