Bug 1319879 - using pyudev wildcard import does not work at top level
Summary: using pyudev wildcard import does not work at top level
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-pyudev
Version: 7.2
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-21 18:00 UTC by mulhern
Modified: 2018-11-16 15:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-16 15:23:43 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description mulhern 2016-03-21 18:00:40 UTC
Description of problem:

In interpreter,

> from pyudev import *

causes exception:

>>> from pyudev import *
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: Item in ``from list'' not a string

Version-Release number of selected component (if applicable):

0.16.1 through current (0.19)

How reproducible:

Always.

Steps to Reproduce:
1. Use wildcard import at pyudev top level, observe exception.

Actual results:

TypeError raised.

Expected results:

Exposed names successfully imported.

Additional info:

Low priority because the work-around is just to specify the name to be imported,
and that is generally considered better practice anyway.

The problem is because pyudev treats all literal strings as unicode.

Comment 2 mulhern 2016-03-22 12:23:28 UTC
I'll take this until I manage to fix it upstream.

Comment 3 mulhern 2016-04-29 21:24:27 UTC
This is fixed in version 0.20. I wouldn't recommend back-porting the fix. There were a lot of text changes in a lot of import lines, the patch would not apply cleanly.

Comment 7 Red Hat Bugzilla Rules Engine 2018-11-16 15:23:43 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.


Note You need to log in before you can comment on or make changes to this bug.