Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
Fixed with r73114 (trunk), r73117 (py3k), r73119 (2.6) and r73120 (3.0)
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
Changes by Amaury Forgeot d'Arc amaur...@gmail.com:
--
assignee: - amaury.forgeotdarc
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4547
___
___
Georg Brandl ge...@python.org added the comment:
I think you can apply this.
--
nosy: +georg.brandl
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4547
___
New submission from fboule [EMAIL PROTECTED]:
This concerns a known bug in the frame_setlineno() function for Python
2.5.x and 2.6.x (maybe in earlier/later version too). It is not possible
to use this function when the address or line offset in lnotab are
greater than 127. The problem comes
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Attached patch is similar (it declares the variable as unsigned char*)
and adds a test.
--
keywords: +needs review, patch
nosy: +amaury.forgeotdarc
stage: - patch review
Added file:
fboule [EMAIL PROTECTED] added the comment:
Is it intended to be applied on Python 2.5.x and/or Python 2.6.x (and
when)? The current Python 2.6.1 release does not have the fix.
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4547
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment:
Yes, target is 2.6.2 and up, 3.0.1 and up.
--
versions: +Python 3.0 -Python 2.5, Python 2.5.3
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue4547
