Package: python-scipy
Version: 0.7.2+dfsg1-1
Severity: normal
Applying scipy.stats.kde.gaussian_kde to a list of integers, e.g. [1,2,3,4,5],
is not same as applying it to a list of floats [1.0, 2.0, 3.0, 4.0, 5.0]. This
is quite surprising and should probably be fixed. The output for integers
Package: virtualbox-ose
Version: 3.2.10-dfsg-1
Severity: important
Hosting VirtualBox VMs on this machine often results in scheduling
issues for user processes, and sometimes the machine becomes
unresponsible for a long time, after which a message about soft lockup
is found in system log. The
On 2011-04-07 06:09, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the python-scipy package:
#569008: python-scipy: scipy.stats.kde.gaussian_kde fails with non-obvious
exception
It has been closed by Varun Hiremath
Package: python-scipy
Version: 0.7.0-2+b1
Severity: normal
When single-element input is given to scipy.stats.kde.gaussian_kde, it
raises ValueError about infs or NaNs even if the input doesn't contain
any. If computing KDE from single-element input does not make sense, the
exception should
Package: python-matplotlib
Version: 0.99.1.2-1
Severity: important
After updating to latest python-matplotlib version, importing pylab
from matplotlib causes a segfault. Presumably this issue is specific
to my system/package configuration since it has not been reported yet
(assuming 556943 is
Root cause for this issue seems to be somewhere in init_path of
src/_path.c in matplotlib, which calls init_array() of numpy. Upgrading
numpy to 1:1.3.0-3 fixed the segfault. Perhaps the dependency version
should be bumped.
signature.asc
Description: OpenPGP digital signature
I ran into this kind of problem today as well.
First notes about emacs -q and emacs --no-site-file. When the
problem occurs, it occurs with them as well as with plain emacs.
Then some tracing attempts:
It was rather difficult to get the problem to show up under GDB, since
for some reason I
Package: xmlstarlet
Version: 1.0.1-2
Severity: normal
Xmlstarlet produces incorrect validation result on the following file:
http://www.laurinolli.fi/~tazle/invalid.xml. The final validation
result is 'valid' even though the document does not conform to its DTD
and validation against embedded
Package: octave-image
Version: 1.0.8-3+b1
Severity: normal
Whenever imtophat is called with parameters that pass its parameter validation,
and it attempts to perform the actual top-hat filtering operation, it attempts
to access undefined variable and causes an error.
Test code:
test.m:
I =
On 2009-07-29, at 12:30, Francesco P. Lovergine wrote:
On Wed, Jul 29, 2009 at 02:36:51AM +0300, Tuure Laurinolli wrote:
The problem has been fixed in upstream GEOS release 3.1.1.
Due to a license issue, you have to wait next geos release, or need
to provide a minimal patch
Package: libgeos-3.1.0
Version: 3.1.0-1
Severity: normal
When doing 0-distance buffer on the geometry in script test2.py, GEOS prints
a message stderr and causes the process to exit with code 134.
Test script test2.py:
from shapely import wkt
mp = wkt.loads('MULTIPOLYGON (((3375988.599
Hm, yes. Perhaps this shouldn't be fixed in stable. In any case, the
same problem applies to python-ctypes package at least in testing. I
will file another bug for that.
signature.asc
Description: OpenPGP digital signature
Package: python-ctypes
Version: 1.0.2-6
Severity: normal
ctypes.string_at and ctypes.wstring_at are not safe to use in software
with multiple threads because they do not hold GIL. There is a report
of this same issue in the version of ctypes packaged with Python in
version 2.5 at at
Package: python2.5
Version: 2.5.2-15
Severity: normal
ctypes.string_at and ctypes.wstring_at are not safe to use in software
with multiple threads because they do not hold GIL. There is an
upstream issue report about this at http://bugs.python.org/issue3554,
and it has been fixed in new upstream
Package: d-feet
Version: 0.1.8-2
Severity: normal
When started with empty $DISPLAY, d-feet causes a segmentation
fault. I did not explore further as to what the exact cause is, but if
$DISPLAY is set so that it can connect to an X server, the segfault
does not happen.
Steps to reproduce:
1. %
Package: python-iptcdata
Version: 1.0.2+libtool01-2
Severity: important
Accessing one of the data fields provided by the iptcdata python
module for image http://fop3.kyla.fi/~tazle/PICT6104.JPG causes
segfault.
Steps to reproduce:
1. Download the image linked above.
2. Execute python
This bug is probably fixed in upstream version 0.76. At least there is a
report of adding fault tolerance to SVNPoller in the changelog.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Apparently level 0 matches are different from level 0 matches to file.
Forcing it to level 1 allows if-then-else structures like the following
I used for testing:
0 string \?xml
0 string \?xml
38 string \\!DOCTYPE\040svg image/svg+xml
38 string
Package: mono-gmcs
Version: 1.1.8.2-1
Severity: serious
Justification: Policy 3.5
Apt-get installing mono-gmcs causes following error report when trying
to use it for compiling C# files:
[0:24:[EMAIL PROTECTED]/cs]% gmcs testprop.cs
The assembly mscorlib.dll was not found or could not
Package: libgstreamer0.8-dev
Version: 0.8.8-1
Severity: normal
When compiling a DVB module for gstreamer from their CVS, it depends on
gstreamer-libs-0.8.pc providing correct CFLAGS etc.
This file did not exist on my system. The module compiled fine when I created
gstreamer-libs-0.8.pc that
20 matches
Mail list logo
