mirror of
https://github.com/vale981/ray
synced 2025-03-07 02:51:39 -05:00
16fd099b8b
@SongGuyang @Catch-Bull @edoakes I know we discussed this earlier, but after thinking about it some more I think a more reasonable default is for `pip check` to be `False` by default. My guess is that a lot of users (including myself) work inside an environment where `python -m pip check` fails, but the environment doesn't cause them any problems otherwise. So a lot of users will hit an error when trying a simple `runtime_env` `pip` example, and possibly give up. Another less important piece of evidence is that we had to set `pip_check = False` to make some CI tests pass in the original PR. This also matches the default behavior of pip which allows this situation to occur in the first place: `pip install` doesn't error when there's a dependency conflict; rather the command succeeds, the package is installed and usable, and it prints a warning (which is confusingly titled "ERROR") |
||
|---|---|---|
| .. | ||
| _examples/datasets_train | ||
| actors | ||
| doc_code | ||
| examples | ||
| images | ||
| objects | ||
| tasks | ||
| actors.rst | ||
| advanced.rst | ||
| configure.rst | ||
| cross-language.rst | ||
| handling-dependencies.rst | ||
| key-concepts.rst | ||
| more-topics.rst | ||
| namespaces.rst | ||
| objects.rst | ||
| package-ref.rst | ||
| placement-group.rst | ||
| ray-dashboard.rst | ||
| starting-ray.rst | ||
| tasks.rst | ||
| tips-for-first-time.rst | ||
| troubleshooting.rst | ||
| user-guide.rst | ||
| using-ray-with-jupyter.rst | ||
| walkthrough.rst | ||