quarto-dev / quarto-dev/quarto-cli
Getting "Executed file not found" error when .py file present along with .ipynb
Open
@cderv is already working on this.
Since May 23, 2024.
bug
early-in-release
engines-jupyter
- Dominant language
- JavaScript
- Stars
- 6k
- Forks
- 458
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 41
Description
Bug description
I am trying to compile a book with quarto, sourced by .ipynb files. I have chapters specified in the _quarto.yml and they are all .ipynb files. When doing quarto render I get the error if any of the .ipynb files also have a .py file with the same name, and no error if I remove the .py file. Is this expected? I usually have as a default for my Jupyter to always save a .py with my .ipynb to make it easier for searching through old work. Thanks!
Steps to reproduce
No response
Expected behavior
No response
Actual behavior
No response
Your environment
- Python 3 installation....Version: 3.11.8 (Conda)
- Mac 14.4.1
Quarto check output
Quarto 1.4.554
[✓] Checking versions of quarto binary dependencies...
Pandoc version 3.1.11: OK
Dart Sass version 1.69.5: OK
Deno version 1.37.2: OK
[✓] Checking versions of quarto dependencies......OK
[✓] Checking Quarto installation......OK
Version: 1.4.554
Path: /Applications/quarto/bin
[✓] Checking tools....................OK
TinyTeX: (not installed)
Chromium: (not installed)
[✓] Checking LaTeX....................OK
Using: Installation From Path
Path: /Library/TeX/texbin
Version: 2023
[✓] Checking basic markdown render....OK
[✓] Checking Python 3 installation....OK
Version: 3.11.8 (Conda)
Path: /opt/anaconda3/envs/work/bin/python
Jupyter: 5.5.0
Kernels: python3
[✓] Checking Jupyter engine render....OK
[✓] Checking R installation...........(None)
Unable to locate an installed version of R.
Install R from https://cloud.r-project.org/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.