-
Notifications
You must be signed in to change notification settings - Fork 26
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
hashes (or something) prepended to output from python chunks? #17
Comments
I probably need to change this S3 method to |
I think it has something to do with whether the port that runR is listening on is open somewhere else. My current hypothesis is that depending on its exact state I get one or more of the following ...
or
or those weird strings in the output. The clue was that it seemed to work OK when I was running interactively but not from a Makefile. My guess is that when I was running it non-interactively I had a socket already open from a previous This suggests that if Anyway, I think you can probably close this -- I'll try to be careful to make sure I don't have a process already listening at the specified port ... |
I do not really like the current implementation based on socket connections. If I take it seriously, I should use a better backend like rPython/rJython (they may be difficult for Windows users to install, though). |
I ran into rPython today and was really excited about using the idea to support Python code more seamlessly in knitr. But, I guess you already knew. 😓 If you need help implementing this idea, I will be happy to contribute. |
Don't know if this should go as a knitr or a runr issue, but ... I'm using a fresh install of
runr
(devtools::install_github(yihui/runr)
,packageVersion("runr") == 0.0.7
)Every python output chunk seems to have some kind of hash value prepended to it ... ? I would try to dig in further, but I'm having a hard time getting far enough into the guts of
knitr
to debug it ...I have a minimal example posted here (the output is here)
FWIW it seems to happen with both python and python3 ...
any quick thoughts ... ?
The text was updated successfully, but these errors were encountered: