Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install on Arch linux fails #120

Closed
youngmit opened this issue Jun 22, 2016 · 10 comments
Closed

Install on Arch linux fails #120

youngmit opened this issue Jun 22, 2016 · 10 comments

Comments

@youngmit
Copy link

I am trying to install cldoc on an Arch system, and having issues with the pyparsing dependency. cldoc seems to want exactly version 1.5.7, which appears to be incompatible with the current version of python2:

 % pip2 install --user pyparsing==1.5.7 --no-cache-dir
Collecting pyparsing==1.5.7
  Downloading pyparsing-1.5.7.zip (965kB)
    100% |████████████████████████████████| 972kB 26.0MB/s
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/usr/lib/python2.7/site-packages/setuptools/__init__.py", line 11, in <module>
        from setuptools.extern.six.moves import filterfalse, map
      File "/usr/lib/python2.7/site-packages/setuptools/extern/__init__.py", line 1, in <module>
        from pkg_resources.extern import VendorImporter
      File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 71, 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)

I'm not sure if this failure is due to some other issue, or if version 1.5.7 of pyparsing is not compatible with my current version of python (2.7.11). I'm unfamiliar with the MARKER_EXPR that is giving me the issue.

The version of pyparsing that is currently installed on my system is 2.1.4. Does cldoc need pyparsing==1.5.7, or would pyparsing>=1.5.7 suffice?

@refi64
Copy link

refi64 commented Jun 22, 2016

Pyparsing 1.5.7 does work under Python 2. This seems like something weird going on with your packaging...

@jessevdk
Copy link
Owner

I'm not against bumping the pyparsing version, but it does seem like it's a problem on your system as @kirbyfan64 mentions.

@Salamandar
Copy link

I got the exact same problem and I dont know where there would be a problem on my system ^^
The repositories of my distro are up to date:

1 extra/python-pyparsing 2.1.8-1 [installed]
    General parsing module for Python
2 extra/python2-pyparsing 2.1.8-1 [installed]
    General parsing module for Python

And there's just no (correct and clean) way to install the "old" (or not so much ?) pyparsing 1.5.7.

@refi64
Copy link

refi64 commented Sep 10, 2016

@Salamandar Try pip install pyparsing==1.5.7.

@Salamandar
Copy link

I just modified the file /usr/lib/python2.7/site-packages/cldoc-1.9-py2.7.egg-info/requires.txt to say
pyparsing >=1.5.7, and that works amazingly fine :)

@Salamandar
Copy link

@kirbyfan64 I could but that basically would break my distro's package management (or not, but I would not tempt the devil). I worked for some weeks on my laptop with this fix (and bumped on this problem today on my desktop) without issue.

@xgdgsc
Copy link

xgdgsc commented Oct 9, 2016

Works with anaconda2 python on archlinux.

@fennecdjay
Copy link

I just modified the file /usr/lib/python2.7/site-packages/cldoc-1.9-py2.7.egg-info/requires.txt to say
pyparsing >=1.5.7, and that works amazingly fine :)

I did it in setup.py and it is fine!

@catskul
Copy link

catskul commented Feb 17, 2018

This pull request upgrades pyparsing:

#131

@jessevdk
Copy link
Owner

jessevdk commented Apr 1, 2018

pyparsing has been upgraded to 2.2. Could you verify this now works for you?

@jessevdk jessevdk closed this as completed Apr 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants