Package Details: python2-empy 3.3.4-1

Git Clone URL: https://aur.archlinux.org/python2-empy.git (read-only, click to copy)
Package Base: python2-empy
Description: A powerful and robust templating system for Python.
Upstream URL: http://www.alcyone.com/software/empy
Licenses: LGPL
Submitter: hauptmech
Maintainer: ljmf00
Last Packager: ljmf00
Votes: 20
Popularity: 0.000000
First Submitted: 2012-04-06 14:59 (UTC)
Last Updated: 2019-07-02 19:58 (UTC)

Latest Comments

de-vries commented on 2015-03-19 20:04 (UTC)

Also needs a makedep on python2-setuptools I believe.

neoDEH commented on 2014-10-05 03:34 (UTC)

@bchretien good idea. Thanks for the help. And good job on adding support in Arch linux. If you need help with future releases just ping me.

bchretien commented on 2014-10-04 21:33 (UTC)

@neoDEH: just to be sure, use the full command. You can make an alias for it, e.g.: alias catkin_make="catkin_make -DPYTHON_EXECUTABLE=/usr/bin/python2 -DPYTHON_INCLUDE_DIR=/usr/include/python2.7 -DPYTHON_LIBRARY=/usr/lib/libpython2.7.so"

neoDEH commented on 2014-10-04 18:57 (UTC)

@bchretien So even if i do alias python=/usr/bin/python2 i will have to use catkin_make -DPYTHON_EXECUTABLE=/usr/bin/python2 -DPYTHON_INCLUDE_DIR=/usr/include/python2.7 -DPYTHON_LIBRARY=/usr/lib/libpython2.7.so

bchretien commented on 2014-10-04 18:40 (UTC)

@neoDEH: this is explained in the documentation you just linked. "Finally, when initializing a catkin workspace, as specified in the tutorial pages, instead of issuing the command catkin_make some Python 2 flags will need to be added, as in catkin_make -DPYTHON_EXECUTABLE=/usr/bin/python2 -DPYTHON_INCLUDE_DIR=/usr/include/python2.7 -DPYTHON_LIBRARY=/usr/lib/libpython2.7.so"

neoDEH commented on 2014-10-04 17:56 (UTC)

@bchretien i am having problems with catkin_make. Whatever i do it makes use of /usr/bin/python instead of /usr/bin/python2 but if i do catkin_make -DPYTHON_EXECUTABLE=/usr/bin/python2 it works I tried everything suggested in http://wiki.ros.org/indigo/Installation/Arch If this is the wrong place to ask this kindly do advise appropiate forum.

bchretien commented on 2014-08-23 10:04 (UTC)

@exuvo: thanks for the report, indeed pypi servers should be more reliable.

exuvo commented on 2014-08-23 03:39 (UTC)

alcyone.com seems to be down. I found an identical source (same md5 hash) at https://pypi.python.org/packages/source/E/EmPy/empy-3.3.2.tar.gz .

ccryp7 commented on 2014-07-25 12:10 (UTC)

@bchretien: thanks, I had a failing hydro build before, can't reproduce/remember which package was problematic though.

bchretien commented on 2014-07-24 14:07 (UTC)

@ccryp7: I double-checked the install, gave execute permissions to the script in /usr/lib/... and made sure that Python 2 is called when the script is used. If you still have problems, please let me know.

bchretien commented on 2014-07-24 13:35 (UTC)

@ccryp7: for instance, while building ros-indigo-rosbash: -- Found PythonInterp: /usr/bin/python2 (found version "2.7.8") -- Using PYTHON_EXECUTABLE: /usr/bin/python2 -- Using default Python package layout -- Found PY_em: /usr/lib/python2.7/site-packages/em.pyc -- Using empy: /usr/lib/python2.7/site-packages/em.pyc Have you actually had a problem with empy and Hydro/Indigo packages?

bchretien commented on 2014-07-24 13:26 (UTC)

@ccryp7: I don't think that this is a requirement. In /opt/ros/{hydro,indigo}/shared/catkin/cmake/empy.cmake, if the executable is not found, then it relies on the Python module. Also, this would create a conflict between Python 2/3 versions of this package if both start providing /usr/bin/empy.

ccryp7 commented on 2014-07-22 08:39 (UTC)

ROS makes use of this package, but requires the em.py binary to be installed at /usr/bin/empy. Here's a patch to handle that: --- ../aur-python2-empy/PKGBUILD 2014-02-12 15:00:14.000000000 +0100 +++ PKGBUILD 2014-07-22 10:09:49.703716772 +0200 @@ -21,4 +21,6 @@ package() { cd ${srcdir}/empy-$pkgver python2 setup.py install -O2 --skip-build --prefix=/usr --root=${pkgdir} + mkdir -p ${pkgdir}/usr/bin + install em.py ${pkgdir}/usr/bin/empy }

bchretien commented on 2014-01-19 12:18 (UTC)

@hauptmech: thanks, I adopted it, and split install between build() and package().

hauptmech commented on 2014-01-19 11:09 (UTC)

Updated as requested and disowning since I don't use this stuff anymore...

bchretien commented on 2014-01-18 22:32 (UTC)

Hi, thanks for your responsiveness :-) I think the install command should be: python2 setup.py install --prefix=/usr --root=$pkgdir

hauptmech commented on 2014-01-18 17:17 (UTC)

Cleaned up dependency error and warning.

bchretien commented on 2014-01-18 15:26 (UTC)

+1 on r00tine's comment. This should use python2 as a dependency.

silent_crash commented on 2013-09-25 18:51 (UTC)

building and installing the package using yaourt yielded this warning: WARNING: Using a PKGBUILD without a package() function is deprecated This doesn't seem to break anything, though.

r00tine commented on 2013-08-17 14:21 (UTC)

the dependency should be python2, not python since python == python3

hauptmech commented on 2013-01-17 11:33 (UTC)

Fixed...

morxa commented on 2012-10-29 15:27 (UTC)

PKGBUILD doesn't work anymore. I suppose you use $srcdir and $pkgdir instead of $startdir.