Issue 15281: pyvenv --symlinks option is a no-op? (original) (raw)

Created on 2012-07-07 15:37 by pitrou, last changed 2022-04-11 14:57 by admin. This issue is now closed.

| Messages (10) | | | | | | | | | | | | | | | | | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | ---------------------- | | -------- | | ----------- | | ---------------------- | | ----------------------- | ------------------------------------------------- | ---------- | ------ | -------------- | --------------------------------------------------------- | | msg164879 - (view) | Author: Antoine Pitrou (pitrou) * | Date: 2012-07-07 15:38 | | | | | | | | | | | | | | | It seems that, regardless of whether I specify --symlinks or not, pyvenv always creates symlinks: $ pyvenv-3.3 env $ tree env/ env/ |-- bin | | -- activate | | -- pydoc | | -- pysetup3 | | -- python -> python3.3 | | -- python3 -> python3.3 | `-- python3.3 -> /home/antoine/opt/bin/python3.3 | -- include | -- lib | `-- python3.3 | `-- site-packages `-- pyvenv.cfg 5 directories, 7 files | | msg164895 - (view) | Author: Martin v. Löwis (loewis) * | Date: 2012-07-07 16:06 | | | | | | | | | | | | | | | Try --no-symlinks. | | | | | | | | | | | | | | | | | msg164899 - (view) | Author: Antoine Pitrou (pitrou) * | Date: 2012-07-07 16:09 | | | | | | | | | | | | | | | $ pyvenv-3.3 --no-symlinks env usage: venv [-h] [--system-site-packages] [--symlinks] [--clear] [--upgrade] ENV_DIR [ENV_DIR ...] venv: error: unrecognized arguments: --no-symlinks :-) | | | | | | | | | | | | | | | | | msg164927 - (view) | Author: Vinay Sajip (vinay.sajip) * | Date: 2012-07-07 19:52 | | | | | | | | | | | | | | | Following discussions on python-dev, the default is always to symlink, except on Windows (no support for true symlinks on XP and older) and Mac OS X (problems with framework builds). The --symlinks indicates, on those platforms where symlinks is not the default, to use symlinks anyway. This will most likely only be useful on Windows Vista, Windows 7 and Mac OS X with a non-framework build of Python. | | | | | | | | | | | | | | | | | msg164928 - (view) | Author: Antoine Pitrou (pitrou) * | Date: 2012-07-07 20:00 | | | | | | | | | | | | | | | > Following discussions on python-dev, the default is always to symlink, > except on Windows (no support for true symlinks on XP and older) and > Mac OS X (problems with framework builds). The --symlinks indicates, > on those platforms where symlinks is not the default, to use symlinks > anyway. This will most likely only be useful on Windows Vista, Windows > 7 and Mac OS X with a non-framework build of Python. Ok, then it might be nice to make the usage string (which is printed with pyvenv --help) clearer. | | | | | | | | | | | | | | | | | msg164930 - (view) | Author: Vinay Sajip (vinay.sajip) * | Date: 2012-07-07 20:07 | | | | | | | | | | | | | | | > Ok, then it might be nice to make the usage string (which is printed with pyvenv --help) clearer. Fair point, I'll update the help text to be clearer. | | | | | | | | | | | | | | | | | msg165024 - (view) | Author: Roundup Robot (python-dev) | Date: 2012-07-08 16:51 | | | | | | | | | | | | | | | New changeset 9c345b4bd97e by Vinay Sajip in branch 'default': Closes #15281, #15283: Don't make venv scripts executable, but copy source mode instead, and provide better help for pyvenv. http://hg.python.org/cpython/rev/9c345b4bd97e | | | | | | | | | | | | | | | | | msg186961 - (view) | Author: Piotr Dobrogost (piotr.dobrogost) | Date: 2013-04-14 22:20 | | | | | | | | | | | | | | | > Following discussions on python-dev, the default is always to symlink, > except on Windows (no support for true symlinks on XP and older) and In this case couldn't symlinks be automatically used on Windows Vista or newer? | | | | | | | | | | | | | | | | | msg186969 - (view) | Author: Vinay Sajip (vinay.sajip) * | Date: 2013-04-15 08:45 | | | | | | | | | | | | | | | > In this case couldn't symlinks be automatically used on Windows Vista or newer? It seems simpler if the default behaviour is the same on all Windows flavours - you can specify --symlinks if you're on Windows Vista or later. | | | | | | | | | | | | | | | | | msg187034 - (view) | Author: Piotr Dobrogost (piotr.dobrogost) | Date: 2013-04-15 21:57 | | | | | | | | | | | | | | | It's simpler but is it better this way? I doubt. I think we should take advantage of symlinks whenever we can and only fallback to copying if they are not available. | | | | | | | | | | | | | | | |