diff --git a/notes-en/python-packaging.md b/notes-en/python-packaging.md
new file mode 100644
index 0000000..c697e6d
--- /dev/null
+++ b/notes-en/python-packaging.md
@@ -0,0 +1,223 @@
+# Python packaging for your team
+
+I love [decoupling](https://en.wikipedia.org/wiki/Coupling_(computer_programming)). This make project maintaining easier. We have 2 main ways do it:
+
+1. [Git submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules). This is good conception but sometimes very confusable. Also you must commit updates in parent project for each submodule changing.
+2. Packaging. I think this is better solution because you already use many packages in your project. You can easy package your project and explain this conception for any junior.
+
+This article about creating [python package](https://packaging.python.org/) without pain.
+
+
+## Setuptools
+
+Most python packages what you want contains [setup.py](https://packaging.python.org/tutorials/packaging-projects/#creating-setup-py) file into it's root directory. This file describe package name, version, requirements (required third party packages), package content and some optional information. Just call `setuptools.setup(...)` with this info as kwargs. It's enough for package distribution. If you have setup.py then you already can distribute it. For example, upload into [pypi.org](https://pypi.org/).
+
+
+## Pip and virtualenv
+
+[Pip](https://pip.pypa.io/en/stable/) -- de facto standard for python packages installing in your system. Simple and well known.
+
+By default, pip install all packages for all users in system and required root privileges for it. [Don't sudo pip](https://pages.charlesreid1.com/dont-sudo-pip/). Use virtualenv to install packages into an isolated environments. Besides security troubles some packages can have incompatible required versions of some mutual package.
+
+Also I'm recommend use [pipsi](https://github.com/mitsuhiko/pipsi) for some global entry points like [isort](https://github.com/timothycrosley/isort). Yeah, pipsi use virtualenv.
+
+
+
+## Editable packages
+
+Sometimes you want get actual package version directly from your other repository. This is very useful for non-distributable projects. Setuptools doesn't support it, but you can do it via pip:
+
+```bash
+pip install -e git+git@bitbucket.org:...git@master#egg=package_name
+```
+
+And you can pin this and any other requirements into [requirements.txt](https://caremad.io/posts/2013/07/setup-vs-requirement/):
+
+```
+-e git+git@bitbucket.org:...git@master#egg=package_name
+...
+deal
+Django>=1.11
+...
+```
+
+Also pip support constraints.txt with same syntax for pinning versions for optional dependencies:
+
+```
+djangorestframework>=3.5
+```
+
+For installing this dependencies pass it into pip:
+
+```bash
+pip install -r requirements.txt -c constraints.txt
+```
+
+Requirements.txt very useful when you don't want create setup.py for your internal projects.
+
+
+## Pip-tools
+
+In most commercial projects you have at least 2 environments:
+
+1. Development. Here you get last available packages versions, develop and test project with it.
+2. Production. Here you want create same environment as where you're test this code. And this requirements must not be updated while you're not test and improve code for changes in new versions. Also other developers want get same environment as you, because it's already tested and save their time.
+
+[Pip-tools](https://github.com/jazzband/pip-tools) provide some tools for this conception.
+
+
+## Pipfile and pipenv
+
+Pip developers decided to [improve requirements.txt](https://github.com/pypa/pip/issues/1795) for dependencies grouping and native support for versions locking. in result their create [Pipfile specification](https://github.com/pypa/pipfile) and [pipenv](https://docs.pipenv.org/) -- tool for working with it. Pipenv can lock versions in [Pipfile.lock], manage virtual environments, install and resolve dependencies. So cool, but for distributable packages you all the same must duplicate main dependencies into setup.py.
+
+
+## Poetry
+
+[Poetry](https://github.com/sdispater/poetry) -- beautiful alternative to setuptools and pip. You should place all package info and all requirements into [pyproject.toml](https://poetry.eustace.io/docs/pyproject/). It's all. Beautiful. But poetry have some problems:
+
+1. It's not compatible with setuptools. As result, your users can't install your project without poetry. Everybody have setuptools, but many users doesn't know about poetry. You can use it for your internal projects, but poetry can't install dependencies from file or repository without `pyproject.toml` generating. Yeah, if you fork aand improve some project, you must make [sdist](https://docs.python.org/3/distutils/sourcedist.html) for any changes and bump version for all projects that depend on it. Or manually convert project's `setup.py` to `pyproject.toml`.
+2. Poetry [doesn't manage your virtual environment](https://poetry.eustace.io/docs/basic-usage/#poetry-and-virtualenvs) and python version. Pipenv as opposed to poetry always create virtual environment for project and [can choose right python version](https://docs.pipenv.org/advanced/#automatic-python-installation).
+3. Poetry use [version specifiers](https://poetry.eustace.io/docs/versions/#version-constraints) incompatible with [PEP-440](https://www.python.org/dev/peps/pep-0440/#version-specifiers). This make me sad.
+
+For backward compatibility you can generate setup.py and requirements.txt from pyproject.toml via [poetry-setup](https://github.com/orsinium/poetry-setup).
+
+
+## Flit
+
+If pyproject.toml cool, why only poetry use it? Not only. [Flit](https://github.com/takluyver/flit) support pyproject.toml too. This is very simple tool with only 4 commands:
+
+1. **init** -- interactive create pyproject.toml.
+2. **build** -- make sdist or wheel.
+3. **publish** -- upload package into PyPI (or other repository).
+4. **install** -- install local package into current environment.
+
+That's all. And enough in common cases. Flit use pip for packages installation. And flit listed in [alternatives by PyPA](https://packaging.python.org/key_projects/?#flit). As in poetry you need manage virtual environments by other tools.
+
+
+## Let's make best packaging for your team!
+
+All solutions below have some problems. Let's fix it!
+
+
+### Poetry based packaging
+
+1. Always create virtual environment for each project. I'm recommend use [pew](https://github.com/berdario/pew) or [virtualenvwrapper](https://virtualenvwrapper.readthedocs.io/en/latest/) for better experience.
+2. Use [pyenv](https://github.com/pyenv/pyenv) or [pythonz](https://github.com/saghul/pythonz) for python versions managing. Also I'm recommend try to use [pypy](https://pypy.org/) for some your small and well tested projects. It's really fast.
+3. Sometimes you want depend on some package some setuptools-based projects. Use [poetry-setup](https://github.com/orsinium/poetry-setup) for compatibility with it.
+
+
+### Pipenv based packaging
+
+As we remember, with pipenv we need duplicate all requirements in old format for setup.py. Let's improve it! Recently pipenv's developers move some actions with pipfile and requirements.txt into [requirementslib](https://github.com/sarugaku/requirementslib) package. I'm [fix some problems into Lockfile processing](https://github.com/sarugaku/requirementslib/pull/9#issuecomment-397834329) and now you can use it for [Pipfile.lock converting into old format](https://github.com/sarugaku/requirementslib#importing-a-lockfile-into-your-setuppy-file). Let's create our pipenv-based setup.py!
+
+Install `requirementslib`:
+
+```python
+from pip._internal import main as pip
+
+pip(['install', 'requirementslib'])
+```
+
+Feel free to use pip here: pipenv install pip into virtualenv initialization step.
+
+Read Pipfile.lock and convert it into setuptools-compatible format:
+
+```python
+from pathlib import Path
+from requirementslib import Lockfile # noQA
+
+path = Path(__file__).parent
+lockfile = Lockfile.create(path)
+requirements = lockfile.as_requirements(dev=False)
+```
+
+And now we must call setuptools.install with minimal package information:
+
+```python
+setup(
+ name='package-name',
+ version='0.1.0',
+ description='Package description also required. Place it here.',
+ packages=find_packages(),
+ install_requires=requirements,
+)
+```
+
+And this is full setup.py listing:
+
+```python
+from setuptools import setup, find_packages
+from pathlib import Path
+from pip._internal import main as pip
+
+
+pip(['install', 'requirementslib'])
+
+
+from requirementslib import Lockfile # noQA
+
+
+path = Path(__file__).parent
+lockfile = Lockfile.create(path)
+requirements = lockfile.as_requirements(dev=False)
+
+
+setup(
+ name='package-name',
+ version='0.1.0',
+ description='Package description also required. Place it here.',
+ packages=find_packages(),
+ install_requires=requirements,
+)
+
+```
+
+Do not use it for distributable packages: PyPA recommend [place into install_requires not locked versions](https://packaging.python.org/discussions/install-requires-vs-requirements/).
+
+
+### Old school: parse requirements.txt
+
+If you still use pip-tools then you can parse requirements.txt instead of Pipfile.lock:
+
+```python
+# https://github.com/orsinium/poetry-setup/blob/master/poetry_setup.py
+try:
+ # pip>=10
+ from pip._internal.download import PipSession
+ from pip._internal.req import parse_requirements
+except ImportError:
+ from pip.download import PipSession
+ from pip.req import parse_requirements
+
+
+requirements = parse_requirements('requirements.txt', session=PipSession())
+requirements = [str(r.req) for r in requirements]
+```
+
+
+## Setuptools is dead?
+
+Many developers (me too) love poetry because it's use beautiful project metadata describing format as setup.py alternative. But setuptools allow you [use setup.cfg instead of setup.py](https://setuptools.readthedocs.io/en/latest/setuptools.html#configuring-setup-using-setup-cfg-files) and it's also beautiful. Furthermore, [isort](https://github.com/timothycrosley/isort) and [flake8](http://flake8.pycqa.org/en/latest/) supports setup.cfg too. One config for all your tools! I like it.
+
+Setuptools supports requirements from VCS, file or archive via [dependency_links parameter](https://setuptools.readthedocs.io/en/latest/setuptools.html#dependencies-that-aren-t-in-pypi). And requirements grouping via [extras_require](https://setuptools.readthedocs.io/en/latest/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies).
+
+So, what's wrong with setuptools? I think, this tool have 2 problems:
+1. No native virtualenv and python version managing. And poetry can't do it too. But we have pew, virtualenvwrapper, pyenv, pythonz and many other useful tools. This is UNIX-way.
+2. No dependencies locking. Poetry, pipenv and pip (`pip freeze`) can lock dependencies from it's own files. Setuptools can't.
+
+
+## Further reading
+
+1. [How to install other Python version](https://realpython.com/installing-python/) (sometimes you don't need pyenv).
+1. [Installing packages using pip and virtualenv](https://packaging.python.org/guides/installing-using-pip-and-virtualenv/).
+1. [Beautiful example for setuptools configuring via setup.cfg](https://github.com/4383/sampleproject/blob/c503301e4b381790e5a9125c3dd636921052e8e1/setup.cfg).
+1. [Setuptools documentation](https://setuptools.readthedocs.io/en/latest/setuptools.html)
+1. [install_requires vs requirements files](https://packaging.python.org/discussions/install-requires-vs-requirements/)
+
+
+## Further reading (rus)
+
+1. [About poetry](https://t.me/itgram_channel/152)
+1. [About PyPy and python dev environment](https://t.me/itgram_channel/97)
+1. [About toml format](https://t.me/itgram_channel/113)
+