1. 20 Oct, 2016 5 commits
  2. 17 Oct, 2016 2 commits
  3. 16 Oct, 2016 2 commits
    • Wenzel Jakob's avatar
      Merge pull request #449 from jagerman/no-implicit-conversions · 135fd149
      Wenzel Jakob authored
      Disable most implicit conversion constructors
      135fd149
    • Jason Rhinelander's avatar
      Disable most implicit conversion constructors · 12d76600
      Jason Rhinelander authored
      We have various classes that have non-explicit constructors that accept
      a single argument, which is implicitly making them implicitly
      convertible from the argument.  In a few cases, this is desirable (e.g.
      implicit conversion of std::string to py::str, or conversion of double
      to py::float_); in many others, however, it is unintended (e.g. implicit
      conversion of size_t to some pre-declared py::array_t<T> type).
      
      This disables most of the unwanted implicit conversions by marking them
      `explicit`, and comments the ones that are deliberately left implicit.
      12d76600
  4. 15 Oct, 2016 2 commits
  5. 14 Oct, 2016 3 commits
  6. 13 Oct, 2016 6 commits
  7. 12 Oct, 2016 3 commits
  8. 11 Oct, 2016 1 commit
  9. 09 Oct, 2016 6 commits
  10. 08 Oct, 2016 1 commit
    • Wenzel Jakob's avatar
      unpacking_collector: allow nullptr-valued kwargs argument · e71ab8f4
      Wenzel Jakob authored
      This fixes an issue that can arise when forwarding (*args, **kwargs)
      captured from a pybind11-bound function call to another Python function.
      When the initial function call includes no keyword arguments, the
      py::kwargs field is set to nullptr and causes a crash later on.
      e71ab8f4
  11. 07 Oct, 2016 1 commit
  12. 02 Oct, 2016 2 commits
  13. 30 Sep, 2016 2 commits
  14. 29 Sep, 2016 3 commits
  15. 27 Sep, 2016 1 commit