chore: regen fullstack to incorporate other template changes#48
Conversation
CiottiGiorgio
left a comment
There was a problem hiding this comment.
LGTM, I only have one comment that is not required to be addressed in this PR.
| python-dotenv = "^1.0.0" | ||
| algorand-python = "^2.0.0" | ||
| algorand-python-testing = "^0.4.0" | ||
| algorand-python-testing = "~0" |
There was a problem hiding this comment.
I wonder if this is a good way to enforce the constraint that a specific version of the language stubs should be installed together with a specific version of the testing library.
Would it work if we added an optional dependency group to the stubs called testing-stubs that requires at least a compatible version of algorand-python-testing so that, if you install the language with the testing-stubs option, you get at least a compatible version?
There was a problem hiding this comment.
Yeah that's an interesting idea.
Typically the install happens via algokit boostrap all, which doesn't have support for passing optional group info and is also executed as an optional step when running algokit init. It's possible to incorporate this, however it'd need some changes.
No description provided.