[BUG]: eval_file cannot accept zip file
Open
Nobody has claimed this yet.
triage
- Dominant language
- C++
- Stars
- 18k
- Forks
- 2.3k
- Avg merge
- 5d 17h
- Merged PRs (30d)
- 10
Description
Required prerequisites
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker and Discussions to verify that this hasn't already been reported. +1 or comment there if it has.
- Consider asking first in the Gitter chat room or in a Discussion.
What version (or hash if on master) of pybind11 are you using?
v3.9.2
Problem description
command can run like this,there is a main.py file in the zip:
python mm.zip
but pybind11 eval_file cannot run:
result = "mma.zip";
std::string py_str = result;
py::object scope = py::module_::import("__main__").attr("__dict__");
auto local = py::dict();
// local["arr1"] = arr1;
// Execute the main python file
py::eval_file(py_str, scope);
Reproducible example code
void executePy() {
// Get main.py file contents
std::string result;// File path for the main python file
// Return read contents
result = "mma/__main__.py";
result = "mma.zip";
std::string py_str = result;
py::object scope = py::module_::import("__main__").attr("__dict__");
auto local = py::dict();
// local["arr1"] = arr1;
// Execute the main python file
py::eval_file(py_str, scope);
}
Is this a regression? Put the last known working version here if it is.
Not a regression
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.
Research direction
Start by reading the py::eval_file documentation and implementation, then reproduce the reported call with mma.zip containing main.py. Check how Python handles python mm.zip versus the current eval_file path and add coverage for the reported archive case; done means the example executes successfully or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, python
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100