Opened 11 years ago
Last modified 7 years ago
#6545 assigned Bugs
boost:::python doesn't recognize std::shared_ptr
| Reported by: | Owned by: | Jim Bosch | |
|---|---|---|---|
| Milestone: | To Be Determined | Component: | python USE GITHUB |
| Version: | Boost 1.48.0 | Severity: | Problem |
| Keywords: | Cc: | jhasse@… |
Description
boost::python specially handles boost::shared_ptr, but special handling is also needed for std::shared_ptr
Change History (12)
comment:1 by , 10 years ago
| Component: | None → Python |
|---|---|
| Owner: | set to |
comment:2 by , 10 years ago
| Cc: | added |
|---|
comment:3 by , 10 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
I'm going to take a crack at implementing this.
comment:5 by , 9 years ago
Sorry, no...I'm probably too busy to do this, and certainly too busy to do this if it involves teaching myself SVN again. I'd been putting it off until Boost converted fully to git, which has been right around the corner for several years now.
If anyone would like to take ownership of the ticket, please feel free to. Otherwise I might get to it when I can do it with git, but even then, no promises. (I'd reliquish ownership back to whoever it would default to if I could, but Trac doesn't seem to provide a way to do that).
Sorry!
comment:7 by , 8 years ago
I'm hitting this issue extensively at the moment... can you give me a couple tips on what verification needs to happen for a proposed patch to get merged into boost::python?
Peter Karasev karasevpa@…
comment:8 by , 8 years ago
I'm afraid I don't know much more than you do. I'd be happy to provide a code review, but I don't have commit privileges myself, and I've only ever contributed trivial bugfixes to Boost in the past. So we'd need to find someone to help with the last few steps, and I while there are many people who could do that, I don't know that anyone in particular actually considers merging Boost.Python patches their responsibility.
comment:10 by , 7 years ago
Seriously, this is important. This makes an artificial island where one cannot safely pass from code module to another. The converters/details look mostly copy paste. FYI I tried to do an "overlay" fix with detail/is_shared_ptr, value_is_shared_ptr and the converters but got sidelined on the other files as it's beyond the time I can sink into this.
boost::get recognizes std::shared_ptr now adays.
And while we're at it, add support for std::array -> http://stackoverflow.com/questions/17885639/exposing-a-c-style-array-data-member-to-python-via-boost-python and maybe update the old ndarray support to the current c-interface :-)
Please come back to us jbosch!
comment:12 by , 7 years ago
This (or at least a similar) issue is now tracked in https://github.com/boostorg/python/issues/29, so I'm going to close this issue.
Please set the component in the future if you want it to be analyzed.