Yup. (pulp) [vagrant@pulp3 pulp_python]$ which rq > ~/.virtualenvs/pulp/bin/rq >
Inside a virtualenv everything is kind of weird, for example "pip" and "python" both map to the python 3 variants instead of the python 2 variants, which you would typically expect those names to map to. On Tue, Aug 7, 2018 at 2:46 PM, David Davis <davidda...@redhat.com> wrote: > In the vagrant environment, there is no /usr/bin/rq. Instead it uses the > rq executable inside the pulp virtualenv: > > https://github.com/pulp/devel/blob/0a37a02c1bbe809509c0215a0ff349 > 15f090068e/ansible/roles/systemd/templates/pulp_resource_manager.j2#L11 > > David > > > On Tue, Aug 7, 2018 at 2:38 PM Jeff Ortel <jor...@redhat.com> wrote: > >> It has been my experience that /usr/bin/rq is only installed by 'pip >> install rq' and it's not installed by 'pip3 install rq'. >> >> The only work around I have found is to: >> >> 1. pip install rq >> 2. pip3 install rq >> 3. edit /usr/bin/rq to use python3. >> >> How is this handled in the vagrant environment? It's not obvious to me >> looking at pulp-devel. >> >> _______________________________________________ >> Pulp-dev mailing list >> Pulp-dev@redhat.com >> https://www.redhat.com/mailman/listinfo/pulp-dev >> > > _______________________________________________ > Pulp-dev mailing list > Pulp-dev@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-dev > >
_______________________________________________ Pulp-dev mailing list Pulp-dev@redhat.com https://www.redhat.com/mailman/listinfo/pulp-dev