Skip to content

Fails when requirements.txt doesn't exist? #8

@AlecTaylor

Description

@AlecTaylor

I note from your code in worker.js that it shouldn't be happening... but it is:

$ virtualenv.py /home/alectaylor/.strider/.venv python 9m

New python executable in /home/alectaylor/.strider/.venv/bin/python
Installing setuptools...............................done.
Installing pip.....................done.

prepare
$ git clone --recursive git@bitbucket.com:<company_name>/<proj_name> . -b master --single-branch bitbucket

Cloning into '.'...
Checking connectivity... done

$ git checkout -qf master bitbucket 9m

$ sh -x -c 'pip install -r requirements.txt' 

This particular project is simple; and has no dependencies outside the stdlib; so doesn't need a requirements.txt.

Can you please fix this bug? - Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions