FS#21374 - Pychecker not using /usr/bin/env python2

Attached to Project: Community Packages
Opened by Andy McMillan (mcmillan) - Wednesday, 20 October 2010, 22:21 GMT
Last edited by Ionut Biru (wonder) - Thursday, 21 October 2010, 04:34 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Forum post saying pychecker is failing after switch to python2. grepping for /usr/bin/env python gives the following output

/usr/lib/python2.7/site-packages/pychecker/CodeChecks.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/Config.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/OP.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/Stack.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/Warning.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/checker.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/function.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/msgs.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/printer.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/python.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/utils.py:#!/usr/bin/env python
/usr/lib/python2.7/site-packages/pychecker/warn.py:#!/usr/bin/env python


I think adding the following to the PKGBUILD should correct it

sed -i -e "s|#![ ]*/usr/bin/python$|#!/usr/bin/python2|" \
-e "s|#![ ]*/usr/bin/env python$|#!/usr/bin/env python2|" \
$(find $pkgdir -name '*.py')
This task depends upon

Closed by  Ionut Biru (wonder)
Thursday, 21 October 2010, 04:34 GMT
Reason for closing:  Fixed
Additional comments about closing:  pychecker-0.8.18-5
Comment by Ionut Biru (wonder) - Wednesday, 20 October 2010, 22:27 GMT
those shebangs are not used at all in pychecker and if is failing is doing from other reasons.
Comment by Andy McMillan (mcmillan) - Wednesday, 20 October 2010, 22:35 GMT
Ahh you're right, I missed they were shebanged. Would it be make sense to close this since it seems to incorrectly describe the problem and have a different bug report that's more appropriate?
Comment by Ionut Biru (wonder) - Wednesday, 20 October 2010, 22:36 GMT
fedora for example is removing them for good :P

Loading...