Changes by David Edelsohn :
--
components: Extension Modules
nosy: David.Edelsohn
priority: normal
severity: normal
status: open
title: test_wave failing on PPC64 Linux
type: behavior
versions: Python 3.3, Python 3.4, Python 3.5
___
Python tracker
David Edelsohn added the comment:
The patch does not appear to fix the tests for wave on big-endian PPC64 Linux.
--
___
Python tracker
<http://bugs.python.org/issue19
David Edelsohn added the comment:
>>> import array
>>> print array.array('l').itemsize
8
>>> print array.array('i').itemsize
4
--
___
Pyt
David Edelsohn added the comment:
Thanks!
--
___
Python tracker
<http://bugs.python.org/issue19276>
___
___
Python-bugs-list mailing list
Unsubscribe:
David Edelsohn added the comment:
AIX buildbot is experiencing a similar failure:
[276/382/4] test_asyncio
Timeout (1:00:00)!
Thread 0x0001:
File
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/selectors.py",
line 265 in select
File
"/home/shager/cpyt
David Edelsohn added the comment:
How is this ready for release? The patch does not work on numerous POSIX
systems.
--
___
Python tracker
<http://bugs.python.org/issue19
New submission from David Edelsohn:
test_asyncio times out after one hour on AIX and leaves a process consuming
100% of a thread.
[145/382/3] test_asyncio
Timeout (1:00:00)!
Thread 0x0001:
File
"/home/shager/cpython-buildarea/3.x.edelsohn-aix-ppc64/build/Lib/selectors.py",
l
David Edelsohn added the comment:
Commenting out poll in selectors.py does not help.
AIX has its own epoll/kqueue efficient I/O event polling feature "pollset",
which I will open as a separate enhancement request issue.
Some of the subprocess tests in test_asyncio/test_events.py
David Edelsohn added the comment:
My understanding of the issue is POSIX and The Open Group specification are
ambiguous about the handling of Unix socket API calls when interrupted by a
signal. Linux implements a more liberal, accommodating behavior and the Python
Async I/O implementation is
David Edelsohn added the comment:
Also, the Python buildbot for AIX is running on a POWER AIX 7.1 system at OSU
OSL that is a member of the "GCC Compile Farm" cluster on which FOSS developers
can obtain free accounts. If you want access to an AIX system for testing, it&#x
New submission from David Edelsohn:
Implement AIX pollset in Modules/selectmodule.c
--
components: Extension Modules
messages: 200457
nosy: David.Edelsohn
priority: normal
severity: normal
status: open
title: Add support for AIX pollset efficient event I/O polling
type: enhancement
David Edelsohn added the comment:
Either create new pollset object or use pollset to provide implementation of
Python epoll API on AIX.
--
___
Python tracker
<http://bugs.python.org/issue19
David Edelsohn added the comment:
Check that which processes are terminated? The test eventually timed out after
1 hour and the process running echo.py continued to run.
--
___
Python tracker
<http://bugs.python.org/issue19
David Edelsohn added the comment:
poll() vs select() does not make a difference. Using the default poll(), if I
run python in GDB, test_process_interactive hangs in poll(). The top of the
traceback looks like:
#0 0xd02389d4 in __fd_poll () from /usr/lib/libc.a(shr.o)
#1 0xd717e604 in poll
David Edelsohn added the comment:
Patch against current trunk
--
keywords: +patch
Added file: http://bugs.python.org/file32229/issue18235.patch
___
Python tracker
<http://bugs.python.org/issue18
David Edelsohn added the comment:
With my patch applied, _sysconfig.py looks like
'BLDSHARED': '/usr/local/lib/python3.4/config/ld_so_aix gcc -pthread '
'-bI:/usr/local/lib/python3.4/config/python.exp',
'LDSHARED': '/usr/loca
David Edelsohn added the comment:
The patch cleans up a lot of the other failures for asyncio on AIX, but does
not fix the hang.
--
___
Python tracker
<http://bugs.python.org/issue19
David Edelsohn added the comment:
AIX has an equivalent to strace (called truss). I have recorded all AIX system
calls and signals for test_process_interactive, which hangs, following all
children created by fock. The uncompressed file is 82MB or 939KB compressed.
The highlights are
David Edelsohn added the comment:
Separate question for David: if CF's patch were committed, would we still need
your patch to disable three subprocess-related tests on AIX? (That can be dealt
with after the alpha release though -- in fact I propose not to wait for AIX if
we can get the
David Edelsohn added the comment:
I added
if not buf: break
after
buf = os.read()
to echo.py, echo2.py and echo3.py. They now exit and do not spin, but the test
still hangs.
--
___
Python tracker
<http://bugs.python.
David Bolen added the comment:
I've been trying to test this on the Ubuntu 8.04 buildbot, but so far, using
the latest hg default head, haven't gotten test_asyncio to hang even before the
patch. It also looks like the last 4 regular buildbot builds were fine too. I
even tried ro
New submission from David Coles:
Tools/gdb/libpython.py is currently Python 3 incompatible. Unfortunately recent
versions of gdb (such as the one provided in Ubuntu 13.10) may be linked
against Python 3 rather than Python 2, breaking debugging support.
Most of the issues appear to be trivial
David Edelsohn added the comment:
> To test this theory, it should be sufficient to comment out
> self._loop.add_reader(self._fileno, self._read_ready)
When I comment out this line, test_subprocess_interactive succeeds on AIX.
--
___
Python t
David Edelsohn added the comment:
For completeness, the highlights of the new truss trace output after the
echo.py change and only tracing the main process to avoid confusion from the
interleaved output:
test_subprocess_interactive (test.test_asyncio.test_events.PollEventLoopTests
David Coles added the comment:
Sure thing. I've got a patch attached to
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1241668 but want to make
sure that it doesn't break things on the py2-linked version.
--
___
Python trac
David Edelsohn added the comment:
CF,
If you don't mean to be rude, then don't be rude. I never claimed that AIX is
the most widely used or most important platform. It implements POSIX and Open
Group specifications correctly, so it is a good cross-check that features are
i
David Coles added the comment:
I ended up with a very similar looking patch - and so merged my changes into
Pitrou's patch.
I also had a go at fixing up the `test_gdb` unit test, which revealed a few
more string/unicode issues. Finally tracked them down to the `write_unicode`
function.
David Coles added the comment:
Attached is a patch that enables the test for gdb linked against py3k.
All test failures should be fixed by the patch on issue19308.
--
keywords: +patch
nosy: +dcoles
Added file: http://bugs.python.org/file32272/test_gdb-py3k-compat.patch
David Coles added the comment:
Should probably also be applied to Python 2.7 branch since it's possible be
debugging Python 2.7 with a version of py3k-linked gdb.
--
versions: +Python 2.7
___
Python tracker
<http://bugs.python.org/is
David Edelsohn added the comment:
pollset is the AIX equivalent of Linux epoll (or kqueue). The API is almost
identical to epoll except with different interface names and a few minor
tweaks. I will try to work on it. I mainly opened this issue as a placeholder
to discuss the implementation
David Edelsohn added the comment:
> I added many tests when I added this feature to Python: see test_signal.py.
> By the way, it uses select.select() :-) Does test_signal pass successfully on
> AIX?
@haypo: test_signal skips some tests on AIX. See Iss
David Coles added the comment:
And here's the patch for Python 2.7.
The result of testing is as follows:
- python (default) against py2-linked gdb: All tests pass
- python (2.7) against py2-linked gdb: `test_long` fails.
- python (default) against py3-linked gdb: All tests pass
- python
David Edelsohn added the comment:
CF,
Pre-built binaries of Python for AIX are available on the Bull Freeware and
Perzl sites of Open Source Software for AIX. The "GetIt" page should be updated
and the packages can be made available through python.org
Other parts of your rea
Changes by David Edelsohn :
--
nosy: +David.Edelsohn
___
Python tracker
<http://bugs.python.org/issue19334>
___
___
Python-bugs-list mailing list
Unsubscribe:
David Edelsohn added the comment:
The testsuite is hanging in test_asyncio again and
test_subprocess_close_client_stream needs to be skipped.
--
Added file: http://bugs.python.org/file32289/issue19293.patch2
___
Python tracker
<h
David Edelsohn added the comment:
Other than the skipped tests, test_asyncio now passes on AIX except for:
FAIL: test_write_pipe (test.test_asyncio.test_events.PollEventLoopTests)
--
Traceback (most recent call last):
File
David Edelsohn added the comment:
With the latest changeset applied to default, the test_subprocess tests no
longer hang, but test_write_pipe_disconnect_on_close now hangs.
The attached patch changes test_event.py to not skip test_subprocess_* but now
skips test_write_pipe_disconnect_on_close
David Edelsohn added the comment:
I think I see the source of the confusion. test_distutils fails because it runs
in the build tree and without files installed. The test does not use the
installed version of sysconfig, so it looks for ./Modules/ld_so_aix, which
fails. The kludge from 2000 was
David Edelsohn added the comment:
test_asyncio no longer hangs on AIX with the aixfix.diff patch. Thanks!
--
___
Python tracker
<http://bugs.python.org/issue19
David Edelsohn added the comment:
You have to try harder to break it again. aixfix2.diff still works. ;-)
--
___
Python tracker
<http://bugs.python.org/issue19
New submission from David Planella:
It seems getdefaultlocale does not return the correct encoding when the locale
is set to ca_ES@valencia:
>>> import locale
>>> locale.setlocale(locale.LC_ALL, "")
'LC_CTYPE=ca_ES.UTF-8@valencia;LC_NUMERIC=ca_ES.UTF-8;LC_TIME
New submission from David Evans:
The pager functions used by help() in StdLib's pydoc.py don't detect IronPython
correctly and the result is a lack of functionality or in some cases a hang.
This is similar to issue 8110 in that the code attempts to detect windows with
a check for &q
David Edelsohn added the comment:
+1
--
___
Python tracker
<http://bugs.python.org/issue18235>
___
___
Python-bugs-list mailing list
Unsubscribe:
David Edelsohn added the comment:
LGTM
--
nosy: +David.Edelsohn
___
Python tracker
<http://bugs.python.org/issue19529>
___
___
Python-bugs-list mailing list
Unsub
David Edelsohn added the comment:
+1
--
nosy: +David.Edelsohn
___
Python tracker
<http://bugs.python.org/issue19521>
___
___
Python-bugs-list mailing list
Unsub
David Chambers added the comment:
These commits contain a typo: s/preceeded/preceded/
--
___
Python tracker
<http://bugs.python.org/issue19238>
___
___
Python-bug
David Edelsohn added the comment:
$ LC_ALL=C python -c 'import locale; print(locale.getpreferredencoding(False))'
ISO8859-1
It's possible that some additional locales were not installed by default with
the system, e.g., UTF-8.
--
___
Changes by David Edelsohn :
--
nosy: +David.Edelsohn
___
Python tracker
<http://bugs.python.org/issue19634>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by David Edelsohn :
--
nosy: +David.Edelsohn
___
Python tracker
<http://bugs.python.org/issue19633>
___
___
Python-bugs-list mailing list
Unsubscribe:
David Edelsohn added the comment:
By the way, test_wave also fails on zLinux, which also is Big Endian.
--
___
Python tracker
<http://bugs.python.org/issue19
David Edelsohn added the comment:
Can you try compiling the module using xlc_r without -O ? One possible guess is
XLC optimizations can speculate through NULL pointers because AIX maps address
0 as valid in processes. I don't know why Python is finding an invalid value in
the stru
David Jones added the comment:
Has there been any progress made on fixing this? I ran into this trying to
install numpy via pip, 32-bit python installation on 64-bit Centos 6.4. It
get's the compile flags right, but not the linker:
C compiler: gcc -pthread -fno-strict-aliasing -g -O2
David Edelsohn added the comment:
I have installed debuginfo on the system, but it is not being recognized. I
have been inquiring with SuSE zLinux to understand how to resolve this.
--
___
Python tracker
<http://bugs.python.org/issue19
David Edelsohn added the comment:
The valid range is 00:00:00 UTC, January 1, 1970 to 03:14:07 UTC, January 19,
2038.
--
___
Python tracker
<http://bugs.python.org/issue19
David Edelsohn added the comment:
Do you want me to open a new issue or do you want to open a new issue?
--
___
Python tracker
<http://bugs.python.org/issue18
David Watson added the comment:
Looking again at cmsg_min_space(), I see that it already returns
false when msg_controllen is less than cmsg_len_end, so you could
do a (signed) comparison against that, rather than 0. Patch
attached.
--
Added file: http://bugs.python.org/file32992
David Bolen added the comment:
I've been experimenting with setting up a Windows 8.1 buildbot, and found this
ticket after finding a problem with test_threaded_import, testing against the
3.4 branch.
I seem to be have a low syscheckinterval issue similar to that discussed here
on
David Bolen added the comment:
Interesting - it's got a "Visual Studio Just-In-Time Debugger" dialog on the
screen for an unhandled win32 exception in the compiler (cl.exe).
That's a dialog my pop-up AutoIt script wasn't expecting, so I've added it to
the other
David Bolen added the comment:
Ok, the last spurt of exceptions on the XP buildbot in the 3.x branch were all
related to the fact that somehow the .hg folder in the 3.x branch build tree
was missing. The rest of the build files seemed present. I've removed the
build tree completely to
David Bolen added the comment:
I'm seeing an apparent side-effect of the new clean script (or it seems to
correlate). Since it started running, the Windows buildbots (both 7 and XP)
seem to always perform a full clone of the master repository for each build
rather than just a pull/u
New submission from David Edelsohn:
The patch for Issue #21881 causes CPython test_tcl to crash on AIX.
$ ./python -m test -v test_tcl
== CPython 3.5.0a0 (default:d1f89eb9ea1e+, Jul 10 2014, 10:21:22) [GCC 4.8.1]
== AIX-1-00F84C0C4C00-powerpc-32bit big-endian
== hash algorithm: siphash24
David Edelsohn added the comment:
If I comment out all three tests, it runs.
--- a/Lib/test/test_tcl.py Thu Jul 10 01:17:11 2014 -0400
+++ b/Lib/test/test_tcl.py Sat Jul 12 16:59:33 2014 -0700
@@ -455,9 +455,9 @@
check(float('inf'), 'Inf', eq=float_eq)
David Edelsohn added the comment:
> Is following test passed?
> check((1,), '1')
That test succeeds.
> Is CPython crashes when change signature of testfunc?
--- a/Lib/test/test_tcl.py Sat Jul 12 18:26:03 2014 +0300
+++ b/Lib/test/test_tcl.py Sun Jul 13
David Edelsohn added the comment:
#5 0x1019bb90 in PyCFunction_Call (func=0x30533b5c, arg=0x305d8ab4, kw=0x0)
at Objects/methodobject.c:94
#6 0x1012534c in call_function (pp_stack=0x2ff16144, oparg=2)
at Python/ceval.c:4269
94 CHECK_RESULT(res);
(gdb) print res
$9
David Edelsohn added the comment:
No difference with the patch. The problem is not a a malloc() failure.
--
___
Python tracker
<http://bugs.python.org/issue21
New submission from David Wilson:
This is a followup to the thread at
https://mail.python.org/pipermail/python-dev/2014-July/135543.html , discussing
the existing behaviour of BytesIO copying its source object, and how this
regresses compared to cStringIO.StringI.
The goal of posting the
David Wilson added the comment:
Submitted contributor agreement. Please consider the demo patch licensed under
the Apache 2 licence.
--
___
Python tracker
<http://bugs.python.org/issue22
David Wilson added the comment:
Good catch :( There doesn't seem to be way a to ask for an immutable buffer, so
perhaps it could just be a little more selective. I think the majority of use
cases would still be covered if the sharing behaviour was restricted only to
BytesType.
In that
David Halter added the comment:
I would vote for the inclusion of that patch. I just stumbled over this.
--
nosy: +davidhalter
___
Python tracker
<http://bugs.python.org/issue12
David Wilson added the comment:
This version is tidied up enough that I think it could be reviewed.
Changes are:
* Defer `buf' allocation until __init__, rather than __new__ as was previously
done. Now upon completion, BytesIO.__new__ returns a valid, closed BytesIO,
whereas previou
David Wilson added the comment:
New patch also calls unshare() during getbuffer()
--
Added file: http://bugs.python.org/file36005/cow3.patch
___
Python tracker
<http://bugs.python.org/issue22
David Wilson added the comment:
I'm not sure the "read only buffer" test is strong enough: having a readonly
view is not a guarantee that the data in the view cannot be changed through
some other means, i.e. it is read-only, not immutable.
Pretty sure this approach is broken.
David Wilson added the comment:
Stefan,
Thanks for digging here. As much as I'd love to follow this interpretation, it
simply doesn't match existing buffer implementations, including within the
standard library.
For example, mmap.mmap(..., flags=mmap.MAP_SHARED, prot=mmap.PROT_
David Wilson added the comment:
I'm not sure how much work it would be, or even if it could be made sufficient
to solve our problem, but what about extending the buffers interface to include
a "int stable" flag, defaulting to 0?
It seems though, that it would just be making the
Changes by David Wilson :
Added file: http://bugs.python.org/file36016/cow4.patch
___
Python tracker
<http://bugs.python.org/issue22003>
___
___
Python-bugs-list mailin
David Wilson added the comment:
Hi Stefan,
How does this approach in reinit() look? We first ask for a writable buffer,
and if the object obliges, immediately copy it. Otherwise if it refused, ask
for a read-only buffer, and this time expect that it will never change.
This still does not
David Wilson added the comment:
Stefan, I like your new idea. If there isn't some backwards compatibility
argument about mmap.mmap being hashable, then it could be considered a bug, and
fixed in the same hypothetical future release that includes this BytesIO
change. The only cost now is
David Edelsohn added the comment:
Huh? What does officially supported platform mean? CPython builds and runs on
AIX.
--
___
Python tracker
<http://bugs.python.org/issue17
David Edelsohn added the comment:
ffi_closure_helper_DARWIN should have been declared "extern" in the assembly
file. This has been fixed in more recent versions of libffi and imported into
more recent versions of CPython, including 2.7.
.extern .ffi_closure_helper_DARWIN
Is it wort
David Wilson added the comment:
This new patch abandons the buffer interface and specializes for Bytes per the
comments on this issue.
Anyone care to glance at least at the general structure?
Tests could probably use a little more work.
Microbenchmark seems fine, at least for construction
David Wilson added the comment:
Hey Antoine,
Thanks for the link. I'm having trouble getting reproducible results at
present, and running out of ideas as to what might be causing it. Even after
totally isolating a CPU for e.g. django_v2 and with frequency scaling disabled,
numbers still
David Wilson added the comment:
Newest patch incorporates Antoine's review comments. The final benchmark
results are below. Just curious, what causes e.g. telco to differ up to 7%
between runs? That's really huge
Report on Linux k2 3.14-1-amd64 #1 SMP Debian 3.14.9-1 (2014-06-30) x8
David Edelsohn added the comment:
Setting the environment variable LDR_CNTRL is discouraged. It is much better
to set the value in the executable header. Best to set it at link time, but one
can use ldedit.
The issue with the segments in 32 bit mode is a trade off between heap memory
and
David Wilson added the comment:
I suspect it's all covered now, but is there anything else I can help with to
get this patch pushed along its merry way?
--
___
Python tracker
<http://bugs.python.org/is
David Beazley added the comment:
There are other kinds of libraries that might want to access the .buf
attribute. For example, the llvmpy extension. Exposing it would be useful.
--
___
Python tracker
<http://bugs.python.org/issue15
David Beazley added the comment:
Well, a lot of things in this big bad world are dangerous. Don't see how this
is any more dangerous than all of the peril that tools like ctypes and llvmpy
already provide.
--
___
Python tracker
David Beazley added the comment:
One of the other goals of memoryviews is to make memory access less hacky. To
that end, it would be nice to have the .buf attribute available given that all
of the other attributes are already there. I don't see why people should need
to do some even
New submission from David Wilson:
The attached patch (hopefully) silences the signedness warnings generated by
Visual Studio and reported on python-dev in
<https://mail.python.org/pipermail/python-dev/2014-July/135603.html>.
This was sloppiness on my part, I even noted the problem
David Edelsohn added the comment:
I tried the patch with Python-2.7.8 and it fixes the test_glob failure. Thanks!
--
___
Python tracker
<http://bugs.python.org/issue17
David Edelsohn added the comment:
The failure also occurs with Python 3 and the patch fixes test_glob for those
releases.
--
___
Python tracker
<http://bugs.python.org/issue17
David Edelsohn added the comment:
3.4 and default also. The failure occurs on all branches and default.
--
___
Python tracker
<http://bugs.python.org/issue17
David Wilson added the comment:
Hey Serhiy,
The implementation for your readline optimization seems less contentious (and
less risky) than the remainder of the patch -- it could perhaps be easily split
off into a separate patch, which may be far more easily committed.
I love the concept of
Changes by David Halter :
--
nosy: +davidhalter
___
Python tracker
<http://bugs.python.org/issue1>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by David Thiede :
--
nosy: +davet
___
Python tracker
<http://bugs.python.org/issue16808>
___
___
Python-bugs-list mailing list
Unsubscribe:
David Szotten added the comment:
after some trial and error it only appears to break for 3rd party packages (all
20 or so i happened to have installed), whereas everything i tried importing
from the standard library worked fine
```
>>> __import__('requests.', fromlist=
David Szotten added the comment:
first ever patch to python, so advice on the patch would be appreciated
found an example in the stdlib that triggers bug (used in test):
`__import__('encodings', fromlist=[u'aliases'])`
--
keywords: +patch
Added file: http://bugs.
David Szotten added the comment:
not sure i follow. we need a different message if e.g. an integer is passed in
updated the patch to only run the unicode check for non-strings
or do you have a suggestion for an error message that works nicely in both
cases?
--
Added file: http
David Edelsohn added the comment:
When the failing test is re-enabled, the _tkinter patch produces the following
output:
test_user_command (test.test_tcl.TclTest) ... Assertion failed: __EX, file
/home/dje/src/cpython/Modules/_tkinter.c, line 1277
Fatal Python error: Aborted
Current thread
David Edelsohn added the comment:
$ ./python -m test -v test_tcl
== CPython 3.5.0a0 (default:9ab404cdcaa1+, Sep 4 2014, 10:06:33) [GCC 4.8.1]
== AIX-1-00F84C0C4C00-powerpc-32bit big-endian
== hash algorithm: siphash24 32bit
== /home/dje/src/cpython/build/test_python_48694044
Testing with
David Bolen added the comment:
While troubleshooting an issue with test_distutils consistently failing on my
XP buildbot, I narrowed it down to the test.bat change to use run_tests.py. I
don't yet know fully what's happening, but after replacing the new test.bat
with the older ver
1401 - 1500 of 9549 matches
Mail list logo
