You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Plutus Ledger Specification in Python is baked into eopsin.
This causes two issues
hebi also uses the specification, which leads to code duplication
if pycardano wants to build things on top of the ledger specification (i.e. for deriving the ScriptContext) we would get a circular dependency
So, the Plutus Ledger definition should move to a seperate python package, that can be depended upon and re-used.
Moreover pycardano might consider moving the entire plutus data definitions out. Otherwise we will get trouble when both eopsin and pycardano explicitly depend on non-consistent versions of the ledger-spec, leading to complications (CC @cffls)
The text was updated successfully, but these errors were encountered:
Currently, the Plutus Ledger Specification in Python is baked into eopsin.
This causes two issues
So, the Plutus Ledger definition should move to a seperate python package, that can be depended upon and re-used.
Moreover pycardano might consider moving the entire plutus data definitions out. Otherwise we will get trouble when both eopsin and pycardano explicitly depend on non-consistent versions of the ledger-spec, leading to complications (CC @cffls)
The text was updated successfully, but these errors were encountered: