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

Add conda-forge recipe #902

Open
spinoch opened this issue Dec 23, 2020 · 10 comments
Open

Add conda-forge recipe #902

spinoch opened this issue Dec 23, 2020 · 10 comments

Comments

@spinoch
Copy link

spinoch commented Dec 23, 2020

Add a recipe to https://github.com/conda-forge/staged-recipes to have brownie available as a package on conda-forge, so that brownie can be installed using conda.

Not all of brownie's dependencies are available as conda packages, though, so we may want to look into adding recipes for those before we add a recipe for brownie (it shouldn't take more than a few minutes if the package specification is up to date).
Those packages are:

eth-event
py-solc-ast
pygments-lexer-solidity
pythx
vvm
vyper (xref: vyperlang/vyper#2214)

@iamdefinitelyahuman
Copy link
Member

I'm fully in support of this, but unfamiliar with how conda works. I'm the principal maintainer of eth-event, py-solc-ast, and vvm so consider them in support as well.

I'll reach out to you on telegram to discuss.

@spinoch
Copy link
Author

spinoch commented Mar 4, 2021

We now have most dependencies on conda-forge, but we're missing a few for which I haven't yet found any maintainers apart from myself: pygments-lexer-solidity, pythx, web3 and one more (the state of Ethereum python packages is messier than I thought).
Any volunteers that would like to step up as a maintainer of these conda packages? I'd rather not be just myself as maintainer as having a bus factor of 1 is not very resilient

@spinoch
Copy link
Author

spinoch commented Mar 7, 2021

Will close this for now given the state of Ethereum Python packages on which brownie depends.
Unfortunate, as this would have resolved environments getting corrupted because of pytest conflicts

@spinoch spinoch closed this as completed Mar 7, 2021
@spinoch
Copy link
Author

spinoch commented Apr 19, 2021

Well, all deps are on conda-forge now, but for some reason, even with soft pinning, grayskull still gives me an old version for mythx-models (1.9.1 to be precise).
For the hard pinning version, the following dependency versions are not on conda atm:

conda.exceptions.ResolvePackageNotFound: 
  - lru-dict==1.1.7
  - pythx==1.6.1
  - pygments-lexer-solidity==0.5.1
  - web3==5.11.1
  - mythx-models==1.9.1
  - netaddr==0.8.0

@spinoch
Copy link
Author

spinoch commented Apr 19, 2021

Perhaps bumping web3's dependencies would solve the issues for the soft pinning, see: conda-forge/staged-recipes#14625

@spinoch spinoch reopened this Apr 19, 2021
@calina-c
Copy link
Contributor

calina-c commented Jan 6, 2023

Hello, all! I know this is an older issue but maybe it is time to revive it. I tried running grayskull and the only dependency that is missing is eip712. A grayskull run for eip712 works perfectly, no missing dependencies on their side. Is it worth exploring this, maybe opening a request with them? If eip712 adds a conda recipe, then it's all clear for brownie as well.

@spinoch
Copy link
Author

spinoch commented Jan 14, 2023

@calina-c by all means, go ahead and add a recipe for eip712. You can add me as maintainer if you want. Same goes for brownie

@calina-c
Copy link
Contributor

calina-c commented Feb 17, 2023

@spinoch conda-forge/staged-recipes#22056

It took a while for me to get back to this, but thank you very much for the support :) Let me know once you've completed the step for conda (agreeing to be a maintainer by commenting on that PR) and I'll ping the team to approve

@calina-c
Copy link
Contributor

@spinoch unfortunately I can't add both packages in the same PR, but I added eip712 for now. I tagged you as a maintainer and you need to confirm in that PR that you agree. I'll come back with the brownie recipe after eip712 is confirmed and merged. Thank you a lot!

@calina-c
Copy link
Contributor

calina-c commented Apr 5, 2023

I haven't heard about this one in a while, so I'm commenting again. @spinoch are you still up to be a maintainer? Or should I add someone else?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants