[issue15281] pyvenv --symlinks option is a no-op?

2013-04-15 Thread Vinay Sajip
Vinay Sajip added the comment: 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. --

[issue15281] pyvenv --symlinks option is a no-op?

2013-04-15 Thread Piotr Dobrogost
Piotr Dobrogost added the comment: 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. -- ___ Python tracker rep...@bugs.python.org

[issue15281] pyvenv --symlinks option is a no-op?

2013-04-14 Thread Piotr Dobrogost
Piotr Dobrogost added the comment: 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? -- nosy: +piotr.dobrogost

[issue15281] pyvenv --symlinks option is a no-op?

2012-07-08 Thread Roundup Robot
Roundup Robot devn...@psf.upfronthosting.co.za added the comment: 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.

[issue15281] pyvenv --symlinks option is a no-op?

2012-07-07 Thread Antoine Pitrou
Changes by Antoine Pitrou pit...@free.fr: -- nosy: pitrou priority: normal severity: normal status: open title: pyvenv --symlinks option is a no-op? ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15281

[issue15281] pyvenv --symlinks option is a no-op?

2012-07-07 Thread Antoine Pitrou
New submission from Antoine Pitrou pit...@free.fr: 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

[issue15281] pyvenv --symlinks option is a no-op?

2012-07-07 Thread Martin v . Löwis
Martin v. Löwis mar...@v.loewis.de added the comment: Try --no-symlinks. -- nosy: +loewis ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue15281 ___

[issue15281] pyvenv --symlinks option is a no-op?

2012-07-07 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: $ 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 :-) --

[issue15281] pyvenv --symlinks option is a no-op?

2012-07-07 Thread Vinay Sajip
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment: 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

[issue15281] pyvenv --symlinks option is a no-op?

2012-07-07 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: 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

[issue15281] pyvenv --symlinks option is a no-op?

2012-07-07 Thread Vinay Sajip
Vinay Sajip vinay_sa...@yahoo.co.uk added the comment: 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. -- ___ Python tracker