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#46866 - [python-pexpect] 4.0.1-1 pkgbuild does not reflect dependency on python-ptyprocess

Attached to Project: Community Packages
Opened by Andy (andydecleyre) - Sunday, 25 October 2015, 05:47 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 25 October 2015, 13:25 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The upstream source has a new doc/requirements.txt listing ptyprocess. Without it, programs like ipython will fail to launch with "ImportError: No module named ptyprocess".

This affects python-pexpect and python2-pexpect 4.0.1-1, in turn breaking ipython and ipython2 4.0.0-4.

Steps to reproduce:
# pacman -S ipython
$ ipython
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 25 October 2015, 13:25 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#46864 
Comment by Chih-Hsuan Yen (yan12125) - Sunday, 25 October 2015, 05:51 GMT
Another duplicate lol #46864
Comment by Andy (andydecleyre) - Sunday, 25 October 2015, 05:54 GMT
Ah, well the string "python-pexpect" does not appear in #46864, making it invulnerable to searches.
Comment by Chih-Hsuan Yen (yan12125) - Sunday, 25 October 2015, 06:01 GMT
Well I got the same embarrassment https://bugs.archlinux.org/task/46865 :D

Loading...