Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is ray or ray[serve] compatible with python3.9 and pipenv/poetry? #12788

Closed
dashsatish opened this issue Dec 11, 2020 · 5 comments
Closed

Is ray or ray[serve] compatible with python3.9 and pipenv/poetry? #12788

dashsatish opened this issue Dec 11, 2020 · 5 comments
Labels
bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)

Comments

@dashsatish
Copy link

Ray and Ray-Serve

What is the problem?

Unable to install latest version of ray a.k.a 1.0.1.post1 in a virtual env running with python3.9. The error so described
here is same when run with pipenv or poetry.

Ray version and other system information (Python version, TensorFlow version, OS):
OS version: MacOS catalina, version: 10.15.6(19G73)
Python: 3.9
Poetry: Poetry version 1.1.4
(or
pipenv: 2018.11.26
)

Reproduction (REQUIRED)

Please provide a short code snippet (less than 50 lines if possible) that can be copy-pasted to reproduce the issue. The snippet should have no external library dependencies (i.e., use fake or mock data / environments):

python -m pip install -U pip pipenv==2018.11.26 poetry --no-cache-dir
poetry new demo
cd demo
# edit pyproject.toml file to add "ray" in the project dependencies (sample toml file attached):
# neither of these work when put in the pyproject.toml file
# >>> ray = "*"
# >>> ray = { version = "*" }
poetry update

pyproject.toml.zip

[Error obtained]


 • Installing ray (1.0.1.post1): Failed

  RuntimeError

  Unable to find installation candidates for ray (1.0.1.post1)

  at ~/.pyenv/versions/3.9.0/lib/python3.9/site-packages/poetry/installation/chooser.py:72 in choose_for
       68│ 
       69│             links.append(link)
       70│ 
       71│         if not links:
    →  72│             raise RuntimeError(
       73│                 "Unable to find installation candidates for {}".format(package)
       74│             )
       75│ 
       76│         # Get the best link

If the code snippet cannot be run by itself, the issue will be closed with "needs-repro-script".

  • [Yes ] I have verified my script runs in a clean environment and reproduces the issue.
  • [Yes ] I have verified the issue also occurs with the latest wheels.
@dashsatish dashsatish added bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Dec 11, 2020
@edoakes
Copy link
Contributor

edoakes commented Dec 11, 2020

Hi @dashsatish, unfortunately Ray (and therefore Ray Serve) does not support Python 3.9 yet. We are actively working on this and you can expect to see support for it soon. We currently support Python 3.6-3.8.

@edoakes
Copy link
Contributor

edoakes commented Dec 11, 2020

Closing due to duplicate with #12788

@edoakes edoakes closed this as completed Dec 11, 2020
@dashsatish
Copy link
Author

@edoakes Just curious, is the work to support ray-core with python 3.8 to 3.9 intensive? The reason I ask this is because I assume supporting different python 3.x versions for a library(including a huge stack system) should be seamless. Do correct me.

@edoakes
Copy link
Contributor

edoakes commented Dec 14, 2020

@dashsatish see the above issue for details. It's not quite that simple because Ray contains a significant amount of C++/cython code.

@frankier
Copy link

That above link is a link to this issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something that is supposed to be working; but isn't triage Needs triage (eg: priority, bug/not-bug, and owning component)
Projects
None yet
Development

No branches or pull requests

3 participants