Durgaprasad-Budhwani
commented
9 months ago Tackling the issue where you're unable to call Python code from your Next.js application, I've got a great solution that should clear up the confusion and have your application communicating with Python in no time! The key here is to switch from using exec to spawn, which is a bit more flexible and suited for your needs. Here's how you can do it:
export const pythonExec = async () => {
const { spawn } = require('child_process');
console.log("I am called");
return new Promise((resolve, reject) => {
const pyprog = spawn('python', ["/path/to/the/code/sample-script.py"]);
pyprog.stdout.on('data', function(data) {
console.log(data.toString());
resolve(data.toString());
});
pyprog.stderr.on('data', (data) => {
console.log(data.toString());
reject(data.toString());
});
});
};This approach uses spawn from the child_process module, providing a neat, promise-based solution to asynchronously execute your Python script and handle both success and error cases. Just remember to replace "/path/to/the/code/sample-script.py" with the absolute path to your Python script. Absolute paths ensure that your Python code is correctly located and executed, regardless of where your Next.js app is running.
Also, to make sure your Python script is included in your Next.js build, consider using the copy-webpack-plugin in your next.config.js file. This plugin will help you copy your Python code into the build directory, making deployment smoother and more reliable. Here's a quick example of how you might set it up:
const CopyPlugin = require('copy-webpack-plugin');
module.exports = {
webpack: (config, { isServer }) => {
if (!isServer) {
config.plugins.push(
new CopyPlugin({
patterns: [
{ from: 'path/to/the/code', to: 'destination/path' },
],
}),
);
}
return config;
},
};Just adjust path/to/the/code and destination/path to match your project's structure. This little tweak ensures your Python script is right where it needs to be, ready to be called by your Next.js app. Keep up the great work, and I'm here if you have any more questions or need further assistance!
"Let's make the digital world smaller! Connect with me across the web on these social platforms and let's create, share, and inspire together." ✨🌐 #StayConnected
zheng-liu-seattle
cysbyte
Link to the code that reproduces this issue
https://github.com/krishnaacharyaa/python-nextjs
To Reproduce
Just clone the repo Breif is: I am trying to run simple py/sh scripts from nextjs using exec but i am not able to achieve it.
Kind help would be much appreciated.
Process is simple:
page.tsx
server action
sample-script.py
p.s: I am called is being logged, only the "Hello world" is not getting logged. I also want to return values from the script and use consume it in my server action
Reproducible code: https://github.com/krishnaacharyaa/python-nextjs
Current vs. Expected behavior
Along with log of "I am called in ", I expect to see the "Hello world" message aswell
Provide environment information
Which area(s) are affected? (Select all that apply)
Data fetching (gS(S)P, getInitialProps), Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link), Script optimization (next/script)
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
No response