Opening mmap with access=ACCESS_COPY
Modifying copy-on-write memory map.
Traceback (most recent call last):
File Lib/test/test_mmap.py, line 393, in module
test_both()
File Lib/test/test_mmap.py, line 247, in test_both
m.flush()
EnvironmentError: [Errno 22] Invalid argument
On Apr 22, 11:17 am, Martin v. Löwis [EMAIL PROTECTED] wrote:
test test_mmap crashed -- type 'exceptions.EnvironmentError': [Errno
22] Invalid argument
You should run this with -v. This is too little detail to know what
exactly failed.
Sorry it took so long to get back to you. At this
On Apr 20, 10:17 pm, Martin v. Löwis [EMAIL PROTECTED] wrote:
I recommend you disable compilation of ctypes (by removing the call
to detect_ctypes from setup.py). It's fairly unlikely that you can
manage to make ctypes work on your system.
Martin, Thanks again. I'm much closer now. Here is
test test_mmap crashed -- type 'exceptions.EnvironmentError': [Errno
22] Invalid argument
You should run this with -v. This is too little detail to know what
exactly failed.
self.assertEqual(spid, cpid)
AssertionError: 0 != 6840386
What do these failures indicate?
That suggests a
On Apr 15, 11:33 pm, Martin v. Löwis [EMAIL PROTECTED] wrote:
What is Py_UNICODE_SIZE and why was it not defined? There are current
questions I have.
Py_UNICODE_SIZE is the number of bytes that a Py_UNICODE value should
have in the interpreter. With --enable-unicode=ucs2, it should be 2.
Thus it would seem use cif here resulted in a segment violation. I'll
continue to research this issue and report back to the group as I know
more. Perhaps solving the issue with the 'c' and 'm' libraries
(whatever they might be) will make the core dump go away. However,
for tonight, I'll
What is Py_UNICODE_SIZE and why was it not defined? There are current
questions I have.
Py_UNICODE_SIZE is the number of bytes that a Py_UNICODE value should
have in the interpreter. With --enable-unicode=ucs2, it should be 2.
I cannot guess why it is not defined; check pyconfig.h to find out
On 2008-04-13 18:57, [EMAIL PROTECTED] wrote:
I'm investigating the possible use of Mecurial SCM as a replacement
for CVS. Mecurial is written in Python. I have a background in GNU/
Linux, Solaris, sparc and Perl. However AIX, powerpc and Python are
new to me.
On AIX 5.3, Python 2.5.2
On Apr 14, 7:01 am, M.-A. Lemburg [EMAIL PROTECTED] wrote:
On AIX 5.3, Python 2.5.2 should build out of the box using gcc.
We've successfully build Python 2.3, 2.4 and 2.5 on AIX 5.3
using the gcc compiler suite and tools installed from the
AIX Linux Toolbox:
I'm investigating the possible use of Mecurial SCM as a replacement
for CVS. Mecurial is written in Python. I have a background in GNU/
Linux, Solaris, sparc and Perl. However AIX, powerpc and Python are
new to me.
--uname output--
$ uname -rvp
2 5 powerpc
--end uname output--
I used this
10 matches
Mail list logo
