Matthias Klose d...@debian.org added the comment:
looks good. checked with a plain and a debug build and installation.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
Matthias Klose d...@debian.org added the comment:
-L. should appear before -L/usr/local/lib.
--
nosy: +doko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10520
Matthias Klose d...@debian.org added the comment:
that seems to be the wrong report. did you mean
Package: python3.1
Version: 3.1.2+20101012-1
Severity: normal
curses.tigetstr() returns bytes (which makes sense), but curses.tparm() expects
a Unicode string as first argument. As a consequence
Matthias Klose d...@debian.org added the comment:
I still fail to see the rationale for being able to build with a different
soabi name. But anyway, as long as the default is to build with the soabi
name, I'm +/-0 on this option.
Note that the soabi name isn't fixed but changes with other
Matthias Klose d...@debian.org added the comment:
shouldn't that option work on platforms too, which currently default to not
using the soabi? It would make sense for all posix, and macos, maybe not for
Windows.
--
___
Python tracker rep
Matthias Klose d...@debian.org added the comment:
The java/openjdk tests allow setting an attribute `samevm' for running a
specific test. maybe something like this could be used for some problematic
tests which occasionally hang on some buildds
Matthias Klose added the comment:
$ python Lib/test/test_resource.py
True
Traceback (most recent call last):
File Lib/test/test_resource.py, line 42, in module
f.close()
IOError: [Errno 27] File too large
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org
New submission from Matthias Klose:
libffi needs an update to support mips64, arm and armeabi on linux; the
current bits are all available in GCC trunk. as an alternative, those
systems should be default to --with-system-ffi, unless this is
xplicitely disabled.
--
assignee: theller
New submission from Matthias Klose:
The test_resource test fails at least on all non x86 linux systems; the
test case notes:
# Now check to see what happens when the RLIMIT_FSIZE is small. Some
# versions of Python were terminated by an uncaught SIGXFSZ, but
# pythonrun.c has been fixed
Matthias Klose added the comment:
committed the following patch to the trunk (lets the buildds test the
ctypes extension)
Added file: http://bugs.python.org/file8605/arm.diff
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1292
New submission from Matthias Klose:
This breaks building _ctypes with the upstream libffi.
r58034 | thomas.heller | 2007-09-07 08:32:17 +0200 (Fr, 07 Sep 2007) | 1
line
Add a 'c_longdouble' type to the ctypes module.
gcc -pthread -fPIC -fno-strict-aliasing -g -Wall -Wstrict-prototypes
-I/usr
Changes by Matthias Klose:
--
type: - compile error
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1324
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Matthias Klose added the comment:
Index: Modules/_ctypes/cfield.c
===
--- Modules/_ctypes/cfield.c(revision 58651)
+++ Modules/_ctypes/cfield.c(working copy)
@@ -1753,6 +1753,9 @@
ffi_type ffi_type_float = { sizeof(float
Changes by Matthias Klose:
--
keywords: +patch
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1324
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Matthias Klose added the comment:
oops, did the same for arm* on trunk, but in configure.in
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1292
__
___
Python-bugs-list mailing
New submission from Matthias Klose:
as seen in the logs from
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=455400
both pyconfig.h and png.h define _BSD_SOURCE, which leads to a build
failure with current GCC from the trunk, when both headers are included
by an extension. Either define
Changes by Matthias Klose:
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1699
__
___
Python-bugs-list mailing list
Unsubscribe:
http
Matthias Klose added the comment:
there's a buildbot for mips-linux, none for mips64, so lets close this one.
--
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1292
Matthias Klose d...@debian.org added the comment:
Per, on 2010-03-17, I asked you via email:
I was looking at
http://bugs.python.org/issue5689
http://bugs.python.org/issue6715
and Martin's comments about the licensing of the bindings; is there a special
reason for the lgpl3 license
Changes by Matthias Klose d...@debian.org:
--
nosy: +doko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6715
___
___
Python-bugs-list mailing list
New submission from Matthias Klose d...@debian.org:
string exceptions still used in a couple of places:
Tools/msi/msi.py:354
Tools/msi/msi.py:368
Tools/msi/msilib.py:238
--
components: Demos and Tools
messages: 108900
nosy: doko
priority: normal
severity: normal
status: open
title
Matthias Klose d...@debian.org added the comment:
this breaks the build if the time and datetime extensions are built statically
into the python interpreter.
The build fails with a link error; adding the _time extension to
Modules/Setup.dist
@@ -160,6 +160,7 @@
#cmath cmathmodule.c _math.c
Changes by Matthias Klose d...@debian.org:
--
resolution: fixed -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9012
___
___
Python-bugs-list
Matthias Klose d...@debian.org added the comment:
please find attached a patch to build as a statically linked extension,
registering the empty _time module.
--
Added file: http://bugs.python.org/file17853/time.diff
___
Python tracker rep
Matthias Klose d...@debian.org added the comment:
doesn't work:
ranlib libpython3.2.a
Modules/_time.o: In function `_PyTime_DoubleToTimet':
/scratch/packages/python/3.2/python3.2-3.2~~20100704/build-shared/../Modules/_time.c:11:
multiple definition of `_PyTime_DoubleToTimet'
Modules/_time.o
Matthias Klose d...@debian.org added the comment:
yes, same issue with math/cmath.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9012
New submission from Matthias Klose d...@debian.org:
[forwarded from https://launchpad.net/bugs/597763]
seen with all version, built with Tcl8.5
To reproduce the bug, use the following class:
class x(object):
TEST = hello
THE_MAXIMUM = 55
def __init__(self, a, b):
self.a = 3
self.b
Matthias Klose d...@debian.org added the comment:
what version of gcc is being used by this buildslave
you already found out, but it's mentioned at the top of the test stdio. I'll
update the compiler and recheck.
--
___
Python tracker rep
Matthias Klose d...@debian.org added the comment:
I updated the compiler on the buildbot to trunk 20100709, and your reduced
testcase is fixed. will update the gcc-snapshot package in maverick later.
--
resolution: - fixed
status: open - closed
Matthias Klose d...@debian.org added the comment:
shouldn't `initialised_setupterm' be tested instead?
--
nosy: +doko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7567
Matthias Klose d...@debian.org added the comment:
see https://lists.ubuntu.com/archives/ubuntu-devel/2010-July/031010.html
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9415
Matthias Klose d...@debian.org added the comment:
committed in r83306 (2.7) and r83307 (3.2); verified that the behaviour in
offlineimap (reported in http://bugs.debian.org/586433 is fixed).
will apply it to 2.6 and 3.1 after a few days.
--
resolution: - fixed
status: open - pending
Matthias Klose d...@debian.org added the comment:
IMO using lsb_release is not an option, because it can take some time to
complete. So maybe it's better for the Ubuntu change to guard the check with
the existance of /etc/debian_version.
Please could you attach a Mandriva lsb-release file
New submission from Matthias Klose d...@debian.org:
[ forwarded from http://bugs.debian.org/571317 ]
I'm writing a program that uses the popularity contest results. Since
downloading the compressed results takes about a quarter of the time
it takes to download the uncompressed results, I'd
Matthias Klose d...@debian.org added the comment:
I checked with gcc-4.4 from the 4.4 branch, and with a recent build from the
trunk. The check fails with -O0, and succeeds with -O1 and higher.
Is the testcode from r82957 really using the optimization flags
Matthias Klose d...@debian.org added the comment:
validated with 3.2, the interpreter doesn't crash anymore and all expat tests
succeed.
should be applied for 2.7, 3.1 and 3.2.
--
nosy: +doko
versions: +Python 3.1, Python 3.2
___
Python tracker rep
New submission from Matthias Klose d...@debian.org:
the SOABI is always defined, no need to try loading an extension without the
SOABI in its name.
ok to commit?
--
components: Interpreter Core
files: dynload.diff
keywords: patch
messages: 115922
nosy: barry, doko
priority: normal
Changes by Matthias Klose d...@debian.org:
--
stage: - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9806
___
___
Python-bugs-list
New submission from Matthias Klose d...@debian.org:
currently, much of the configuration information is fetched by opening the
config.h and the Makefile for the build. The locations of these files are
derived from the prefix given at configure time.
If you want to have two distinct builds
Changes by Matthias Klose d...@debian.org:
--
nosy: +dmalcolm
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
___
___
Python-bugs-list mailing
Matthias Klose d...@debian.org added the comment:
+1
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
___
___
Python-bugs-list mailing list
Matthias Klose d...@debian.org added the comment:
On 09.09.2010 21:51, Dave Malcolm wrote:
# * Debian's patch to dynload_shlib.c looks for module_d.so, then module.so,
# but this can potentially find a module built against the wrong DSO ABI. We
# instead search for just module_d.so
New submission from Matthias Klose d...@debian.org:
files in Modules/expat reference a file COPYING for the copyright/license, but
this is file is not included in the Python sources.
Proposing to add the attached file, taken from the expat sources.
--
assignee: doko
components: None
New submission from Matthias Klose d...@debian.org:
PC/V[CS]* contain the information to build the wininst-[678]* files, but I
don't see any information how to build wininst-9.0*.
--
components: Build
messages: 115988
nosy: doko
priority: normal
severity: normal
status: open
title
Matthias Klose d...@debian.org added the comment:
however we should expose the name of the SOABI string/extension in
python-config, so that people can build with this name if they want to.
--
___
Python tracker rep...@bugs.python.org
http
Matthias Klose d...@debian.org added the comment:
--extension-suffix ?
doesn't use the `so', which you don't see on MacOs, HpUX and Windows.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9806
Matthias Klose d...@debian.org added the comment:
the .rst file is missing the zlib and libffi licenses too. will add them.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9817
Matthias Klose d...@debian.org added the comment:
fixed in r84743, r84745 and r84746
--
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9817
Matthias Klose d...@debian.org added the comment:
my bad
--
resolution: - invalid
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9818
New submission from Matthias Klose d...@debian.org:
use the SOABI for GNU/kfreeBSD and the GNU Hurd
afaik, the only distribution for GNU/kfreeBSD and the GNU Hurd currently is
Debian, and Debian already has this turned on for Linux too.
--
assignee: doko
components: Build
files
Matthias Klose d...@debian.org added the comment:
checked in, r85481
--
resolution: accepted - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10103
Matthias Klose d...@debian.org added the comment:
two fixes, the configure.in differentiates the name for the static library, as
mentioned in msg118832.
the python-config.in fix prints the library name with the abiflags.
Index: configure.in
Matthias Klose d...@debian.org added the comment:
Index: Misc/python.pc.in
===
--- Misc/python.pc.in (Revision 85644)
+++ Misc/python.pc.in (Arbeitskopie)
@@ -8,6 +8,6 @@
Requires:
Version: @VERSION@
Libs.private: @LIBS
Matthias Klose d...@debian.org added the comment:
the name of the library should not differ for the static and the shared library.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
Matthias Klose d...@debian.org added the comment:
the python.pc installation name should be changed too, and a symlink added.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
Matthias Klose d...@debian.org added the comment:
Lib/distutils/command/install.py () needs updates in INSTALL_SCHEMES/headers.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
Matthias Klose d...@debian.org added the comment:
this adds the modifier to the prefix/python3.2abi/config directory.
Now you end up with both
prefix/python3.2abi/config
and
prefix/python3.2/
for anything else. This is not what Debian, Fedora and Ubuntu are currently
doing
Matthias Klose d...@debian.org added the comment:
the change to python.pc should make the abi change to includedir, not Cflags.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9807
Matthias Klose d...@debian.org added the comment:
I think this is not a good idea, because then you have different names for
extension modules, which will be recognized by one configuration but not the
other. This configure option should not change the sonames. If this option is
to keep
Matthias Klose d...@debian.org added the comment:
On 15.11.2010 23:57, Barry A. Warsaw wrote:
you mean $prefix/lib/python3.2 and $prefix/lib/python3.2$abiflags, right?
The latter has just a config directory, and you'd rather see that become
$prefix/lib/python3.2/config-$abiflags, right
Matthias Klose d...@debian.org added the comment:
On 16.11.2010 00:01, Barry A. Warsaw wrote:
When you say the python.pc change should change includedir instead of Cflags,
that seems weird. includedir does not currently include the 'pythonX.Y'
subdirectory so there's no place to put
Matthias Klose [EMAIL PROTECTED] added the comment:
/etc/lsb-release is not yet specified by the lsb.
See
https://lists.linux-foundation.org/pipermail/lsb-discuss/2008-March/004842.html
https://lists.linux-foundation.org/pipermail/lsb-discuss/2008-March/004843.html
https://lists.linux
New submission from Matthias Klose [EMAIL PROTECTED]:
the files
Lib/lib2to3/Grammar2.6.0.final.0.pickle
Lib/lib2to3/PatternGrammar2.6.0.final.0.pickle
are created/modfied during a build/test cycle. Is this expected, should
these be included in the release at all?
--
messages: 74617
New submission from Matthias Klose [EMAIL PROTECTED]:
ctypes fails to build on arm-linux-gnu, see
http://python.org/dev/buildbot/2.5/ARM Linux 2.5/builds/3/step-compile/0
gcc -pthread -fPIC -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I.
-I/home/pybot/buildarea-arm/2.5.klose-linux-arm
New submission from Matthias Klose [EMAIL PROTECTED]:
seen on the mipsel buildbot
running build
running build_ext
INFO: Can't locate Tcl/Tk libs and/or headers
Traceback (most recent call last):
File ./setup.py, line 1880, in module
main()
File ./setup.py, line 1875, in main
'Lib
New submission from Matthias Klose [EMAIL PROTECTED]:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507317
needs backport of rev 61350 from the trunk.
fixed in newer versions.
--
components: Interpreter Core
messages: 76638
nosy: doko
priority: release blocker
severity: normal
New submission from Matthias Klose [EMAIL PROTECTED]:
Python-2.6/Doc/tools/sphinxext/patchlevel.pyc
Python-2.6/Doc/tools/sphinxext/pyspecific.pyc
Python-2.6/Doc/tools/roman.pyc
same for 3.0
--
assignee: barry
components: Build
messages: 76875
nosy: barry, doko
severity: normal
status
New submission from Matthias Klose [EMAIL PROTECTED]:
Doc/tools/sphinxext not included in the 2.6.1 tarball, but it is checked in.
--
components: Build
messages: 77067
nosy: doko
priority: deferred blocker
severity: normal
status: open
title: Doc/tools/sphinxext not included
Matthias Klose [EMAIL PROTECTED] added the comment:
In my opinion the tar balls should contain all necessary bits and pieces
to build the docs yourself. It makes no sense to include the Doc/ folder
w/o any means to use them.
+ 1
Let's include sphinxext and document the required versions
New submission from Matthias Klose d...@debian.org:
there are some problems with ctypes.util.find_library(), which I would
like to see fixed on active branches.
- find_library is not robust, if either objdump or gcc are not
installed. fixed by raising an exception if the tools
Matthias Klose d...@debian.org added the comment:
new version of the patch using os instead of platform, and selecting the
correct library for biarch platforms, tested on ia64, sparc, s390,
amd64, ppc64. unsure if there's a better way to find out if the
executable is 32 or 64bit.
Added file
Matthias Klose d...@debian.org added the comment:
I think 4861 provides a solution for this issue. I don't see any system
where objdump is in /sbin or /usr/sbin.
--
nosy: +doko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Matthias Klose d...@debian.org added the comment:
I keep this open for now, I don't have access to AIX. Yes, if objdump is
found in some /sbin PATH, then maybe we should search there explicitely.
___
Python tracker rep...@bugs.python.org
http
Matthias Klose d...@debian.org added the comment:
this patch looks wrong, as it only works with libffi = 3.0 (the standalone
libffi releases, which introduces the pkg-config stuff).
--
nosy: +doko
___
Python tracker rep...@bugs.python.org
http
New submission from Matthias Klose d...@debian.org:
[forwarded from http://bugs.debian.org/565713]
If the bug submitter is correct about these, it would be nice to replace these,
or clarify the copyright for these files.
the python source packages contain a non-free audio clip that is
from
Matthias Klose d...@debian.org added the comment:
current status with 2.7 alpha3:
FAIL: test_get_python_inc (distutils.tests.test_sysconfig.SysconfigTestCase)
--
Traceback (most recent call last):
File
/home/packages/python
Matthias Klose d...@debian.org added the comment:
this works with 2.7 alpha3, won't fix for 3.0
--
versions: -Python 2.7, Python 3.0
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5217
New submission from Matthias Klose d...@debian.org:
when byte-compiling files in a deb/rpm package distributed e.g. in a Linux
distribution, it is sometimes wanted to only touch the files found in the
deb/rpm, which can be a subset of the files in a directory. the attached patch
now lets
Matthias Klose d...@debian.org added the comment:
the remaining test failure is
test_bsddb3
Berkeley DB 4.8.24: (August 14, 2009)
Test path prefix: /tmp/z-test_bsddb3-25705
Exception in thread reader 0:
Traceback (most recent call last):
File /home/packages/python/2.6/python2.6-2.6.5~rc2/Lib
New submission from Matthias Klose d...@debian.org:
opening a report to track issues with the update of the internal libffi copy to
3.0.9. will commit this update to the trunk, and later to the py3k branch.
--
assignee: theller
components: ctypes
messages: 101072
nosy: doko, theller
Changes by Matthias Klose d...@debian.org:
--
assignee: theller - doko
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8142
___
___
Python-bugs-list
Matthias Klose d...@debian.org added the comment:
checked in after testing on {arm,i486,x86_64,powerpc,sparc,ia64}-linux with no
test failures.
fixed in r78974 on the trunk
fixed in r78975 on the py3k branch
--
resolution: - fixed
status: open - closed
Matthias Klose d...@debian.org added the comment:
updated on the trunk and the py3k branch
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8142
Matthias Klose d...@debian.org added the comment:
fixed for 2.7, 3.1, 3.2, will fix for 2.6 after the 2.6.5 release.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7356
Matthias Klose d...@debian.org added the comment:
changed the @ syntax to an option -i, and added a test for
compile_file/compile_dir.
--
Added file: http://bugs.python.org/file16556/compileall.py.diff
___
Python tracker rep...@bugs.python.org
http
Matthias Klose d...@debian.org added the comment:
fixed for 2.7 and 3.2
--
resolution: accepted - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8140
Matthias Klose d...@debian.org added the comment:
jcea: yes, but we want _dbm be able to build with 4.8.x as well.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6949
Matthias Klose d...@debian.org added the comment:
the patch works for me with tcl8.5
--
nosy: +doko
stage: test needed - patch review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4961
Matthias Klose d...@debian.org added the comment:
fixed for 2.7, 3.1, 3.2, commit pending for 2.6 until after the 2.6.5 release
--
resolution: - fixed
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4961
New submission from Matthias Klose d...@debian.org:
calling os.execlp('true') with the wrong number of arguments (missing 2nd arg),
the interpreter crashes. fixed in 3.x, this is a backport of the patch to 2.x
--
components: Extension Modules
files: p.diff
keywords: patch
messages
Matthias Klose d...@debian.org added the comment:
it does crash:
$ python
Python 2.6.5rc2 (r265rc2:78822, Mar 11 2010, 13:01:50)
[GCC 4.4.3] on linux2
Type help, copyright, credits or license for more information.
import os
os.execlp('true')
Segmentation fault (core dumped)
arg[0
Matthias Klose d...@debian.org added the comment:
crash seen on both Debian unstable and recent Ubuntu lucid.
(gdb) run
Starting program: /home/doko/a.out
process 30155 is executing new program: /bin/ls
[Thread debugging using libthread_db enabled]
Program received signal SIGSEGV
Matthias Klose d...@debian.org added the comment:
no access to solaris hardware. please could you run the libffi testsuite on
this machine? make sure that expect is installed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org
Matthias Klose d...@debian.org added the comment:
the ports which are maintained separately still need an update:
libffi_msvc
libffi trunk now has a port to x86/msvc. might require some
extra updates from libffi.
libffi_osx:
3.0.9 has support for darwin on powerpc and x86
libffi_wince
Matthias Klose d...@debian.org added the comment:
commited to the trunk, commit to the 2.6 branch pending
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8154
Matthias Klose d...@debian.org added the comment:
On 18.03.2010 16:44, Thomas Heller wrote:
Thomas Hellerthel...@ctypes.org added the comment:
the ports which are maintained separately still need an update:
libffi_msvc
libffi trunk now has a port to x86/msvc. might require some
Matthias Klose d...@debian.org added the comment:
Can you make this change, run autoconf, and commit please?
done, and updated the patch for the merge from the trunk.
--
Added file: http://bugs.python.org/file16590/libffi-update3.diff
___
Python
Changes by Matthias Klose d...@debian.org:
Removed file: http://bugs.python.org/file16588/libffi-update2.diff
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8142
Matthias Klose d...@debian.org added the comment:
committed to the 2.6 branch as well
--
resolution: - fixed
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8154
Matthias Klose d...@debian.org added the comment:
committed to the 2.6 branch as well
--
assignee: gpolo -
status: pending - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4961
1 - 100 of 819 matches
Mail list logo
