osmgpsmap python bindings placed in site-packages rather than dist-packages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
osm-gps-map (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
During the jaunty development cycle, the transition was made from site-packages in python, to dist-packages. The configure script in the python-osmgpsmap didn't pick up the right location, until I just fixed this in a patch. However this is not available in jaunty. So when a user tries to use the module, they are told it cannot be found.
==Solution==
The bug was addressed in the development version by modifying the python/configure and python/aclocal.m4 files in the package, using a patch. The script now picks up the correct location for the python modules.
==Test Case==
TEST CASE: Using a python prompt, typing "import osmgpsmap" doesn't produce any errors.
TEST CASE: Alternatively, use this script, execute it, and observe the map loading. http://
summary: |
- [jaunty] Python bindings are still built against 2.5 rather than 2.6 + [jaunty] Python bindings placed in wrong directory |
Changed in osm-gps-map (Ubuntu): | |
assignee: | Andrew Gee (andrewgee) → nobody |
status: | Confirmed → Fix Committed |
tags: |
added: verification-done removed: verification-needed |
Creating a debdiff with a new changelog entry...