On 11/02/14 07:33, Jay Lozier wrote:
According to https://pypi.python.org/pypi/appy.pod is written in Python
2.4. AFAIK, is should run on the Python 2.7.5 interpreter correctly
which is installed on Ubuntu. The only issue I see with the older
version of Python is the possibility of features deleted in Python 2.7.5
being used by appy.pod. I would check with www.python.org to see if
there are any issues.
I had Python 2.7 and Ubuntu 13.04 before, and it worked perfectly. The
problem came with the upgrade to Ubuntu 13.10. Before the upgrade I
could launch python (version 2.7.x) and say "import uno" and it worked.
Now it doesn't work anymore:
$ python -m uno
/home/luc/pythonenvs/py27/bin/python: No module named uno
$
And it *does* work with python3:
$ python3 -m uno
$
Oops, while explaining this, I googled again and found that this is a
known problem in Ubuntu packaging:
https://bugs.launchpad.net/ubuntu/+bug/1244974
This doesn't solve the problem, but I shows that this list is not the
right place to complain. Thanks, Jay, for your answers which helped me
to understand.
Luc
--
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.