Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cython
Commits
2879c9fa
Commit
2879c9fa
authored
Nov 07, 2015
by
scoder
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #463 from jwilk/spelling
docs: Remove duplicated words.
parents
3dc2f80a
595ca06d
Changes
4
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
5 additions
and
5 deletions
+5
-5
docs/src/reference/extension_types.rst
docs/src/reference/extension_types.rst
+1
-1
docs/src/reference/language_basics.rst
docs/src/reference/language_basics.rst
+2
-2
docs/src/userguide/extension_types.rst
docs/src/userguide/extension_types.rst
+1
-1
docs/src/userguide/memoryviews.rst
docs/src/userguide/memoryviews.rst
+1
-1
No files found.
docs/src/reference/extension_types.rst
View file @
2879c9fa
...
@@ -448,7 +448,7 @@ External
...
@@ -448,7 +448,7 @@ External
print "Imag:", c.cval.imag
print "Imag:", c.cval.imag
.. note:: Some important things in the example:
.. note:: Some important things in the example:
#. ``ctypedef`` has been used because
because
Python's header file has the struct decalared with::
#. ``ctypedef`` has been used because Python's header file has the struct decalared with::
ctypedef struct {
ctypedef struct {
...
...
...
...
docs/src/reference/language_basics.rst
View file @
2879c9fa
...
@@ -66,7 +66,7 @@ cimport
...
@@ -66,7 +66,7 @@ cimport
* Use the **cimport** statement, as you would Python's import statement, to access these files
* Use the **cimport** statement, as you would Python's import statement, to access these files
from other definition or implementation files.
from other definition or implementation files.
* **cimport** does not need to be called in ``.pyx`` file for
for
``.pxd`` file that has the
* **cimport** does not need to be called in ``.pyx`` file for ``.pxd`` file that has the
same name, as they are already in the same namespace.
same name, as they are already in the same namespace.
* For cimport to find the stated definition file, the path to the file must be appended to the
* For cimport to find the stated definition file, the path to the file must be appended to the
``-I`` option of the **Cython compile command**.
``-I`` option of the **Cython compile command**.
...
@@ -705,7 +705,7 @@ Error and Exception Handling
...
@@ -705,7 +705,7 @@ Error and Exception Handling
.. note:: Python Objects
.. note:: Python Objects
* Declared exception values are **not** need.
* Declared exception values are **not** need.
* Remember that Cython assumes that a function
function
without a declared return value, returns a Python object.
* Remember that Cython assumes that a function without a declared return value, returns a Python object.
* Exceptions on such functions are implicitly propagated by returning ``NULL``
* Exceptions on such functions are implicitly propagated by returning ``NULL``
.. note:: C++
.. note:: C++
...
...
docs/src/userguide/extension_types.rst
View file @
2879c9fa
...
@@ -132,7 +132,7 @@ you can use a cast to write::
...
@@ -132,7 +132,7 @@ you can use a cast to write::
This may be dangerous if :meth:`quest()` is not actually a :class:`Shrubbery`, as it
This may be dangerous if :meth:`quest()` is not actually a :class:`Shrubbery`, as it
will try to access width as a C struct member which may not exist. At the C level,
will try to access width as a C struct member which may not exist. At the C level,
rather than raising an :class:`AttributeError`, either an nonsensical result will be
rather than raising an :class:`AttributeError`, either an nonsensical result will be
returned (interpreting whatever data is at
at that address as an int) or a segfault
returned (interpreting whatever data is at
that address as an int) or a segfault
may result from trying to access invalid memory. Instead, one can write::
may result from trying to access invalid memory. Instead, one can write::
print (<Shrubbery?>quest()).width
print (<Shrubbery?>quest()).width
...
...
docs/src/userguide/memoryviews.rst
View file @
2879c9fa
...
@@ -649,7 +649,7 @@ None Slices
...
@@ -649,7 +649,7 @@ None Slices
===========
===========
Although memoryview slices are not objects they can be set to None and they can
Although memoryview slices are not objects they can be set to None and they can
be
be
checked for being None as well::
be checked for being None as well::
def func(double[:] myarray = None):
def func(double[:] myarray = None):
print(myarray is None)
print(myarray is None)
...
...
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