-[Writing your own contextmanager using generator syntax](#writing-your-own-contextmanager-using-generator-syntax)

-[`__main__` Top-level script environment](#main-top-level-script-environment)

-[Advantages](#advantages)

-[setup.py](#setuppy)

-[Virtual Environment](#virtual-environment)

-[virtualenv](#virtualenv)

-[pipenv](#pipenv)

[*Return to the Top*](#python-cheatsheet)

The setup scriptis the centre ofall activityin building, distributing,and installing modules using the Distutils. The main purpose of the setup scriptis to describe your module distribution to the Distutils, so that the various commands that operate on your modules do the right thing.

The`setup.py`fileis at the heart of a Python project. It describesall of the metadata about your project. There a quite a few fields you can add to a project to give it a richset of metadata describing the project. However, there are only three required fields: name, version,and packages. The name field must be uniqueif you wish to publish your package on the Python Package Index (PyPI). The version field keeps track of different releases of the project. The packages field describes where you’ve put the Python source code within your project.

This allows you to easily install Python packages. Often it's enough to write:

python setup.py install

and module will install itself.

Our initial setup.py will also include information about thelicenseand will re-use theREADME.txtfilefor the long_description field. This will look like:

>>>from distutils.coreimport setup

>>> setup(

...name='pythonCheatsheet',

...version='0.1',

...packages=['pipenv',],

...license='MIT',

...long_description=open('README.txt').read(),

... )

Find more information visit [http://docs.python.org/install/index.html](http://docs.python.org/install/index.html).

[*Return to the Top*](#python-cheatsheet)

The use of a Virtual Environmentis to test python codein encapsulated environmentsand to also avoid filling the base Python installationwith libraries we might usefor only one project.

-[args and kwargs](#args-and-kwargs)

-[Context Manager](#context-manager)

-[`__main__` Top-level script environment](#main-top-level-script-environment)

-[setup.py](#setup.py)

-[Virtual Environment](#virtual-environment)

This allows you to easily install Python packages. Often it's enough to write:

$python setup.py install

python setup.py install

and module will install itself.

... )

Find more information visit http://docs.python.org/install/index.html.

Find more information visit[http://docs.python.org/install/index.html](http://docs.python.org/install/index.html).

"- [Context Manager](#context-manager)\n",

" - [with statement](#with-statement)\n",

" - [Writing your own contextmanager using generator syntax](#writing-your-own-contextmanager-using-generator-syntax)\n",

"- [__main__ Top-level script environment](#main-top-level-script-environment)\n",

"- [`__main__` Top-level script environment](#main-top-level-script-environment)\n",

" - [Advantages](#advantages)\n",

"- [setup.py](#setuppy)\n",

"- [Virtual Environment](#virtual-environment)\n",

" - [virtualenv](#virtualenv)\n",

" - [pipenv](#pipenv)\n",

"source": [

"[*Return to the Top*](#python-cheatsheet)\n",

"\n",

"## __main__ Top-level script environment\n",

"##`__main__` Top-level script environment\n",

"\n",

"`__main__` is the name of the scope in which top-level code executes.\n",

"A module’s __name__ is set equal to `__main__` when read from standard input, a script, or from an interactive prompt.\n",

"\n",

"[*Return to the Top*](#python-cheatsheet)\n",

"\n",

"## setup.py\n",

"\n",

"The setup script is the centre of all activity in building, distributing, and installing modules using the Distutils. The main purpose of the setup script is to describe your module distribution to the Distutils, so that the various commands that operate on your modules do the right thing.\n",

"\n",

"The `setup.py` file is at the heart of a Python project. It describes all of the metadata about your project. There a quite a few fields you can add to a project to give it a rich set of metadata describing the project. However, there are only three required fields: name, version, and packages. The name field must be unique if you wish to publish your package on the Python Package Index (PyPI). The version field keeps track of different releases of the project. The packages field describes where you’ve put the Python source code within your project.\n",

"\n",

]

},

{

"cell_type":"code",

"execution_count":null,

"metadata": {},

"outputs": [],

"source": [

"%%bash\n",

]

},

{

"cell_type":"markdown",

"metadata": {},

"source": [

"and module will install itself.\n",

"\n",

]

},

{

"cell_type":"code",

"execution_count":null,

"metadata": {},

"outputs": [],

"source": [

">>> from distutils.core import setup\n",

">>> setup(\n",

"... name='pythonCheatsheet',\n",

"... version='0.1',\n",

"... packages=['pipenv',],\n",

"... license='MIT',\n",

"... long_description=open('README.txt').read(),\n",

]

},

{

"cell_type":"markdown",

"metadata": {},

"source": [

"Find more information visit [http://docs.python.org/install/index.html](http://docs.python.org/install/index.html).\n",

"\n",

"[*Return to the Top*](#python-cheatsheet)\n",

"\n",

"## Virtual Environment\n",

"\n",

"The use of a Virtual Environment is to test python code in encapsulated environments and to also avoid filling the base Python installation with libraries we might use for only one project.\n",