-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Exception when adding apache-beam[gcp] to empty project #4888
Comments
I'm also experiencing this issue. I tried it on a non-empty project as well, and that also fails. |
Works on linux for me at least. It looks to me like you need pip installed somewhere. Is it available on the host at all? |
Sorry, should have said- I'm on linux mint (cinnamon 20.2). My python set up is: I'm always in a conda environment with the python I want to be using, and that has pip installed. Then I use poetry within that conda environment. I can install apache-beam[GCP] using pip in the conda environment, but that means that poetry isn't being used to manage my package dependencies, which of course defeats the object of using poetry |
That's the issue. Works when directly installing via Pip, but not when done through Poetry. |
Just fixed this on my machine :D My issue was that I had a mess of poetry installations, through partly installing them through pip, and partly through the installation script. My solution was to remove all poetry installations, clean up my conda environments and ensure it only uses pip. Then to tell poetry to not use the installer:
My suggestion would be to start with
and go from there Hope this helps |
@RobMcKiernan thanks for you solution insight! |
apache-beam is making a wholly redundant check that a recent version of pip is available in its environment. But
Suggest that anyone who cares about this issue raise an MR at apache-beam removing this block of code |
In my case, the issue was related to the experimental installer
fixed the issue |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
-vvv
option).Issue
I'm receiving an exception when trying to add
apache-beam[gcp]
to a new and empty project.It is possible that the issue resides with the library itself and not Poetry. If that's the case I'll make sure to open a ticket for them instead :)
The issue can easily be replicated with Poetry by creating a new empty folder, and running:
This is the full exception I received:
The text was updated successfully, but these errors were encountered: