@scheidegger 😔 bummer. I was thinking each post is rendered in a separate process and could maybe use a different virtual env? As someone who writes about code on the bleeding edge of development it’d be helpful (although freezing a post also helps with that too)
@grrrck it’s very hard to do because we run some Python/R code that calls Jupyter/knitr. So we’d be calling different versions while rendering the same project, a recipe for disaster
@grrrck making quarto work across multiple knitr/jupyter versions is already a lot of work. Making it work with multiple versions at once would be a lot more, for honestly relatively narrow use cases. You can always call knitr from a separate process and keep that .md around to be used in (eg) include shortcodes. That way you’re pretty clearly on your own terms
@scheidegger oh nice thanks for the suggestion! I’m more thinking of third party packages, like a preview post about a dev version of a Python package. I could commit to a single version of knitr/jupyter but don’t want a global version of the dev pkg
@grrrck Yeah, there's clearly a narrow-but-valid use case, imagine eg quartodoc being able to render multiple versions of the documentation. It's just that it adds a pretty deep complication where we're not ready to commit the resources yet.
Add comment