On Monday, October 29, 2012 1:38:04 AM UTC-7, Chris Rebert wrote:
> On Mon, Oct 29, 2012 at 1:24 AM,
>
> > On Sunday, October 28, 2012 9:44:56 PM UTC-7, alex23 wrote:
>
> >> On Oct 29, 2:09 pm, Andrew < wrote:
>
> You never wrapped `a` in a RangedSlicer or otherwise made use of RangedSlicer!
>
On Sunday, October 28, 2012 9:44:56 PM UTC-7, alex23 wrote:
> On Oct 29, 2:09 pm, Andrew wrote:
>
> > I use this arbitrary range code *often* so I need a general purpose
> > solution.
>
> > I looked up slice() but the help is of no use, I don't even know how I might
>
> > overload it to embed
On Sunday, October 28, 2012 10:14:03 PM UTC-7, Paul Rubin wrote:
> Andrew writes:
>
> > So: Why does python choose to convert them to positive indexes, and
>
> > have slice operate differently than xrange
>
>
>
> There was a thread a few years back, I think started by Bryan Olson,
>
> that m
On Sunday, October 28, 2012 8:43:30 PM UTC-7, Ian wrote:
> On Sun, Oct 28, 2012 at 9:12 PM, andrew wrote:
>
> > The slice operator does not give any way (I can find!) to take slices from
> > negative to positive indexes, although the range is not empty, nor the
> > expected indexes out of range
The slice operator does not give any way (I can find!) to take slices from
negative to positive indexes, although the range is not empty, nor the expected
indexes out of range that I am supplying.
Many programs that I write would require introducing variables and logical
statements to correct t
