Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#23730 - [python] patchs to fix a couple of solved upstream issues.

Attached to Project: Arch Linux
Opened by Thomas Dziedzic (tomd123) - Tuesday, 12 April 2011, 22:39 GMT
Last edited by Andrea Scarpino (BaSh) - Sunday, 15 May 2011, 21:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Stéphane Gaudreault (stephane)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

The current python 3.2-1 in [extra] contains a condition which causes a segfault:
http://bugs.python.org/issue9319

This is made very apparent when you try to run something like bpython3, which causes the interpretor to segfault within a couple of commands.
It has prevented me from implementing " FS#23536  - [bpython] Why bpython is NOT bpython3?"

I have attached patches which fix this issue.
I have been running python 3.2 with the patches mentioned and all is well so far :)

Cheers!
   PKGBUILD.diff (1.5 KiB)
   6e9dc970ac0e.diff (12.2 KiB)
   7b8d625eb6e4.diff (5.5 KiB)
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Sunday, 15 May 2011, 21:18 GMT
Reason for closing:  None
Additional comments about closing:  Thomas asked the closure
Comment by Stéphane Gaudreault (stephane) - Wednesday, 13 April 2011, 11:17 GMT
There is a rejected hunk when applying the patch on Parser/tokenizer.c. I will look at this later today.
EDIT : Probably a download error ... working now.
Comment by Thomas Dziedzic (tomd123) - Wednesday, 13 April 2011, 13:23 GMT
Strange.. I built it fine using makepkg and extra-x86_64-build.
I have attached a tar file of my files in case there is a weirdness issue going on somewhere.
Hope this helps.

Relevant output:

patching file Include/parsetok.h
patching file Makefile.pre.in
Hunk #1 succeeded at 236 (offset -2 lines).
Hunk #2 succeeded at 251 (offset -2 lines).
patching file Modules/parsermodule.c
patching file Parser/parsetok.c
Hunk #5 succeeded at 276 (offset 1 line).
patching file Parser/parsetok_pgen.c
patching file Parser/tokenizer.c
patching file Parser/tokenizer.h
patching file Python/pythonrun.c
Hunk #2 succeeded at 1870 (offset -18 lines).
Hunk #3 succeeded at 1901 (offset -18 lines).
Hunk #4 succeeded at 1923 (offset -18 lines).
Hunk #5 succeeded at 1938 (offset -18 lines).
Hunk #6 succeeded at 1951 (offset -18 lines).
Hunk #7 succeeded at 1965 (offset -18 lines).
Hunk #8 succeeded at 1989 (offset -18 lines).
Hunk #9 succeeded at 2074 (offset -18 lines).
patching file Lib/test/test_imp.py
patching file Parser/tokenizer.c
patching file Parser/tokenizer.h
patching file Python/import.c
Hunk #1 succeeded at 120 with fuzz 1 (offset -4 lines).
Hunk #2 succeeded at 3174 with fuzz 2 (offset -366 lines).
patching file Python/traceback.c
Hunk #1 succeeded at 13 with fuzz 2 (offset -5 lines).
Hunk #2 succeeded at 246 (offset -5 lines).
   python.tar (30 KiB)
Comment by Stéphane Gaudreault (stephane) - Wednesday, 13 April 2011, 16:21 GMT
Running the test suite with this patch, I get a failure with test_imp :

test test_imp failed -- File "<string>", line None
SyntaxError: Non-UTF-8 code starting with '\xf6' in file <string> on line 1, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/build/src/Python-3.2/Lib/test/test_imp.py", line 65, in test_find_module_encoding
imp.find_module, 'badsyntax_pep3120', path)
AssertionError: "Non-UTF-8 code starting with '\\xf6' in file .*badsyntax_pep3120.py" does not match "Non-UTF-8 code starting with '\xf6' in file <string> on line 1, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details"
Comment by Thomas Dziedzic (tomd123) - Wednesday, 20 April 2011, 19:40 GMT
As I am running short on time and I'm not particularly interested in fixing this any time soon, you could probably close this bug if no one else is interested in investigating the issue.
Sorry, wish I had more time :(

Loading...