[issue1020] pydoc doesn't work on pyexpat
Changes by Sean Reifschneider: -- priority: - low __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1020 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1021] logging.basicConfig does not allow to set NOTSET level
Changes by Sean Reifschneider: -- assignee: - vsajip nosy: +vsajip priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1021 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1025] tracebacks from list comps (probably other comps) don't show full stack
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1025 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1042] test_glob fails with UnicodeDecodeError
Changes by Sean Reifschneider: -- priority: - high __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1042 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1053] bogus attributes reported in asyncore doc
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1053 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1053] bogus attributes reported in asyncore doc
Changes by Sean Reifschneider: -- assignee: - fdrake nosy: +fdrake __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1053 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1060] zipfile cannot handle files larger than 2GB (inside archive)
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1060 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1003] zipfile password fails validation
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1003 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1067] test_smtplib failures (caused by asyncore)
Changes by Sean Reifschneider: -- priority: - high __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1067 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1079] decode_header does not follow RFC 2047
Sean Reifschneider added the comment: Can you provide an example of an address that triggers this? Preferably in a code sample that can be used to reproduce it? Uber-ideally, a patch to the email module test suite would be great. -- nosy: +jafo priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1079 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1597011] Reading with bz2.BZ2File() returns one garbage character
Changes by Sean Reifschneider: -- resolution: - fixed _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1597011 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1081] file.seek allows float arguments
Changes by Sean Reifschneider: -- assignee: - loewis nosy: +loewis priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1081 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1082] platform system may be Windows or Microsoft since Vista
Sean Reifschneider added the comment: Attached a patch which I *THINK* fixes this, but I don't run Windows. Can someone else check this? -- assignee: - lemburg nosy: +jafo, lemburg priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1082 __Index: Lib/platform.py === --- Lib/platform.py (revision 58178) +++ Lib/platform.py (working copy) @@ -1158,7 +1158,9 @@ An empty string is returned if the value cannot be determined. -return uname()[0] +systemName = uname()[0] +if systemName == 'Microsoft': return 'Windows' +return systemName def node(): @@ -1177,7 +1179,10 @@ An empty string is returned if the value cannot be determined. -return uname()[2] +unameInfo = uname() +if unameInfo[0] == 'Microsoft' and unameInfo == 'Windows': +return 'Vista' +return unameInfo[2] def version(): ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1087] py3k os.popen result is not iterable, patch attached
Changes by Sean Reifschneider: -- assignee: - aimacintyre nosy: +aimacintyre priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1087 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1004] MultiMethods with type annotations in 3000
Changes by Sean Reifschneider: -- assignee: - gvanrossum nosy: +gvanrossum priority: - low __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1004 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1082] platform system may be Windows or Microsoft since Vista
Sean Reifschneider added the comment: Supplied patch passes make test, BTW. -- keywords: +patch __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1082 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1027] uudecoding (uu.py) does not supprt base64, patch attached
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1027 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1254718] GCC detection for runtime_library_dirs when ccache is used
Sean Reifschneider added the comment: NOTE: See also issue1032 which has a patch for this. Can we come to a consensus on which one has the best patch? -- assignee: - loewis nosy: +jafo, loewis _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1254718 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1032] Improve the hackish runtime_library_dirs support for gcc
Changes by Sean Reifschneider: -- assignee: - loewis nosy: +loewis priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1032 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1047] py3k: corrections for test_subprocess on windows
Changes by Sean Reifschneider: -- priority: - low __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1047 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1061] ABC caches should use weak refs
Changes by Sean Reifschneider: -- assignee: - georg.brandl priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1061 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1086] test_email failed
Changes by Martin v. Löwis: __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1086 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1086] test_email failed
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1086 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1022] use bytes for code objects
Changes by Sean Reifschneider: -- assignee: - gvanrossum priority: - low resolution: - remind __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1022 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1045] Performance regression in 2.5
Changes by Sean Reifschneider: -- assignee: - tim_one nosy: +tim_one priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1045 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1077] itertools missing, causes interactive help to break
Changes by Sean Reifschneider: -- assignee: - georg.brandl priority: - low severity: urgent - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1077 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1102] Add support for _msi.Record.GetString() and _msi.Record.GetInteger()
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1102 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1110] Problems with the msi installer - python-3.0a1.msi
Changes by Sean Reifschneider: -- assignee: - loewis priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1110 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1115] Minor Change For Better cross compile
Changes by Sean Reifschneider: -- assignee: - loewis nosy: +loewis priority: - low __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1115 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1109] Warning required when calling register() on an ABCMeta subclass
Changes by Sean Reifschneider: -- assignee: - gvanrossum nosy: +gvanrossum priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1109 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1005] Patches to rename Queue module to queue
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1005 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1108] Problem with doctest and decorated functions
Changes by Sean Reifschneider: -- assignee: - tim_one nosy: +tim_one priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1108 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1014] cgi: parse_qs and parse_qsl misbehave on empty strings
Changes by Sean Reifschneider: -- assignee: - gvanrossum nosy: +gvanrossum priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1014 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1128] msilib.Directory.make_short only handles file names with a single dot in them
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1128 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1140] re.sub returns str when processing empty unicode string
Sean Reifschneider added the comment: Applied as revision 58179 to 2.5 maintenance branch, passes tests. -- nosy: +jafo priority: - low status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1140 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1144] parsermodule validation out of sync with Grammar
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1144 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1530559] struct.pack raises TypeError where it used to convert
Changes by Sean Reifschneider: -- priority: urgent - normal _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1530559 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1692335] Fix exception pickling: Move initial args assignment to BaseException.__new__
Sean Reifschneider added the comment: It's not clear to me what the next step is here, does one or more of the other folks need to provide some input? Georg: If you are looking for something from someone, can you assign the ticket to them? -- assignee: - georg.brandl nosy: +jafo _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1692335 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1727780] 64/32-bit issue when unpickling random.Random
Shawn Ligocki added the comment:
I've got a patch! The problem was that the state was being cast from a
C-type unsigned long to a long.
On 32-bit machines this makes large 32-bit longs negative.
On 64-bit machines this preserves the sign of 32-bit values (because
they are stored in 64-bit longs).
My patch returns the values with PyLong_FromUnsignedLong() instead of
PyInt_FromLong(), therefore there is no casting to long and both 32-bit
and 64-bit machines produce the same result.
I added code to read states from the old (buggy) version and decypher it
appropriately (from either 32-bit or 64-bit source!). In other words,
old pickles can now be opened on either architecture with the new patch.
This patch is taken from the svn head, but also works on Python 2.5.1 .
I haven't tested this patch fully on 64-bit machine yet. I'll let you
know when I have.
Cheers,
-Shawn
_
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1727780
_Index: Lib/random.py
===
--- Lib/random.py (revision 58178)
+++ Lib/random.py (working copy)
@@ -83,7 +83,7 @@
-VERSION = 2 # used by getstate/setstate
+VERSION = 3 # used by getstate/setstate
def __init__(self, x=None):
Initialize an instance.
@@ -120,9 +120,20 @@
def setstate(self, state):
Restore internal state from object returned by getstate().
version = state[0]
-if version == 2:
+if version == 3:
version, internalstate, self.gauss_next = state
super(Random, self).setstate(internalstate)
+elif version == 2:
+version, internalstate, self.gauss_next = state
+# In version 2, the state was saved as signed ints, which causes
+# inconsistencies between 32/64-bit systems. The state is
+# really unsigned 32-bit ints, so we convert negative ints from
+# version 2 to positive longs for version 3.
+try:
+internalstate = tuple( long(x) % (2**32) for x in internalstate )
+except ValueError, e:
+raise TypeError, e
+super(Random, self).setstate(internalstate)
else:
raise ValueError(state with version %s passed to
Random.setstate() of version %s %
Index: Modules/_randommodule.c
===
--- Modules/_randommodule.c (revision 58178)
+++ Modules/_randommodule.c (working copy)
@@ -319,12 +319,12 @@
if (state == NULL)
return NULL;
for (i=0; iN ; i++) {
- element = PyInt_FromLong((long)(self-state[i]));
+ element = PyLong_FromUnsignedLong(self-state[i]);
if (element == NULL)
goto Fail;
PyTuple_SET_ITEM(state, i, element);
}
- element = PyInt_FromLong((long)(self-index));
+ element = PyLong_FromLong((long)(self-index));
if (element == NULL)
goto Fail;
PyTuple_SET_ITEM(state, i, element);
@@ -339,7 +339,8 @@
random_setstate(RandomObject *self, PyObject *state)
{
int i;
- long element;
+ unsigned long element;
+ long index;
if (!PyTuple_Check(state)) {
PyErr_SetString(PyExc_TypeError,
@@ -353,16 +354,16 @@
}
for (i=0; iN ; i++) {
- element = PyInt_AsLong(PyTuple_GET_ITEM(state, i));
+ element = PyLong_AsUnsignedLong(PyTuple_GET_ITEM(state, i));
if (element == -1 PyErr_Occurred())
return NULL;
- self-state[i] = (unsigned long)element;
+ self-state[i] = element 0xUL; /* Make sure we get sane state */
}
- element = PyInt_AsLong(PyTuple_GET_ITEM(state, i));
- if (element == -1 PyErr_Occurred())
+ index = PyLong_AsLong(PyTuple_GET_ITEM(state, i));
+ if (index == -1 PyErr_Occurred())
return NULL;
- self-index = (int)element;
+ self-index = (int)index;
Py_INCREF(Py_None);
return Py_None;
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue815646] thread unsafe file objects cause crash
Sean Reifschneider added the comment: If I read the 2003 python-dev thready correctly, there isn't a solution to this. Does this need to go back to python-dev, or do we just call it wont fix? Or...? -- assignee: - tim_one nosy: +jafo, tim_one Tracker [EMAIL PROTECTED] http://bugs.python.org/issue815646 ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1150] Rename PyBUF_WRITEABLE to PyBUF_WRITABLE
Sean Reifschneider added the comment:
Attached is a patch that fixes writeable. I'm thinking, close this if
the patch looks ok, and open another for a general identify
non-englishisms ticket, once they're identified a ticket could be
opened to fix them.
I fixed only the PyBUF instances but also documents and comments and doc
strings and printfs where it occurred. Yes? Let me know if it looks
good to commit.
Does this need a fix in 2to3?
--
assignee: - gvanrossum
keywords: +patch
nosy: +jafo
priority: - low
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1150
__Index: Include/abstract.h
===
--- Include/abstract.h (revision 58179)
+++ Include/abstract.h (working copy)
@@ -524,9 +524,9 @@
Py_ssize_t *buffer_len);
/*
- Takes an arbitrary object which must support the (writeable,
+ Takes an arbitrary object which must support the (writable,
single segment) buffer interface and returns a pointer to a
- writeable memory location in buffer of size buffer_len.
+ writable memory location in buffer of size buffer_len.
0 is returned on success. buffer and buffer_len are only
set in case no error occurrs. Otherwise, -1 is returned and
Index: Include/object.h
===
--- Include/object.h (revision 58179)
+++ Include/object.h (working copy)
@@ -162,7 +162,7 @@
/* Flags for getting buffers */
#define PyBUF_SIMPLE 0
#define PyBUF_CHARACTER 1
-#define PyBUF_WRITEABLE 0x0002
+#define PyBUF_WRITABLE 0x0002
#define PyBUF_LOCKDATA 0x0004
#define PyBUF_FORMAT 0x0008
#define PyBUF_ND 0x0010
@@ -172,19 +172,19 @@
#define PyBUF_ANY_CONTIGUOUS (0x0100 | PyBUF_STRIDES)
#define PyBUF_INDIRECT (0x0200 | PyBUF_STRIDES)
-#define PyBUF_CONTIG (PyBUF_ND | PyBUF_WRITEABLE)
+#define PyBUF_CONTIG (PyBUF_ND | PyBUF_WRITABLE)
#define PyBUF_CONTIG_RO (PyBUF_ND)
#define PyBUF_CONTIG_LCK (PyBUF_ND | PyBUF_LOCKDATA)
-#define PyBUF_STRIDED (PyBUF_STRIDES | PyBUF_WRITEABLE)
+#define PyBUF_STRIDED (PyBUF_STRIDES | PyBUF_WRITABLE)
#define PyBUF_STRIDED_RO (PyBUF_STRIDES)
#define PyBUF_STRIDED_LCK (PyBUF_STRIDES | PyBUF_LOCKDATA)
-#define PyBUF_RECORDS (PyBUF_STRIDES | PyBUF_WRITEABLE | PyBUF_FORMAT)
+#define PyBUF_RECORDS (PyBUF_STRIDES | PyBUF_WRITABLE | PyBUF_FORMAT)
#define PyBUF_RECORDS_RO (PyBUF_STRIDES | PyBUF_FORMAT)
#define PyBUF_RECORDS_LCK (PyBUF_STRIDES | PyBUF_LOCKDATA | PyBUF_FORMAT)
-#define PyBUF_FULL (PyBUF_INDIRECT | PyBUF_WRITEABLE | PyBUF_FORMAT)
+#define PyBUF_FULL (PyBUF_INDIRECT | PyBUF_WRITABLE | PyBUF_FORMAT)
#define PyBUF_FULL_RO (PyBUF_INDIRECT | PyBUF_FORMAT)
#define PyBUF_FULL_LCK (PyBUF_INDIRECT | PyBUF_LOCKDATA | PyBUF_FORMAT)
Index: Include/memoryobject.h
===
--- Include/memoryobject.h (revision 58179)
+++ Include/memoryobject.h (working copy)
@@ -33,15 +33,15 @@
The buffertype argument can be PyBUF_READ, PyBUF_WRITE,
PyBUF_UPDATEIFCOPY to determine whether the returned buffer
- should be READONLY, WRITEABLE, or set to update the
+ should be READONLY, WRITABLE, or set to update the
original buffer if a copy must be made. If buffertype is
PyBUF_WRITE and the buffer is not contiguous an error will
be raised. In this circumstance, the user can use
- PyBUF_UPDATEIFCOPY to ensure that a a writeable temporary
+ PyBUF_UPDATEIFCOPY to ensure that a a writable temporary
contiguous buffer is returned. The contents of this
contiguous buffer will be copied back into the original
object after the memoryview object is deleted as long as
- the original object is writeable and allows setting its
+ the original object is writable and allows setting its
memory to readonly. If this is not allowed by the
original object, then a BufferError is raised.
Index: Objects/abstract.c
===
--- Objects/abstract.c (revision 58179)
+++ Objects/abstract.c (working copy)
@@ -304,9 +304,9 @@
pb = obj-ob_type-tp_as_buffer;
if (pb == NULL ||
pb-bf_getbuffer == NULL ||
-((*pb-bf_getbuffer)(obj, view, PyBUF_WRITEABLE) != 0)) {
+((*pb-bf_getbuffer)(obj, view, PyBUF_WRITABLE) != 0)) {
PyErr_SetString(PyExc_TypeError,
-expected an object with a writeable buffer interface);
+expected an object with a writable buffer interface);
return -1;
}
@@ -659,10 +659,10 @@
Cannot make this object read-only.);
return -1;
}
-if (((flags PyBUF_WRITEABLE) == PyBUF_WRITEABLE)
+if (((flags
[issue1130] Idle - Save (buffer) - closes IDLE and does not save file (Windows XP)
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1130 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1599254] mailbox: other programs' messages can vanish without trace
Changes by Peter Lloyd: -- nosy: +peter.ll _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1599254 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1019] Cleanup pass on _curses and _curses_panel
Changes by Sean Reifschneider: -- priority: - low __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1019 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1123] split(None, maxsplit) does not strip whitespace correctly
Sean Reifschneider added the comment: I believe this is just a place where the documentation could be cleared up. Seems to me the confusion is from the document saying (paraphrased): white space is removed from both ends. Perhaps it should say something like runs of 1 or more whitespace are collapsed (up to the maximum split), and then split on or simply split on runs of 1 or more whitespace. In other words, 3 spaces together would be treated as a single split-point instead of 3 0-length fields separated by spaces. So, in the first example provided by nirs in this issue, both ends refers to both the left and right side of k:. Since maxsplit is 1, the second part (v) is left untouched. This is the intended operation. This is a documentation bug, not a library bug. Fred: Thoughts on wording? -- assignee: - fdrake components: +Documentation -Library (Lib) nosy: +fdrake, jafo priority: - low __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1123 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1126] file.fileno and file.isatty() should be implementable by any file like object
Fred L. Drake, Jr. added the comment: The documentation does not say what's implied by msg55724; they methods can (and arguably should) be implmented by types for which they apply (for which there is a corresponding file descriptor, for example). There is an API issue here as well: what about a wrapper type that is sometimes associated with a real file, and sometimes not? I suppose in that case the factory (constructor) needs to detect the situation and return an instance of an appropriate type. The documentation is clear, so far as it goes, but is arguably incomplete. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1126 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1150] Rename PyBUF_WRITEABLE to PyBUF_WRITABLE
Guido van Rossum added the comment:
Looks good. Check it in, with one small addition: add
#define PyBUF_WRITEABLE PyBUF_WRITABLE
for those NumPy folks who can't help writing the alternate spelling
('writeable' *is* in some dictionaries, though it is consistently
flagged as invalid by spell checkers).
--
assignee: gvanrossum - jafo
resolution: - accepted
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1150
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1170] shlex have problems with parsing unicode
Changes by dexen deVries: -- components: Library (Lib), Unicode severity: normal status: open title: shlex have problems with parsing unicode type: behavior versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1170 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1158] %f format for datetime objects
Brett Cannon added the comment: In terms of strptime, I would just change _strptime.strptime() to _strptime._strptime() and have it return everything along with the microseconds measurement. Then have public functions that call that function and either strip off the microseconds or not. -Brett On 9/17/07, Skip Montanaro [EMAIL PROTECTED] wrote: Skip Montanaro added the comment: Brett, Continuing the discussion of strptime... It returns a time.struct_time. Would it cause too much breakage (only do this in 3.0) to add a tm_usec field to the end of that object? It seems a lot of bits of code might still expect a length 9 tuple-ish thing and do this: yy, mm, dd, hh, mm, ss, wk, j, tz = time.strptime(...) If we could make that change for 3.0 that might allow strptime to parse %f format codes. S __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1158 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/brett%40python.org __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1158 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1170] shlex have problems with parsing unicode
New submission from dexen deVries: Feeding unicode to shlex object created in POSIX compat mode causes UnicodeDecodeError to be raised. It appears that shlex object defines sting .wordchars, containing latin-1 (iso8859-1) encoded characters with charcodes =128, which is used to check whether a character from input constitues a word character or not. -- nosy: +dexen __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1170 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1170] shlex have problems with parsing unicode
dexen deVries added the comment: A quick paste to illustrate: the exception is raised only when unicode object is passed to shlex. Warning: the cStringIO module is unsuitable for use there, only the StringIO. cStringIO does not output unicode. dexen!muraena!~$ python Python 2.5.1 (r251:54863, May 4 2007, 16:52:23) [GCC 4.1.2] on linux2 Type help, copyright, credits or license for more information. from StringIO import StringIO import shlex lx = shlex.shlex( StringIO( unicode( abc ) ) ) lx.get_token() u'abc' lx = shlex.shlex( StringIO( unicode( abc ) ), None, True ) lx.get_token() Traceback (most recent call last): File stdin, line 1, in module File /usr/lib/python2.5/shlex.py, line 96, in get_token raw = self.read_token() File /usr/lib/python2.5/shlex.py, line 150, in read_token elif nextchar in self.wordchars: UnicodeDecodeError: 'ascii' codec can't decode byte 0xdf in position 63: ordinal not in range(128) __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1170 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1170] shlex have problems with parsing unicode
dexen deVries added the comment: One remark to previous message: the first time i created shlex object in non-POSIX mode (the default), in later it's in POSIX mode (due to the third parameter to shlex being True). The bug in question manifests only in POSIX mode. BTW, that so-called POSIX mode would be more POSIX-ish, if instead of comparing characters with a fixed, short list, would use the ctype() function as found in standard C library. The functions takes current locale (setable in process) into account when deciding what is leter, whitespace, punctuation etc. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1170 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1171] allow subclassing of bytes type
New submission from Mathieu Fenniak: Uploading patch to make bytes type subclassable. As e-mailed to python-3000 list during discussion with Guido, attached patch to make bytes type subclassable. Included are unit tests, and a minor fix for pickling subclass instances (including __dict__ in bytes_reduce). -- files: bytes-subclass-patch.diff messages: 55970 nosy: mfenniak severity: minor status: open title: allow subclassing of bytes type type: rfe versions: Python 3.0 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1171 __ bytes-subclass-patch.diff Description: Binary data ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1082] platform system may be Windows or Microsoft since Vista
Pat LaVarre added the comment:
I recommend we reject this first draft of the python-trunk-
vistaplatform.patch.
I reason as follows ...
ACTUAL RESULTS OF 2.5.1 PLUS PATCH IN VISTA WINDOWS:
import platform
...
platform.uname()
('Microsoft', '[redacted]', 'Windows', '6.0.6000', '', '')
platform.system()
'Windows'
platform.release()
'Windows'
EXPECTED RESULTS OF 2.5.1 PLUS PATCH IN VISTA WINDOWS:
import platform
...
platform.uname()
('Windows', '[redacted]', 'Vista', '6.0.6000', '', '')
platform.system()
'Windows'
platform.release()
'Vista'
ACTUAL RESULTS OF 2.5 IN SP2 XP WINDOWS:
import platform
...
platform.uname()
('Windows', '[redacted]', 'XP', '5.1.2600', '', '')
platform.system()
'Windows'
platform.release()
'XP'
DISCUSSION:
Four thoughts:
1.
I think we meant to write { unameInfo[2] == 'Windows' } where we wrote
{ unameInfo == 'Windows' } in this patch.
2.
To run the patch I created a copy of platform.py in the same folder and
applied the patch by hand. I redacted the host names by hand and elided
the { platform = ... } source line I wrote to let me run the patch in
place of the original.
3.
I think we should substitute a different kind of patch, a patch to
correct the platform.uname rather than a patch to redefine
platform.system and platform.version.
I'd like us to hold to such cross-platform invariants as:
( platform.system() == platform.uname()[0] )
( platform.system() == platform.uname()[2] )
Out on the web I see that we have documented these invariants. I quote:
14.12.1 Cross Platform
uname()
... Returns a tuple of strings (system, node, release, version,
machine, processor) identifying the underlying platform.
2007-09-17 fetch of http://docs.python.org/lib/node442.html
near http://docs.python.org/lib/module-platform.html
4.
I don't think we can totally fix this trouble in code: we have
distributed 2.5.1 to Vista too massively already now.
Specifically, I think we should also fix the doc to admit the hereafter
frequent need for people using Python to write code such as:
if not (platform.system() in ('Microsoft', 'Windows')):
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1082
__
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1082] platform system may be Windows or Microsoft since Vista
Sean Reifschneider added the comment:
Attached is a patch that fixes uname() instead of the individual
helpers. I agree that is the better way to do it. Again, not tested on
Windows because I don't have it.
What about adding a isWindows() sort of method that does the right
thing, or amIRunningOn('Vista')? I suggest the latter because I
imagine the former might just lead to a bunch of Where is isX()? for
different platforms. This could implement the logic so that users don't
have to know the details of this issue.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1082
__Index: Lib/platform.py
===
--- Lib/platform.py (revision 58178)
+++ Lib/platform.py (working copy)
@@ -1146,6 +1146,12 @@
machine = ''
if processor == 'unknown':
processor = ''
+
+# normalize name
+if system == 'Microsoft' and release == 'Windows':
+system = 'Windows'
+release = 'Vista'
+
_uname_cache = system,node,release,version,machine,processor
return _uname_cache
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1172] Documentation for done attribute of FieldStorage class
New submission from Bob Kline: I have attached a patch which adds partial documentation for the done attribute of the cgi.FieldStorage class. This addition is needed in order to make it safe to rely on the current behavior of the class, which sets this attribute to the value -1 when an uploaded file from a CGI form does not arrive intact. If I have sufficient free time to do so at some point in the future, I would like to submit a more extensive modification for the module's documentation, using a format which matches that used for most of the other modules (that is, including documentation of all of the methods and attributes intended for public use), and I'd be inclined to modify the cgi.py module itself, to use a less opaque approach for conveying the failure than the 'done' attribute. I'd want some indication that there was a reasonable chance that if I were to invest the work on this improvement the results would actually be used (I see my latest patch for the module has been languishing in the 'ignored' pile for over a year). If anyone else is doing some overhaul work in this area, please speak up so we don't end up with duplication of effort. I would think that this module would be one of the most commonly used in the entire Python library, and would thus warrant careful maintenance (including addressing all of the XXX let's fix this ... comments. Cheers! -- components: Documentation files: cgi.rst.diff messages: 55975 nosy: bkline severity: normal status: open title: Documentation for done attribute of FieldStorage class type: rfe __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1172 __--- cgi.rst 2007-09-17 13:40:51.0 -0400 +++ cgi.rst-20070917 2007-09-17 14:57:00.0 -0400 @@ -147,6 +147,11 @@ if not line: break linecount = linecount + 1 +If an error is encountered when obtaining the contents of an uploaded file +(for example, when the user interrupts the form submission by clicking on +a Back or Cancel button) the :attr:`done` attribute of the object for the +field will be set to the value -1. + The file upload draft standard entertains the possibility of uploading multiple files from one field (using a recursive :mimetype:`multipart/\*` encoding). When this occurs, the item will be a dictionary-like :class:`FieldStorage` item. ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1158] %f format for datetime objects
Skip Montanaro added the comment: Brett In terms of strptime, I would just change _strptime.strptime() to Brett _strptime._strptime() and have it return everything along with Brett the microseconds measurement. Then have public functions that Brett call that function and either strip off the microseconds or not. Sounds good. I'll work that into my patch(es). Skip __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1158 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1082] platform system may be Windows or Microsoft since Vista
Marc-Andre Lemburg added the comment: A couple of notes: * platform.uname() needs to be fixed, not the individual query functions. * The third entry of uname() should return Vista instead of Microsoft on MS Vista. * A patch should go on trunk and into 2.5.2, since this is a real bug and not a feature change. Any other changes to accommodate for differences between used marketing names and underlying OS names should go into system_alias(). __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1082 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1082] platform system may be Windows or Microsoft since Vista
Sean Reifschneider added the comment: Shall I commit my v2 patch then, to 2.5.2 and trunk? It has the code in the uname() method, as you say. __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1082 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1174] new generator methods not documented in Library Reference
New submission from Bruce Frederiksen: The 2.5 library documentation mentions the new GeneratorExit exception, but does not show Generator Types with the new 'send', 'throw', 'close' and '__del__' methods. -- components: Documentation messages: 55981 nosy: dangyogi severity: minor status: open title: new generator methods not documented in Library Reference type: rfe versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1174 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1082] platform system may be Windows or Microsoft since Vista
Changes by Sean Reifschneider: -- versions: +Python 2.6 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1082 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1014] cgi: parse_qs and parse_qsl misbehave on empty strings
Senthil added the comment: Hi Sean, This is a very minor issue (IMO) with Python 2.4. Why did you assign it to gvanrossum? Makes me wonder at your assignments. Thanks, Senthil __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1014 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1173] yield expressions not documented in Language Reference
Changes by Bruce Frederiksen: -- components: Documentation severity: minor status: open title: yield expressions not documented in Language Reference type: rfe versions: Python 2.5 __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1173 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1014] cgi: parse_qs and parse_qsl misbehave on empty strings
Guido van Rossum added the comment: I don't see what the problem is. You requested strict_parsing=True, and this is what strict parsing does. -- resolution: - wont fix status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1014 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1082] platform system may be Windows or Microsoft since Vista
Sean Reifschneider added the comment: Commited in trunk revision 58183 and 25-maint revision 58184. -- resolution: - accepted status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1082 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1727780] 64/32-bit issue when unpickling random.Random
Changes by Martin v. Löwis: -- keywords: +patch _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1727780 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1131] Reference Manual: for statement links to break statement
Sean Reifschneider added the comment: I don't know anything about the .chm file. Fred: Do you know where this comes from? -- assignee: jafo - fdrake nosy: +fdrake status: pending - open __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1131 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1686386] Python SEGFAULT on tuple.__repr__ and str()
Changes by Brett Cannon: -- status: pending - open _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1686386 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1149] fdopen does not work as expected
Sean Reifschneider added the comment: I do not believe this is a Python problem but instead a problem with your code. I believe the problem is likely that you still have a copy of the stdout is open, the fork that is reading also gets associated with that same file. I can't point you at any specific references, but you should check Posix references or possibly other sources for more information about side-effects such as this. These interactions, I have found, can be pretty subtle, so you may need to spend some time on getting everything right. -- nosy: +jafo resolution: - invalid status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1149 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1141] reading large files
Sean Reifschneider added the comment: I'm closing this because the slow I/O issue is known and expected to be resolved as part of the Python 3.0 development. The Windows problems with missing lines should be opened as a separate issue. -- nosy: +jafo resolution: - duplicate status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1141 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1727780] 64/32-bit issue when unpickling random.Random
Shawn Ligocki added the comment: Yep, tested it on a 64-bit machine and 2 32-bit machines and back and forth between them. It seems to resolve the problem. _ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1727780 _ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1155] Carbon.CF memory management problem
Changes by Sean Reifschneider: -- priority: - normal __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1155 __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
