-
Notifications
You must be signed in to change notification settings - Fork 526
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
Implicit Resolvers do not appear to work with PyYAML 5.1 #294
Comments
After looking around this appears to be the same issue as #266 , I confirmed it does work with |
@ingydotnet I suggest to reopen because |
I'm reopening this for @ingydotnet |
I created #305 to fix this |
We just released 5.2b1 https://pypi.org/project/PyYAML/5.2b1/ which should fix this. |
We released 5.2: https://pypi.org/project/PyYAML/5.2/ |
Closing. Please reopen if necessary. Thanks! |
I've noticed that with PyYAML 5.1 implicit resolvers do not seem to work at all. Using this example script:
I confirmed that w/ 3.13 we correctly get the
uuid.UUID
object, while it is a string with 5.1 is it just the string'UUID(6a02171e-6482-11e9-ab43-f2189845f1cc)'
. The way I found this was that it broke the environment variable interpolation thatelasticsearch-curator
provides.Sorry if this is a duplicate, I searched around and could not find an equivalent issue.
The text was updated successfully, but these errors were encountered: