The current setup (where we always install from requirements.txt) means that if we try to run a ckan-dev container with a local CKAN install, we end up with a broken install because the python3 requirements are installed on python2. This switches it so that when we are running CKAN 2.9 on python2, we first look for requirements-py2.txt and fall back to requirements.txt if it does not exist.
The current setup (where we always install from
requirements.txt) means that if we try to run a ckan-dev container with a local CKAN install, we end up with a broken install because the python3 requirements are installed on python2. This switches it so that when we are running CKAN 2.9 on python2, we first look forrequirements-py2.txtand fall back torequirements.txtif it does not exist.