That sounds more like a bug with web3.py then Vyper
Solidity doesn't have a working decimal type yet I don't think, so that might be why web3 doesn't implement it properly
P.S. Technically our biweekly call is in 7 mins, but I say we push that until tomorrow or Wednesday lol
Yeah, I think it's a case of the ABI for "decimal" not being set in stone. As far as I can tell, pyethereum is the only client that implements support for it, and Vyper depends on that for testing? I've posted a comment on ethereum/EIPs#598
Ah yeah, that totally makes sense. I was looking into porting pyrthereum to web3.py, probably would've ran into that issue as I got in the weeds
sooo errmmm ummm... guess i'll help out with guide to install viper?
im going to see if we can make it nice and neat. anyone got any suggestions on what they want to see?
i'll be destroying and spinning up ubuntu/deebian servers like no other :)
[Jarrad Hope 侯家睿] Hey guys I was wondering what peoples time estimations for Vyper beta would be? ie should we start pushing it as the language to use?
[Vitalik Buterin] my personal preference is we get a spec freeze ASAP (ie. days), get remaining stuff coded up (as far as I can tell, basically the extra restrictions I mentioned in the gitter channel) and then aim for audit-readiness
[Jarrad Hope 侯家睿] okay sweet
Hi guys, I'm Denis Bogdanas. Currently I'm maintaining the Viper semantics in K.