Is your feature request related to a problem? Please describe.
Whilst not a strict necessity for Python projects, it's fairly conventional to specify dependencies via Pip, the de facto standard package manager for Python. This is achieved via a requirements.txt manifest file conforming to the expected format.
Describe the solution you'd like
A requirements.txt file located in the project root containing the necessary dependencies extracted from the existing setup script:
Describe alternatives you've considered
We could separate out the different profiles (i.e. distinguish between production and development requirements) but this seems overengineering at the moment.
Is your feature request related to a problem? Please describe. Whilst not a strict necessity for Python projects, it's fairly conventional to specify dependencies via Pip, the de facto standard package manager for Python. This is achieved via a
requirements.txtmanifest file conforming to the expected format.Describe the solution you'd like A
requirements.txtfile located in the project root containing the necessary dependencies extracted from the existing setup script:https://github.com/kieran-mackle/AutoTrader/blob/9478b6253bcd9456ad3dee99cd8b961950196ba3/setup.py#L52-L78
Describe alternatives you've considered We could separate out the different profiles (i.e. distinguish between production and development requirements) but this seems overengineering at the moment.
Additional context None.