The path for python extensions should reflect the 2.0 api
Bug #215714 reported by
Stani
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Phatch |
Fix Released
|
Medium
|
Stani | ||
nautilus-python |
Fix Released
|
Medium
|
|||
nautilus-python (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
phatch (Ubuntu) |
Fix Released
|
Undecided
|
Stani |
Bug Description
Right now python-nautilus creates the folder according to the 2.0 api for nautilus extensions:
/usr/lib/
but nautilus loads python extensions from the deprecated 1.0 api location:
/usr/lib/
This is inconsistent and causes the following problems:
- any extension in /usr/lib/
- incompatible scripts (based on the 1.0 api) might be loaded from /usr/lib/
A patch is needed which makes sure nautilus loads from the 2.0 folder.
Changed in nautilus-python: | |
status: | New → Confirmed |
Changed in phatch: | |
status: | Confirmed → In Progress |
status: | Confirmed → In Progress |
status: | In Progress → Fix Committed |
Changed in phatch: | |
status: | In Progress → Fix Committed |
Changed in nautilus-python: | |
status: | Unknown → New |
Changed in nautilus-python: | |
status: | New → Fix Released |
Changed in nautilus-python: | |
importance: | Unknown → Medium |
To post a comment you must log in.
I think this is indeed a problem. I'm working on a patch.