anyhow, it is not related to scribus but to python itself, as said in the
comment.
And anyway, both Lucid and Maverick are EOL and now with scribus 1.4.2 and
trusy this is fine.
Fix released.
** Changed in: scribus-ng (Ubuntu)
Status: New => Fix Released
--
You received this bug notific
Upstreem Status "Fix Released" seems not correct to me.
The status is "Status resolvedResolution no change required"
And the latest entry is a note from the bug submitter saying it is not fixed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: scribus
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/685625
Title:
Incorrect python path in scripter
--
ubuntu-bugs mailing list
ubuntu-bugs@
This affects many people on ubuntu, no idea if it really is an ubuntu bug, or a
scribus bug, it would just be nice to get it fixed (someplace).
Additional Places this shows up:
http://bugs.scribus.net/view.php?id=9756
http://bugs.scribus.net/view.php?id=9736
http://lists.scribus.info/pipermail/scr
Additional note to the bug description:
There is a type: it should read << it does __NOT__ include
/usr/lib/python2.6 >>
Apologies if people get confused.
Note to Philip:
Apparently, it's not just a packaging problem. Perhaps there's a patch
somewhere that Fedora applied.
--
You received this
Looked at this a bit after the IRC discussion. It seems like the python C api
on ubuntu sets sys.path[0] not to an empty string but to "/usr/lib/python2.6"
which is sys.path[1] usually and scribus overwrites sys.path[0] with it's own
include path when the scriptengine is initialized.
Could be so
