Generate requirements.txt files

[gribok]

To ensure interoperability with other python package manager, it makes senses to generate requirements.txt and requirements-dev.txt.
pipenv provides capabilities to generate requirements-files for production and development-environment.
See https://pipenv.readthedocs.io/en/stable/advanced/#generating-a-requirements-txt

[Kilo59]

@gribok
Not saying I'm against it but, what's the benefit?
As you said, anybody who wants to can generate requirements file with pipenv lock -r --dev > requirements.txt

1. Won't having 2 sets of dependency/requirements files lead to confusion?
2. How do we ensure they stay in sync?

[gribok]

@gribok
Not saying I'm against it but, what's the benefit?
As you said, anybody who wants to can generate requirements file with pipenv lock -r --dev > requirements.txt

1. Won't having 2 sets of dependency/requirements files lead to confusion?
2. How do we ensure they stay in sync?

1. I'm more confused about Pipefile, if I worked always with requirements.txt inside a virtuelenv.
   It provides capability to use desired package manager directly without workaround to export package list from pipenv first.
2. Same procedure as with update of Pipefile. Change requester have to update the Pipfile.lock.
   Additonally requirements.txt files have to be generated to PR.
   Maybe, is it a topic to add into CONTRIBUTION guide.

[Kilo59]

I think there's 2 things we need in order for this to happen.

1. generate-reqs (or similar name) invoke task to generate the requirements files
2. pytest test or CI step that ensures that the requirements.txt and Pipfile.lock are in sync

[gribok]

I think there's 2 things we need in order for this to happen.

1. generate-reqs (or similar name) invoke task to generate the requirements files
2. pytest test or CI step that ensures that the requirements.txt and Pipfile.lock are in sync

Good point. I'm going to check it out and will add it to PR #245.

[gribok]

Please check my PR.