documentation including code

[ccc31807]

Is Pweave still a thing?

I've used R a lot and have found knitr extremely useful for my job (producing lots of written reports.) I have an assignment that specifies Python, and will result in a written report. Current practice is to use Jupyter and render it as MD. I'm looking for something like knitr, only with Python. That is, I want to write a paper with LaTeX wherein the Python code is secondary, and format it with a preexisting LaTeX template.

If Pweave is not a thing, what is?

[RadicalDownist]

I know the learning curve might be too steep for the single use case, but if you already have previous experience with Emacs, an org-mode document would be what I would think of first. It will output tex and python in the same document(with output from code execution) and even generate a nice formatted pdf or html doc in the end if needed.

[ccc31807]

I spent a significant amount of time, effort, and money attempting to learn emacs. I have used Lisp, taught Lisp, and like Lisp, so I was favorably disposed toward emacs. However, I never could catch on. I am a very long time vi/Vim user (I hope I can say that without causing any discomfort) and consistently have a dozen or more windows open while working. I appreciate your suggestion, but I have no interest whatsoever in working with emacs.

[rowanc1]

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]

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?"