Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix/igd #165

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Fix/igd #165

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9ecc161
[igd] Emphasis words, instead of quoting in asterisks
etanot Sep 6, 2021
ae70c77
[igd] Fix indentation issue in "Generators" section
etanot Sep 6, 2021
e844eab
[igd] Fix a typo
etanot Sep 6, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/igd.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,22 +130,22 @@ in a for loop.

Inside the while loop when it reaches to the *yield* statement, the value of low is returned
and the generator state is suspended. During the second *next* call the generator resumed where
it freeze-ed before and then the value of *low* is increased by one. It continues with the
it suspended before and then the value of *low* is increased by one. It continues with the
while loop and comes to the *yield* statement again.

When you call an generator function it returns a \*generator* object. If you call \*dir*
on this object you will find that it contains *__iter__* and \*__next__* methods among the
When you call an generator function it returns a **generator** object. If you call **dir**
on this object you will find that it contains **__iter__** and **__next__** methods among the
other methods.

::

>>> c = counter_generator(5,10)
>>> dir(c)
['__class__', '__delattr__', '__dir__', '__doc__', '__eq__', '__format__',
'__ge__', '__getattribute__', '__gt__', '__hash__', '__init__', '__iter__',
'__le__', '__lt__', '__name__', '__ne__', '__new__', '__next__', '__reduce__',
'__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__',
'close', 'gi_code', 'gi_frame', 'gi_running', 'send', 'throw']
'__ge__', '__getattribute__', '__gt__', '__hash__', '__init__', '__iter__',
'__le__', '__lt__', '__name__', '__ne__', '__new__', '__next__', '__reduce__',
'__reduce_ex__', '__repr__', '__setattr__', '__sizeof__', '__str__', '__subclasshook__',
'close', 'gi_code', 'gi_frame', 'gi_running', 'send', 'throw']

We mostly use generators for laze evaluations. This way generators become a good approach
to work with lots of data. If you don't want to load all the data in the memory, you can use
Expand Down Expand Up @@ -245,7 +245,7 @@ The syntax of generator expression says that always needs to be directly inside
<generator object <genexpr> at 0x7fc559516b90>

We can have chaining of generators or generator expressions. In the following
example we will read the file \*/var/log/cron* and will find if any particular
example we will read the file **/var/log/cron** and will find if any particular
job (in the example we are searching for anacron) is running successfully or not.

We can do the same using a shell command *tail -f /var/log/cron |grep anacron*
Expand Down