Your Pine comments now come through to Python
Since PyneComp 6.1.3, the Pyne code you get back keeps every comment you wrote in Pine, in the place you wrote it. A comment above a line stays above it, an end-of-line comment stays at the end of its line, an input’s comment follows it into the script’s settings, and your license header goes to the top of the file.
Library authors get something extra: //@function, //@param, //@returns, //@type and //@field become real Python docstrings, so your library’s users see your documentation in their editor.
The spacing of the output now follows PEP 8 as well. The compiled program itself is unchanged: on 1,090 real-world scripts, all 52,255 comments came through and the code is identical apart from the new docstrings.
The full story, with a before-and-after example, is on the PyneSys blog: “Your Pine comments now come through to Python”.