Community Packages

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#23536 - [bpython] Why bpython is NOT bpython3?

Attached to Project: Community Packages
Opened by Kiril Vladimiroff (Vladimiroff) - Thursday, 31 March 2011, 16:57 GMT
Last edited by Thomas Dziedzic (tomd123) - Friday, 15 July 2011, 20:37 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Thomas Dziedzic (tomd123)
Architecture All
Severity Low
Priority Normal
Reported Version 3.5.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
Some months ago, in Arch Linux, Python is Python3. I've just noticed that there is a package bpython which is for python 2.7.
Why so NOT consistence? I think bpython3(http://aur.archlinux.org/packages.php?ID=37543) to be bpython, and current bpython to be bpython2?
This task depends upon

Closed by  Thomas Dziedzic (tomd123)
Friday, 15 July 2011, 20:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  bpython/bpython2 are in community now
Comment by Thomas Dziedzic (tomd123) - Friday, 01 April 2011, 04:52 GMT
The reason why I haven't moved this into [community] is because python has a bug in it which is causing bpython3 to crash the interpretor within minutes of starting the program.
Relevant upstream BR: http://bugs.python.org/issue10509

I haven't had time to investigate it further besides finding out bpython community already experienced this and recommended patching python.
As soon as I figure out what to do about the segfault in python, I will bring it into [community].

If you want to help out, find out what exactly is the problem, if the patch fixes it, if it has been accepted by upstream, and post a request to the tracker to add the patch to arch's python if so.
Comment by Kiril Vladimiroff (Vladimiroff) - Friday, 01 April 2011, 13:02 GMT
Oh, this is a solid reason.
I will follow this bug ticket, that you gave me, and will make some investigation for a patch and when it comes something that fixes the current issue, will notice you here.

Thank you, for your response!
Comment by Thomas Dziedzic (tomd123) - Friday, 01 April 2011, 13:33 GMT
ok, any help is appreciated :)
Also, as a heads up, the BR I linked to is marked as a duplicate.
Comment by Kiril Vladimiroff (Vladimiroff) - Wednesday, 13 April 2011, 00:12 GMT
This is the ticket: http://bugs.python.org/issue9319
And it's marked as fixed since 4th, this month.
I'm going to give it a try building it, tomorrow.
Comment by Thomas Dziedzic (tomd123) - Sunday, 17 April 2011, 06:30 GMT
@kiril, it seems there's a stumbling block in getting the patches accepted.
If you would have some time to investigate it, please check out the last comment on https://bugs.archlinux.org/task/23730
Comment by Kiril Vladimiroff (Vladimiroff) - Sunday, 17 April 2011, 09:29 GMT
@Thomas, I've tried it and I get the same issue.
Comment by Thomas Dziedzic (tomd123) - Thursday, 19 May 2011, 14:45 GMT
This bug will have to wait for python 3.2.1 to come out
Comment by Kiril Vladimiroff (Vladimiroff) - Thursday, 19 May 2011, 17:34 GMT
Yep. I've compiled Python 3.2.1 RC1 with quite little changes in current PKGBUILD.
The only thing I've noticed is that on check() test_pydoc is breaking.

However bpython3 from AUR is working like a charm with 3.2.1 RC1, where this bug blocking bpython3 is fixed.
Comment by Thomas Dziedzic (tomd123) - Monday, 11 July 2011, 21:56 GMT
bpython in community-testing is now the python3 version, please test, otherwise I will close this bug when bpython (v3) moves to community

Loading...