5 ms·

I have a lot of python code from my PhD which will be released when I pass my viva (with full version history, of course) - I'm not looking forward to working o

I have a lot of python code from my PhD which will be released when I pass my viva (with full version history, of course) - I'm not looking forward to working out how to deal with pypi after reading this! I have always tried to make self-contained packages with a simple "just run setup.py" install procedure for my smaller public projects on github, but my larger codebase uses lots of libraries, and specifying which ones people should install is going to be a nightmare...

ubernostrum 13y ago
I think you're really overcomplicating this if your use case is to make something installable from PyPI. Think of it like this: * "install_requires" in setup.py = "I don't really care how you get this, or possibly even what version of it you get, just get this". * requirements file = "I have a known-good, tested and functioning setup using these specific versions, from these specific URLs, of these specific packages; I cannot vouch for whether other versions or other distributions of those packages will work".