We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent fbb2ef7 commit 2406a0cCopy full SHA for 2406a0c
docs/faq.rst
@@ -271,3 +271,19 @@ Common gotchas to watch out for involve not ``free()``-ing memory region
271
that that were ``malloc()``-ed in another shared library, using data
272
structures with incompatible ABIs, and so on. pybind11 is very careful not
273
to make these types of mistakes.
274
+
275
+How to cite this project?
276
+=========================
277
278
+We suggest the following BibTeX template to cite pybind11 in scientific
279
+discourse:
280
281
+.. code-block:: bash
282
283
+ @misc{pybind11,
284
+ author = {Wenzel Jakob and Jason Rhinelander and Dean Moldovan},
285
+ year = {2017},
286
+ note = {https://github.com/pybind/pybind11},
287
+ title = {pybind11 -- Seamless operability between C++11 and Python}
288
+ }
289
0 commit comments