[issue11217] python-32 not linked in /usr/local/bin in framework builds

New submission from Tom Loredo : When building a universal framework Python-2.7.1 with homebrew on 10.6.6, python-32 (and its target, python2.7-32) are built and installed in the framework executable path, but they are not linked in /usr/local/bin. msg101156 in Issue 8089 recognized this as a

[issue11188] test_time error on AIX

STINNER Victor added the comment: > http://code.google.com/p/y2038/wiki/AmazingDiscoveries <<< AIX again Merijn informs me that before year 0 AIX gets very, very slow. >>> -- ___ Python tracker _

[issue9960] test_structmembers fails on s390x (bigendian 64-bit): int/Py_ssize_t issue

Dave Malcolm added the comment: FWIW, this regressed in 2.6.6 relative to 2.6.5, due to r79646 adding the T_STRING_INPLACE test code to the 2.6 branch. Note to self: https://bugzilla.redhat.com/show_bug.cgi?id=677392 -- ___ Python tracker

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Changes by Martin v. Löwis : -- nosy: -loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue11216] email.message.Message set_charset does not encode properly?

R. David Murray added the comment: Well, the docs don't say that the headers will be removed or modified as needed, only added as needed ;/. And in fact the set_charset code does "if 'Content-Transfer-Encoding' not in self". set_payload also says it is the caller's responsibility to "mainta

[issue11216] email.message.Message set_charset does not encode properly?

Shay Rojansky added the comment: Sorry, the "print part" below doesn't work on Python3 (I'm back in 2.6), but I see the same trouble by using part.__str__() -- ___ Python tracker _

[issue11216] email.message.Message set_charset does not encode properly?

New submission from Shay Rojansky : This may be my misunderstanding of the correct behavior, thanks in advance for your patience... The issue happens when calling set_charset (or set_payload charset) after a Message has already been created and contains a Content-Transfer-Encoding header. Her

[issue11171] Python 2.7.1 does not start when "./configure" is used with "--prefix" != "--exec-prefix"

Barry A. Warsaw added the comment: Fixed in release27-maint: r88422 I am unable to reproduce in Python 3.1 (which does not have the sysconfig module) or 3.2 (which uses a different build-flags specific location for its Makefile). -- resolution: -> fixed status: open -> closed versio

[issue11213] distutils2 test issue

Alexis Metaireau added the comment: yeah, thanks for that ! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue11208] example misprint in documentation whatsnew/3.2

Raymond Hettinger added the comment: Fixed. Thank for the report. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue11212] Python memory limit on AIX

Antoine Pitrou added the comment: > We could change the option to become: > --with-aix-maxdata=value > where value could be between 0 and 8, with a default at 0 (nothing > passed to the compiler). Doesn't LDFLAGS work for that? I don't think we want a lot of platform-specific options like that.

[issue11212] Python memory limit on AIX

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: --with

[issue11214] test_asyncore fails on AIX

Giampaolo Rodola' added the comment: I'd say the test can be removed. It's not really important. -- assignee: -> giampaolo.rodola ___ Python tracker ___ ___

[issue11215] test_fileio error on AIX

Antoine Pitrou added the comment: This looks vaguely similar to http://bugs.python.org/issue6236#msg91007, although the latter has been fixed. -- nosy: +pitrou ___ Python tracker _

[issue11188] test_time error on AIX

Alexander Belopolsky added the comment: I have come across the following post: http://code.google.com/p/y2038/wiki/AmazingDiscoveries I think some of the findings there may be relevant as we push the boundaries of supported time values. -- ___ Pyth

[issue11214] test_asyncore fails on AIX

Changes by Antoine Pitrou : -- nosy: +giampaolo.rodola ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue11215] test_fileio error on AIX

New submission from Sébastien Sablé : I have the following error when running test_fileio on AIX: == FAIL: testAbles (test.test_fileio.OtherFileTests) -- Traceb

[issue11214] test_asyncore fails on AIX

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", line 332,

[issue11188] test_time error on AIX

STINNER Victor added the comment: > but tm_wday = 42 did not solve the problem it seems. Can you try with tm_yday=-1 or tm_isdst=-2? -- ___ Python tracker ___ _

[issue11188] test_time error on AIX

STINNER Victor added the comment: > So test_negative is now OK Ok, I converted your comment to a patch: strftime_aix.patch. -- keywords: +patch Added file: http://bugs.python.org/file20762/strftime_aix.patch ___ Python tracker

[issue11213] distutils2 test issue

Antoine Pitrou added the comment: Ok, works fine! -- resolution: -> invalid status: open -> closed ___ Python tracker ___ ___ Python

[issue11213] distutils2 test issue

New submission from Antoine Pitrou : Just to test that auto-nosy works. -- assignee: tarek components: Distutils2 messages: 128559 nosy: alexis, eric.araujo, pitrou, tarek priority: normal severity: normal status: open title: distutils2 test issue versions: 3rd party ___

[issue11212] Python memory limit on AIX

Antoine Pitrou added the comment: I don't see why we would provide an option to replace a magic number with another magic number. I find it strange that AIX doesn't simply enable unbounded virtual address spaces. (by "unbounded" I mean "bounded by CPU limitations only") -- nosy: +pitr

[issue9920] test_cmath on atan fails on AIX

Sébastien Sablé added the comment: Here is the result after applying that patch: == FAIL: test_specific_values (__main__.CMathTests) -- Traceback (most recent

[issue11188] test_time error on AIX

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)

[issue11193] test_subprocess error on AIX

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_langinfo(locale.CODESET))" ISO8859-1 $ LANG=C ./python -Wd -E -bb -c

[issue11212] Python memory limit on AIX

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 _

[issue11212] Python memory limit on AIX

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 def

[issue11211] gzip.open() fails for gzipped file

STINNER Victor added the comment: test.jml is a ZIP archive, not a gzip archive. "gzip -d" is kind enough to unpack it even if it is ZIP file and not a gzip file. So it's not a Python bug at all. -- nosy: +haypo resolution: -> invalid status: open -> closed

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Pauli Virtanen added the comment: Nick's plan of action above seems mostly OK to me. Though, it might be simpler to collapse the PyManagedBuffer object to PyMemoryView, even if this requires memoryviews to serve two purposes. [Nick:] > I'm still not comfortable with a convention that relies o

[issue11211] gzip.open() fails for gzipped file

New submission from Toni Mueller : I have files that I would like to read with Python, but can't: $ python jmlreader.py woerter-allg.jml Traceback (most recent call last): File "jmlreader.py", line 14, in readFile(sys.argv[1]) File "jmlreader.py", line 10, in readFile for line in f:

[issue11193] test_subprocess error on AIX

STINNER Victor added the comment: >>> sys.getfilesystemencoding() 'iso8859-1' Ok, I expected this result. Can you also try: $ LC_ALL=C ./python -c "import sys; print(ascii(sys.argv))" $(echo -ne "abc\xff") ['-c', 'abc\udcff'] $ LC_ALL=C python3.1 -c "import locale; print(locale.nl_langinfo(

[issue11193] test_subprocess error on AIX

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. >>> import sys >>> sys.getfilesystemencoding() 'iso8859-1' >

[issue7305] urllib2.urlopen() segfault using SSL on Solaris

Fabian Groffen added the comment: Perhaps I should have been a bit more clear. Python 2.6 works fine for me on Solaris 10/Sparc64 (64-bits). Python 2.7.1 also works on Solaris 10/Sparc (32-bits), but not on Sparc64 (64-bits). -- ___ Python tracke

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: If it helps, one way to think of it is that post-redesign, the PyManagedBuffer would be the "real" API object, with Py_buffer merely a way for data exporters to provide the information needed to initialise the managed buffer properly. (That actually fairly accu

[issue11208] example misprint in documentation whatsnew/3.2

Changes by R. David Murray : -- nosy: +rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.p

[issue7305] urllib2.urlopen() segfault using SSL on Solaris

Fabian Groffen added the comment: I can reproduce this on Solaris 10/Sparc64 only, using Python 2.7.1. My core files aren't really useful though, nothing it can point to, everything is corrupt. -- nosy: +grobian versions: +Python 2.7 ___ Python tr

[issue670664] HTMLParser.py - more robust SCRIPT tag parsing

Changes by R. David Murray : -- nosy: +r.david.murray ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: The managed buffer needs to be a separate object so that multiple memoryview objects can share it. Essentially, we would end up with two APIs - the raw Py_buffer API and the higher level PyManagedBuffer one. C extensions would have the choice of using the low l

[issue11193] test_subprocess error on AIX

STINNER Victor added the comment: > I don't understand why the test pass on FreeBSD, Solaris and > Mac OS X, but not on AIX. Oh, the command line and the filesystem encodings may be different. test_undecodable_env() of test_subprocess.py uses os.environ which uses sys.getfilesystemencoding(),

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Antoine Pitrou added the comment: > >> I'm *much* happier with the rule based on malloc/free semantics where > >> the *pointer* passed to PyObject_GetBuffer must match a single later > >> call to PyObject_ReleaseBuffer. > > > > Agreed that Py_buffer should have been a PyObject from the start, bu

[issue11188] test_time error on AIX

STINNER Victor added the comment: > File ".../Lib/test/test_time.py", line 351, in test_mktime >self.assertEqual(time.mktime(tt), t) > OverflowError: mktime argument out of range I don't know which values are "out of range". But I guess that the test fails because of t=-1, which would mea

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: On further reflection, I realised point 4 in that suggestion isn't reliable in a formal sense. Consider: with memoryview(a) as m: m[:] The slice won't reference the buffer again, but isn't guaranteed by the language definition to have been garbage collecte

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: OK, to summarise that revisit into a coherent proposal: 1. Add "PyManagedBuffer" as an even lower level wrapper around Py_buffer. The only thing this would support is doing GetBuffer on construction and ReleaseBuffer when destroyed (or when explicitly asked to

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: Another idea we may want to revisit is the PyManagedBuffer concept, which would be a true PyObject that existed solely to simplify sharing of Py_buffer structs. If memoryview used such an object internally, then copying and slicing would be quite simple - just

[issue10181] Problems with Py_buffer management in memoryobject.c (and elsewhere?)

Nick Coghlan added the comment: On Mon, Feb 14, 2011 at 8:33 AM, Antoine Pitrou wrote: >> I'm still not comfortable with a convention that relies on *clients* >> of the PEP 3118 API not mucking with the internals of the Py_buffer >> struct. > > Which clients? Those who export the buffer, or tho

[issue11210] PyErr_SetFromWindowsErrWithFilenameObject() doesn't exist: remove it from pyerrors.h

New submission from STINNER Victor : PyAPI_FUNC(PyObject *) PyErr_SetFromWindowsErrWithFilenameObject(int, const char *); has a strange prototype: "FilenameObject" usually indicates a PyObject* argument, not a char* argument. The function doesn't exist in Python/errors.c, but there is a PyErr_