New function to_python() / to_ruby()

[smortex]

Add two new utility functions to transform Puppet data structures into their corresponding representation in Python and Ruby.

These functions are aimed to help writing templates of Ruby / Python code when managing configuration files in these languages with Puppet. Quoting strings, managing undef can be a bit tedious:

EMAIL_USE_TLS = <%= String($taiga::back::email_use_tls, '%T') %>
EMAIL_HOST = <%= if $taiga::back::email_host { String($taiga::back::email_host, '%p') } else { 'None' } %>

These functions make this more readable:

EMAIL_USE_TLS = <%= $taiga::back::email_use_tls.to_python %>
EMAIL_HOST = <%= $taiga::back::email_host.to_python %>

This initial work took place in voxpupuli/puppet-python#616 but it was suggested to move the code in stdlib.

[puppet-community-rangefinder]

to_python is a function

that may have no external impact to Forge modules.

to_ruby is a function

that may have no external impact to Forge modules.

This module is declared in 319 of 578 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[bastelfreak]

looks good to me / the windows failures don't look related to the change.

[david22swan]

@smortex @bastelfreak
Windows failure seems to be a transient so gonna go ahead and merge.
Thanks for putting in the work, they seem like two pretty interesting functions.