By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,550 Members | 1,161 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,550 IT Pros & Developers. It's quick & easy.

module import problem

P: n/a
I have a Kubuntu upgrade script that fails to run:

File "/tmp/kde-root//DistUpgradeFetcherCore.py",
line 34, in <module>
import GnuPGInterface
ImportError
No module named GnuPGInterface

I got a folder /usr/share/python-support/python-gnupginterface with
a "GnuPGInterface.py" but no __init__.py.

In python command line, print sys.path shows that /usr/share/python-support/
is not among python paths.

If I cd into /usr/share/python-support/python-gnupginterface and launch Python
I can "import GnuPGInterface". But when I run DistUpgradeFetcherCore.py in
that folder it always fails with No module named GnuPGInterface.

I do not know much about setting python path.

--
Milos Prudek
Jun 27 '08 #1
Share this Question
Share on Google+
2 Replies


P: n/a
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[ Milos Prudek <pr****@bvx.cz]
If I cd into /usr/share/python-support/python-gnupginterface and launch
Python I can "import GnuPGInterface". But when I run
DistUpgradeFetcherCore.py in that folder it always fails with No module
named GnuPGInterface.

I do not know much about setting python path.
Reinstall the package "python-gnupginterface" with "sudo aptitude reinstall
python-gnupginterface". This should fix the problem, unless your package
management is broken.

- --
Freedom is always the freedom of dissenters.
(Rosa Luxemburg)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkg4mb0ACgkQn3IEGILecb6jpACfc80saFQz/Q6F5lYbuCUQxJt2
Z+8AoKkB+5hqm0tMmK/d1s1IjsSSCqAz
=Z6/t
-----END PGP SIGNATURE-----
Jun 27 '08 #2

P: n/a
Reinstall the package "python-gnupginterface" with "sudo aptitude reinstall
Your advice helped! Upgrade is running now. Thanks!

--
Milos Prudek
Jun 27 '08 #3

This discussion thread is closed

Replies have been disabled for this discussion.