Greg Roodt

> Maybe we should just document that fact @hrfuller Ok, that works for me. Happy if I just add a note to the deprecation paragraph in README.md?

@hrfuller I've added a small note to the README. LGTY? ``` The maintainers have taken all reasonable efforts to faciliate a smooth transition, but some users of `pip_install` will need...

Just for context, all_requirements is considered a bit of an anti-pattern. Is there a way for you to explicitly list your dependencies instead? Does the same error occur?

@anuragkanungo Yes, it's still an antipattern though. You can build tooling outside the rules to enumerate things explicitly if you need to.

Any thoughts @TahirJalilov @cvzi ?

Can't this be closed now @sbarzowski ? The [docs website](https://jsonnet.org/ref/stdlib.html) does include `parseYaml`...

Decided to go ahead with this simpler approach, that has a similar outcome. https://github.com/bazelbuild/rules_python/pull/773

Same root cause as: https://github.com/bazelbuild/rules_python/issues/691

Agreed. I think I'll create an "umbrella" tracking issue for "legacy scripts support". fwiw, it seems that perhaps hsjon will switch to entrypoints (or at least are being encouraged by...

This particular issue with hjson is fixed in `hjson==3.1.0`. Tested against the minimal reproduction and it works. ``` ❯ ../../bazel-5.2.0-darwin-x86_64 run //:hjson -- --help INFO: Analyzed target //:hjson (0 packages...