quarchive VS PyCall.jl

I've had this problem a few times., For example it happened with the 0.800+ versions. It got stricter, and was more aggressive in finding code (eg small scripts in not in the proper python hierarchy).

I can't show any of my professional work (no publicly available src) but this side project of mine is locked to 0.790 until I can find time to sort the issues: https://github.com/calpaterson/quarchive/tree/master/src/ser...

It's hard to classify anything as a "false negative" with mypy since it is very liberal (often unexpectedly so, which I think is one of the sharp edges of gradual typing).

Glad you think it's promising. There is still some distance to go - it needs a second pass over some of the (pretty rough) features.

Regarding tags: I am not sure I completely agree with you how easy it will be to remove all the current limits on tags but I do share your sentiment and I have filed the matter as a github issue: https://github.com/calpaterson/quarchive/issues/67 . I can't promise any priority because as this is a side project I can only work at my own pace but I foresee it happening "soon" - just that my main task right now is showing what I have to people and getting feedback.

On the unread flag: you're probably right. That was implemented before tags were, in order to allow for importing my own bookmarks from pinboard (I personally do not use tags).

Private flags: as a usability matter, yes. But my plan is to allow for more fine-grained sharing/permissions (the MVP of which is the current share feature).

Thanks for your feedback. I really appreciate the time you took to try it out and leave your comments. Do keep in touch over email! [email protected]

This is my side project. It's basically a social bookmarking site, but with a few extra features I wanted. It's open source on my github.

For point 3 you can use https://github.com/cjdoris/PythonCall.jl or https://github.com/JuliaPy/PyCall.jl (and their respective Python sister packages).

PyCall.jl is really handy. Are there any similar projects for calling Chapel code, or Carbon/zig?

Julia and Python interop should not be a problem at all. Actually Julia has one of the best interops I’ve ever seen, so much that swift copied it. https://github.com/JuliaPy/PyCall.jl

One small note, julia also has great python interop via PyCall.jl

It is possible to call Python from Julia using PyCall. Then to install PyCall, run the command in the Julia REPL.

That said, you can run python modules in Julia. So you can just export your code as a module and then use it in Julia via the PyCall package. short description here github here <— you’d just add the pacakge via the really nice package manager built into julia, but for link for more detailed documentation