doomemacs / doomemacs/core

Python script cannot be compiled into the BUILD directory

Open
#7,208 2 comments 0 reactions 0 assignees View on GitHub
is:bug needs-triage
Dominant language
Emacs Lisp
Stars
22.7k
Forks
3.1k
Avg merge
10h 46m
Merged PRs (30d)
4

Description

### I confirm that...

- [X] I have searched the [issue tracker](https://github.com/doomemacs/doomemacs/issues), [documentation](https://docs.doomemacs.org), [FAQ](https://docs.doomemacs.org/-/faq), [Discourse](https://discourse.doomemacs.org), and [Google](https://google.com), in case this issue has already been reported/resolved.

- [X] I have read "[How to Debug Issues](https://doomemacs.org/d/how2debug)", and will use it to provide as much information about this issue as possible.

- [X] The issue can be reproduced on the **latest** available commit of Doom.

- [X] The issue can be reproduced on a stable release of Emacs, such as 27 or 28. *(Doom does not support development builds like 29+ or any version ending in .50 or .9x)*

### Expected behavior

Hello, I install mind-wave package that uses the EPC function and needs to call Python scripts, but Python scripts cannot be compiled into the build directory. This is my configuration.
packages.el
(package! mind-wave
:recipe (:host github :repo "manateelazycat/mind-wave"))
config.el
(use-package! mind-wave)

![image](https://user-images.githubusercontent.com/6092914/234625393-b89fc344-df1b-4075-b808-ed8005378933.png)

Is there any way to automatically compile Python scripts into the build directory?

### Current behavior

Mind-Wave cannot call the Python script,path not found

### Steps to reproduce

step1. Add the following configuration in packages.el
(package! mind-wave
:recipe (:host github :repo "manateelazycat/mind-wave"))
step2. Add the following configuration in config.el
(use-package! mind-wave)

### System Information

ubuntu emacs28.1

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.