Arch Linux

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#48363 - python2-packaging 16.5-1 issue

Attached to Project: Arch Linux
Opened by Denis (mexus) - Sunday, 28 February 2016, 11:15 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 28 February 2016, 14:20 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After a recent system upgrade (28 Feb 2016) I've found that I'm not able to use a python application anymore:

Traceback (most recent call last):
File "test.py", line 1, in <module>
from pkg_resources import load_entry_point
File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 78, in <module>
__import__('pkg_resources.extern.packaging.requirements')
File "/usr/lib/python2.7/site-packages/pkg_resources/extern/__init__.py", line 42, in load_module
__import__(extant)
File "/usr/lib/python2.7/site-packages/packaging/requirements.py", line 59, in <module>
MARKER_EXPR = originalTextFor(MARKER_EXPR())("marker")
TypeError: __call__() takes exactly 2 arguments (1 given)

So I've asked about this on #archlinux (on freenode) and I was told that most probably it's an issue in the "originalTextFor" function.
I'm not good at python so maybe it's an issue somewhere else, so please tell me if I'm wrong and show me the right way to do the things.


Additional info:
* package version(s)
extra/python2-packaging 16.5-1
extra/python2 2.7.11-1
extra/python2-setuptools 1:20.2.2-1

Steps to reproduce:
$ echo "from pkg_resources import load_entry_point" > test.py
$ python2 test.py
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 28 February 2016, 14:20 GMT
Reason for closing:  Not a bug
Comment by Denis (mexus) - Sunday, 28 February 2016, 13:03 GMT
It was my local user configuration that was screwed: for some reason there was a file "pyparsing.py" in my "~/.local/lib/python2.7/site-packages". I've removed it and now everything works fine.
Sorry for a false report.

Loading...