Changes by Stefan Krah :
--
resolution: -> duplicate
stage: patch review -> committed/rejected
status: open -> closed
superseder: -> Refleaks in pythonrun.c
___
Python tracker
<http://bugs.python
Changes by Stefan Krah :
--
nosy: +skrah
___
Python tracker
<http://bugs.python.org/issue9778>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
Stefan Krah added the comment:
The patch works. I agree that no test is needed, since no one will
attempt to revert this. :)
--
___
Python tracker
<http://bugs.python.org/issue7
Stefan Krah added the comment:
> why should _PyUnicode_Init() try to call _PyUnicode_InitGlobals() again?
For the embedding scenario (when only Py_Initialize() is called) I wanted
to preserve the old behavior of _PyUnicode_Init().
But this is not really enough. I wrote a new patch that a
Stefan Krah added the comment:
There are two issues here:
(1) If libreadline is already linked against ncurses, there is no way that
the readline module should be linked against ncursesw. This was the
direct cause of the FreeBSD segfault, so this configuration is also
prohibited in
Stefan Krah added the comment:
Hmm, I understood that your ldd lines implied that things don't work as
intended in 3.1, hence the explanation. Perhaps this wasn't the case. :)
--
___
Python tracker
<http://bugs.python.
Stefan Krah added the comment:
Hi, I've problems with two recent commits (r85814 and r85817):
Example:
r85812 is ok:
==
Python 3.2a3+ (py3k:85812:85835M, Oct 28 2010, 22:02:19)
[GCC 4.2.4 (Ubuntu 4.2.4-3ubuntu4)] on linux2
Type "help", "copyright", &
Changes by Stefan Krah :
--
resolution: fixed ->
status: closed -> open
___
Python tracker
<http://bugs.python.org/issue10186>
___
___
Python-bugs-list
Stefan Krah added the comment:
I've seen that one as well, but very rarely.
--
nosy: +skrah
___
Python tracker
<http://bugs.python.org/issue6661>
___
___
Stefan Behnel added the comment:
I find it a lot easier to appreciate patches that implement a single change
than those that mix different changes. There are three different things in your
patch, which I would like to see in at least three different commits. I'd be
happy if you
New submission from Stefan Behnel :
Lib/test/test_unicode_file.py contains dead code:
def _test_equivalent(self, filename1, filename2):
remove_if_exists(filename1)
self.assertTrue(not os.path.exists(filename2))
f = file(filename1, "w")
f.close()
New submission from Stefan Krah :
When the __hash__ method is called directly, the hash of -1
is -1:
>>> from decimal import *
>>> Decimal(-1).__hash__()
-1
>>> hash(Decimal(-1))
-2
I've a patch, which also sneaks in a ValueError.
--
Stefan Krah added the comment:
I don't see a file attached. Could you attach your patches in plain text?
It is the preferred method, since files can be easily viewed in the browser.
--
nosy: +skrah
___
Python tracker
<http://bugs.py
Stefan Krah added the comment:
This is the history of the issue:
In r16757 the current version of get_export_symbols() was added to
distutils. This function adds /EXPORT initfunc to the command line.
In 27697 PyMODINIT_FUNC was defined as __declspec(dllexport) void.
I'd suggest to r
Stefan Krah added the comment:
I think this might be more than a documentation bug. Akira's example shows
that the maintainer is erroneously listed as the author. This does not
seem fair to an author who in general will have written most of a package.
I'd prefer a separate mainta
Stefan Krah added the comment:
Hirokazu's patch works for me. Could this approach be taken in general to
suppress all buildbot pop-ups?
--
___
Python tracker
<http://bugs.python.org/i
Stefan Krah added the comment:
I agree that the buffer should be released. The patch fixes this leak
and another one. All tests pass.
--
keywords: +patch
nosy: +skrah
Added file: http://bugs.python.org/file19606/posixmodule_leak.patch
___
Python
Stefan Krah added the comment:
Fixed the hash in r86492, excluding the TypeError fix.
Should I fix the TypeError in both 2.7 and 3.2?
--
___
Python tracker
<http://bugs.python.org/issue10
Stefan Behnel added the comment:
I agree that this is annoying, we get the same thing in Cython's test suite all
over the place. Any foreign warning that doesn't get triggered helps in
debugging your own code. And this one is easy to avoid.
--
nos
Stefan Krah added the comment:
Works fine for me (Windows 7, 64-bit, 32-bit Python-3.2). I do have the
plain US English version. Do you have localized versions?
--
nosy: +skrah
___
Python tracker
<http://bugs.python.org/issue11
Stefan Krah added the comment:
Python works fine with Notepad generated scripts. I think this is a
CGI issue. Try following this tutorial:
http://www.imladris.com/Scripts/PythonForWindows.html
If you still suspect a bug, you should provide the exact CGI script
and all details of the Apache
New submission from Stefan Behnel :
http://docs.python.org/library/xml.dom.minidom.html
presents MiniDOM as a "Lightweight DOM implementation". The word "lightweight"
is easily misunderstood as meaning "efficient" or "memory friendly". MiniDOM is
w
Stefan Behnel added the comment:
Well, I'm not aware of many people who use 4DOM these days, and if that's what
it's meant to refer to, maybe that should be made more obvious, because it
currently is not at all. Even cDomlette uses only half of the memory according
to
http://
Stefan Behnel added the comment:
It's the tree based API most python users are parsing XML with, though. So I do
not agree that it's comparing apples and oranges, not at all. It's comparing
tree based XML libraries, only one of which is worth being called "light
weight&
Stefan Behnel added the comment:
> If that is a real concern, I'd rather reduce the memory footprint of
> minidom than put actual performance figures into the documentation
> that will likely outdate over time.
Personally, I do not think it's worth putting much work into M
New submission from Stefan Krah :
Several files rely on properly substituted subversion keywords. In
the cpython clone the keywords aren't substituted.
3.3 example:
$ find . -name "*.c" | xargs grep -n '"\$'
./Modules/_bsddb.c:102:static char *rcs_id
Stefan Krah added the comment:
I've also looked at the keyword extension, but for example HeadURL does
not seem to be supported by default:
http://comments.gmane.org/gmane.comp.version-control.mercurial.devel/31214
--
___
Python tracker
Stefan Krah added the comment:
I can't reproduce it any more. Looks like it has been fixed in the
meantime.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.pyth
Stefan Krah added the comment:
Sandro Tosi wrote:
> Hi Stefan, can you please expand a bit this issue and details the places
> you think can benefit from pyctype macros? you know, a patch would be the
> best :)
Indeed. While working on #9036 I thought that there were several pl
Stefan Krah added the comment:
Is there another (authoritative) source for locale aliases apart
from X.org? On Ubuntu Lucid, many aliases for installed locales
are missing:
f = open("/var/lib/locales/supported.d/local")
locale_list = [loc.split()[0] for loc in f
Stefan Krah added the comment:
Marc-Andre Lemburg wrote:
> The "local" file you mention only contains "en_US.UTF-8 UTF-8" on
> our Ubuntu 10.04.1 default installation.
>
> Have you installed some other package to get support for all those
> locales ?
On
Stefan Krah added the comment:
For the new FreeBSD bot, the issue was simply insufficient swap space.
With 1GB of memory and 2GB of swap test_zlib runs fine.
--
___
Python tracker
<http://bugs.python.org/issue11
Stefan Krah added the comment:
Since I do automated module testing against all Python versions,
my vote would be:
2.5: +1
2.6: +1
3.1: +1
This with the caveat that of course Martin has to decide for 2.5.
I'm just indicating my preference.
--
nosy: +
Stefan Krah added the comment:
The FreeBSD and Solaris bots are failing:
dpkg-architecture: not found
error: build/temp.freebsd-8.2-RELEASE-amd64-3.3-pydebug/multiarch: No such file
or directory
[62607 refs]
*** Error code 1
find_executable.patch should solve the problem.
--
Added
New submission from Stefan Krah :
Hi, the tests fail on Debian if the option --without-threads is used:
./configure --with-pydebug --without-threads
make
make test
./python -Wd -E -bb ./Lib/test/regrtest.py -l
== CPython 3.3a0 (default:9140f2363623+, Jan 30 2011, 04:52:32) [GCC 4.1.2
New submission from Stefan Krah :
Valgrind reports a leak (definitely lost) in atexitmodule.c. The
patch fixes the problem.
--
components: Extension Modules
files: atexit-leak.patch
keywords: patch
messages: 133501
nosy: skrah
priority: normal
severity: normal
stage: patch review
status
Stefan Krah added the comment:
[Merging with issue 11402]
Daniel's patch is much simpler, but I think that unicode_empty and
unicode_latin1 would need to be protected before _PyUnicode_Init
is called.
Is the module initialization procedure documented somewhere? I get
the impression
Stefan Krah added the comment:
This should be a duplicate of issue 10156.
--
nosy: +skrah
resolution: -> duplicate
stage: patch review -> committed/rejected
status: open -> closed
superseder: -> Initialization of globals in uni
Stefan Krah added the comment:
Stefan Krah wrote:
> Is the module initialization procedure documented somewhere? I get
> the impression that unicodeobject.c depends on dict.c and dict.c
> depends on unicodeobject.c.
s/dict.c/dic
Stefan Krah added the comment:
The patch works. Is it expected that dump_tracebacks_later is missing
when building --without-threads? If so, the warning is probably
confusing for the uninitiated.
--
___
Python tracker
<http://bugs.python.
Stefan Krah added the comment:
Just to give another data point: A couple of days ago I reduced the
memory on the AMD64 FreeBSD bot to (375MB RAM, 2GB swap) and the zlib
tests still pass.
--
___
Python tracker
<http://bugs.python.org/issue11
Stefan Krah added the comment:
I cannot reproduce this on Lucid with:
$ uname -r
2.6.32-28-generic
Isn't this an Ubuntu problem if sem_open only works with some
specific kernels?
--
nosy: +skrah
___
Python tracker
<http://bugs.py
Stefan Krah added the comment:
This line...
>>> from multiprocessing.synchronize import Semaphore
... works on Ubuntu Lucid with the 2.7, 3.1, 3.2 and default
branches from:
http://hg.python.org/cpython
Since you mention Ubuntu's build configuration, I suggest that you
try
Stefan Krah added the comment:
Buck Golemon wrote:
> > I suggest that you try to build from the above mercurial repository and see
> > if the problem persists.
>
> How do I know the configuration options that the Ubuntu packager used?
I'd use the default configuratio
New submission from Stefan Behnel :
In test file test_logging.py, around line 2359, list.append() is called with
two arguments instead of one. I suppose it is meant to be called with a tuple.
class ModuleLevelMiscTest(BaseTest):
[...]
def _test_log(self, method, level=None
Stefan Krah added the comment:
I wrote to the maintainer of vmspython, and he said this:
"Python on VMS is actively maintained, for example you can take a look at
http://www.vmspython.org/ and http://www.vmspython.org/History
Our plan are to port, this year 2.7, then 3.x."
So the
New submission from Stefan Krah :
The FreeBSD-AMD64 bot exhibits sporadic hanging in unspecific places.
FreeBSD is running under kvm in the background. When the hanging occurs,
the virtual machine uses 100% CPU and I can't log in via ssh, so I have
to kill the kvm process.
The fact that th
Stefan Krah added the comment:
Thanks Victor, I can try some of that.
Could this also be a problem with the buildbot software or a networking
problem? The Ubuntu PPC bot might have the same issue. Here the tests
appear to be finished but the clean doesn't start:
http://www.python.or
Stefan Krah added the comment:
R. David Murray wrote:
> The failing test is launching a subprocess to compile python code, waiting
> for the subprocess to exit, and then checking to see if the file was
> created. So the timing issue would appear to be that the file created by
> th
Stefan Pfeiffer added the comment:
Happens in 3.2, too...
Would be nice to see that fixed.
Stefan
--
nosy: +Stefan.Pfeiffer
___
Python tracker
<http://bugs.python.org/issue11
Stefan Krah added the comment:
Going through the logs, this indeed looks like a buildbot software
issue to me. I attach the logs that correspond to this incident:
http://www.python.org/dev/buildbot/all/builders/AMD64%20FreeBSD%208.2%203.2/builds/85
After ...
2011-04-30 01:10:56+0200 [Broker
Stefan Krah added the comment:
Another instance:
2011-05-03 20:18:08+0200 [Broker,client] closing stdin
2011-05-03 20:18:08+0200 [Broker,client] using PTY: False
2011-05-03 20:20:38+0200 [-] sending app-level keepalive
Again this is missing:
... [-] command finished with signal None
Changes by Stefan Krah :
--
nosy: +barry
___
Python tracker
<http://bugs.python.org/issue11962>
___
___
Python-bugs-list mailing list
Unsubscribe:
Stefan Krah added the comment:
The poster should get the same error messages from:
ml64 /c /Cx x64dll.asm
Perhaps the assembly isn't MASM?
--
___
Python tracker
<http://bugs.python.org/i
New submission from Stefan Krah :
I can reproduce this only with gcc-4.4.3, so it could also be
a compiler bug. Also, the segfault only occurs when python is
compiled with optimizations and run under valgrind.
hg up 2.7
make distclean
./configure
make
valgrind --suppressions=Misc/valgrind
Stefan Krah added the comment:
STINNER Victor wrote:
> You should try to disable compiler optimization: pass -O0 to gcc. E.g. use
> ./configure --with-pydebug CFLAGS="-O0".
I did, see "only occurs when python is compil
Stefan Krah added the comment:
I just ran into this with test_httpserver/Python2.7, which fails if run
as root. If I understand correctly this is the main problem here. Jason,
do you agree to change the issue title to reflect this?
--
nosy: +skrah
versions: +Python 2.7, Python 3.1
Stefan Krah added the comment:
The FreeBSD bot had these error messages in the log files:
1) kernel: swap_pager: indefinite wait buffer: device
2) Approaching the limit on PV entries, consider increasing either the
vm.pmap.shpgperproc or the vm.pmap.p
v_entry_max sysctl.
I set up the bot
Stefan Krah added the comment:
On second thought, I don't want to debug possible qcow2 issues, so
I made another change:
d) Use raw format for the image.
--
___
Python tracker
<http://bugs.python.org/is
Stefan Krah added the comment:
Terry J. Reedy wrote:
> "Also, the segfault only occurs when python is
> compiled with optimizations and run under valgrind."
>
> This says to me that the segfault is not a Python issue.
> What change do you expect in the Python source co
Stefan Krah added the comment:
I think the FreeBSD bot changes are working out fine. The Ubuntu-PPC
issues were unrelated, so I'm closing this.
--
keywords: +buildbot
resolution: -> fixed
stage: -> committed/rejected
status: ope
Stefan Krah added the comment:
The segfault also occurs with a self-compiled gcc-4.4.6, but not
with gcc-4.5.3.
--
___
Python tracker
<http://bugs.python.org/issue11
Stefan Krah added the comment:
There are warnings on the FreeBSD and OSX buildbots, where pthread_t
is not a long.
http://www.python.org/dev/buildbot/all/builders/AMD64%20FreeBSD%208.2%203.x/builds/237/steps/compile/logs/warnings%20%283%29
http://www.python.org/dev/buildbot/all/builders/AMD64
New submission from Stefan Krah :
The FreeBSD-AMD64 bot shows an error in test_logging:
http://www.python.org/dev/buildbot/all/builders/AMD64%20FreeBSD%208.2%203.x/builds/243/steps/test/logs/stdio
Exception in thread Thread-281:
Traceback (most recent call last):
File "/usr/home/bui
Changes by Stefan Krah :
--
keywords: +buildbot
___
Python tracker
<http://bugs.python.org/issue12039>
___
___
Python-bugs-list mailing list
Unsubscribe:
Stefan Krah added the comment:
We might have two issues here. On FreeBSD the select.error occurs
reliably starting with r69723 (when the tests were added):
[buildbot@freebsd-amd64 /usr/home/buildbot/cpython]$ ./python -m test -uall
test_logging
[1/1] test_logging
/usr/home/buildbot/cpython
Stefan Krah added the comment:
Maybe this link to the revision works: 2ab07776510c
--
___
Python tracker
<http://bugs.python.org/issue12039>
___
___
Python-bug
New submission from Stefan Krah :
Hi, I think that TypeError should take precedence over InvalidOperation
in these two cases:
>>> Decimal('Infinity').fma(Decimal('0'), (3.91224318126786e+19+0j))
Traceback (most recent call last):
File "", line
New submission from Stefan Krah :
I found another performance issue in _power_exact:
>>> Decimal(4) ** Decimal("-1.2e-9")
^CTraceback (most recent call last):
File "", line 1, in
File "/home/stefan/pydev/cpython/Lib/decimal.py", line 2343,
Stefan Krah added the comment:
Ok, I'll write a patch.
--
___
Python tracker
<http://bugs.python.org/issue12079>
___
___
Python-bugs-list mailing list
New submission from Stefan Krah :
The new Fedora buildbot (--without-threads) fails to compile:
http://www.python.org/dev/buildbot/all/builders/AMD64%20Fedora%20without%20threads%203.2/builds/1
I didn't check the release branch yet.
--
components: Build
keywords: buildbot
mes
Stefan Krah added the comment:
A backport of 79fcd71d0356 fixes the problem.
--
___
Python tracker
<http://bugs.python.org/issue12090>
___
___
Python-bugs-list m
Stefan Krah added the comment:
test_os fails on the Fedora bot (--without-threads):
test test_os crashed -- Traceback (most recent call last):
File "./Lib/test/regrtest.py", line 1037, in runtest_inner
File
"/home/buildbot/buildarea/3.x.krah-fedora/build/Lib/importli
Changes by Stefan Behnel :
--
nosy: +scoder
___
Python tracker
<http://bugs.python.org/issue12131>
___
___
Python-bugs-list mailing list
Unsubscribe:
Stefan Krah added the comment:
Georg, I think this might be a release blocker. I hope it is
not too late for 3.2.1.
Victor, was there any reason that 79fcd71d0356 wasn't backported?
Otherwise I'll go ahead and push it to 3.2.
--
priority: normal -> re
Stefan Krah added the comment:
An update on the progress:
All development currently happens in my private mpdecimal repository. The
next version of mpdecimal (2.0) is finished, stable and will be released
once all tests have completed successfully. Running the whole test suite
can take several
Stefan Krah added the comment:
Thanks for all the comments! I agree that a change in 2.7 might cause
trouble.
Committed the ValueError in r86517 (py3k).
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -&g
Stefan Krah added the comment:
Raymond Hettinger wrote:
> The choice between ValueError and TypeError can sometimes be ambiguous and
> seem arbitrary and I understand why you're gravitating towards ValueError
> (because it works some values and not others), but in this c
Stefan Krah added the comment:
If I'm not mistaken, signaling NaNs are only created when the user
explicitly initializes a variable. I see this as direct request to
raise an exception whenever the variable is accessed in a way that
changes the outcome of the program:
This is the example I
New submission from Stefan Krah :
On Windows, test_compileall fails due to #10197:
==
FAIL: test_quiet (test.test_compileall.CommandLineTests)
--
Traceback
Stefan Krah added the comment:
On Windows, test_compileall fails due to #10197. The patch uses
subprocess.check_output() instead. Technically, now byte strings
are compared instead of strings, but that should not matter for
the outcome.
--
nosy: +skrah
Added file: http
Stefan Krah added the comment:
Since I was the one who reopened this: The issues I found were fixed in
r85358 and #9047 seems to be ok now. Setting to pending.
--
resolution: -> fixed
stage: -> committed/rejected
status: open -> pending
_
Changes by Stefan Krah :
--
nosy: skrah
priority: normal
severity: normal
status: open
title: Build with --enable-shared fails
___
Python tracker
<http://bugs.python.org/issue10
New submission from Stefan Krah :
Building the modules fails if --enable-shared is used. The linker picks
up an existing library from /usr/local/lib, which has not been compiled
with -fPIC:
gcc -pthread -shared
build/temp.linux-x86_64-3.2/home/stefan/svn/py3k/Modules/_struct.o
-L/usr/local
Stefan Krah added the comment:
Since I'm on Linux, I did a prior install into /usr/local. But I'm pretty
sure that BSD ports (which you might view as the system install) also use
/usr/local.
--
___
Python tracker
<http://bugs.python.o
Stefan Krah added the comment:
Yes, the patch is tested on Windows. Feel free to commit it if you have
a chance.
--
___
Python tracker
<http://bugs.python.org/issue10
Stefan Krah added the comment:
Fixed original leaks in r86804, r86806 and r86804.
Fixed additional leaks in r86829.
--
components: +Extension Modules -Library (Lib), Windows
resolution: -> fixed
stage: -> committed/rejected
status: open -> closed
versions: +Python 2.7, P
New submission from Stefan Krah :
On FreeBSD, the config variable LDSHARED contains the literal '${LDFLAGS}',
causing this failure in test_distutils:
'test_get_outputs (distutils.tests.test_build_ext.BuildExtTestCase) ... gcc: ':
No such file or directory
ERROR
The patch
Changes by Stefan Krah :
--
keywords: +buildbot -needs review, patch
___
Python tracker
<http://bugs.python.org/issue10547>
___
___
Python-bugs-list mailin
New submission from Stefan Krah :
C:\Users\stefan\svn\py3k_64>PCbuild\amd64\python_d.exe Lib\test\regrtest.py -R
: test_concurrent_futures
[1/1] test_concurrent_futures
beginning 9 repetitions
123456789
.
test_concurrent_futures leaked [6912, 6912, 6912, 6912] references, sum=2764
Stefan Krah added the comment:
posixmodule_listdir.patch fixes a leak in test_macpath. test_concurrent_futures
still leaks.
--
keywords: +patch
Added file: http://bugs.python.org/file19839/posixmodule_listdir.patch
___
Python tracker
<h
Changes by Stefan Krah :
--
nosy: +bquinlan
___
Python tracker
<http://bugs.python.org/issue10550>
___
___
Python-bugs-list mailing list
Unsubscribe:
Stefan Krah added the comment:
Committed posixmodule_listdir.patch in r86843. Unfortunately this
is unrelated to the test_concurrent_futures leak.
--
___
Python tracker
<http://bugs.python.org/issue10
Stefan Krah added the comment:
Anurag, could you check out #941346 and see if there is anything that
might help? I think this is AIX specific.
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue10
Stefan Krah added the comment:
Upgrading to critical, since I just verified that C extensions in
general don't build on FreeBSD due to this issue.
Sorry for bringing this up on the release day, it's a coincidence that
I discovered it today...
--
priority: normal -
Stefan Krah added the comment:
Checked python-3.1.2.msi with f-prot, no viruses. Checked download
with firefox (which claims to do a short virus scan), no results.
--
nosy: +skrah
___
Python tracker
<http://bugs.python.org/issue10
Stefan Krah added the comment:
Thinking about it, declaring PyMODINIT_FUNC as void would be a huge
step backwards. Using PyMODINIT_FUNC is the correct way of doing things.
The current situation punishes developers who actually read the docs.
If a C module stops working because of the change
Stefan Krah added the comment:
Right, Debian's solution is quite reasonable. Closing as wont_fix.
--
resolution: -> wont fix
stage: -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.pyt
Stefan Behnel added the comment:
File checked with ClamAV under Linux, no findings.
--
nosy: +scoder
___
Python tracker
<http://bugs.python.org/issue10
Stefan Krah added the comment:
r86848: backported r85422, as required by the changes in r85358.
Antoine, there are some remaining {LDFLAGS}, two in the Darwin sections,
one in the OpenBSD section.
I think all of those should be removed as well. Do you agree?
--
nosy: +pitrou
401 - 500 of 4949 matches
Mail list logo
