From: takashikkbn@... Date: 2018-12-29T06:29:23+00:00 Subject: [ruby-core:90790] [Ruby trunk Bug#15478][Third Party's Issue] [RFC] erb: remove deprecation warnings from ERB.new Issue #15478 has been updated by k0kubun (Takashi Kokubun). File olddoc-erb-ruby26.patch added Status changed from Feedback to Third Party's Issue I don't know how to send a patch to your git repository, so I attached it in this ticket. I will still welcome your opinion on this thread, but at least I'm going to eliminate the second argument once $SAFE is removed from Ruby itself, and I don't think it's a good idea to avoid warning users in a noticeable way prior to that. My suggestion to fix the issue on other closed codes would be postponing $SAFE deprecation to Ruby 4 or later in another ticket. If it's changed so, I'm fine to keep the warn level to 2 during Ruby 2.x. ---------------------------------------- Bug #15478: [RFC] erb: remove deprecation warnings from ERB.new https://bugs.ruby-lang.org/issues/15478#change-75966 * Author: normalperson (Eric Wong) * Status: Third Party's Issue * Priority: Normal * Assignee: k0kubun (Takashi Kokubun) * Target version: * ruby -v: * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- erb: remove deprecation warnings from ERB.new There's too much code relying on the old ordering; so any deprecation or removal of the old way is too annoying and only serves to make users angry. ---Files-------------------------------- 0001-erb-remove-deprecation-warnings-from-ERB.new.patch (2.87 KB) olddoc-erb-ruby26.patch (510 Bytes) -- https://bugs.ruby-lang.org/ Unsubscribe: