Bug 966102

Summary:	pyquery not compatible with current lxml
Product:	[Fedora] Fedora	Reporter:	Jan ONDREJ <ondrejj>
Component:	python-pyquery	Assignee:	Brendan Jones <brendan.jones.it>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	18	CC:	brendan.jones.it, jeff, mcepl, mcepl
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-05 17:10:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jan ONDREJ 2013-05-22 13:30:38 UTC

Description of problem:
After stable update of python-lxml, pyquery looks to be not compatible with this version. Is there any chance to update pyquery to fix this problem?

Version-Release number of selected component (if applicable):
python-pyquery-0.6.1-5.fc18.noarch
python-lxml-3.2.1-1.fc18.x86_64

How reproducible:
always

Steps to Reproduce:
1. python
2. import pyquery

Actual results:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python2.7/site-packages/pyquery/__init__.py", line 12, in <module>
    from ajax import PyQuery
  File "/usr/lib/python2.7/site-packages/pyquery/ajax.py", line 3, in <module>
    from pyquery import PyQuery as Base
  File "/usr/lib/python2.7/site-packages/pyquery/pyquery.py", line 6, in <module>
    from cssselectpatch import selector_to_xpath
  File "/usr/lib/python2.7/site-packages/pyquery/cssselectpatch.py", line 6, in <module>
    from lxml.cssselect import Pseudo, XPathExpr, XPathExprOr, Function, css_to_xpath, Element
ImportError: cannot import name Pseudo

Comment 1 Jan ONDREJ 2013-05-22 13:38:30 UTC

Looks like pyquery-1.2.4 is compatible. Can you build it for fedora?
Even if this version looks to be not 100% backward compatible, it at least runs.

Comment 2 Matěj Cepl 2013-08-05 17:10:24 UTC


*** This bug has been marked as a duplicate of bug 980856 ***