Issue1716

{{{

Jython 2.5.2 (Release_2_5maint:7220, Mar 12 2011, 17:25:54) 
[Java HotSpot(TM) 64-Bit Server VM (Apple Inc.)] on java1.6.0_17
Type "help", "copyright", "credits" or "license" for more information.
>>> xrange(3)[0:1]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
java.lang.NullPointerException
	at org.python.core.PySystemState.displayhook(PySystemState.java:1234)
	at org.python.core.PySystemStateFunctions.__call__(PySystemState.java:1409)
	at org.python.core.PyObject.invoke(PyObject.java:3585)
	at org.python.core.Py.printResult(Py.java:1800)
	at org.python.pycode._pyx1.f$0(<stdin>:1)
	at org.python.pycode._pyx1.call_function(<stdin>)
	at org.python.core.PyTableCode.call(PyTableCode.java:165)
	at org.python.core.PyCode.call(PyCode.java:18)
	at org.python.core.Py.runCode(Py.java:1261)
	at org.python.core.Py.exec(Py.java:1305)
	at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:215)
	at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter.java:89)
	at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:70)
	at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:46)
	at org.python.util.InteractiveConsole.push(InteractiveConsole.java:110)
	at org.python.util.InteractiveConsole.interact(InteractiveConsole.java:90)
	at org.python.util.jython.run(jython.java:317)
	at org.python.util.jython.main(jython.java:129)

java.lang.NullPointerException: java.lang.NullPointerException




Python 2.5.4 (r254:67916, Aug  2 2010, 20:09:39) 
[GCC 4.2.1 (Apple Inc. build 5646)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> xrange(3)[0:1]
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: sequence index must be integer, not 'slice'
}}}

Patch that makes slicing a xrange object raise a TypeError.

Fix looks simple enough to me. Ok to merge?

Alex: This one and four others that I identified yesterday look good for merging - but I'd like to put out 2.5.3 final first on Monday. Would it help if I promise that 2.5.4 will come out *much* faster than 2.5.3 did? I'm thinking that 2.5.4 should come out in 1-3 months. I really want to get a final 2.5.3 out ASAP, but new bugfixes trigger another RC.

As long as they aren't regressions from 2.5.2. I recall that at least one of them was a regression.

Alex: while I agree that regressions are particularly annoying, this release is already way overdue - I will strive to get a 2.5.4 out soon (1-3 months is my goal). Do you remember which bug is a regression? I remember one about bytecode length limits, but that's too big a fix for any short term.

oops fixed in 2.7 but I really should have fixed for 2.5.4 - will backport shortly and close.

Fully fixed for 2.5 and 2.7 in http://hg.python.org/jython/rev/353121061da9 Thanks Andreas Stührk!

Patch actually applied in these:
2.5 http://hg.python.org/jython/rev/3345d6e15c79
2.7 http://hg.python.org/jython/rev/d77503b7a755