More flexible pip requirements.txt layout

[ethan-mm]

I've re-arranged requirements.pip into a directory that contains a base list of packages (requirements/base.txt) which gets inherited by dev.txt and prod.txt. The purpose is to modularize the set of requirements that are required for different deployment environments (development, staging, ci, qa, testing, production, etc.)

For example, we do not want to deploy some django and/or python debugging packages to production servers. For example: django debug toolbar, ipdb, coverage, pep8, cx_oracle, etc.

I replaced the original requirements.pip with a top level requirements.txt that defaults to the production settings. (It seems that the ".pip" extension is being phased out, in favor of ".txt")

[tomyam1]

+1

[easp]

I'm not a confident enough coder to be sure (or to fix it on my own), but it looks like the fabfile.py is halfway between using "requirements.pip" and "requirements.txt." Might be good to fix that at the same time as merging this.

[bartTC]

I think your changes make sense but at the same time they don't add enough value. The packages in a dev environment are usually very short, django-debug-toolbar is the only one that comes to my mind. In general you want to keep your packages across all deployments the same, to minimize confusions and errors. Also this adds even more complexity at the beginning while its very easy to add, if you really need it.

This ticket is old and there was no other opinion so far, I'm going to close this. I will however add a little note in the current requirements file that it's possible to load other files using the -r argument.