Skip to content
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

Move out the Plutus Ledger API definition into a seperate package #91

Open
nielstron opened this issue Mar 15, 2023 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@nielstron
Copy link
Contributor

Currently, the Plutus Ledger Specification in Python is baked into eopsin.
This causes two issues

  1. hebi also uses the specification, which leads to code duplication
  2. 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)

@nielstron
Copy link
Contributor Author

An alternative to this is that pycardano decides to host the entire ledger specification, which is a viable option too.

@nielstron nielstron added the enhancement New feature or request label Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant