Skip to content
This repository was archived by the owner on Apr 14, 2021. It is now read-only.

Removed self-hosted YAML Serializer and PsychedYAML#6536

Closed
hsbt wants to merge 3 commits intomasterfrom
remove-self-hosted-yaml
Closed

Removed self-hosted YAML Serializer and PsychedYAML#6536
hsbt wants to merge 3 commits intomasterfrom
remove-self-hosted-yaml

Conversation

@hsbt
Copy link
Copy Markdown
Member

@hsbt hsbt commented May 17, 2018

What was the end-user problem that led to this PR?

It is not compatible with YAML spec of the standard library of Ruby.

I did revert a feature in last year: ruby/psych#336

What was your diagnosis of the problem?

YAMLSerializer was introduced from bfd4be3

I'm not sure why that was required.

What is your fix for the problem, implemented in this PR?

Removed YAMLSerializer. and use YAML provided by pyched_yaml.

@segiddins
Copy link
Copy Markdown
Contributor

It is required since YAML is in a gem, and we load the list of plugins & settings before Bundler.setup, so using the Psych gem will mean no Bundler users can choose what version of pysch they use

@hsbt hsbt force-pushed the remove-self-hosted-yaml branch from 1a26d67 to 6eda701 Compare June 28, 2018 16:06
@hsbt hsbt force-pushed the remove-self-hosted-yaml branch from 6eda701 to 9cdaaa3 Compare October 17, 2018 02:48
@hsbt hsbt force-pushed the remove-self-hosted-yaml branch from 9cdaaa3 to d1f2f87 Compare March 14, 2019 12:25
@hsbt
Copy link
Copy Markdown
Member Author

hsbt commented Mar 14, 2019

I know the problem that is psych activation problem. But Bundler already uses psych directly. Users couldn't specify its version.

@hsbt hsbt changed the title Removed self-hosted YAML Serializer Removed self-hosted YAML Serializer and PsychedYAML Mar 14, 2019
@deivid-rodriguez
Copy link
Copy Markdown
Contributor

I thinking, what @segiddins said makes sense. But what @hsbt says makes sense too. Even though we have our own YAML implementation in order to not interfere with yaml / psych loading, we were actually activating psych. Shouldn't we use our custom implementation everywhere instead of using the default gem?

@hsbt
Copy link
Copy Markdown
Member Author

hsbt commented Mar 14, 2019

FYI: https://bugs.ruby-lang.org/issues/13847

@hsbt hsbt force-pushed the remove-self-hosted-yaml branch from d1f2f87 to 4f01b28 Compare August 4, 2019 12:15
@hsbt hsbt closed this Mar 17, 2020
@hsbt hsbt deleted the remove-self-hosted-yaml branch March 17, 2020 06:22
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants