pybind / pybind/pybind11

[BUG]: Can't bind std::vector<std::pair<int64_t, pybind11::bytes>> such type in pybind11

Open
#4,940 1 comment 0 reactions 0 assignees View on GitHub

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
What version (or hash if on master) of pybind11 are you using?

2.11.1

Problem description

When working ,I encountered a problem that need to bind std::vector<std::pair<int64_t, pybind11::bytes>> such type in pybind11.
but this build failed in VS.
report error C4996: 'pybind11::handle::operator ==': Use obj1.is(obj2) instead
message : see reference to function template instantiation 'bool std::operator ==<int64_t,pybind11::bytes>(const std::pair<int64_t,pybind11::bytes> &,const std::pair<int64_t,pybind11::bytes> &)' being compiled

Did I do something wrong? I use std c++20 and pybind11 2.11.1.
Looking forward to reply. Thanks

Reproducible example code
std::vector<std::pair<int64_t, pybind11::bytes>> _LoadFlow(const std::string& filename)
namespace py = pybind11;
PYBIND11_MAKE_OPAQUE(std::vector<std::pair<int64_t, py::bytes>>);
PYBIND11_MODULE(flow_loader, m) {
	py::class_<FlowLoader>(m, "FlowLoader")
		.def(py::init<>())
		.def("load_flowfile", &FlowLoader::_LoadFlow)
	py::bind_vector<std::vector<std::pair<int64_t, py::bytes>>>(m, "VectorPair");
}
Is this a regression? Put the last known working version here if it is.

Not a regression

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Visual Studio C4996 failure with the shown std::vector<std::pair<int64_t, py::bytes>> type, PYBIND11_MAKE_OPAQUE, and py::bind_vector entry points. No source files or tests are named; inspect the binding implementation and existing coverage to establish whether this combination should compile, with completion requiring a verified resolution or clearly documented limitation.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, python
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.