Paul Moore wrote:
> On Tuesday, 2 April 2013 12:28:40 UTC+1, mattn wrote:
> > I prefer rename python in current to python2, And define aliased command
> > 'python'.
> > And I think that command must not be modifiable for users.
> > So :python is specified python2 or python3 if it possible. And if both are
> > enabled, I prefer it's python3.
>
> I agree. Python 3 is becoming more common, so at some point having "python"
> mean "Python 2" will become obsolete. It requires some work to write Python
> code that is portable between Python 2 and 3, but it is certainly possible
> (and indeed it is the recommended approach to writing Python code that is
> portable between 2 and 3 these days).
>
> Very definitely, having :python mean "whichever of Python 2 or 3 is
> compiled in" makes sense.
Actually it doesn't. Python 2 and 3 are not compatible. You can't use
:python without knowing what version it is. Therefore :python will
always mean Python 2. Otherwise some percentage of the scripts will
just not work.
If you don't like this, complain to those who decided to make Python 3
not compatible with Python 2.
--
"A clear conscience is usually the sign of a bad memory."
-- Steven Wright
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
