[Bug 1250877] [NEW] Python3 modules are not installed in the right path

[Shu Hung (Koala)]

Public bug reported:

[Note: this might be a bug in autoconf rather than automake, I'm not
entirely sure]

On Ubuntu (and I think also on Debian), Python3 modules are installed in
/usr/lib/python3/dist-packages

However, that's different from the upstream path, which is
/usr/lib/python3.3/site-packages

Python3 modules building with the Autotools will get installed in the
upstream-preferred path, and as a result, Python3 won't find them.

Here is a way to reproduce it:

1. First, install libcangjie from Git:

    git clone git://github.com/Cangjians/libcangjie
    cd libcangjie
    ./autogen.sh --prefix=/usr && make && sudo make install

2. Now, install pycangjie:

    git clone git://github.com/Cangjians/pycangjie
    cd pycangjie
    ./autogen.sh --prefix=/usr && make && sudo make install

(you might need to install some dependencies, like libsqlite3-dev,
python3-de and cython)

Now, observe how the module was installed in /usr/lib/python3.3/site-
packages/cangjie, where Python3 won't find it.

This installation path is not hardcoded in the pycangjie build process,
it is **automatically discovered by the autotools**.

If Ubuntu (or is it Debian?) decides to change where Python3 modules are
installed, then shouldn't it also try to ensure that they actually get
installed there?

** Affects: automake (Ubuntu)
     Importance: Undecided
         Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to automake in Ubuntu.
https://bugs.launchpad.net/bugs/1250877

Title:
  Python3 modules are not installed in the right path

Status in “automake” package in Ubuntu:
  Confirmed

Bug description:
  [Note: this might be a bug in autoconf rather than automake, I'm not
  entirely sure]

  On Ubuntu (and I think also on Debian), Python3 modules are installed
  in /usr/lib/python3/dist-packages

  However, that's different from the upstream path, which is
  /usr/lib/python3.3/site-packages

  Python3 modules building with the Autotools will get installed in the
  upstream-preferred path, and as a result, Python3 won't find them.

  Here is a way to reproduce it:

  1. First, install libcangjie from Git:

      git clone git://github.com/Cangjians/libcangjie
      cd libcangjie
      ./autogen.sh --prefix=/usr && make && sudo make install

  2. Now, install pycangjie:

      git clone git://github.com/Cangjians/pycangjie
      cd pycangjie
      ./autogen.sh --prefix=/usr && make && sudo make install

  (you might need to install some dependencies, like libsqlite3-dev,
  python3-de and cython)

  Now, observe how the module was installed in /usr/lib/python3.3/site-
  packages/cangjie, where Python3 won't find it.

  This installation path is not hardcoded in the pycangjie build
  process, it is **automatically discovered by the autotools**.

  If Ubuntu (or is it Debian?) decides to change where Python3 modules
  are installed, then shouldn't it also try to ensure that they actually
  get installed there?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/automake/+bug/1250877/+subscriptions