Package Details: pyenv-virtualenvwrapper 20140609-1

Git Clone URL: https://aur.archlinux.org/pyenv-virtualenvwrapper.git (read-only, click to copy)
Package Base: pyenv-virtualenvwrapper
Description: An alternative approach to manage virtualenvs from pyenv.
Upstream URL: https://github.com/pyenv/pyenv-virtualenvwrapper
Licenses: MIT
Submitter: mdemierre
Maintainer: ayr-ton
Last Packager: mdemierre
Votes: 2
Popularity: 0.24
First Submitted: 2017-09-12 19:17
Last Updated: 2017-09-12 19:17

Pinned Comments

ayr-ton commented on 2018-10-20 12:12

https://github.com/ayr-ton/PKGBUILDs/tree/master/pyenv-virtualenvwrapper

Latest Comments

Cbhihe commented on 2019-04-19 07:39

The bug report below was forwarded to peek824545201@gmail.com, owner / maintainer of the github repo.

Cbhihe commented on 2019-04-18 19:26

=======

I report this here because the corresponding github page does not have an issue report form available.

=======

I installed pyenvand pyenv-virtualenvwrapper exactly 4 days ago. Config + getting the hang of things took me a while, but done.

After creating a virtual environment, say 'py2.7sphinx', and trying to switch to it with workon py2.7sphinx, I got an error message and although the virtualenv was activated $(pwd) was not changed to the project's directory. Instead I systematically got the following in stderr: bash: cd: $' 1\t/home/$USER/Academic-research/py2.7sphinx': No such file or directory

This is reproducible. I ran the same with set -x and discovered that after unalias -a, the anomaly disappeared. So I set out to find which of my aliases conflicted with workon. It turns out the conflict came from my modifying the cat cmd, with: alias cat='cat -n'

pyenv devs should be made aware of this if anyone has a direct channel to reach them.

ayr-ton commented on 2018-10-20 12:12

https://github.com/ayr-ton/PKGBUILDs/tree/master/pyenv-virtualenvwrapper