Add tools/requirements.txt - #1060
Conversation
|
I know nothing about this but should it be in the root directory like other projects? Should it have the following dependencies? |
PyPI / pip dependencies for running gPodder.
afc31c6 to
77a78d0
Compare
|
I don't mind putting the requirements to the root dir, but since gPodder is not in PyPI, I don't think it needs to be there. The other installer related files are all under tools/, including tools/mac-osx/release_on_mac.sh and tools/win_installer/_base.sh which contain a variant of this list. The packages you list are all pulled in by pip as dependencies for requests or html5lib (webencodings). PySocks was missing, but is now pulled in by 'requests[socks]'. There's no direct imports of these in the code, so letting pip handle the versioning should be fine. |
|
BTW, there should perhaps also be a 'requirements-test.txt' file, which would have the testing dependencies listed in the README. |
|
Merged, thanks. That would solve the Tor user issue #1026 |
There seems to be no machine readable dependency list for the Python packages used by gPodder. This PR adds a pip-compatible requirements file, which can be used to get the correct dependencies. I hope I did not miss anything.
I needed this when fixing the dependencies in the flatpak package. There's a tool called flatpak-pip-generator which converts the requirements file to the format understood by flatpak-builder.