-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
yaml.constructor.ConstructorError: could not determine a constructor for the tag #811
Comments
@facelessuser could this be related to some upstream change in the Pymdown Extensions package? See:
|
btw, line 49 is
I have no idea whether I need it, just copied from this repo |
I'm in the woods camping at least till the end of the week. I won't be able to look at this until I get back. I will say you can't use the svg output unless you are using the old emojione assets or the twemoji assets. But we do test for svg and it is currently passing: https://github.com/facelessuser/pymdown-extensions/blob/master/tests/extensions/emoji/tests.yml#L48. |
@facelessuser no hurry, enjoy the time off! I'm a bit jealous :-) |
I cannot reproduce this issue. I tried using Something is wrong with either your yaml config or something with your local setup. Maybe even with your I did not install |
Hmm, maybe a corrupted cache then? Had some fun with this problem on Travis. |
Could be... there is a way to install without using the cache with pip. As far as pymdown-extensions is concerned, I've made no changes in regards to |
I build it via wercker on official alpine-based python 3 image, the build file can be found at https://github.com/wodby/php-docs/blob/master/.wercker.yml. The issue has been resolved after I deleted |
Okay, so as you say your issue is resolved (and it sounds like a cache inconsistency problem), I'm closing this issue. |
Actually, the latest automated build from https://hub.docker.com/r/squidfunk/mkdocs-material/ ( |
This may be an issue with the docker image then, but I don't see an issue directly with pymdown-extensions unless some new evidence that shows otherwise surfaces. I'll let @squidfunk investigate this for now. |
Will investigate asap. |
I can confirm this issue with the latest Docker image. However, when I rebuild the image locally, everything works as expected. I will now try to rebuild the Docker image on Travis, maybe it was just some kind of hiccup / inconsistency. |
The image is fixed now. I will re-open this issue to remember checking after the next release build if the Docker image works - I just pushed my local build because I lack the time for debugging the Travis build at the moment. |
BTW @facelessuser the bug seems to be entirely related to the YAML parser, because my google_analytics:
- !!python/object/apply:os.getenv ["GOOGLE_ANALYTICS_KEY"]
- auto results in:
However, thanks for your time investigating! |
markdown_extensions:
- pymdownx.emoji:
emoji_generator: !!python/name:pymdownx.emoji.to_svg becomes: markdown_extensions:
- pymdownx.emoji:
emoji_generator: "!!python/name:pymdownx.emoji.to_svg" |
Using quotes will make it pass, but not treat the entry as a function, it will be treated as a string. |
Hmm okay, I don't really know much Python to debug this properly. For what it looks like it is almost certainly related to different versions of PyYaml. Sometimes 3.10 gets installed, sometimes 3.12, locally I have >4.1. Very weird. |
Hmm, I'll play with it and see what I see when I get a chance. |
So it seems some things have changed with pyyaml and safe mode (safe mode would restrict things like |
FYI, I don't see this issue with 3.12 pyyaml. |
4.2b1 seems to be the one at fault. It's the one I can reproduce the issue on. 4.2b2+ seems fine. Is there a dependency forcing a beta of pyyaml? 3.12 should be the current stable version being installed. It looks like there is nothing stable above 3.x currently. I would not force pyyaml >4.1. Maybe there was a stable 4.1 briefly, and they might have released it and then took it down when they discovered issues... |
Thanks for taking the time to debug this. It's really strange that the best got installed on my local system, while Travis keeps installing 3.10 or 3.12. I fixed the Docker image yesterday by building and pushing it from my machine, but I'll leave this issue open until the next release and check again if the issue still persists. |
Seems to be fixed, just rolled out 2.9.4 and checked the Docker image - it's working. |
Starting today I'm getting the following error during a build, same for python 2 and 3.
https://app.wercker.com/Wodby/php-docs/runs/build/5b3365e4a296ce0001c90842?step=5b3365ec37b4370001c4f556
My build command:
mkdocs.yml:
The text was updated successfully, but these errors were encountered: