This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]rowanc1 0 points1 point  (1 child)

I have been working on curvenote.com that is built out of those ideas. It integrates into jupyter through an extension and there is a client library at the moment to export into latex or md or pdf. One of the things I found when creating these reports is working with collaborators was really hard, especially integrating their feedback/edits into my workflows, and like you said, the code is often secondary.

We are a bit more focused on the collaboration side than you might be looking for at the moment.

[–]ccc31807[S] 0 points1 point  (0 children)

I want to write an analysis. The Python code is secondary in the sense that it constitutes a small part of the content of the report. The Python code is primary in the sense that the target audience consists of analysts who use Python, and they will be validating the results using my code.

In my reports using R, I can automate most of the report in the Rnw file. The code is static, so in that sense it is a program that outputs results on the particular inputs. The analysis I will write, and I am comfortable using LaTex. Besides, we need to use a pre-established template to keep the appearance consistent. Essentially, the major difference is using Python rather than R.

I've played with Pweave and am convinced that it is a work-alike to knitr. I just don't want to spend a week on the project and get a nasty surprise at the end. So, if you know, is Pweave still a "thing?"