Sébastien Sablé added the comment:
I don't have any AIX environment to try to reproduce the issue, so feel free to
close it.
--
___
Python tracker
<http://bugs.python.org/is
Sébastien Sablé added the comment:
This issue has been fixed as part of issue 941346 and should be closed in my
opinion.
--
___
Python tracker
<http://bugs.python.org/issue6
Sébastien Sablé added the comment:
I have started working on python default branch.
My patch queue is available here:
https://bitbucket.org/sablefr/py3kvs2010/
The result is the following so far:
323 tests OK.
8 tests failed:
test_distutils test_fileio test_gettext test_io test_os
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue7833>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Sébastien Sablé :
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue11732>
___
___
Python-bugs-list mailing list
Unsubscribe:
Sébastien Sablé added the comment:
OK Brian, I checked your clone and I will keep an eye on it.
I have done almost the same thing for the moment. My patch queue includes some
additional corrections for a few more bugs that prevented me from completely
running the test suite (crash dumps).
I
Sébastien Sablé added the comment:
Thanks Terry, I am aware of that.
We are working on making Python work with VS2010 in issue 13210.
I will check with the py3k branch soon and report here if the same problem
applies.
--
___
Python tracker
<h
Sébastien Sablé added the comment:
I had the same issue while compiling Python 2.7 with ActivePerl on windows, and
I can confirm that the proposed patch solves the issue.
--
nosy: +sable
versions: +Python 2.7
___
Python tracker
<h
Sébastien Sablé added the comment:
Thanks Antoine! It solved the issue.
I will check soon with Python trunk to see if the same thing applies.
--
___
Python tracker
<http://bugs.python.org/issue13
Sébastien Sablé added the comment:
Yes I know, but this is my primary target as this is the version that I use in
my product for the moment.
I will test python trunk soon now that Python 2.7 with VS2010 is in a rather
good shape.
--
___
Python
Sébastien Sablé added the comment:
I don't have commit access on hg.python.org, so I also created a clone on
bitbucket at:
https://bitbucket.org/sablefr/py27vs2010/overview
I work with a patch queue for the moment since everything is not completely
settled yet.
The patch are against p
Sébastien Sablé added the comment:
The problem is in CTextIOWrapperTest.test_issue1395_5
Here is the backtrace:
msvcr100d.dll!memset() Line 145Asm
> msvcr100d.dll!_heap_alloc_dbg_impl(unsigned __int64 nSize, int
> nBlockUse, const char * szFileName, int nLin
Sébastien Sablé added the comment:
OK, sorry. Done in issue 13461.
--
___
Python tracker
<http://bugs.python.org/issue1395>
___
___
Python-bugs-list mailin
New submission from Sébastien Sablé :
I am trying to get Python working when compiled with Visual Studio 2010 (cf
issue 13210).
When running the tests with the python 2.7 branch compiled with VS2010, the
"test_issue_1395_5" in test_io.py will cause Python to eat the whole memory
wi
Sébastien Sablé added the comment:
I am trying to get Python working when compiled with Visual Studio 2010 (cf
issue 13210).
When running the tests with the python 2.7 branch compiled with VS2010, the
"test_issue_1395_5" in test_io.py will cause Python to eat the whole memory
wi
Sébastien Sablé added the comment:
I don't have the issue anymore when bumping the stack size to 230.
--
___
Python tracker
<http://bugs.python.org/i
Sébastien Sablé added the comment:
I had the exact same problem when compiling the Python 2.7 branch with Visual
Studio 2010.
In debug mode and 64 bits, python will crash on test_loads_recursion in
test_marshal and on the code provided in msg63536.
Could you please reopen this issue
Sébastien Sablé added the comment:
I can also confirm that this patch corrects the problem with test_asyncore for
Python 2.7 built with VS2010.
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue10
Sébastien Sablé added the comment:
Packaging makes it easier to distribute Python among my colleagues and
customers, so I think it is a nice addition.
OK for the hg clone, I will set up that (I actually already use mercurial
internally to handle those modifications
Sébastien Sablé added the comment:
Martin, what I want to achieve is to ensure that someone can download Python
sources and compile them without any modification using a standard install of
Windows + Visual Studio 2010 SP1.
I don't really care what is the default compiler used to gen
Sébastien Sablé added the comment:
Here is a quick and dirty draft of the modifications I had to do in order to
get Python 2.7.2 to compile with VS2010 on the wiki:
http://wiki.python.org/moin/VS2010
I will improve/complete it as I progress.
I will also do a 64 bits version
Sébastien Sablé added the comment:
Amaury:
Great! I have opened issue 13210 to achieve that.
Mark:
Mixing the 2 CRTs results in plenty of crashes in our application. The
application also uses a lot of Qt. It is not an option to use a prebuilt Python
binary generated with VS2008.
I added you
New submission from Sébastien Sablé :
Python for Windows is currently compiled with Visual Studio 2008.
It is not possible to use Visual Studio 2010.
It would be great to be able to compile Python with Visual Studio 2010:
* some people may only have access to this compiler which is more recent
Sébastien Sablé added the comment:
I need Python compiled with Visual Studio 2010 because I use it embedded in an
application compiled with Visual Studio 2010.
I am pretty sure there are quite a lot of people who would like to compile
Python with this compiler.
I have compiled Python 2.7.2
Sébastien Sablé added the comment:
I had the same issue today. The patch solved the problem.
Thanks
--
nosy: +sable
___
Python tracker
<http://bugs.python.org/issue6
Sébastien Sablé added the comment:
I got this problem again this morning while compiling pywin32.
This problem is not specific to me, anyone using Visual Studio 2010 to compile
Python is experiencing the same issue:
http://nukeit.org/compile-python-2-7-packages-with-visual-studio-2010
Sébastien Sablé added the comment:
I encountered the same problem while compiling the psutil package.
I used Python 3.2.2 that I compiled myself using Visual Studio 2010 SP1 in
Debug mode by following the PCBuild/readme.txt documentation.
I could not compile psutil until I added in setup.py
Sébastien Sablé added the comment:
> Does it mean the project to have an AIX buildbot is abandoned?
We have a buildbot running internally on AIX. I could not get the necessary
modifications integrated upstream in the official Python buildbot so that we
could plug directly on it.
cf t
Changes by Sébastien Sablé :
Added file: http://bugs.python.org/file22698/patch_dlmalloc_Python_2_7_1.diff
___
Python tracker
<http://bugs.python.org/issue3526>
___
___
Sébastien Sablé added the comment:
Sorry for the very late reply; I have been quite busy recently with the
birth of my second daughter, a new job, a new home town and soon a new home.
...
> But with your patch, such code wouldn't be thread-safe anymore. This
> patch implies th
Sébastien Sablé added the comment:
Hi,
sorry for the late reply.
> STINNER Victor added the comment:
>
> At least, I would like to know if Sébastien Sablé (the author of the original
> patch) changed his opinion about this issue since 2007 ;-)
I haven't changed my min
Sébastien Sablé added the comment:
Another reason why you should not force dlmalloc for all applications linked
with libpython is because dlmalloc is (by default) not thread safe, while the
system malloc is (generally) thread-safe. It is possible to define a constant
in dlmalloc to make it
Sébastien Sablé added the comment:
I share the opinion of Floris on this: just because you link your application
with python does not mean you want it to handle all memory management.
If you want the memory to be handled by Python, you should call PyMem_Malloc.
Otherwise people may want to
Sébastien Sablé added the comment:
Yes, I was probably not clear:
When --with-dlmalloc is activated, PyMem_MALLOC/PyMem_Malloc will call
dlmalloc, PyMem_REALLOC/PyMem_Realloc will call dlrealloc and
PyMem_FREE/PyMem_Free will call dlfree.
While calls to malloc/free/realloc will use the
Sébastien Sablé added the comment:
> I'm just proposing an alternative that I find cleaner, simpler and easier to
> maintain.
I understand how LD_PRELOAD works but I find it neither clean nor simple to
maintain.
Also by using a wrapper to call Python you still impact all the a
Sébastien Sablé added the comment:
Hi Charles-François,
it is possible to impact the memory allocation system on AIX using some
environment variables (MALLOCOPTIONS and others), but it is not very elegant
(it will impact all applications running with this environment and it is
difficult to
Sébastien Sablé added the comment:
Yes, for the test, as I put in msg128727, it works fine by removing WNOHANG.
However I should put a note in the AIX-NOTES file to explain that wait4 is
broken with WNOHANG on AIX and suggest the 2 workarounds
Sébastien Sablé added the comment:
I had seen that post you mentioned and already tested the -lbsd without success.
wait4 is not even present in libbsd.
phenix:~$ nm /usr/lib/libbsd.a | grep wait
phenix:~$
Maybe it was present on older versions of the system. But I couldn't fin
Sébastien Sablé added the comment:
Great!
I intend to check that branch 2.7 works fine on AIX once I will have finished
with 3.x (which should be soon).
I will then update this file for Python 2.7 (there shouldn't be much changes
hope
Sébastien Sablé added the comment:
I updated the documentation in issue 10709 so that it mentions ldedit rather
than the linker flags (more convenient to activate support for more memory).
Once Python 3.2 is released, we may add LDR_CNTRL or ldedit in the Makefile
when running buildbottest
Sébastien Sablé added the comment:
Here is a new version of the file:
It integrates the corrections by R. David, and I also modified the "memory
limitations" section in order to use ldedit rather than some flags for the
linker.
--
Added file: http://bugs.python.org/fil
Sébastien Sablé added the comment:
Yes it is correct. And thank you for proof reading it too.
--
___
Python tracker
<http://bugs.python.org/issue10709>
___
___
Sébastien Sablé added the comment:
The doc would become:
"""
To allocate more segment registers to Python, you must use the linker option
-bmaxdata or ldedit to specify the number of bytes you need in the data
segment.
For example, if you want to allow 512MB of memory for
Sébastien Sablé added the comment:
The AIX documentation says:
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.itame3.doc_5.1/am51_perftune113.htm
"""It is a good idea to unset the LDR_CNTRL environment variable, so that it
does not unintentional
Sébastien Sablé added the comment:
This issue already existed on Python 2.5.2 with AIX 5.2:
http://www.mail-archive.com/python-list@python.org/msg192219.html
The documentation for WNOHANG says:
http://docs.python.org/library/os.html#os.WNOHANG
"""
The option for wait
Sébastien Sablé added the comment:
Could this doc be added before the 3.2 release?
I think it is convenient for the (few) AIX users and harmless.
--
___
Python tracker
<http://bugs.python.org/issue10
Sébastien Sablé added the comment:
I kinda feel this is related to issue 11185 which I reported earlier.
--
___
Python tracker
<http://bugs.python.org/issue11
Sébastien Sablé added the comment:
At the time of the lock, there is only one python process running. So I guess
the other processes have already left but this is not correctly detected.
I will try again with all_threads=True.
--
___
Python
Sébastien Sablé added the comment:
faulthandler is great by the way! I will use that in my application.
--
___
Python tracker
<http://bugs.python.org/issue11
Sébastien Sablé added the comment:
Here is what faulthandler reports when I trigger it as Python is locked in
test_socket:
"""
[108/349] test_socket
Traceback (most recent call first):
File
"/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/fork_wai
Sébastien Sablé added the comment:
test_socket didnot lock this time (I will retry next).
But test_subprocess.ProcessTestCasePOSIXPurePython.test_leaking_fds_on_error
did.
Looping forever on the following syscall:
pipe(0x2FF1FD88)= 0
kfcntl(15, F_GETFD
Sébastien Sablé added the comment:
Well I don't know precisely:
* when running make buildbottest, test_socket will systematically hang on AIX
5.3 and 6.1.
* but when running ./python -Wd -E -bb Lib/test/test_socket.py, the tests
complete rather quickly (with one failure cf 11192).
Ra
Sébastien Sablé added the comment:
Thanks Antoine, the patch solved the problem.
I have other tests locking semi-randomly on AIX 5.3 and/or AIX 6.1, like
test_socket and test_io. That may be related.
--
___
Python tracker
<http://bugs.python.
Sébastien Sablé added the comment:
I am not sure this is directly related, but test_socket.py will hang forever on
AIX 6.1 when this script is run as part of "make buildbottest".
It won't hang when running the script alone.
--
___
Sébastien Sablé added the comment:
$ grep SEM pyconfig.h
#define HAVE_BROKEN_POSIX_SEMAPHORES 1
/* #undef HAVE_BROKEN_SEM_GETVALUE */
#define HAVE_SEM_GETVALUE 1
#define HAVE_SEM_OPEN 1
#define HAVE_SEM_TIMEDWAIT 1
#define HAVE_SEM_UNLINK 1
/* #undef POSIX_SEMAPHORES_NOT_ENABLED */
#ifndef
New submission from Sébastien Sablé :
The test test_lock_acquire_interruption in test_threadsignals.py will lock
forever on AIX 5.3.
It works fine on 6.1.
truss shows it is stuck in thread_tsleep:
$ truss -p 1404986
thread_tsleep(0, 0x, 0x, 0x) (sleeping
Sébastien Sablé added the comment:
Here is a first version of this doc for Python 3.2.
It would be great if someone could proof read it since I am not a native
english speaker (though it is not high level literature...).
--
Added file: http://bugs.python.org/file20770/AIX-NOTES
Sébastien Sablé added the comment:
This has been corrected for python 3.2 in issue 941346.
Need to be tested on python 2.7.
--
___
Python tracker
<http://bugs.python.org/issue11
Sébastien Sablé added the comment:
Here is the patch.
It only impacts AIX systems and is minimalist, so I think it should be safe for
Python 3.2.
--
keywords: +patch
Added file: http://bugs.python.org/file20767/patch_aix_largefile.diff
___
Python
Sébastien Sablé added the comment:
Also Michael, I am working on the 3.2 branch, it may be different with Python
2.7.1 but I haven't tested yet.
--
___
Python tracker
<http://bugs.python.org/iss
Sébastien Sablé added the comment:
By the way... thanks Georg!
--
___
Python tracker
<http://bugs.python.org/issue941346>
___
___
Python-bugs-list mailin
Sébastien Sablé added the comment:
Are you using --enable-shared when compiling python?
That is when you should see the error (it could not find python.exp at some
stage).
--
___
Python tracker
<http://bugs.python.org/issue941
Sébastien Sablé added the comment:
gmtime(-1) worked fine :/
>>> import time
>>> time.gmtime(-1)
time.struct_time(tm_year=1969, tm_mon=12, tm_mday=31, tm_hour=23, tm_min=59,
tm_sec=59, tm_wday=2, tm_yday=365, tm_isdst=0)
--
Sébastien Sablé added the comment:
Antoine,
can you take a look at issue 730467? That's a trivial patch to correct a
compilation issue on AIX with a C++ compiler; and that means one less entry in
the AIX-NOTES file to write before the 3.2 re
Sébastien Sablé added the comment:
Python 3.2rc3+ (py3k:88422M, Feb 15 2011, 16:57:29) [C] on aix6
Type "help", "copyright", "credits" or "license" for more information.
>>> import time
>>> for t in (-2, -1, 0, 1):
... print(time.
Sébastien Sablé added the comment:
I can only bypass this by explicitly specifying -L/usr/lib so that it will take
precedence over -L/usr/local/lib.
But this behavior is still broken...
"Explicit is better than implicit."
I can see no reason why /usr/local should be implicitly add
Sébastien Sablé added the comment:
This bug is still present in Python 2.7.1. I have also just been beaten by it
on solaris.
I have libintl.so.1 in /usr/lib and libintl.so.8 in /usr/local/lib.
I have never specified that I wanted to use /usr/local/lib anywhere, but the
compilation scripts
Sébastien Sablé added the comment:
Here is what I could find in the "man mktime":
"""
Upon successful completion, the mktime subroutine sets the values of the
tm_wday and tm_yday fields appropriately. Other fields are set to
represent the specified t
Sébastien Sablé added the comment:
I don't know distutils well enough, but I am afraid the LDFLAGS flag used to
compile python is reused in some way when linking some python extensions or
some application that embed python.
(I use an application that embed python on AIX, I should check
Changes by Sébastien Sablé :
--
versions: +Python 2.6, Python 2.7, Python 3.1
___
Python tracker
<http://bugs.python.org/issue11212>
___
___
Python-bugs-list m
Sébastien Sablé added the comment:
This link flag should only be applied to the python executable.
There is already LINKFORSHARED which is great for that.
LDFLAGS will apply it to all the shared libraries which is not really what we
want.
I can compile Python with support for 512MB without
Sébastien Sablé added the comment:
Here is the full patch.
I also modified Makefile.pre.in to clean Modules/python.exp when doing
distclean.
--
Added file: http://bugs.python.org/file20764/patch_aix_shared_32.diff
___
Python tracker
<h
Sébastien Sablé added the comment:
OK, Python with shared libraries is broken in trunk since the library was
renamed to libpython3.2m.
Here is a patch to correct that:
Index: Modules/ld_so_aix.in
===
--- Modules/ld_so_aix.in
Sébastien Sablé added the comment:
Hum, I was incorrect in previous note:
You can remove -L\$(srcdir) on this line, but then you need to specify the full
path to Modules/python.exp. See patch below:
Index: configure.in
Sébastien Sablé added the comment:
If have the same issue with Oracle Studio 12.2 on Solaris 10 with Python 2.7.1:
cc -G -L/livraison/test/sparc-sun-solaris2.10/support/support-2.6.x-py27/lib
-L/livraison/test/sparc-sun-solaris2.10/support/support-internal-2.6.x-py27/lib
-L/livraison
Sébastien Sablé added the comment:
Yes, welcome into the strange world of AIX...
You can allow up to 8 segments, which represent 2GB:
http://publib.boulder.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=/com.ibm.itame3.doc_5.1/am51_perftune113.htm
We could change the option to become
New submission from Sébastien Sablé :
I have the following error when running test_fileio on AIX:
==
FAIL: testAbles (test.test_fileio.OtherFileTests
New submission from Sébastien Sablé :
When running test_asyncore on AIX, I get the following error:
[122/337] test_asyncore
test test_asyncore failed -- Traceback (most recent call last):
File
"/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_asyncore.py",
Sébastien Sablé added the comment:
Here is the result after applying that patch:
==
FAIL: test_specific_values (__main__.CMathTests)
--
Traceback (most recent
Sébastien Sablé added the comment:
I tried the following patch (_AIX is defined on AIX platforms):
Index: Modules/timemodule.c
===
--- Modules/timemodule.c(révision 88420)
+++ Modules/timemodule.c(copie de travail
Sébastien Sablé added the comment:
$ LANG=C ./python -Wd -E -bb -c "import sys; print(ascii(sys.argv))" $(echo -ne
"abc\xff")['-c', 'abc\xff']
['-c', 'abc\xff']
$ LANG=C ./python -Wd -E -bb -c "import locale;
print(locale.nl_lan
Sébastien Sablé added the comment:
Here is a patch that would provide an --enable-aix-maxdata option to configure,
in order to support 512MB of mermory.
I have not tested it yet.
--
keywords: +patch
Added file: http://bugs.python.org/file20761/patch_maxdata.diff
New submission from Sébastien Sablé :
On AIX, executables are compiled by default so that they cannot allocate more
than 256MB of memory.
This is not enough in some cases; for example this is not enough to get the
Python test suite to run completely.
As explained in IBM documentation:
By
Sébastien Sablé added the comment:
I am not sure this is what you want:
> LC_ALL=C ./python
Python 3.2rc3 (py3k:88417M, Feb 14 2011, 10:37:42)
[GCC 4.2.0] on aix6
Type "help", "copyright", "credits" or "license" for more information.
>>> i
New submission from Sébastien Sablé :
The following tests fail in test_subprocess on AIX:
==
FAIL: test_undecodable_env (test.test_subprocess.POSIXProcessTestCase
Sébastien Sablé added the comment:
This is a duplicate of issue 678264.
--
resolution: -> duplicate
status: open -> closed
___
Python tracker
<http://bugs.python.org/i
New submission from Sébastien Sablé :
I have the following error in test_socket on AIX:
==
FAIL: testGetaddrinfo (__main__.GeneralModuleTests)
--
Traceback
Changes by Sébastien Sablé :
--
title: test_search_cpp error on AIX (aith xlc) -> test_search_cpp error on AIX
(with xlc)
___
Python tracker
<http://bugs.python.org/issu
New submission from Sébastien Sablé :
I have the following error in distutils on AIX.
==
ERROR: test_search_cpp (distutils.tests.test_config_cmd.ConfigTestCase
New submission from Sébastien Sablé :
I have the following errors on test_locale on AIX:
==
FAIL: test_strcoll_with_diacritic (test.test_locale.TestEnUSCollation
New submission from Sébastien Sablé :
I have the following error on test_resource on AIX:
test_resource
test test_resource failed -- Traceback (most recent call last):
File
"/san_cis/home/cis/.buildbot/python-aix6/3.x.phenix.xlc/build/Lib/test/test_resource.py",
line 28, in test_f
New submission from Sébastien Sablé :
I have the following errors on test_time on AIX:
==
ERROR: test_mktime (test.test_time.TestAsctime4dyear)
--
Traceback
Sébastien Sablé added the comment:
Also:
is it OK if I open a new issue for each broken unit test on AIX even if I have
not investigated them at the moment?
I have a dozen broken unit tests on AIX that need to be investigated, but I
don't want to spam the bug tracker followers too muc
Changes by Sébastien Sablé :
--
title: test_io error on AIX -> Broken large file support on AIX
___
Python tracker
<http://bugs.python.org/issue11184>
___
_
Sébastien Sablé added the comment:
test_largefile complains about the filesystem having no largefile support.
It is probably the case, I will ask a sysadmin, and see if he can get me a file
system with large file support so that I can test this feature.
> ./python -Wd -E -bb ./Lib/t
Sébastien Sablé added the comment:
Sorry I made a mistake in my previous patch (_LARGEFILES instead of
_LARGE_FILES).
Here is a better one:
Index: configure.in
===
--- configure.in(révision 88395)
+++ configure.in
Sébastien Sablé added the comment:
the error is different now that _LARGEFILES is defined:
==
ERROR: test_large_file_ops (__main__.CIOTest)
--
Traceback (most
Sébastien Sablé added the comment:
OK, so the following patch should help:
Index: configure.in
===
--- configure.in(revision 88393)
+++ configure.in(working copy)
@@ -1375,6 +1375,8 @@
if test "$use_lfs&qu
New submission from Sébastien Sablé :
I get an error when running test_wait4 with trunk on AIX:
test_wait (__main__.Wait4Test) ... FAIL
==
FAIL: test_wait (__main__.Wait4Test
New submission from Sébastien Sablé :
I get 2 errors when running test_io.py with trunk on AIX.
==
ERROR: test_large_file_ops (__main__.CIOTest)
--
Traceback
1 - 100 of 205 matches
Mail list logo
