2010/8/18 Mateusz Paprocki :
>
> The syntax was added in polys11 branch, e.g.:
>
> In [1]: symbols('x:z')
> Out[1]: (x, y, z)
>
> In [2]: symbols('a:d,x:z')
> Out[2]: (a, b, c, d, x, y, z)
>
> In [3]: symbols(('a:d', 'x:z'))
> Out[3]: ((a, b, c, d), (x, y, z))
>
> In [4]: symbols('xx:zz')
> (...)
>
2010/8/19 Aaron S. Meurer :
> But you can still go back and fix commit messages, without changing any of
> the actual code history.
Beware, changing the commit message also changes the commit hash I think.
Vinzent
--
You received this message because you are subscribed to the Google Groups
"s
Yes it does (and as I said, you should use the original hash for the code
samples). But it won't change any of the code history, or related attribution,
which is what seemed to be worrying Brian.
It's best to start a hilbert3 to do this if you are going to do it, so you
don't loose anything.
Would it be possible to have it recognize numbers as in
symbols('a1:10') -> a1, a2, a3, ..., a10? One could also have the
parser only recognize the number(s) or single characters on either
side of the : so that symbols('aa:z') would give aa, ab, ac, ..., az.
--
You received this message because y
