This function is nowhere used as confirmed by codesearch:
http://codesearch.openstack.org/?q=is_in_projects_txt&i=nope&files=&repos=
We can remove the function.
Note that usage of this function was removed in change
I843208e2e982eb04931b76f5cb4bd219fbcd70de in 2015.
This came up in context of https://review.openstack.org/619089 where
requirements/projects.txt is getting removed.
Change-Id: I487d3f9e340bd45e83245b9ca91e8e3b5ac3ae02
... | ... |
@@ -490,17 +490,6 @@ function setup_develop { |
490 | 490 |
_setup_package_with_constraints_edit $project_dir -e $extras |
491 | 491 |
} |
492 | 492 |
|
493 |
-# determine if a project as specified by directory is in |
|
494 |
-# projects.txt. This will not be an exact match because we throw away |
|
495 |
-# the namespacing when we clone, but it should be good enough in all |
|
496 |
-# practical ways. |
|
497 |
-function is_in_projects_txt { |
|
498 |
- local project_dir=$1 |
|
499 |
- local project_name |
|
500 |
- project_name=$(basename $project_dir) |
|
501 |
- grep -q "/$project_name\$" $REQUIREMENTS_DIR/projects.txt |
|
502 |
-} |
|
503 |
- |
|
504 | 493 |
# ``pip install -e`` the package, which processes the dependencies |
505 | 494 |
# using pip before running `setup.py develop` |
506 | 495 |
# |