Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
P
pybind11
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
open
pybind11
Commits
a4642736
Commit
a4642736
authored
May 06, 2018
by
luzpaz
Committed by
Wenzel Jakob
Sep 11, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Misc. typos (#1384)
Found via `codespell`
parent
ae6f0959
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
6 additions
and
6 deletions
+6
-6
docs/advanced/cast/eigen.rst
+1
-1
docs/changelog.rst
+3
-3
include/pybind11/cast.h
+1
-1
tests/test_smart_ptr.cpp
+1
-1
No files found.
docs/advanced/cast/eigen.rst
View file @
a4642736
...
@@ -275,7 +275,7 @@ Vectors versus column/row matrices
...
@@ -275,7 +275,7 @@ Vectors versus column/row matrices
Eigen and numpy have fundamentally different notions of a vector. In Eigen, a
Eigen and numpy have fundamentally different notions of a vector. In Eigen, a
vector is simply a matrix with the number of columns or rows set to 1 at
vector is simply a matrix with the number of columns or rows set to 1 at
compile time (for a column vector or row vector, respectively). Numpy, in
compile time (for a column vector or row vector, respectively). Numpy, in
contast, has comparable 2-dimensional 1xN and Nx1 arrays, but *also* has
cont
r
ast, has comparable 2-dimensional 1xN and Nx1 arrays, but *also* has
1-dimensional arrays of size N.
1-dimensional arrays of size N.
When passing a 2-dimensional 1xN or Nx1 array to Eigen, the Eigen type must
When passing a 2-dimensional 1xN or Nx1 array to Eigen, the Eigen type must
...
...
docs/changelog.rst
View file @
a4642736
...
@@ -586,7 +586,7 @@ Happy Christmas!
...
@@ -586,7 +586,7 @@ Happy Christmas!
being (notably dynamic attributes in custom types).
being (notably dynamic attributes in custom types).
`#527 <https://github.com/pybind/pybind11/pull/527>`_.
`#527 <https://github.com/pybind/pybind11/pull/527>`_.
* Significant work on the documentation -- in particular, the monolitic
* Significant work on the documentation -- in particular, the monolit
h
ic
``advanced.rst`` file was restructured into a easier to read hierarchical
``advanced.rst`` file was restructured into a easier to read hierarchical
organization. `#448 <https://github.com/pybind/pybind11/pull/448>`_.
organization. `#448 <https://github.com/pybind/pybind11/pull/448>`_.
...
@@ -654,8 +654,8 @@ Happy Christmas!
...
@@ -654,8 +654,8 @@ Happy Christmas!
<https://github.com/pybind/pybind11/pull/527>`_.
<https://github.com/pybind/pybind11/pull/527>`_.
3. This version of pybind11 uses a redesigned mechnism for instantiating
3. This version of pybind11 uses a redesigned mech
a
nism for instantiating
tr
e
mpoline classes that are used to override virtual methods from within
tr
a
mpoline classes that are used to override virtual methods from within
Python. This led to the following user-visible syntax change: instead of
Python. This led to the following user-visible syntax change: instead of
.. code-block:: cpp
.. code-block:: cpp
...
...
include/pybind11/cast.h
View file @
a4642736
...
@@ -1171,7 +1171,7 @@ private:
...
@@ -1171,7 +1171,7 @@ private:
#else
#else
// PyPy seems to have multiple problems related to PyUnicode_UTF*: the UTF8 version
// PyPy seems to have multiple problems related to PyUnicode_UTF*: the UTF8 version
// sometimes segfaults for unknown reasons, while the UTF16 and 32 versions require a
// sometimes segfaults for unknown reasons, while the UTF16 and 32 versions require a
// non-const char * arguments, which is also a nuis
s
ance, so bypass the whole thing by just
// non-const char * arguments, which is also a nuisance, so bypass the whole thing by just
// passing the encoding as a string value, which works properly:
// passing the encoding as a string value, which works properly:
return
PyUnicode_Decode
(
buffer
,
nbytes
,
UTF_N
==
8
?
"utf-8"
:
UTF_N
==
16
?
"utf-16"
:
"utf-32"
,
nullptr
);
return
PyUnicode_Decode
(
buffer
,
nbytes
,
UTF_N
==
8
?
"utf-8"
:
UTF_N
==
16
?
"utf-16"
:
"utf-32"
,
nullptr
);
#endif
#endif
...
...
tests/test_smart_ptr.cpp
View file @
a4642736
...
@@ -19,7 +19,7 @@
...
@@ -19,7 +19,7 @@
// ref<T> is a wrapper for 'Object' which uses intrusive reference counting
// ref<T> is a wrapper for 'Object' which uses intrusive reference counting
// It is always possible to construct a ref<T> from an Object* pointer without
// It is always possible to construct a ref<T> from an Object* pointer without
// possible incosistencies, hence the 'true' argument at the end.
// possible inco
n
sistencies, hence the 'true' argument at the end.
PYBIND11_DECLARE_HOLDER_TYPE
(
T
,
ref
<
T
>
,
true
);
PYBIND11_DECLARE_HOLDER_TYPE
(
T
,
ref
<
T
>
,
true
);
// Make pybind11 aware of the non-standard getter member function
// Make pybind11 aware of the non-standard getter member function
namespace
pybind11
{
namespace
detail
{
namespace
pybind11
{
namespace
detail
{
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment