Matthew R. Becker
Matthew R. Becker
Any public method should be assumed to be used. As I said before on another pr, unless we plan to release v4, there can be no api changes.
Also, we should not be introducing any deprecation processes unless core is in agreement on how they work.
Yes a new issue is fine and then on a core call. We're going to bust something for somebody even if we don't know about it. We use semver and...
Also while I'm not opposed to making the functions shorter here, the style in which these PRs are being made is making them difficult/impossible for me to review. - This...
@reneehlozek
This is done for everything but vector-valued parameters.
I think bump is about the potential namespace collision? I'm ok with this name being used by another package.
This is the expected outcome AFAIK. In YAML, the line continuation stuff (`|` or `>`) is for strings only AFAIK. So the sequence of steps is ```yaml build_plus_2: >- ${{...
Stated more simply, as soon as you use `>` or `|` you are explicitly casting the thing as a string in the same way that using single or double quotes...
Unfortunately rattler-build-conda-compat does set properly types when rendering context sections via https://github.com/prefix-dev/rattler-build-conda-compat/blob/df3646efc79435a5f07e73c67be248f97c41d888/src/rattler_build_conda_compat/jinja/jinja.py#L91. The issue there is that the rendered text is not then put through the yaml type inference. In...