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!
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!
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
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
|
DetailsThe 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 " 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! |
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
Sunday, 15 May 2011, 21:18 GMT
Reason for closing: None
Additional comments about closing: Thomas asked the closure
EDIT : Probably a download error ... working now.
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).
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"
Sorry, wish I had more time :(