Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gevent
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
gevent
Commits
18241ee1
Commit
18241ee1
authored
Sep 15, 2011
by
Denis Bilenko
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
minor change in intro.rst
parent
533607d9
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
3 deletions
+2
-3
doc/intro.rst
doc/intro.rst
+2
-3
No files found.
doc/intro.rst
View file @
18241ee1
...
@@ -115,9 +115,8 @@ Lightweight pseudothreads
...
@@ -115,9 +115,8 @@ Lightweight pseudothreads
The greenlets are spawned by creating a :class:`Greenlet` instance and calling its :meth:`start <Greenlet.start>`
The greenlets are spawned by creating a :class:`Greenlet` instance and calling its :meth:`start <Greenlet.start>`
method. (The :func:`spawn` function is a shortcut that does exactly that). The :meth:`start <Greenlet.start>`
method. (The :func:`spawn` function is a shortcut that does exactly that). The :meth:`start <Greenlet.start>`
method schedules an :class:`event <gevent.core.active_event>` that will switch to the greenlet created, as soon
method schedules a switch to the greenlet that will happen as soon as the current greenlet gives up control.
as the current greenlet gives up control. If there is more than one active event, they will be executed
If there is more than one active event, they will be executed one by one, in an undefined order.
one by one, in an undefined order.
If there was an error during execution it won't escape greenlet's boundaries. An unhandled error results
If there was an error during execution it won't escape greenlet's boundaries. An unhandled error results
in a stacktrace being printed complemented by failed function signature and arguments:
in a stacktrace being printed complemented by failed function signature and arguments:
...
...
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