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

ape plugins install doesn't work if ape installed via uv tool #2350

Open
2 tasks done
fubuloubu opened this issue Oct 28, 2024 · 4 comments
Open
2 tasks done

ape plugins install doesn't work if ape installed via uv tool #2350

fubuloubu opened this issue Oct 28, 2024 · 4 comments
Assignees
Labels
category: bug Something isn't working

Comments

@fubuloubu
Copy link
Member

Have you ensured that all of these are up to date?

  • Ape
  • Ape plugins

What version of Ape are you on?

v0.8.18

What command(s) is the bug in?

ape plugins install

Operating System

Linux

Description

plugins:
- name: aws
  veresion: 0.8.0a3
$ uv tool install eth-ape[recommended-plugins]
...
$ ape plugins install .
INFO:     Installing 'aws' plugin ...
error: No virtual environment found; run `uv venv` to create an environment, or pass `--system` to install into a non-virtual environment
ERROR:    Failed to install plugin 'aws.

Reproduction code

No response

@fubuloubu fubuloubu added the category: bug Something isn't working label Oct 28, 2024
Copy link

linear bot commented Oct 28, 2024

@bitwise-constructs bitwise-constructs self-assigned this Oct 28, 2024
@bitwise-constructs
Copy link
Contributor

is this intentionally being done with uv tool install over uv pip install? tool installs globally on the path, so if you run an ape plugins install . on a tool version of ape then it will collide with whatever else is there

@bitwise-constructs
Copy link
Contributor

but tested with uv pip install and it behaves as expected

@fubuloubu
Copy link
Member Author

is this intentionally being done with uv tool install over uv pip install? tool installs globally on the path, so if you run an ape plugins install . on a tool version of ape then it will collide with whatever else is there

Specifically with tool, because I feel like downstream users might find it interesting to use in that way

I think we could do some detection it was installed with tool and mutate the install so that the plugin actually can be added to the install other tool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants