Closed sabotagebeats closed 2 years ago
did you try this:
"recommended-plugins": [
"ape-alchemy>=0.3", # Alchemy public network provider
"ape-ens>=0.3", # ENS converter
"ape-etherscan>=0.3", # Etherscan explorer plugin
"ape-foundry>=0.3", # Foundry local and fork network EVM provider
"ape-hardhat>=0.3", # Hardhat local and fork network EVM provider
"ape-infura>=0.3", # Infura public network provider
"ape-ledger>=0.3", # Ledger Nano S/X hardware wallet
"ape-solidity>=0.3", # Solidity compiler support
"ape-template>=0.3", # Cookiecutter template support
"ape-tokens>=0.3", # Tokenlists converter
"ape-trezor>=0.3", # Trezor Model T/One hardware wallet
"ape-vyper>=0.3", # Vyper compiler support
],
(specifying the version to be the same minor as eth-ape minimally)
I just tried pip install eth-ape'[recommended-plugins]'
in a fresh environment and it worked!
I believe the culprit lies in the fact that ape-foundry
was broken regarding its dependency constraints previously and is now fixed. If one of plugins in the recommended-plugins
set is broken in such as way, pip
will attempt to find a solution by brute forcing things (and always failing).
Please re-opened if you still experience this issue. However, I believe we can close this now that ape-foundry
is installable again.
Environment information
OS: wsl2 ubuntu 20.04
Python Version: 3.9.9
ape
and plugin versions: ape 0.3.6.dev15+g8034d8ff Installed Plugins: fantom 0.3.0 tokens 0.3.0 ens 0.3.0 vyper 0.3.0 hardhat 0.3.0 alchemy 0.3.0 infura 0.3.0 etherscan 0.3.1.dev0+g27b52bb.d20220620 solidity 0.3.0Contents of your
ape-config.yaml
(NOTE: do not post anything private like RPC urls or secrets!): n/aWhat went wrong?
Please include information like:
pip install .[recommended-plugins]
and in docker:
How can it be fixed?
not sure but it works fine if we do the following:
ape plugins install