-
Notifications
You must be signed in to change notification settings - Fork 377
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
Utilize pyeth changes for solc >= 0.4.9 #351
Changes from 3 commits
dbf6ef0
85d2292
3280d0a
a9f37d0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,16 @@ | ||
pysha3 | ||
# temporary until https://github.com/ethereum/pyethapp/pull/184 comes upstream (see also setup.py) | ||
-e git+https://github.com/konradkonrad/pyethapp@71f940c6d287b98a35ef524f4c5e3c13d530bfc5#egg=pyethapp | ||
#-e git+https://github.com/konradkonrad/pyethapp@71f940c6d287b98a35ef524f4c5e3c13d530bfc5#egg=pyethapp | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this should be removed instead of commented out There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yes it should, left it in there to ask @konradkonrad if we still need it but it's actually included in my branch anyway so it can go away |
||
# temporary until new version of pyethereum is released, that supports solc >= v0.4.9 | ||
-e git+https://github.com/LefterisJP/pyethapp@use_new_solc_combinedjson_key#egg=pyethapp | ||
ipython<5.0.0 | ||
rlp>=0.4.3,<=0.4.6 | ||
secp256k1==0.12.1 | ||
pycryptodome>=3.4.3 | ||
miniupnpc | ||
networkx | ||
ethereum>=1.3.2 | ||
# temporary until new version of pyethereum is released, that supports solc >= v0.4.9 | ||
-e git+https://github.com/LefterisJP/pyethereum@fix_solidity_key_combinedjson#egg=ethereum | ||
ethereum-serpent | ||
repoze.lru | ||
gevent-websocket==0.9.4 | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use the exposed abi from the
raiden.blockchain.abi
module?https://github.com/raiden-network/raiden/blob/master/raiden/blockchain/abi.py#L90
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, that is a really good idea
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I see, the
abi.py
only computes the abi, it doesn't compile the smart contract, that's why the test is usingcompile_file
, so the question is then, what is the difference betweensolidity_get_contract_data
andcompile_file
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
compile_file
just compiles the file and returns the output.solidity_get_contract_data()
is a new function I added in the linked pyethapp PR, to abstract away the reading of the contract data (thecompile_file
output) in a backwards compatible way which would work with all currentsolc
versions.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, so never mind my comment then, I had the impression that
solidity_get_contract_data
called the compiler again.