[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4
New submission from Henry Precheur [EMAIL PROTECTED]:
I tried to compile Python 3000 under OpenBSD and the compilation fails
because of a 'MemoryError':
Fatal Python error: can't create sys.path
object : MemoryError()
type: MemoryError
refcount: 4
address : 0x20abfbd08
lost sys.stderr
Abort trap (core dumped)
*** Error code 134
Stop in /home/henry/compile/py3k (line 410 of Makefile).
The command which fail is:
CC='gcc -pthread' LDSHARED='gcc -pthread -shared -fPIC ' OPT='-DNDEBUG
-g -O3 -Wall -Wstrict-prototypes' ./python -E ./setup.py build
Here is the backtrace:
(gdb) r -E ./setup.py build
Starting program: /home/henry/compile/py3k/python -E ./setup.py build
Fatal Python error: can't create sys.path
object : MemoryError()
type: MemoryError
refcount: 4
address : 0x2042d3d08
lost sys.stderr
Program received signal SIGABRT, Aborted.
[Switching to process 20134, thread 0x2015d4800]
0x00020dc4432a in kill () from /usr/lib/libc.so.48.0
(gdb) bt full
#0 0x00020dc4432a in kill () from /usr/lib/libc.so.48.0
No symbol table info available.
#1 0x00020dc8b105 in abort () at /usr/src/lib/libc/stdlib/abort.c:68
p = (struct atexit *) 0x2064fd000
cleanup_called = 1
mask = 4294967263
#2 0x00468a59 in Py_FatalError (msg=0x4ea6 Address 0x4ea6 out
of bounds)
at Python/pythonrun.c:1880
No locals.
#3 0x0046e06c in PySys_SetPath (path=0x4ea6) at
Python/sysmodule.c:1390
v = (PyObject *) 0x0
#4 0x00466b8c in Py_InitializeEx (install_sigs=1) at
Python/pythonrun.c:213
interp = (PyInterpreterState *) 0x20f8af900
tstate = (PyThreadState *) 0x20adeda00
bimod = (PyObject *) 0x2042dc128
sysmod = (PyObject *) 0x2042dc128
pstderr = (PyObject *) 0x2042dc128
p = 0x0
codeset = 0x2042dc128 \034
#5 0x00474136 in Py_Main (argc=4, argv=0x20f0331a0) at
Modules/main.c:497
r1 = 0
r2 = 0
c = 0
sts = 4
command = 0x0
filename = (wchar_t *) 0x0
module = 0x0
fp = (FILE *) 0x964e70
p = 0x6c05 Address 0x6c05 out of bounds
unbuffered = 0
skipfirstline = 0
stdin_is_interactive = 1
help = 0
version = 0
saw_unbuffered_flag = 0
cf = {cf_flags = 0}
#6 0x00412866 in main (argc=4, argv=0x7f7c7920) at
Modules/python.c:57
argsize = 140187732310304
argv_copy = (wchar_t **) 0x20f0331a0
argv_copy2 = (wchar_t **) 0x20f033140
i = 0
res = -231136
oldloc = 0x20e0c1b00 C
I also have core file. If you are interested mail me.
--
messages: 71968
nosy: henry.precheur
severity: normal
status: open
title: Crash while compiling Python 3000 in OpenBSD 4.4
versions: Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3685
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4
Henry Precheur [EMAIL PROTECTED] added the comment: I forgot to mention, I made to following modification to configure.in so I could compile Python 3000 on OpenBSD 4.4 --- configure.in(revision 66037) +++ configure.in(working copy) @@ -250,7 +250,7 @@ # On OpenBSD, select(2) is not available if _XOPEN_SOURCE is defined, # even though select is a POSIX function. Reported by J. Ribbens. # Reconfirmed for OpenBSD 3.3 by Zachary Hamm, for 3.4 by Jason Ish. - OpenBSD/2.* | OpenBSD/3.@:@0123456789@:@ | OpenBSD/4.@:@0123@:@) + OpenBSD*) define_xopen_source=no # OpenBSD undoes our definition of __BSD_VISIBLE if _XOPEN_SOURCE is # also defined. This can be overridden by defining _BSD_SOURCE ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3685 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3686] PKG-INFO file should differentiate between authors and maintainers
New submission from Marc-Andre Lemburg [EMAIL PROTECTED]: The PKG-INFO file currently only provides an Authors field which is mapped to the DistributionMetadata.get_contact() information. However, the latter method is really meant to provide access to contact information and not authorship, which is why it prefers the maintainer infos over the actual author infos. As a result, the maintainer can appear as author in the PKG-INFO file, which is wrong. Ideal would be to have both an Author and Maintainer field in the PKG-FILE with 1-1 mappings to the setup() parameters. -- components: Distutils messages: 71970 nosy: lemburg priority: normal severity: normal status: open title: PKG-INFO file should differentiate between authors and maintainers versions: Python 2.7, Python 3.1 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3686 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2562] Cannot use non-ascii letters in disutils if setuptools is used.
Tarek Ziadé [EMAIL PROTECTED] added the comment: ok I will ask for this on the ML ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2562 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2415] bytes() should respect __bytes__
Barry A. Warsaw [EMAIL PROTECTED] added the comment: Well, if I figured out how to use Rietveld correctly, I've left some questions for you in the review. It looks basically pretty good, so if you could answer those questions, you can commit the change. Should __bytes__ support be backported to 2.6? ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2415 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3663] Extra DECREF on syntax errors
Changes by Barry A. Warsaw [EMAIL PROTECTED]: -- priority: deferred blocker - release blocker ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3663 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3663] Extra DECREF on syntax errors
Barry A. Warsaw [EMAIL PROTECTED] added the comment: Benjamin's reviewed it, so please commit it. Is there a test for this crasher? -- nosy: +barry resolution: - accepted ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3663 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2415] bytes() should respect __bytes__
Antoine Pitrou [EMAIL PROTECTED] added the comment: Should __bytes__ support be backported to 2.6? Isn't it already there in __str__? Or do you mean just add support for the alternate method name? ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2415 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4
Changes by Antoine Pitrou [EMAIL PROTECTED]: -- components: +Interpreter Core priority: - release blocker type: - crash ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3685 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2534] Restore isinstance and issubclass speed in 2.6
Antoine Pitrou [EMAIL PROTECTED] added the comment: Here is the same patch, but backported to 2.6. Added file: http://bugs.python.org/file11261/isinstance26-2.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2534 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2415] bytes() should respect __bytes__
Barry A. Warsaw [EMAIL PROTECTED] added the comment: yep, that's all i meant. it might not be worth it though. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2415 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3548] subprocess.pipe function
Vincent Legoll [EMAIL PROTECTED] added the comment: Hello, I was searching for a bug in subprocess module when I saw your patch. I was implementing the exact same functionality and mixed some of your ideas in what I use now, which is attached... Feel free to use it -- nosy: +vincent.legoll Added file: http://bugs.python.org/file11262/toto.py ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3548 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1759845] subprocess.call fails with unicode strings in command line
Changes by Anders J. Munch [EMAIL PROTECTED]: -- nosy: +andersjm ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1759845 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3548] subprocess.pipe function
Vincent Legoll [EMAIL PROTECTED] added the comment: Here's a clean version with doc test enjoy ! Added file: http://bugs.python.org/file11263/pipeline.py ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3548 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3548] subprocess.pipe function
Changes by Antoine Pitrou [EMAIL PROTECTED]: -- priority: - normal versions: +Python 2.7, Python 3.1 -Python 2.6, Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3548 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2534] Restore isinstance and issubclass speed in 2.6
Raymond Hettinger [EMAIL PROTECTED] added the comment: +1 on applying this patch right away. For 2.6 and 3.0 to be successful, we need people to prefer to upgrade rather than stay with 2.5. A systemic slowdown in not in the best interests of the language moving forward. -- nosy: +rhettinger ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2534 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2534] Restore isinstance and issubclass speed in 2.6
Benjamin Peterson [EMAIL PROTECTED] added the comment: Both patches look correct to me, and I think they can be applied. -- assignee: - pitrou resolution: - accepted ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2534 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3651] eval() leaks 1 reference every time
Antoine Pitrou [EMAIL PROTECTED] added the comment: Amaury, assuming you have tested it :-), the patch is ok to me. You can commit. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3651 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3687] Popen() object stdout attribute reassignment behaviour
New submission from Vincent Legoll [EMAIL PROTECTED]: The subprocess.Popen() object documentation should indicate that the stdout attribute should not be modified after object construction. Because that won't work. Or the attribute may be rendered read-only from subprocess import Popen, PIPE import sys, os p1 = Popen([echo, 1], stdout = PIPE) p2 = Popen([cat], stdin = p1.stdout, stderr = PIPE, stdout = PIPE) p2.stdout = sys.stdout print p2.communicate() This blocks forever -- assignee: georg.brandl components: Documentation messages: 71983 nosy: georg.brandl, vincent.legoll severity: normal status: open title: Popen() object stdout attribute reassignment behaviour type: behavior versions: Python 2.5 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3687 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3149] multiprocessing build fails on Solaris 10
Antoine Pitrou [EMAIL PROTECTED] added the comment: This is a duplicate of #3110. -- nosy: +pitrou resolution: - duplicate status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3149 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3110] Multiprocessing package build problem on Solaris 10
Antoine Pitrou [EMAIL PROTECTED] added the comment: FWIW, this is what I find on a Solaris box. ./sys/param.h:#define _SEM_VALUE_MAX INT_MAX ./sys/sysconfig.h:#define _CONFIG_SEM_VALUE_MAX 21 /* max. value a semaphore may have */ ./sys/unistd.h:#define _SC_SEM_VALUE_MAX 37 ./limits.h:#define _POSIX_SEM_VALUE_MAX32767 -- nosy: +pitrou priority: - high ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3110 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2384] [Py3k] line number is wrong after encoding declaration
Changes by Dwayne Litzenberger [EMAIL PROTECTED]: -- nosy: +dlitz ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2384 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3688] open() rejects bytes as filename
New submission from Dwayne Litzenberger [EMAIL PROTECTED]: On Linux/ext3, filenames are stored natively as sequences of octets. On Win32/NTFS, they are stored natively as sequences of Unicode code points. In Python 2.x, the way to unambiguously open a particular file was to pass the filename as a str object on Linux/ext3 and as a unicode object on Win32/NTFS. os.listdir(.) would return every filename as a str object, and os.listdir(u.) would return every filename as a unicode object---based on the current locale settings---*except* for filenames that couldn't be decoded that way. Consider this bash script (executed on Linux under a UTF-8 locale): export LC_CTYPE=en_CA.UTF-8 # requires the en_CA.UTF-8 locale to be built mkdir /tmp/foo cd /tmp/foo touch $'UTF-8 compatible filename\xc2\xa2' touch $'UTF-8 incompatible filename\xc0' Under Python 2.52, you get this: import os os.listdir(u.) ['UTF-8 incompatible filename\xc0', u'UTF-8 compatible filename\xa2'] os.listdir(.) ['UTF-8 incompatible filename\xc0', 'UTF-8 compatible filename\xc2\xa2'] [open(f, r) for f in os.listdir(u.)] [open file 'UTF-8 incompatible filename�, mode 'r' at 0xb7cee578, open file 'UTF-8 compatible filename¢', mode 'r' at 0xb7cee6e0] Under Python 3.0b3, you get this: import os os.listdir(.) [b'UTF-8 incompatible filename\xc0', 'UTF-8 compatible filename¢'] os.listdir(b.) [b'UTF-8 incompatible filename\xc0', b'UTF-8 compatible filename\xc2\xa2'] [open(f, r) for f in os.listdir(.)] Traceback (most recent call last): File stdin, line 1, in module File stdin, line 1, in listcomp File /home/dwon/python3.0b3/lib/python3.0/io.py, line 284, in __new__ return open(*args, **kwargs) File /home/dwon/python3.0b3/lib/python3.0/io.py, line 184, in open raise TypeError(invalid file: %r % file) TypeError: invalid file: b'UTF-8 incompatible filename\xc0' This behaviour of open() makes it impossible to write code that opens arbitrarily-named files on Linux/ext3. -- components: Windows messages: 71986 nosy: dlitz severity: normal status: open title: open() rejects bytes as filename versions: Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3688 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3688] open() rejects bytes as filename
Changes by Dwayne Litzenberger [EMAIL PROTECTED]: -- components: +Library (Lib) -Windows type: - behavior ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3688 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2415] bytes() should respect __bytes__
Benjamin Peterson [EMAIL PROTECTED] added the comment: Thanks for the review, Barry! Committed in r66038. Sort of backported in r66039 by aliasing PyObject_Bytes to PyObject_Str. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2415 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3688] open() rejects bytes as filename
Amaury Forgeot d'Arc [EMAIL PROTECTED] added the comment: This is actively being discussed (and developed) in issue3187 -- nosy: +amaury.forgeotdarc resolution: - duplicate status: open - closed superseder: - os.listdir can return byte strings ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3688 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3187] os.listdir can return byte strings
Changes by Dwayne Litzenberger [EMAIL PROTECTED]: -- nosy: +dlitz ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3187 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1210] imaplib does not run under Python 3
Ismail Donmez [EMAIL PROTECTED] added the comment: Still fails with beta2: import imaplib mail=imaplib.IMAP4(mail.rtmq.infosathse.com) Traceback (most recent call last): File stdin, line 1, in module File /usr/local/lib/python3.0/imaplib.py, line 185, in __init__ self.welcome = self._get_response() File /usr/local/lib/python3.0/imaplib.py, line 912, in _get_response if self._match(self.tagre, resp): File /usr/local/lib/python3.0/imaplib.py, line 1021, in _match self.mo = cre.match(s) TypeError: can't use a string pattern on a bytes-like object -- nosy: +cartman ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1210 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2464] urllib2 can't handle http://www.wikispaces.com
Facundo Batista [EMAIL PROTECTED] added the comment: Gregory... I tried to fill the path in urlunparse, and other functions that use this started to fail. As we're so close to final releases, I'll leave this as it's right now, that actually fixed the bug... ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2464 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3187] os.listdir can return byte strings
Dwayne Litzenberger [EMAIL PROTECTED] added the comment: I think Guido already understands this, but I haven't seen it stated very clearly here: ** Different systems use different things to identify files. ** On Linux/ext3, all filenames are *octet strings* (i.e. bytes), and *only* the following caveats apply: - a filename/pathname cannot contain the zero-octet (b\x00). - a filename/pathname cannot be empty. - a filename cannot contain the slash (b/); In a pathname, the slash is used to separate filenames. - the filenames b. and b.. have special meanings; They cannot be created, deleted, or renamed. All filenames that meet these criteria are valid, and calling them invalid amounts to plugging one's ears and shouting LA LA LA while imagining Unicode having pre-dated Unix. It is sometimes convenient to imagine filenames on Linux/ext3 as sequences of Unicode code points (where the encoding is specified by LC_CTYPE---it's not necessarily UTF-8), but other times (e.g. in backup tools that need to be robust in the face of mischievous users) it is an unnecessary abstraction that introduces bugs. On Windows/NTFS, the situation is entirely different: Filenames are actually sequences of Unicode code points, and if you pretend they are octet strings, Windows will happily invent phantom filenames for you that will show up in the output of os.listdir(), but that will return File not found if you try to open them for reading (if you open them for writing, you risk clobbering other files that happens to have the same names). To avoid bugs, it should be possible to work exclusively with filenames in the platform's native representation. It was possible in Python 2 (though you had to be very careful). Ideally, Python 3 would recognize and enforce the difference instead of trying to guess the translations; Explicit is better than implicit and all that. ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3187 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1210] imaplib does not run under Python 3
Neal Norwitz [EMAIL PROTECTED] added the comment: This may not be a real release blocker, but I want to raise the priority. It is a regression and we should try to fix it, especially if it's easy. -- priority: normal - release blocker ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue1210 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3689] reversed() not working as intended on lists
New submission from Jeff Hall [EMAIL PROTECTED]: reversed() built in is not functioning correctly with list (specifically with len() ) l = [1,2,3,4] rl = reversed(l) type(rl) type 'listreverseiterator' vs. strings and tuples which just return 'reverse' objects listreverseiterators apparently have a len() defined that changes with each .next() call -- messages: 71993 nosy: laxrulz777 severity: normal status: open title: reversed() not working as intended on lists type: behavior versions: Python 2.5 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3689 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3689] listreverseiterator has a decreasing len()
Changes by Georg Brandl [EMAIL PROTECTED]: -- assignee: - rhettinger nosy: +rhettinger title: reversed() not working as intended on lists - listreverseiterator has a decreasing len() versions: +Python 2.6, Python 3.0 -Python 2.5 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3689 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3689] listreverseiterator has a decreasing len()
Armin Ronacher [EMAIL PROTECTED] added the comment: Just for the record. This original discussion for this bug is here: http://article.gmane.org/gmane.comp.python.devel/96925 -- nosy: +aronacher ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3689 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3690] sys.getsizeof wrong for Py3k bool objects
New submission from Robert Schuppenies [EMAIL PROTECTED]: sys.getsizeof returns wrong results for bool objects in Python 3000. Although bool objects use the same datatype as long objects, they are allocated differently. Thus, the inherited long_sizeof implementation is incorrect. The applied patch addresses this issue. -- components: Interpreter Core files: bool_sizeof.patch keywords: patch messages: 71996 nosy: schuppenies severity: normal status: open title: sys.getsizeof wrong for Py3k bool objects type: behavior versions: Python 3.0, Python 3.1 Added file: http://bugs.python.org/file11264/bool_sizeof.patch ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3690 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3166] Make conversions from long to float correctly rounded.
David Jones [EMAIL PROTECTED] added the comment: I agree, longs should be correctly rounded when coerced to floats. There is an ugly (but amusing) workaround while people wait for this patch: Go via a string: int(float(repr(295147905179352891391)[:-1])) Though I assume this relies on the platform's strtod working correctly. Which it does for me. -- nosy: +drj ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3166 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3691] Incorrect variable reference
New submission from Tim Hemming [EMAIL PROTECTED]: The following line is referencing a variable d, but it should be dict: logging.warning(Protocol problem: %s, connection reset, extra=d) Page:- http://www.python.org/doc/2.5/lib/module-logging.html -- assignee: georg.brandl components: Documentation messages: 71998 nosy: georg.brandl, timh severity: normal status: open title: Incorrect variable reference versions: Python 2.5 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3691 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3691] Incorrect variable reference
Benjamin Peterson [EMAIL PROTECTED] added the comment: This has been fixed in the trunk. -- nosy: +benjamin.peterson resolution: - out of date status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3691 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3663] Extra DECREF on syntax errors
Antoine Pitrou [EMAIL PROTECTED] added the comment: Committed in r66041. Thanks everyone. -- resolution: accepted - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3663 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2534] Restore isinstance and issubclass speed in 2.6
Antoine Pitrou [EMAIL PROTECTED] added the comment: Committed in r66042 and r66043. -- resolution: accepted - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue2534 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3692] improper scope in list comprehension, when used in class declaration
New submission from kai zhu [EMAIL PROTECTED]: in 3rd line, list comprehension tries to access class_attribute1 as a global variable (code is valid in python 2.5) class Foo(object): ... class_attribute1 = 1 ... class_attribute2 = [class_attribute1 for x in range(8)] ... Traceback (most recent call last): File stdin, line 1, in module File stdin, line 3, in Foo File stdin, line 3, in listcomp NameError: global name 'class_attribute1' is not defined -- components: Interpreter Core messages: 72002 nosy: kaizhu severity: normal status: open title: improper scope in list comprehension, when used in class declaration type: behavior versions: Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3692 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3006] subprocess.Popen causes socket to remain open after close
Changes by Nicolas Grilly [EMAIL PROTECTED]: -- nosy: +ngrilly ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3006 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3651] eval() leaks 1 reference every time
Benjamin Peterson [EMAIL PROTECTED] added the comment: Fixed in r66047. -- resolution: - fixed status: open - closed ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3651 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3693] Obscure array.array error message
New submission from Terry J. Reedy [EMAIL PROTECTED]:
In 2.5
import array
a = array.array('b', 'fox')
In 3.0
import array
a = array.array('b', 'fox')
Traceback (most recent call last):
File pyshell#2, line 1, in module
a = array.array('b', 'fox')
TypeError: an integer is required
This puzzled me because an integer argument most certainly is not
allowed (one would raise other exceptions.) Then I realized that 'an
integer' here actually means 'an iterator producing integers' or more
exactly, 'an iterable whose iterator yields integers in the range
implied by the type code'. What I would like to see is something like
TypeError: for typecode 'b', the optional initializer must be an
iterable of 1 byte integers (such as bytes).
I would also like to see a minor change in the array and array.array
docstrings. Array.__doc__ lists the typecodes, array.array.__doc__
lists all the other info needed, so that help(array) gives everything
while help(array.array) omits the needed typecode info. So I would like
to see the typecode info moved to the class docstring with everything
else (and replaced by 'Defines one class: array') so help(array) and
help(array.array) would both give all needed info.
--
components: Library (Lib)
messages: 72004
nosy: tjreedy
severity: normal
status: open
title: Obscure array.array error message
versions: Python 3.0
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue3693
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3694] Undetected error in _struct.pack_into
New submission from Daniel Diniz [EMAIL PROTECTED]: The following code leads to XXX Undetected errors in debug builds of trunk and 3.0: import _struct _struct.pack_into(b8, bytearray(1), None) Besides that, there's something fishy happening in non-debug builds: 2.6: _struct.pack_into(b8, bytearray(1), None); _struct.pack_into(b8, bytearray(1), None); import sys Traceback (most recent call last): File stdin, line 1, in module TypeError: an integer is required 3.0: _struct.pack_into(b8, bytearray(1), None) _struct.pack_into(b8, bytearray(1), None) SystemError: Objects/longobject.c:433: bad argument to internal function Found with Fusil. -- components: Extension Modules messages: 72005 nosy: ajaksu2 severity: normal status: open title: Undetected error in _struct.pack_into versions: Python 2.6, Python 3.0 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3694 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3695] Source tarball for Sphinx 0.4.3 missing
New submission from Michel Salim [EMAIL PROTECTED]: Sphinx's website stated that 0.4.3 has been released; however, the download site only has 0.4.2. Is 0.4.2 still the latest version, or has the source upload been accidentally omitted? -- assignee: georg.brandl components: Documentation tools (Sphinx) messages: 72006 nosy: georg.brandl, hircus severity: normal status: open title: Source tarball for Sphinx 0.4.3 missing type: feature request versions: Python 2.5 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3695 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3692] improper scope in list comprehension, when used in class declaration
Daniel Diniz [EMAIL PROTECTED] added the comment: I believe the problem is that list comprehensions in 3.0 have scope like that of genexprs in 2.5, but the change was deliberate (as it also avoids leaking of temp variables). Compare to 2.5: class Foo(object): ...class_attribute1 = 1 ...class_attribute2 = (class_attribute1 for x in range(8)) ... Foo.class_attribute2.next() Traceback (most recent call last): File stdin, line 1, in module File stdin, line 3, in genexpr NameError: global name 'class_attribute1' is not defined -- nosy: +ajaksu2 ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3692 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3685] Crash while compiling Python 3000 in OpenBSD 4.4
Henry Precheur [EMAIL PROTECTED] added the comment: Indeed it looks like it is the source of the problem. I created a patch to fix it. But it looks like there is another problem, instead of crashing the Python interpreter goes into interactive mode instead of executing the 'setup.py' script ... I don't think it is related, I have checked the result of ws = ws + wcslen(ws) and it seems to be correct. I will investigate the problem and create another entry if it is unrelated. -- keywords: +patch Added file: http://bugs.python.org/file11265/fix_wcschr_openbsd.diff ___ Python tracker [EMAIL PROTECTED] http://bugs.python.org/issue3685 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
