Grier Phillips

Not sure if this is related, but seems likely. Given a config, containing a custom resolver `as_tuple`: ```yaml vec: _target_: sklearn.feature_extraction.text.HashingVectorizer ngram_range: ${as_tuple:2,3} pipe: _target_: sklearn.pipeline.Pipeline steps: - - vec...

@Jasha10 thanks for the workaround. I had been doing the following: ```yaml vec: _target_: sklearn.feature_extraction.text.HashingVectorizer ngram_range: - 2 - 3 ``` This at least instantiates, but I am touch uncomfortable...