René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Better interoperability with pipenv","articleBody":"## Problem\r\n\r\n`pipenv` is a very popular manager for virtual environments and respects `WORKON_HOME` through `pev`, but environments created by `pipenv` end in a hash that causes it to be a little inconvenient to use `virtualenvwrapper` with `pipenv.`\r\n\r\n## Proposed Solution\r\n\r\n`workon` should have an argument to determine the virtualenv directory from the current directory path, using the same logic as `pipenv`.   I think it should be something like `workon --pipenv`.\r\n\r\n## Workaround\r\n\r\nIt isn't that hard if you already can write shell functions and import them when you launch your shell.  My current one looks like this:\r\n\r\n```shell\r\nfunction workonenv () \r\n{ \r\n    if [[ $# -ne 0 ]]; then\r\n        echo \"Usage: $0\" 1\u003e\u00262;\r\n        return 1;\r\n    else\r\n        if [[ ! -f \"./Pipfile\" ]]; then\r\n            echo \"./Pipfile: file not found\" 1\u003e\u00262;\r\n            return 1;\r\n        else\r\n            if [[ -n \"$VIRTUAL_ENV\" ]]; then\r\n                echo \"do not use this command from within a virtualenv\" 1\u003e\u00262;\r\n                return 1;\r\n            fi;\r\n        fi;\r\n    fi;\r\n    ENV_NAME=$(python -c \"from pipenv.project import Project; print(Project('.').virtualenv_name)\");\r\n    HAVE_WORKON=$(type workon | head -1);\r\n    if [[ \"$HAVE_WORKON\" != \"workon is a function\" ]]; then\r\n        echo \"virtualenvwrapper may not be active\" 1\u003e\u00262;\r\n        return 1;\r\n    fi;\r\n    workon $ENV_NAME\r\n}\r\n```\r\n\r\n## Downsides with Workaround\r\n\r\nThe workaround isn't perfect.  Because it isn't part of virtualenvwrapper, it is harder to carry it with me.  It also doesn't recognize that this is different from a normal argument to workon:\r\n\r\n```shell\r\n$ workonenv \r\nERROR: Environment 'scrapeboa-L7gq2F0U' does not exist. Create it with 'mkvirtualenv scrapeboa-L7gq2F0U'.\r\n$ pipenv sync -d\r\n...\r\n$ workonenv\r\n(scrapeboa) $ \r\n```","author":{"url":"https://github.com/danizen","@type":"Person","name":"danizen"},"datePublished":"2024-11-20T03:11:23.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/114/virtualenvwrapper/issues/114"}