Mailman 3 January 2010 - Python-Dev

Data descriptor doc/implementation inconsistency
by Benjamin Peterson 12 Jan '10

12 Jan '10

Consider this program: class Descr(object): def __init__(self, name): self.name = name def __set__(self, instance, what): instance.__dict__[self.name] = what class X(object): attr = Descr("attr") x = X() print(x.attr) x.attr = 42 print(x.attr) It gives in output: <__main__.Descr object at 0x7fe1c9b28150> 42 The documentation [1] says that Descr is a data descriptor because it defines the __set__ method. It also states that data descriptors always override the value in the instance dictionary. So, the second line should also be the descriptor object according to the documentation. My question is: Is this a doc bug or a implementation bug? If the former, it will be the description of a data descriptor much less consistent, since it will require that a __get__ method be present, too. If the latter, the fix may break some programs relying on the ability to "cache" a value in the instance dictionary. [1] http://docs.python.org/reference/datamodel#invoking-descriptors -- Regards, Benjamin

4 5

Improve open() to support reading file starting with an unicode BOM
by Victor Stinner 11 Jan '10

11 Jan '10

Hi, Builtin open() function is unable to open an UTF-16/32 file starting with a BOM if the encoding is not specified (raise an unicode error). For an UTF-8 file starting with a BOM, read()/readline() returns also the BOM whereas the BOM should be "ignored". See recent issues related to reading an UTF-8 text file including a BOM: #7185 (csv) and #7519 (ConfigParser). Such file can be opened in unicode mode with the UTF-8-SIG encoding, but it's possible to do better. I propose to improve open() (TextIOWrapper) by using the BOM to choose the right encoding. I think that only files opened in read only mode should support this new feature. *Read* the BOM in a *write* only file would cause unexpected behaviours. Since my proposition changes the result TextIOWrapper.read()/readline() for files starting with a BOM, we might introduce an option to open() to enable the new behaviour. But is it really needed to keep the backward compatibility? I wrote a proof of concept attached to the issue #7651. My patch only changes the behaviour of TextIOWrapper for reading files starting with a BOM. It doesn't work yet if a seek() is used before the first read. -- Victor Stinner http://www.haypocalc.com/

17 56

Re: [Python-Dev] Data descriptor doc/implementation inconsistency
by Łukasz Rekucki 10 Jan '10

10 Jan '10

> Date: Mon, 11 Jan 2010 01:51:09 +0100 > From: "Amaury Forgeot d'Arc" <amauryfa(a)gmail.com> > To: Benjamin Peterson <benjamin(a)python.org> > Cc: Python Dev <python-dev(a)python.org> > Subject: Re: [Python-Dev] Data descriptor doc/implementation > inconsistency > Message-ID: > <e27efe131001101651y68e1da25je2a8d02f5c62ef19(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi, > > 2010/1/11 Benjamin Peterson <benjamin(a)python.org>: >> Consider this program: >> >> class Descr(object): >> ? ?def __init__(self, name): >> ? ? ? ?self.name = name >> ? ?def __set__(self, instance, what): >> ? ? ? ?instance.__dict__[self.name] = what >> >> class X(object): >> ? ?attr = Descr("attr") >> >> x = X() >> print(x.attr) >> x.attr = 42 >> print(x.attr) >> >> It gives in output: >> >> <__main__.Descr object at 0x7fe1c9b28150> >> 42 >> >> The documentation [1] says that Descr is a data descriptor because it >> defines the __set__ method. It also states that data descriptors >> always override the value in the instance dictionary. So, the second >> line should also be the descriptor object according to the >> documentation. >> >> My question is: Is this a doc bug or a implementation bug? If the >> former, it will be the description of a data descriptor much less >> consistent, since it will require that a __get__ method be present, >> too. If the latter, the fix may break some programs relying on the >> ability to "cache" a value in the instance dictionary. >> >> [1] http://docs.python.org/reference/datamodel#invoking-descriptors > > Quoting the documentation: > """Normally, data descriptors define both __get__() and __set__(), > while non-data descriptors have just the __get__() method. > """ > Your example is neither a data descriptor nor a non-data descriptor... Actually, there is this footnote [1]: """ A descriptor can define any combination of __get__(), __set__() and __delete__(). If it does not define __get__(), then accessing the attribute even on an instance will return the descriptor object itself. If the descriptor defines __set__() and/or __delete__(), it is a data descriptor; if it defines neither, it is a non-data descriptor. """ Which would mean Descr is actually a data descriptor without a __get__(), so x.attr should always return the descriptor object itself (at least in the docs). > The thing that worries me a bit is the "x.attr" returning the Descr > object. Descriptors should remain at the class level, and instance > should only see values. I'd prefer an AttributeError in this case. > > -- > Amaury Forgeot d'Arc [1] http://docs.python.org/reference/datamodel#id7 -- Lukasz Rekucki

1 0

Fwd: [Python-checkins] r77402 - in python/trunk: Doc/library/warnings.rst Lib/test/test_ascii_formatd.py Lib/test/test_exceptions.py Lib/warnings.py Misc/NEWS Python/_warnings.c
by Brett Cannon 10 Jan '10

10 Jan '10

Nick Coghlan thought I should forward this to python-dev so people are aware of this change and why it occurred (plus it indirectly informs Guido I finally finished the work). ---------- Forwarded message ---------- From: brett.cannon <python-checkins(a)python.org> Date: Sat, Jan 9, 2010 at 18:56 Subject: [Python-checkins] r77402 - in python/trunk: Doc/library/warnings.rst Lib/test/test_ascii_formatd.py Lib/test/test_exceptions.py Lib/warnings.py Misc/NEWS Python/_warnings.c To: python-checkins(a)python.org Author: brett.cannon Date: Sun Jan 10 03:56:19 2010 New Revision: 77402 Log: DeprecationWarning is now silent by default. This was originally suggested by Guido, discussed on the stdlib-sig mailing list, and given the OK by Guido directly to me. What this change essentially means is that Python has taken a policy of silencing warnings that are only of interest to developers by default. This should prevent users from seeing warnings which are triggered by an application being run against a new interpreter before the app developer has a chance to update their code. Closes issue #7319. Thanks to Antoine Pitrou, Ezio Melotti, and Brian Curtin for helping with the issue. Modified: python/trunk/Doc/library/warnings.rst python/trunk/Lib/test/test_ascii_formatd.py python/trunk/Lib/test/test_exceptions.py python/trunk/Lib/warnings.py python/trunk/Misc/NEWS python/trunk/Python/_warnings.c Modified: python/trunk/Doc/library/warnings.rst ============================================================================== --- python/trunk/Doc/library/warnings.rst (original) +++ python/trunk/Doc/library/warnings.rst Sun Jan 10 03:56:19 2010 @@ -59,7 +59,7 @@ | :exc:`UserWarning` | The default category for :func:`warn`. | +----------------------------------+-----------------------------------------------+ | :exc:`DeprecationWarning` | Base category for warnings about deprecated | -| | features. | +| | features (ignored by default). | +----------------------------------+-----------------------------------------------+ | :exc:`SyntaxWarning` | Base category for warnings about dubious | | | syntactic features. | @@ -89,6 +89,9 @@ standard warning categories. A warning category must always be a subclass of the :exc:`Warning` class. +.. versionchanged:: 2.7 + :exc:`DeprecationWarning` is ignored by default. + .. _warning-filter: @@ -148,14 +151,6 @@ :mod:`warnings` module parses these when it is first imported (invalid options are ignored, after printing a message to ``sys.stderr``). -The warnings that are ignored by default may be enabled by passing :option:`-Wd` -to the interpreter. This enables default handling for all warnings, including -those that are normally ignored by default. This is particular useful for -enabling ImportWarning when debugging problems importing a developed package. -ImportWarning can also be enabled explicitly in Python code using:: - - warnings.simplefilter('default', ImportWarning) - .. _warning-suppress: @@ -226,6 +221,37 @@ entries from the warnings list before each new operation). +Updating Code For New Versions of Python +---------------------------------------- + +Warnings that are only of interest to the developer are ignored by default. As +such you should make sure to test your code with typically ignored warnings +made visible. You can do this from the command-line by passing :option:`-Wd` +to the interpreter (this is shorthand for :option:`-W default`). This enables +default handling for all warnings, including those that are ignored by default. +To change what action is taken for encountered warnings you simply change what +argument is passed to :option:`-W`, e.g. :option:`-W error`. See the +:option:`-W` flag for more details on what is possible. + +To programmatically do the same as :option:`-Wd`, use:: + + warnings.simplefilter('default') + +Make sure to execute this code as soon as possible. This prevents the +registering of what warnings have been raised from unexpectedly influencing how +future warnings are treated. + +Having certain warnings ignored by default is done to prevent a user from +seeing warnings that are only of interest to the developer. As you do not +necessarily have control over what interpreter a user uses to run their code, +it is possible that a new version of Python will be released between your +release cycles. The new interpreter release could trigger new warnings in your +code that were not there in an older interpreter, e.g. +:exc:`DeprecationWarning` for a module that you are using. While you as a +developer want to be notified that your code is using a deprecated module, to a +user this information is essentially noise and provides no benefit to them. + + .. _warning-functions: Available Functions Modified: python/trunk/Lib/test/test_ascii_formatd.py ============================================================================== --- python/trunk/Lib/test/test_ascii_formatd.py (original) +++ python/trunk/Lib/test/test_ascii_formatd.py Sun Jan 10 03:56:19 2010 @@ -4,6 +4,7 @@ import unittest from test_support import check_warnings, run_unittest, cpython_only +import warnings class FormatDeprecationTests(unittest.TestCase): @@ -17,6 +18,7 @@ buf = create_string_buffer(' ' * 100) with check_warnings() as w: + warnings.simplefilter('default') PyOS_ascii_formatd(byref(buf), sizeof(buf), '%+.10f', c_double(10.0)) self.assertEqual(buf.value, '+10.0000000000') Modified: python/trunk/Lib/test/test_exceptions.py ============================================================================== --- python/trunk/Lib/test/test_exceptions.py (original) +++ python/trunk/Lib/test/test_exceptions.py Sun Jan 10 03:56:19 2010 @@ -309,6 +309,7 @@ # BaseException.__init__ triggers a deprecation warning. exc = BaseException("foo") with warnings.catch_warnings(record=True) as w: + warnings.simplefilter('default') self.assertEquals(exc.message, "foo") self.assertEquals(len(w), 1) self.assertEquals(w[0].category, DeprecationWarning) Modified: python/trunk/Lib/warnings.py ============================================================================== --- python/trunk/Lib/warnings.py (original) +++ python/trunk/Lib/warnings.py Sun Jan 10 03:56:19 2010 @@ -383,8 +383,8 @@ # Module initialization _processoptions(sys.warnoptions) if not _warnings_defaults: - simplefilter("ignore", category=PendingDeprecationWarning, append=1) - simplefilter("ignore", category=ImportWarning, append=1) + for cls in (DeprecationWarning, PendingDeprecationWarning, ImportWarning): + simplefilter("ignore", category=cls, append=True) bytes_warning = sys.flags.bytes_warning if bytes_warning > 1: bytes_action = "error" Modified: python/trunk/Misc/NEWS ============================================================================== --- python/trunk/Misc/NEWS (original) +++ python/trunk/Misc/NEWS Sun Jan 10 03:56:19 2010 @@ -12,6 +12,8 @@ Core and Builtins ----------------- +- Issue #7319: Silence DeprecationWarning by default. + - Issue #2335: Backport set literals syntax from Python 3.x. Library Modified: python/trunk/Python/_warnings.c ============================================================================== --- python/trunk/Python/_warnings.c (original) +++ python/trunk/Python/_warnings.c Sun Jan 10 03:56:19 2010 @@ -85,10 +85,10 @@ default_action = get_warnings_attr("defaultaction"); if (default_action == NULL) { - if (PyErr_Occurred()) { - return NULL; - } - return _default_action; + if (PyErr_Occurred()) { + return NULL; + } + return _default_action; } Py_DECREF(_default_action); @@ -202,12 +202,12 @@ mod_str = PyString_AsString(filename); if (mod_str == NULL) - return NULL; + return NULL; len = PyString_Size(filename); if (len < 0) return NULL; if (len >= 3 && - strncmp(mod_str + (len - 3), ".py", 3) == 0) { + strncmp(mod_str + (len - 3), ".py", 3) == 0) { module = PyString_FromStringAndSize(mod_str, len-3); } else { @@ -251,7 +251,7 @@ name = PyObject_GetAttrString(category, "__name__"); if (name == NULL) /* XXX Can an object lack a '__name__' attribute? */ - return; + return; f_stderr = PySys_GetObject("stderr"); if (f_stderr == NULL) { @@ -341,7 +341,7 @@ rc = already_warned(registry, key, 0); if (rc == -1) goto cleanup; - else if (rc == 1) + else if (rc == 1) goto return_none; /* Else this warning hasn't been generated before. */ } @@ -492,9 +492,9 @@ /* Setup filename. */ *filename = PyDict_GetItemString(globals, "__file__"); if (*filename != NULL) { - Py_ssize_t len = PyString_Size(*filename); + Py_ssize_t len = PyString_Size(*filename); const char *file_str = PyString_AsString(*filename); - if (file_str == NULL || (len < 0 && PyErr_Occurred())) + if (file_str == NULL || (len < 0 && PyErr_Occurred())) goto handle_error; /* if filename.lower().endswith((".pyc", ".pyo")): */ @@ -506,10 +506,10 @@ tolower(file_str[len-1]) == 'o')) { *filename = PyString_FromStringAndSize(file_str, len-1); - if (*filename == NULL) - goto handle_error; - } - else + if (*filename == NULL) + goto handle_error; + } + else Py_INCREF(*filename); } else { @@ -536,8 +536,8 @@ else { /* embedded interpreters don't have sys.argv, see bug #839151 */ *filename = PyString_FromString("__main__"); - if (*filename == NULL) - goto handle_error; + if (*filename == NULL) + goto handle_error; } } if (*filename == NULL) { @@ -839,26 +839,29 @@ static PyObject * init_filters(void) { - PyObject *filters = PyList_New(3); + PyObject *filters = PyList_New(4); const char *bytes_action; if (filters == NULL) return NULL; PyList_SET_ITEM(filters, 0, + create_filter(PyExc_DeprecationWarning, "ignore")); + PyList_SET_ITEM(filters, 1, create_filter(PyExc_PendingDeprecationWarning, "ignore")); - PyList_SET_ITEM(filters, 1, create_filter(PyExc_ImportWarning, "ignore")); + PyList_SET_ITEM(filters, 2, create_filter(PyExc_ImportWarning, "ignore")); if (Py_BytesWarningFlag > 1) bytes_action = "error"; else if (Py_BytesWarningFlag) bytes_action = "default"; else bytes_action = "ignore"; - PyList_SET_ITEM(filters, 2, create_filter(PyExc_BytesWarning, + PyList_SET_ITEM(filters, 3, create_filter(PyExc_BytesWarning, bytes_action)); if (PyList_GET_ITEM(filters, 0) == NULL || PyList_GET_ITEM(filters, 1) == NULL || - PyList_GET_ITEM(filters, 2) == NULL) { + PyList_GET_ITEM(filters, 2) == NULL || + PyList_GET_ITEM(filters, 3) == NULL) { Py_DECREF(filters); return NULL; } _______________________________________________ Python-checkins mailing list Python-checkins(a)python.org http://mail.python.org/mailman/listinfo/python-checkins

3 2

Re: [Python-Dev] Improve open() to support reading file starting with an unicode BOM
by Henning von Bargen 10 Jan '10

10 Jan '10

If Python should support BOM when reading text files, it should also be able to *write* such files. An encoding="BOM" argument wouldn't help here, because it does not specify which encoding to use actually: UFT-8, UTF-16-LE or what? That would be a point against encoding="BOM" and pro an additional keyword argument "use_bom" or whatever with the following values: None: default (old) behaviour: don't handle BOM at all True: reading: expect BOM (raising an exception if it's missing). The encoding argument must be None or it must match the encoding implied by the BOM writing: write a BOM. The encoding argument must be one of the UTF encodings. False: reading: If a BOM is present, use it to determine the file encoding. The encoding argument must be None or it must match the encoding implied by the BOM. (*) Otherwise, use the encoding argument to determine the encoding. writing: do not write a BOM. Use the encoding argument. (*) This is a question of taste. I think some people would prefer a fourth value "AUTO" instead, or to swap the behaviour of None and False. Henning P.S. To make things worse, I have sometimes seen XML files with a UTF-8 BOM, but an XML encoding declaration of "iso-8859-1". For such files, whatever you guess will be wrong anyway...

2 1

Unladen cPickle speedups in 2.7 & 3.1
by skip＠pobox.com 09 Jan '10

09 Jan '10

How much of the Unladen Swallow cPickle speedups have been incorporated into 2.7 & 3.1? I'm working on trying to develop patches for 2.4 and 2.6 (the two versions I currently care about at work - we will skip 2.5 entirely). It appears some of their speedups may have already been merged to trunk, but I'm not sure how much. If a patch to merge this to 2.7 is already under consideration I won't look at it, but I interpreted Collin Winter's response to my query on the u-s mailing list that not everything has been done yet. Thx, Skip

3 4

Quick sum up about open() + BOM
by Victor Stinner 09 Jan '10

09 Jan '10

Hi, Thanks for all the answers! I will try to sum up all ideas here. (1) Change default open() behaviour or make it optional? Guido would like to add an option and keep open() unchanged. He wrote that checking for BOM and using system locale are too much different to be the same option (encoding=None). Antoine would like to check BOM by default, because both options (system locale vs checking for BOM) is the same thing. About Antoine choice (encoding=None): which file modes would check for a BOM? I would like to answer only the read only mode, but then open(filename, "r") and open(filename, "r+") would behave differently? => 1 point for Guido (encoding="BOM" is more explicit) Antoine choice has the advantage of directly support UTF-8+BOM, UTF-16 and UTF-32 for all applications and all modules using open(filename). => 1 point for Antoine (2) Check for a BOM while reading or detect it before? Everybody agree that checking BOM is an interesting option and should not be limited to open(). Marc-Andre proposed a codecs.guess_file_encoding() function accepting a file name or a binary file-like object: it returns the encoding and seek to the file start or just after the BOM. I dislike this function because it requires extra file operations (open (optional), read() and seek()) and it doesn't work if the file is not seekable (eg. a pipe). I prefer to check for a BOM at first read in TextIOWrapper to avoid extra file operations. Note: I implemented the BOM check in TextIOWrapper; so it's already usable for any file-like object. (3) tell() and seek() on a text file starting with a BOM To be consistent with Antoine example: >>> bio = io.BytesIO(b'\xff\xfea\x00b\x00') >>> f = io.TextIOWrapper(bio, encoding='utf-16') >>> f.read() 'ab' >>> f.seek(0) 0 >>> f.read() 'ab' TextIOWrapper: * tell() should return zero at file start, * seek(0) should go be to file start, * and the BOM should always be "ignored". I mean: with open("utf8bom.txt", encoding="BOM") as fp: assert fp.tell() == 0 text = fp.read() # no BOM here fp.seek(0) assert fp.read() == text -- About my patch: - BOM check is explicit: open(filebame, encoding="BOM") - tell() / seek(0) works as expected - BOM bytes are always skipped in read() / readlines() result Hum, I don't know if this email can be called a sum up ;-) -- Victor Stinner http://www.haypocalc.com/

9 13

--enabled-shared broken on freebsd5?
by Nicholas Bastin 08 Jan '10

08 Jan '10

(This may occur on more platforms - I can test on more unix platforms if the consensus is this is an actual problem and I'm not just a nut) On freebsd5, if you do a simple ./configure --enable-shared in current (2.7) trunk, your python shared library will build properly, but all modules will fail to find the shared library and thus fail to build: gcc -shared build/temp.freebsd-5.3-RELEASE-i386-2.7/u1/Python/Python-2.7a1/Modules/_struct.o -L/u1/tmp/python2.7a1/lib -L/usr/local/lib -lpython2.7 -o build/lib.freebsd-5.3-RELEASE-i386-2.7/_struct.so /usr/bin/ld: cannot find -lpython2.7 building '_ctypes_test' extension ... This of course is because libpython2.7.so is in the current directory and not (yet) installed in /usr/local/lib. I've made a very simple fix for this problem that works, but at least to me smells a bit funny, which is to modify setup.py to add the following to detect_modules(): # If we did --enable-shared, we need to be able to find the library # we just built in order to build the modules. if platform == 'freebsd5': add_dir_to_list(self.compiler_obj.library_dirs, '.') Which brings me to a few questions: a) Does this seem like a real problem, or am I missing something obvious? b) Does this fix seem like the sensible thing to do? (it seems at least that we ought to check that the user configured --enable-shared and only set -L. in that case, if that's possible) Setting --enable-shared when you actually have a libpython2.7.so in /usr/local/lib (or whatever --prefix you've selected) is possibly even more dangerous, because it may succeed in linking against a differently-built library than what you intended. -- Nick

4 7

relation between Python.asdl and Tools/compiler/ast.txt
by Yoann Padioleau 08 Jan '10

08 Jan '10

Hi, I would like to use astgen.py to generate python classes corresponding to the AST of something I have defined in a .asdl file, along the line of what is apparently done for the python AST itself. I thought astgen.py would take as an argument a .asdl file, but apparently it instead process a file called ast.txt. Where does this file come from ? Is it generated from Python.asdl ?

2 5

Summary of Python tracker Issues
by Python tracker 08 Jan '10

08 Jan '10

ACTIVITY SUMMARY (01/01/10 - 01/08/10) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue number. Do NOT respond to this message. 2544 open (+27) / 16937 closed (+15) / 19481 total (+42) Open issues with patches: 1017 Average duration of open issues: 708 days. Median duration of open issues: 464 days. Open Issues Breakdown open 2509 (+27) pending 34 ( +0) Issues Created Or Reopened (43) _______________________________ Extended slicing with classic class behaves strangely 01/07/10 http://bugs.python.org/issue7532 reopened mark.dickinson patch optparse library documentation has an insignificant formatting i 01/01/10 CLOSED http://bugs.python.org/issue7618 created vazovsky patch imaplib shouldn't use cause DeprecationWarnings in 2.6 01/01/10 CLOSED http://bugs.python.org/issue7619 created djc Vim syntax highlight 01/02/10 http://bugs.python.org/issue7620 created july patch Test issue 01/02/10 CLOSED http://bugs.python.org/issue7621 created georg.brandl [patch] improve unicode methods: split() rsplit() and replace() 01/03/10 http://bugs.python.org/issue7622 created flox patch PropertyType missing in Lib/types.py 01/03/10 CLOSED http://bugs.python.org/issue7623 created wplappert isinstance(... ,collections.Callable) fails with oldstyle class 01/03/10 http://bugs.python.org/issue7624 created rgammans bytearray needs more tests for "b.some_method()[0] is not b" 01/03/10 http://bugs.python.org/issue7625 created flox patch Entity references without semicolon in HTMLParser 01/03/10 CLOSED http://bugs.python.org/issue7626 created stefan.schweizer mailbox.MH.remove() lock handling is broken 01/04/10 http://bugs.python.org/issue7627 created sraustein round() doesn't work correctly in 3.1.1 01/04/10 CLOSED http://bugs.python.org/issue7628 created bkovt Compiling with mingw32 gcc, content of variable "extra_postargs" 01/04/10 CLOSED http://bugs.python.org/issue7629 created popelkopp Strange behaviour of decimal.Decimal 01/04/10 CLOSED http://bugs.python.org/issue7630 created parmax undefined label: bltin-file-objects 01/04/10 CLOSED http://bugs.python.org/issue7631 created ezio.melotti dtoa.c: oversize b in quorem 01/04/10 http://bugs.python.org/issue7632 created skrah decimal.py: type conversion in context methods 01/04/10 http://bugs.python.org/issue7633 created skrah patch, easy next/previous links in documentation skip some sections 01/05/10 CLOSED http://bugs.python.org/issue7634 created gagenellina 19.6 xml.dom.pulldom doc: stub? 01/05/10 http://bugs.python.org/issue7635 created tjreedy Add a set update action to optparse 01/05/10 CLOSED http://bugs.python.org/issue7636 created hardkrash patch Improve 19.5. xml.dom.minidom doc 01/05/10 http://bugs.python.org/issue7637 created tjreedy Counterintuitive str.splitlines() inconsistency. 01/05/10 CLOSED http://bugs.python.org/issue7638 created vencabot_teppoo bdist_msi fails on files with long names 01/05/10 http://bugs.python.org/issue7639 created mmm77 buffered io seek() buggy 01/05/10 http://bugs.python.org/issue7640 created pakal patch Built-in Formatter accepts undocumented presentation type 01/06/10 CLOSED http://bugs.python.org/issue7641 created lrekucki [patch] Minor improvement in os.system doc 01/06/10 http://bugs.python.org/issue7642 created Val patch What is an ASCII linebreak? 01/06/10 http://bugs.python.org/issue7643 created flox bug in nntplib.body() method with possible fix 01/06/10 http://bugs.python.org/issue7644 created mdmullins easy test_distutils fails on Windows XP 01/06/10 http://bugs.python.org/issue7645 created austin987 test_telnetlib fails in Windows XP 01/06/10 http://bugs.python.org/issue7646 created austin987 Add statvfs flags to the posix module 01/06/10 http://bugs.python.org/issue7647 created ajax(a)redhat.com patch test_urllib2 fails on Windows if not run from C: 01/06/10 http://bugs.python.org/issue7648 created austin987 easy "u'%c' % char" broken for chars in range '\x80'-'\xFF' 01/07/10 http://bugs.python.org/issue7649 created ezio.melotti patch, easy test_uuid is invalid 01/07/10 http://bugs.python.org/issue7650 created austin987 Python3: guess text file charset using the BOM 01/07/10 http://bugs.python.org/issue7651 created haypo patch Merge C version of decimal into py3k. 01/07/10 http://bugs.python.org/issue7652 created mark.dickinson Fix description of the way the PythonPath Windows registry key w 01/07/10 CLOSED http://bugs.python.org/issue7653 created BoarGules patch, needs review [patch] Enable additional bytes and memoryview tests. 01/07/10 http://bugs.python.org/issue7654 created flox patch PEP 374 Title usage & script redirection typo fixes 01/07/10 CLOSED http://bugs.python.org/issue7655 created bab9e9 patch test_hashlib fails on some installations (specifically Neal's re 01/08/10 http://bugs.python.org/issue7656 created r.david.murray test_ctypes failure on AIX 5.3 01/08/10 http://bugs.python.org/issue7657 created mallayya patch OS X pythonw.c compile error with 10.4 or earlier deployment tar 01/08/10 http://bugs.python.org/issue7658 created ned.deily Problems with attribute assignment on object instances 01/08/10 http://bugs.python.org/issue7659 created pakal Issues Now Closed (40) ______________________ shutil fails when copying to NTFS in Linux 762 days http://bugs.python.org/issue1545 benjamin.peterson patch Test 751 days http://bugs.python.org/issue1619 georg.brandl Windows Registry issue with 2.5.2 AMD64 msi 645 days http://bugs.python.org/issue2539 loewis Extension module build fails for MinGW: missing vcvarsall.bat 618 days http://bugs.python.org/issue2698 Daniel26 optparse print_usage(),.. methods are not documented 542 days http://bugs.python.org/issue3340 ezio.melotti reference leaks in test_distutils 500 days http://bugs.python.org/issue3660 ezio.melotti patch _sha256 et al. encode to UTF-8 by default 20 days http://bugs.python.org/issue3745 lemburg 26backport Add Option to Bind to a Local IP Address in httplib.py 464 days http://bugs.python.org/issue3972 gregory.p.smith patch, easy no reference for optparse methods 388 days http://bugs.python.org/issue4635 ezio.melotti PyArg_Parse* should raise TypeError for float parsed with intege 339 days http://bugs.python.org/issue5080 mark.dickinson patch Don't use PyLong_SHIFT with _PyLong_AsScaledDouble() 282 days http://bugs.python.org/issue5576 mark.dickinson patch PyFrame_GetLineNumber 244 days http://bugs.python.org/issue5954 georg.brandl patch PyCode_NewEmpty 244 days http://bugs.python.org/issue5959 georg.brandl patch Add non-command help topics to help completion of cmd.Cmd 241 days http://bugs.python.org/issue5991 georg.brandl patch make error 231 days http://bugs.python.org/issue6067 georg.brandl no longer possible to hash arrays 229 days http://bugs.python.org/issue6071 benjamin.peterson patch zipfile: Invalid argument when opening zero-sized files 173 days http://bugs.python.org/issue6511 r.david.murray use different mechanism for pythonw on osx 127 days http://bugs.python.org/issue6834 ned.deily easy Py3k doc: "from __future__ import division" not necessary 32 days http://bugs.python.org/issue7432 ezio.melotti cPickle: stack underflow in load_pop() 31 days http://bugs.python.org/issue7455 pitrou patch crash in str.rfind() with an invalid start value 25 days http://bugs.python.org/issue7458 pitrou patch Implement fastsearch algorithm for rfind/rindex 26 days http://bugs.python.org/issue7462 ezio.melotti patch GZipFile.readline too slow 20 days http://bugs.python.org/issue7471 pitrou patch ssl module documentation: SSLSocket.unwrap description shown twi 5 days http://bugs.python.org/issue7592 georg.brandl Installation - 2 tests failed: test_cmd_line test_xmlrpc 7 days http://bugs.python.org/issue7601 ezio.melotti optparse library documentation has an insignificant formatting i 2 days http://bugs.python.org/issue7618 ezio.melotti patch imaplib shouldn't use cause DeprecationWarnings in 2.6 1 days http://bugs.python.org/issue7619 djc Test issue 0 days http://bugs.python.org/issue7621 ezio.melotti PropertyType missing in Lib/types.py 0 days http://bugs.python.org/issue7623 benjamin.peterson Entity references without semicolon in HTMLParser 2 days http://bugs.python.org/issue7626 r.david.murray round() doesn't work correctly in 3.1.1 0 days http://bugs.python.org/issue7628 benjamin.peterson Compiling with mingw32 gcc, content of variable "extra_postargs" 0 days http://bugs.python.org/issue7629 r.david.murray Strange behaviour of decimal.Decimal 0 days http://bugs.python.org/issue7630 mark.dickinson undefined label: bltin-file-objects 0 days http://bugs.python.org/issue7631 pitrou next/previous links in documentation skip some sections 0 days http://bugs.python.org/issue7634 georg.brandl Add a set update action to optparse 3 days http://bugs.python.org/issue7636 r.david.murray patch Counterintuitive str.splitlines() inconsistency. 0 days http://bugs.python.org/issue7638 flox Built-in Formatter accepts undocumented presentation type 0 days http://bugs.python.org/issue7641 eric.smith Fix description of the way the PythonPath Windows registry key w 0 days http://bugs.python.org/issue7653 r.david.murray patch, needs review PEP 374 Title usage & script redirection typo fixes 0 days http://bugs.python.org/issue7655 georg.brandl patch Top Issues Most Discussed (10) ______________________________ 22 [patch] improve unicode methods: split() rsplit() and replace() 5 days open http://bugs.python.org/issue7622 14 Test suite emits many DeprecationWarnings when -3 is enabled 91 days open http://bugs.python.org/issue7092 13 unicode_escape codec does not escape quotes 8 days open http://bugs.python.org/issue7615 8 OS X pythonw.c compile error with 10.4 or earlier deployment ta 0 days open http://bugs.python.org/issue7658 8 Merge C version of decimal into py3k. 1 days open http://bugs.python.org/issue7652 8 "u'%c' % char" broken for chars in range '\x80'-'\xFF' 2 days open http://bugs.python.org/issue7649 8 decimal.py: type conversion in context methods 4 days open http://bugs.python.org/issue7633 8 Patch for [ 735515 ] urllib2 should cache 301 redir 906 days open http://bugs.python.org/issue1755841 7 Test issue 0 days closed http://bugs.python.org/issue7621 7 Cannot use both read and readline method in same ZipExtFile obj 8 days open http://bugs.python.org/issue7610

1 0