Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make use of unsafe yaml forward compatible #267

Merged
merged 1 commit into from
Mar 5, 2019
Merged

Make use of unsafe yaml forward compatible #267

merged 1 commit into from
Mar 5, 2019

Commits on Mar 5, 2019

  1. Make use of unsafe yaml forward compatible

    The forthcoming 5.x release of PyYMAL changes how unsafe
    yaml is managed [1]. The default for gabbi is to safe
    load but the option has been present to unsafe load if
    code-executing functionality was desired. The way to
    achieve that in 5.x and beyond is more explicit than
    prior versions.
    
    In this change we adjust the unsafe loading to work with
    both 3.x and the as yet unreleased 5.x.
    
    Fixes #266
    
    [1] https://msg.pyyaml.org/load
    cdent committed Mar 5, 2019
    Configuration menu
    Copy the full SHA
    2ef0eee View commit details
    Browse the repository at this point in the history