Skip to content

Issue with optparse #1

@mwarkentin

Description

@mwarkentin

I'm trying to use virtualenv-tools to clone a virtualenv on our servers during deploy, and ran into an issue while using it as described in the docs.

When attempting to run it like this: virtualenv-tools --update-path=/data/virtualenv/clone6 or this: virtualenv-tools --update-path /data/virtualenv/clone6, I get the following error:

error: . does not refer to a python installation

I added a print statement to debug what options and paths were being set to:
options, paths: {'update_path': '/data/virtualenv/clone6', 'reinitialize': None} []

I ended up running the following command, and it seemed to work:

2013-02-19--17-40-03)[mwarkentin@tide-acct-app-01 site-packages]$ virtualenv-tools --update-path=/data/virtualenv/clone6 /data/virtualenv/clone6
options, paths: {'update_path': '/data/virtualenv/clone6', 'reinitialize': None} ['/data/virtualenv/clone6']
A /data/virtualenv/clone6/bin/activate
A /data/virtualenv/clone6/bin/activate.fish
A /data/virtualenv/clone6/bin/activate.csh
B /data/virtualenv/clone6/lib/python2.7/copy_reg.pyo
B /data/virtualenv/clone6/lib/python2.7/warnings.pyc
B /data/virtualenv/clone6/lib/python2.7/posixpath.pyo
...

Should the docs be updated, or am I doing something wrong here?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions