summaryrefslogtreecommitdiff
path: root/doc/source/using.rst
Commit message (Collapse)AuthorAgeFilesLines
* tweak wordingArmin Rigo2021-12-241-3/+6
|
* Write explicitly that byte strings passed to `char *` arguments are not ↵Armin Rigo2021-12-031-0/+9
| | | | meant to live as long as the byte string is alive, but only for the duration of the call
* Remove trailing whitespace in doc/*Rasmus Bondesson2021-07-171-2/+2
|
* 'bitbucket => heptapod' for most linksArmin Rigo2020-08-081-2/+2
|
* Document issue 391Armin Rigo2019-03-051-1/+17
|
* ffi.release()Armin Rigo2019-01-051-1/+1
|
* Fix a typo in using.rstHiroshi Hatake2018-01-101-1/+1
| | | | convertion ? conversion
* Update the doc, as suggested on python-cffiArmin Rigo2017-09-151-2/+29
|
* Expand the docs about wchar_t/char16_t/char32_tArmin Rigo2017-08-311-0/+3
|
* Document char16_t and char32_tArmin Rigo2017-06-021-3/+10
|
* Write a paragraph about __pypy__.add_memory_pressure()Armin Rigo2017-03-101-0/+53
|
* Expand the warning boxArmin Rigo2017-01-281-6/+14
|
* Update the docs to the style r"""...C source..."""Armin Rigo2016-11-111-6/+6
|
* Update the docs according to issue #281Armin Rigo2016-08-221-27/+24
|
* Document some common mistakes of bad lifetime of ffi.new()Armin Rigo2016-08-171-0/+27
|
* Doc tweaksArmin Rigo2016-06-201-4/+4
|
* Rename 'ffi' to 'ffibuilder' in the docs and in a few demos, whenArmin Rigo2016-06-051-14/+15
| | | | | | it is used in out-of-line builders. I think it makes things clearer, particularly in examples where the two 'ffi' are close together (and even sometimes used in the same sentence...)
* Lies, this didn't print a listArmin Rigo2016-04-231-1/+1
|
* Clean upArmin Rigo2016-04-231-5/+6
|
* ffi.unpack(), extern "Python+C"Armin Rigo2016-04-211-1/+44
|
* Move the FFI Interface and Conversion reference sections to their own page.Armin Rigo2016-04-211-529/+11
|
* Change the API of ffi.list_types()Armin Rigo2016-03-301-4/+4
|
* Document ffi.list_types()Armin Rigo2016-03-291-0/+5
|
* clarify (thanks R?mi)Armin Rigo2016-01-191-10/+14
|
* Add some sectionsArmin Rigo2016-01-141-1/+3
|
* Finalize and review embedding.rst.Armin Rigo2016-01-131-2/+2
|
* more docArmin Rigo2016-01-131-0/+3
|
* Add vararg demoArmin Rigo2016-01-061-1/+4
|
* emphasisArmin Rigo2016-01-061-1/+1
|
* Fix the reasonArmin Rigo2015-12-211-2/+2
|
* fixArmin Rigo2015-12-211-1/+1
|
* Add an example in the old-style callback section that describes theArmin Rigo2015-12-091-10/+33
| | | | "best" style, which is close to the new-style callbacks
* Polish the doc for `extern "Python"'Armin Rigo2015-12-071-13/+16
|
* hg merge static-callbackArmin Rigo2015-12-071-52/+265
|\
| * hg merge defaultArmin Rigo2015-11-301-6/+20
| |\
| * | typoArmin Rigo2015-11-231-1/+1
| | |
| * | hg merge defaultArmin Rigo2015-11-231-5/+7
| |\ \
| * | | meh, fix demoArmin Rigo2015-11-201-1/+1
| | | |
| * | | Change the @ffi.def_extern() decorator to not automatically replace theArmin Rigo2015-11-201-10/+14
| | | | | | | | | | | | | | | | | | | | | | | | function with the cdata. You need to get the cdata from the lib explicitly. This should make it clearer that there is only one cdata, even if you apply the decorator again.
| * | | flowArmin Rigo2015-11-181-1/+1
| | | |
| * | | Change the docs to use extern "Python" as discussed yesterday on ircArmin Rigo2015-11-181-66/+114
| | | | | | | | | | | | | | | | (thanks antocuni)
| * | | link to the reason for the callback new-styleArmin Rigo2015-11-171-1/+4
| | | |
| * | | Write documentation about ffi.call_python().Armin Rigo2015-11-151-52/+210
| | | |
* | | | Document init_once()Armin Rigo2015-12-071-0/+52
| |_|/ |/| |
* | | Mention jamadden's experience on ircArmin Rigo2015-11-241-1/+6
| | |
* | | improve doc for the fix to ffi.new_handle()Armin Rigo2015-11-231-3/+11
| | |
* | | ffi.addressof(lib, "name") does not work with ffi.verify()Armin Rigo2015-11-231-2/+3
| |/ |/|
* | Copy the PyPy behavior on CPython too: two calls to new_handle(x),Armin Rigo2015-11-231-5/+7
|/ | | | even with the same x, now return cdatas that compare as different.
* Document the SELinux issue with callbacksArmin Rigo2015-11-141-0/+10
|
* Clarify documentation for ffi.from_buffer(): it also works on read-onlyArmin Rigo2015-10-241-2/+5
| | | | buffer objects