AngelaKTE
commented
3 years ago Yey, thanks for the hint! You are right, we expect many projects to adopt these primitives in various use cases. And modularizing the model itself as well as modeling approaches (like injecting on-chain transactions) will certainly help to make the most of it. Great TODO for the research group, establishing infrastructure :)
Am 16.03.2021 um 13:49 schrieb Danillo Lessa Bernardineli @.***>:
Given that the model has several primitives for using in other contexts, it would be useful if I could import it directly from existing projects that the users can have.
This would have the advantage of generating a higher visibility about the model, as users would not require to copy & paste but rather to install dependencies, plus, it would make the auxiliary functions more accessible to use cases (like the balancer_math.py functions)
My suggestion is that we make a PyPI pacakge of it. It is relatively straighforward to do so: https://packaging.python.org/tutorials/packaging-projects/ https://packaging.python.org/tutorials/packaging-projects/ — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/TokenEngineeringCommunity/BalancerPools_Model/issues/80, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKDIW22VXGHJ5EE3AYMMFV3TD5HWPANCNFSM4ZIPSYOA.
Given that the model has several primitives for using in other contexts, it would be useful if I could import it directly from existing projects that the users can have.
This would have the advantage of generating a higher visibility about the model, as users would not require to copy & paste but rather to install dependencies, plus, it would make the auxiliary functions more accessible to use cases (like the balancer_math.py functions)
My suggestion is that we make a PyPI pacakge of it. It is relatively straighforward to do so: https://packaging.python.org/tutorials/packaging-projects/