I would be impressed/worried if they were writing it in something else

________________________________

From: Matt Shin [mailto:notifications@github.com] 
Sent: 04 February 2013 16:28
To: metomi/rose
Cc: Fitzpatrick, Ben
Subject: Re: [rose] #419, #420: upgrading, upgrade macro development,
upgrade documentation (#431)



In doc/rose-api.html:

> @@ -499,13 +503,11 @@ <h2 id="macro">Rose Macros</h2>
>      trigger changing and type checking.</p>
>  
>      <p>This section explains how to add your own custom macros to
transform and
> -    validate configurations. Upgrade macros are covered in a
different section -
> -    they are a special type of custom macro and (will be) described
in
> -    <a href="rose-rug-advanced-topics.html">Advanced Topics</a>.</p>
> -    
> -    <p>Macros should be written in Python. They can be
> -    run within <code>rose config-edit</code> or via <code>rose
> -    macro.</code></p>
> +    validate configurations. See <a href="#upgrade">Upgrade Macro
API</a> for
> +    upgrade macros.</p>
> +
> +    <p>Macros should be written in Python. They can be run within
<code>rose

Probably unrelated to this change, but I think we ought to soften
statements such as Macros should be written in Python. We are providing
a Python API, but it does not matter what language a developer uses to
write the guts of their macro.

-
Reply to this email directly or view it on GitHub
<https://github.com/metomi/rose/pull/431/files#r2878456> . 

 
<https://github.com/notifications/beacon/PlVaVh46Oxl2lylB_4sPDahOaVKrGyc
RDTVCsloLqsXEeP7SzoiAXfLNJm1Me5SO.gif>