help with calysto_hy updating #2362
Unanswered
actsasgeek
asked this question in
Q&A
Replies: 1 comment 1 reply
-
Yeah, Hy internals aren't considered part of the public interface, so we may break anything that depends on them without notice.
That's surprising seeing as I've made all the code changes since the release of 0.24.0, and I wouldn't consider any of them particularly big. But, I don't know anything about Jupyter or what it depends on. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I decided to try and tackle an update to calysto_hy, because using Jupyter notebooks is pretty much required for my use cases and the repo hasn't been updated for several years.
I don't really know what I'm doing but I'm willing to be educated. After futzing around a bit, I noticed that things were pretty big changes between hy 0.24 and 0.25. Conceptually, I think hy 0.25 greatly simplifies the task but again there's not much (any?) documentation for Hy's architecture, MetaKernel's docs are out of date.
I replaced this block:
https://github.com/Calysto/calysto_hy/blob/master/calysto_hy/kernel.py#L136-L146
with:
and it actually "works"...if you're an expert programmer who never makes mistakes. However, I can't figure out how to report errors. I thought I could something like this:
https://github.com/hylang/hy/blob/master/hy/cmdline.py#L58-L65
but the return value is never anything by False for me.
At this point, I figured I might need some help understanding what is actually happening.
runsource
?I noticed that TryHy subclassed REPL but I couldn't quite suss out what it was doing.
Beta Was this translation helpful? Give feedback.
All reactions