How about merging your graphene improvements upstream?

[xeroc]

Hey Holger,

as the original author of pysteem/piston-lib and python-graphene, I am looking to cooperate with you.
How about we put our efforts with respect to python-graphene (*graphene* modules) together and merge our improvements our improvements? I think we can both benefit from reduced code duplications and better code maintainability by moving low-level stuff to python-graphene.
What are your thoughts?

[holgern]

Hello xeroc,
sounds like a good plan. I forked beem in february from python-graphenelib and python-bitshares. So I think, it is feasible to merge our libraries and moving low-level stuff to python-graphene.

Can I reach you, so that we can communicate better?

[officiallymarky]

This sounds awesome

[xeroc]

sounds like a good plan. I forked beem in february from python-graphenelib and python-bitshares. So I think, it is feasible to merge our libraries and moving low-level stuff to python-graphene.

Sweet.
You'll notice that I made some improvements to pygraphene in the last few months, hope you like them.

Can I reach you, so that we can communicate better?

You can reach me via Telegram @xeroc, or via mail info@chainsquad.com.
For python-bitshares, we also have a dedicated Telegram group: https://t.me/pybitshares

Looking forward discussing with your :D

[Gandalf-the-Grey]

Are we there yet, @xeroc @holgern ?
Utopian might be able to help with that I guess.