flexdashboard does not works with Python chunk

[djouallah]

Knitr works fine with python chunks, but once I add a header to make it as a flexdashboard, I got this error

Error in py_call_impl(callable, dots$args, dots$keywords) : 
  TypeError: float() argument must be a string or a number, not 'list'

as an example

---
title: "Solar Far"
output: 
  flexdashboard::flex_dashboard
    
---

```{python echo=FALSE, reticulate=FALSE}
import altair as alt
floor_Plan = alt.topo_feature('https://raw.githubusercontent.com/djouallah/R_leaflet_MAP/master/foundation.json', 'foundation')
source = 'https://raw.githubusercontent.com/djouallah/R_leaflet_MAP/master/data/data.csv'
map = alt.Chart(floor_Plan).mark_geoshape().encode(
color='progress:Q',
tooltip=['properties.id:N','progress:N']).transform_lookup(
    lookup='properties.id',
    from_=alt.LookupData(source, 'id', ['progress']))

map.save('map.html')
map

if you removed the first section, everything works fine.

[yihui]

You mean if you change flexdashboard::flex_dashboard to something like html_document, it will work?

I don't know much about Python and I have no idea what the error message means, so I cannot help you here. You may ask it on Stack Overflow or RStudio Community instead. Thanks!

BTW, I don't know what the chunk option reticulate=FALSE means; knitr doesn't support such an option. See https://bookdown.org/yihui/rmarkdown/language-engines.html#python for more info about the python engine.

[djouallah]

You mean if you change flexdashboard::flex_dashboard to something like html_document, it will work?
yes correct, the issue is only with flexdashboard

[yihui]

For the record, this was cross-posted at https://stackoverflow.com/q/54533761/559676

[afogarty85]

What the author was trying to say is that flexdashboard cannot run Python chunks.

Once you told the RMD that it was no longer a flexdashboard object, it runs correctly.

[github-actions]

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary.