[Python-modules-team] Bug#535855: matplotlib._path
Hi Fabrice,
thanks for sending the additional info.
In Fabrice's sys.path output:
...
/usr/share/pyshared
^^^
...
This seems to be the problem. While the matplotlib/__init__.py lives in
that dir, it should be loaded via the symlink in
/usr/lib/pymodules/python2.5. Then it finds the _path module in the
neighboring symlink.
Could you manually remove it and try again?
import sys
sys.path.remove('/usr/share/pyshared')
import matplotlib.transforms
should do the trick.
If that works, one would need to figure out where the pyshared entry in
sys.path comes from.
Kind regards
T.
For reference: My sys.path is
/usr/lib/python2.5
/usr/lib/python2.5/plat-linux2
/usr/lib/python2.5/lib-tk
/usr/lib/python2.5/lib-dynload
/usr/local/lib/python2.5/site-packages
/usr/lib/python2.5/site-packages
/usr/lib/python2.5/site-packages/Numeric
/usr/lib/python2.5/site-packages/PIL
/usr/lib/pymodules/python2.5
/usr/lib/pymodules/python2.5/gtk-2.0
/usr/lib/python2.5/site-packages/wx-2.6-gtk2-unicode
--
Thomas Viehmann, http://thomas.viehmann.net/
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#535855: matplotlib._path
Le mercredi 08 juillet 2009 à 08:58 +0200, Thomas Viehmann a écrit :
In Fabrice's sys.path output:
/usr/share/pyshared
This seems to be the problem. While the matplotlib/__init__.py lives in
that dir, it should be loaded via the symlink in
/usr/lib/pymodules/python2.5. Then it finds the _path module in the
neighboring symlink.
You may be right: on another machine, the pyshared directory is not in
sys.path.
Could you manually remove it and try again?
import sys
sys.path.remove('/usr/share/pyshared')
import matplotlib.transforms
should do the trick. If that works, one would need to figure out where
the pyshared entry in sys.path comes from.
I will try tonight at home. Which are the mechanism that add items to
sys.path ?
Thanks for helping me on this!
--
Fabrice Silva
Laboratory of Mechanics and Acoustics - CNRS
31 chemin Joseph Aiguier, 13402 Marseille, France.
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#535855: matplotlib._path
Fabrice Silva wrote: I will try tonight at home. Which are the mechanism that add items to sys.path ? sys.path is a regular python list, so sys.path.append(/foo) adds to the end, sys.path.insert(i, /foo) adds /foo in i-th position (put in your favorite integer). Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#535855: Bug#535855: matplotlib._path
[Thomas Viehmann, 2009-07-08] Fabrice Silva wrote: I will try tonight at home. Which are the mechanism that add items to sys.path ? sys.path is a regular python list, so sys.path.append(/foo) adds to the end, sys.path.insert(i, /foo) adds /foo in i-th position (put in your favorite integer). ... or you can have PYTHONPATH env. var. set somewhere (f.e. in ~/.bashrc) you can also grep your code (I assume nobody would do such nasty thing in Debian package ;) for siteaddsitedir\( or import site ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#536193: Bug#536193: libapache2-mod-python segmentation fault
Hello Marc, On Wed, Jul 8, 2009 at 06:09, Marc J. Driftmeyerm...@reanimality.com wrote: Package: libapache2-mod-python Version: 3.3.1-8 Severity: normal Setting up libapache2-mod-python (3.3.1-8) ... Reloading web server config: apache2/lib/lsb/init-functions: line 188: 32667 Segmentation fault $TPUT hpa 60 /dev/null 21 .. Mod update doesn't keep Apache2 from reinitializing. I haven't tested how it effects mod-python. Mh, are you sure this is related to mod_python? we don't have any init function in the package and, given you're using my arch and the same versions of libraries, I don't suffer from this segfault. If someone else has some ideas, I'd like to hear them :D Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Processed: Re: Bug#536273: python-lxml: can produce invalid XML
Processing commands for cont...@bugs.debian.org: clone 536273 -1 -2 -3 Bug#536273: python-lxml: can produce invalid XML Bug 536273 cloned as bugs 536278-536280. reassign -1 python2.5 2.5.4-1 Bug#536278: python-lxml: can produce invalid XML Bug reassigned from package `python-lxml' to `python2.5'. retitle -1 python2.5: xml.etree can produce invalid XML Bug#536278: python-lxml: can produce invalid XML Changed Bug title to `python2.5: xml.etree can produce invalid XML' from `python-lxml: can produce invalid XML'. reassign -2 python-elementtree 1.2.6-14 Bug#536279: python-lxml: can produce invalid XML Bug reassigned from package `python-lxml' to `python-elementtree'. retitle -2 python-elementtree: can produce invalid XML Bug#536279: python-lxml: can produce invalid XML Changed Bug title to `python-elementtree: can produce invalid XML' from `python-lxml: can produce invalid XML'. reassign -3 python-celementtree 1.0.5-10 Bug#536280: python-lxml: can produce invalid XML Bug reassigned from package `python-lxml' to `python-celementtree'. retitle -3 python-celementtree: can produce invalid XML Bug#536280: python-lxml: can produce invalid XML Changed Bug title to `python-celementtree: can produce invalid XML' from `python-lxml: can produce invalid XML'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
[Python-modules-team] Bug#536193: marked as done (libapache2-mod-python segmentation fault)
Your message dated Thu, 9 Jul 2009 07:23:57 +0200 with message-id 8b2d7b4d0907082223j72b5fe12v5bfdc23c41b8b...@mail.gmail.com and subject line Re: [Python-modules-team] Bug#536193: libapache2-mod-python segmentation fault has caused the Debian Bug report #536193, regarding libapache2-mod-python segmentation fault to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 536193: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536193 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libapache2-mod-python Version: 3.3.1-8 Severity: normal Setting up libapache2-mod-python (3.3.1-8) ... Reloading web server config: apache2/lib/lsb/init-functions: line 188: 32667 Segmentation fault $TPUT hpa 60 /dev/null 21 .. Mod update doesn't keep Apache2 from reinitializing. I haven't tested how it effects mod-python. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libapache2-mod-python depends on: ii apache2 2.2.11-6 Apache HTTP Server metapackage ii apache2-mpm-prefork [apache2] 2.2.11-6 Apache HTTP Server - traditional n ii apache2.2-common 2.2.11-6 Apache HTTP Server common files ii libc6 2.9-19 GNU C Library: Shared libraries ii python2.5.4-2An interactive high-level object-o ii python-central0.6.11 register and build utility for Pyt ii python2.5 2.5.4-1An interactive high-level object-o libapache2-mod-python recommends no packages. Versions of packages libapache2-mod-python suggests: ii libapache2-mod-python-doc 3.3.1-8Python-embedding module for Apache -- debconf information: libapache2-mod-python/enable_module: true ---End Message--- ---BeginMessage--- Hi Marc, On Thu, Jul 9, 2009 at 01:09, Marc J. Driftmeyerm...@reanimality.com wrote: Sandro, After some further digging your package is clean. It appears to be related to lsb. It's faulting on more packages than just libapache2-mod-python. it seemed strange there was something wrong on the init file :) I encourage to report an accordingly bug against lsb, if there is a bug in it. My apologies for the confusion. absolutely no problem. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ---End Message--- ___ Python-modules-team mailing list Python-modules-team@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/python-modules-team
