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#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
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
|
DetailsSummary 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
Friday, 15 July 2011, 20:37 GMT
Reason for closing: Fixed
Additional comments about closing: bpython/bpython2 are in community now
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.
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!
Also, as a heads up, the BR I linked to is marked as a duplicate.
And it's marked as fixed since 4th, this month.
I'm going to give it a try building it, tomorrow.
If you would have some time to investigate it, please check out the last comment on https://bugs.archlinux.org/task/23730
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.