Menu

#3 Makefile hardcodes sitelib path

v1.0 (example)
closed-fixed
nobody
None
5
2015-05-10
2011-09-20
Rolf
No

The Makefile hardcodes a python 2.6 sitelib path. That's probably not a good idea.

Discussion

  • Andreas Bresser

    Andreas Bresser - 2012-02-13

    the makefile will be removed in the next release and replaced by a setup.py

     
  • Andreas Bresser

    Andreas Bresser - 2012-02-13
    • status: open --> open-accepted
     
  • Jérôme Lafréchoux

    I don't see the setup.py coming...

    Would it be better to change it to 2.7 in the meantime?

     
  • Thomas Spura

    Thomas Spura - 2015-05-07

    A workaround could be to use $(python -c "from distutils.sysconfig import get_python_lib; print get_python_lib(0)"). Would that work for you?

     
  • Jérôme Lafréchoux

    Seems to work on my machine.

    What is the 0 for in get_python_lib(0)? Why not

    $(python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()")

    ?

     
  • Thomas Spura

    Thomas Spura - 2015-05-08

    It makes sure that the platform independent version is taken, which is the default anyway if you omit it.

     
  • Jérôme Lafréchoux

    • status: open-accepted --> closed-fixed
    • Group: --> v1.0 (example)
     

Log in to post a comment.