)]}'
{"diskimage_builder/elements/pip-and-virtualenv/install.d/pip-and-virtualenv-source-install/04-install-pip":[{"author":{"_account_id":13294,"name":"Javier Peña","email":"jpena@redhat.com","username":"jpena"},"change_message_id":"35745ee2b235471a8be6c448b6c886276f1543ec","unresolved":false,"context_lines":[{"line_number":142,"context_line":"    pip install ${pip_args} virtualenv"},{"line_number":143,"context_line":"    mv /usr/bin/virtualenv /usr/bin/virtualenv2"},{"line_number":144,"context_line":"    if [[ $_do_py3 -eq 1 ]]; then"},{"line_number":145,"context_line":"        # We do not touch the python3 virtualenv because it will break"},{"line_number":146,"context_line":"        # /usr/bin/virtualenv-3 command which is harcoded to load specific version"},{"line_number":147,"context_line":"        # of the package. We need to be  sure that both methods of calling"},{"line_number":148,"context_line":"        # virtualenv are working and loading."},{"line_number":149,"context_line":"        if [ \"$(python3 -m virtualenv --version)\" !\u003d \"$(virtualenv-3 --version)\" ]; then"},{"line_number":150,"context_line":"            die \"virtualenv under python3 is broken\""},{"line_number":151,"context_line":"        fi"},{"line_number":152,"context_line":"    fi"},{"line_number":153,"context_line":""},{"line_number":154,"context_line":"    # Reclaim virtualenv to virtualenv2; similar to above, on fedora"}],"source_content_type":"application/x-shellscript","patch_set":1,"id":"ffb9cba7_4b9c710d","line":151,"range":{"start_line":145,"start_character":0,"end_line":151,"end_character":10},"updated":"2019-04-30 10:58:39.000000000","message":"I\u0027m not sure this is going to work as we want it, because it will fail every time the pip virtualenv package version differs from the python3-virtualenv version packaged in the distro.\n\nIs this what we want? Would it be preferable to update jobs using virtualenv-3 to use \"virtualenv -p python3\"?","commit_id":"d9d3df04ee660d5910145611d21653912b475f28"}]}