Python-Dev November 2015

python-dev@python.org

69 participants
47 discussions

congrats on 3.5! Alas, windows 7 users are having problems installing it

by Laura Creighton

webmaster has already heard from 4 people who cannot install it. I sent them to the bug tracker or to python-list but they seem not to have gone either place. Is there some guide I should be sending them to, 'how to debug installation problems'? Laura

1 year, 1 month

PEP 506 secrets module

by Steven D'Aprano

Hi, As extensively discussed on Python-Ideas, the secrets module and PEP 506 is (I hope) ready for pronouncement. https://www.python.org/dev/peps/pep-0506/ There is code and tests here: https://bitbucket.org/sdaprano/secrets or you can run hg clone https://sdaprano@bitbucket.org/sdaprano/secrets The code is written for and tested on Python 2.6, 2.7, 3.1 - 3.4. -- Steve

4 years, 6 months

Request for pronouncement on PEP 493 (HTTPS verification backport guidance)

by Nick Coghlan

Hi folks, I have a confession to make - I dropped the ball on the HTTPS verification backport proposals in PEP 493, and let the upstream and downstream approval processes get out of sequence. As a result, the RHEL 7.2 beta released back in September incorporates the HTTPS verification feature backport based on the current PEP 493 draft, even though that hasn't formally been pronounced as an Active recommendation by python-dev yet. Accordingly, I'm belatedly submitting it for pronouncement now: https://www.python.org/dev/peps/pep-0493/ There's currently no BDFL-Delegate assigned, so if Guido doesn't want to handle it, we'll need to address that question first. Our last discussion back in July seemed to show that folks either didn't care about the question (because they're using unmodified upstream versions so the PEP didn't affect them), or else thought the approach described in the PEP was reasonable, so I'm hoping the consequences of my mistake won't be too severe. Regards, Nick. P.S. I'm aware that this looks like presenting a fait accompli at a point where it's too late to realistically say "No", but the truth is that preparation for the Python in Education miniconf at PyCon Australia ramped up immediately after the July discussion, and then I personally got confused as to the scope of what was being included in 7.2 (I mistakenly thought it was just PEP 466 for now, with 476+493 being deferred to a later release, but it's actually the whole package of 466+476+493). That's my fault for trying to keep track of too many things at once (and thus failing at some of them), not anyone else's. ================================ PEP: 493 Title: HTTPS verification recommendations for Python 2.7 redistributors Version: $Revision$ Last-Modified: $Date$ Author: Nick Coghlan <ncoghlan(a)gmail.com>, Robert Kuska <rkuska(a)redhat.com>, Marc-André Lemburg <mal(a)lemburg.com> Status: Draft Type: Informational Content-Type: text/x-rst Created: 10-May-2015 Post-History: 06-Jul-2015 Abstract ======== PEP 476 updated Python's default handling of HTTPS certificates to be appropriate for communication over the public internet. The Python 2.7 long term maintenance series was judged to be in scope for this change, with the new behaviour introduced in the Python 2.7.9 maintenance release. This PEP provides recommendations to downstream redistributors wishing to provide a smoother migration experience when helping their users to manage this change in Python's default behaviour. Rationale ========= PEP 476 changed Python's default behaviour to better match the needs and expectations of developers operating over the public internet, a category which appears to include most new Python developers. It is the position of the authors of this PEP that this was a correct decision. However, it is also the case that this change *does* cause problems for infrastructure administrators operating private intranets that rely on self-signed certificates, or otherwise encounter problems with the new default certificate verification settings. The long term answer for such environments is to update their internal certificate management to at least match the standards set by the public internet, but in the meantime, it is desirable to offer these administrators a way to continue receiving maintenance updates to the Python 2.7 series, without having to gate that on upgrades to their certificate management infrastructure. PEP 476 did attempt to address this question, by covering how to revert the new settings process wide by monkeypatching the ``ssl`` module to restore the old behaviour. Unfortunately, the ``sitecustomize.py`` based technique proposed to allow system administrators to disable the feature by default in their Standard Operating Environment definition has been determined to be insufficient in at least some cases. The specific case of interest to the authors of this PEP is the one where a Linux distributor aims to provide their users with a `smoother migration path <https://bugzilla.redhat.com/show_bug.cgi?id=1173041>`__ than the standard one provided by consuming upstream CPython 2.7 releases directly, but other potential challenges have also been pointed out with updating embedded Python runtimes and other user level installations of Python. Rather than allowing a plethora of mutually incompatibile migration techniques to bloom, this PEP proposes two alternative approaches that redistributors may take when addressing these problems. Redistributors may choose to implement one, both, or neither of these approaches based on their assessment of the needs of their particular userbase. These designs are being proposed as a recommendation for redistributors, rather than as new upstream features, as they are needed purely to support legacy environments migrating from older versions of Python 2.7. Neither approach is being proposed as an upstream Python 2.7 feature, nor as a feature in any version of Python 3 (whether published directly by the Python Software Foundation or by a redistributor). Requirements for capability detection ===================================== As these recommendations are intended to cover backports to earlier Python versions, the Python version number cannot be used as a reliable means for detecting them. Instead, the recommendations are defined to allow the presence or absence of the feature to be determined using the following technique:: python -c "import ssl; ssl._relevant_attribute" This will fail with `AttributeError` (and hence a non-zero return code) if the relevant capability is not available. The marker attributes are prefixed with an underscore to indicate the implementation dependent nature of these capabilities - not all Python distributions will offer them, only those that are providing a multi-stage migration process from the legacy HTTPS handling to the new default behaviour. Recommendation for an environment variable based security downgrade =================================================================== Some redistributors may wish to provide a per-application option to disable certificate verification in selected applications that run on or embed CPython without needing to modify the application itself. In these cases, a configuration mechanism is needed that provides: * an opt-out model that allows certificate verification to be selectively turned off for particular applications after upgrading to a version of Python that verifies certificates by default * the ability for all users to configure this setting on a per-application basis, rather than on a per-system, or per-Python-installation basis This approach may be used for any redistributor provided version of Python 2.7, including those that advertise themselves as providing Python 2.7.9 or later. Required marker attribute ------------------------- The required marker attribute on the ``ssl`` module when implementing this recommendation is:: _https_verify_envvar = 'PYTHONHTTPSVERIFY' This not only makes it straightforward to detect the presence (or absence) of the capability, it also makes it possible to programmatically determine the relevant environment variable name. Recommended modifications to the Python standard library -------------------------------------------------------- The recommended approach to providing a per-application configuration setting for HTTPS certificate verification that doesn't require modifications to the application itself is to: * modify the ``ssl`` module to read the ``PYTHONHTTPSVERIFY`` environment variable when the module is first imported into a Python process * set the ``ssl._create_default_https_context`` function to be an alias for ``ssl._create_unverified_context`` if this environment variable is present and set to ``'0'`` * otherwise, set the ``ssl._create_default_https_context`` function to be an alias for ``ssl.create_default_context`` as usual Example implementation ---------------------- :: _https_verify_envvar = 'PYTHONHTTPSVERIFY' def _get_https_context_factory(): config_setting = os.environ.get(_https_verify_envvar) if config_setting == '0': return _create_unverified_context return create_default_context _create_default_https_context = _get_https_context_factory() Security Considerations ----------------------- Relative to an unmodified version of CPython 2.7.9 or later, this approach does introduce a new downgrade attack against the default security settings that potentially allows a sufficiently determined attacker to revert Python to the vulnerable configuration used in CPython 2.7.8 and earlier releases. However, such an attack requires the ability to modify the execution environment of a Python process prior to the import of the ``ssl`` module, and any attacker with such access would already be able to modify the behaviour of the underlying OpenSSL implementation. Recommendation for backporting to earlier Python versions ========================================================= Some redistributors, most notably Linux distributions, may choose to backport the PEP 476 HTTPS verification changes to modified Python versions based on earlier Python 2 maintenance releases. In these cases, a configuration mechanism is needed that provides: * an opt-in model that allows the decision to enable HTTPS certificate verification to be made independently of the decision to upgrade to the Python version where the feature was first backported * the ability for system administrators to set the default behaviour of Python applications and scripts run directly in the system Python installation * the ability for the redistributor to consider changing the default behaviour of *new* installations at some point in the future without impacting existing installations that have been explicitly configured to skip verifying HTTPS certificates by default This approach should not be used for any Python installation that advertises itself as providing Python 2.7.9 or later, as most Python users will have the reasonable expectation that all such environments will validate HTTPS certificates by default. Required marker attribute ------------------------- The required marker attribute on the ``ssl`` module when implementing this recommendation is:: _cert_verification_config = '<path to configuration file>' This not only makes it straightforward to detect the presence (or absence) of the capability, it also makes it possible to programmatically determine the relevant configuration file name. Recommended modifications to the Python standard library -------------------------------------------------------- The recommended approach to backporting the PEP 476 modifications to an earlier point release is to implement the following changes relative to the default PEP 476 behaviour implemented in Python 2.7.9+: * modify the ``ssl`` module to read a system wide configuration file when the module is first imported into a Python process * define a platform default behaviour (either verifying or not verifying HTTPS certificates) to be used if this configuration file is not present * support selection between the following three modes of operation: * ensure HTTPS certificate verification is enabled * ensure HTTPS certificate verification is disabled * delegate the decision to the redistributor providing this Python version * set the ``ssl._create_default_https_context`` function to be an alias for either ``ssl.create_default_context`` or ``ssl._create_unverified_context`` based on the given configuration setting. Recommended file location ------------------------- This approach is currently only defined for \*nix system Python installations. The recommended configuration file name is ``/etc/python/cert-verification.cfg``. The ``.cfg`` filename extension is recommended for consistency with the ``pyvenv.cfg`` used by the ``venv`` module in Python 3's standard library. Recommended file format ----------------------- The configuration file should use a ConfigParser ini-style format with a single section named ``[https]`` containing one required setting ``verify``. Permitted values for ``verify`` are: * ``enable``: ensure HTTPS certificate verification is enabled by default * ``disable``: ensure HTTPS certificate verification is disabled by default * ``platform_default``: delegate the decision to the redistributor providing this particular Python version If the ``[https]`` section or the ``verify`` setting are missing, or if the ``verify`` setting is set to an unknown value, it should be treated as if the configuration file is not present. Example implementation ---------------------- :: _cert_verification_config = '/etc/python/cert-verification.cfg' def _get_https_context_factory(): # Check for a system-wide override of the default behaviour context_factories = { 'enable': create_default_context, 'disable': _create_unverified_context, 'platform_default': _create_unverified_context, # For now :) } import ConfigParser config = ConfigParser.RawConfigParser() config.read(_cert_verification_config) try: verify_mode = config.get('https', 'verify') except (ConfigParser.NoSectionError, ConfigParser.NoOptionError): verify_mode = 'platform_default' default_factory = context_factories.get('platform_default') return context_factories.get(verify_mode, default_factory) _create_default_https_context = _get_https_context_factory() Security Considerations ----------------------- The specific recommendations for the backporting case are designed to work for privileged, security sensitive processes, even those being run in the following locked down configuration: * run from a locked down administrator controlled directory rather than a normal user directory (preventing ``sys.path[0]`` based privilege escalation attacks) * run using the ``-E`` switch (preventing ``PYTHON*`` environment variable based privilege escalation attacks) * run using the ``-s`` switch (preventing user site directory based privilege escalation attacks) * run using the ``-S`` switch (preventing ``sitecustomize`` based privilege escalation attacks) The intent is that the *only* reason HTTPS verification should be getting turned off system wide when using this approach is because: * an end user is running a redistributor provided version of CPython rather than running upstream CPython directly * that redistributor has decided to provide a smoother migration path to verifying HTTPS certificates by default than that being provided by the upstream project * either the redistributor or the local infrastructure administrator has determined that it is appropriate to override the default upstream behaviour (at least for the time being) Using an administrator controlled configuration file rather than an environment variable has the essential feature of providing a smoother migration path, even for applications being run with the ``-E`` switch. Combining the recommendations ============================= If a redistributor chooses to implement both recommendations, then the environment variable should take precedence over the system-wide configuration setting. This allows the setting to be changed for a given user, virtual environment or application, regardless of the system-wide default behaviour. In this case, if the ``PYTHONHTTPSVERIFY`` environment variable is defined, and set to anything *other* than ``'0'``, then HTTPS certificate verification should be enabled. Example implementation ---------------------- :: _https_verify_envvar = 'PYTHONHTTPSVERIFY' _cert_verification_config = '/etc/python/cert-verification.cfg' def _get_https_context_factory(): # Check for am environmental override of the default behaviour config_setting = os.environ.get(_https_verify_envvar) if config_setting is not None: if config_setting == '0': return _create_unverified_context return create_default_context # Check for a system-wide override of the default behaviour context_factories = { 'enable': create_default_context, 'disable': _create_unverified_context, 'platform_default': _create_unverified_context, # For now :) } import ConfigParser config = ConfigParser.RawConfigParser() config.read(_cert_verification_config) try: verify_mode = config.get('https', 'verify') except (ConfigParser.NoSectionError, ConfigParser.NoOptionError): verify_mode = 'platform_default' default_factory = context_factories.get('platform_default') return context_factories.get(verify_mode, default_factory) _create_default_https_context = _get_https_context_factory() Copyright ========= This document has been placed into the public domain. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

4 years, 10 months

Avoiding CPython performance regressions

by Fabio Zadrozny

Hi python-dev, I've seen that on and off CPython had attempts to measure benchmarks over time to avoid performance regressions (i.e.: https://speed.python.org), but had nothing concrete so far, so, I ended up creating a hosted service for that (https://www.speedtin.com) and I'd like to help in setting up a structure to run the benchmarks from https://hg.python.org/benchmarks/ and properly upload them to SpeedTin (if CPython devs are Ok with that) -- note that I don't really have server to run the benchmarks, only to host the data (but https://speed.python.org seems to indicate that such a server is available...). There's a sample report at: https://www.speedtin.com/reports/1_CPython27x_Performance_Over_Time/ (it has real data from running using the PyPy benchmarks as I only discovered about the benchmarks from https://hg.python.org/benchmarks/ later on -- also, it doesn't seem to support Python 3 right now, so, it's probably not that useful for the current Python dev, but it does have some nice insight on CPython 2.7.x performance over time). Later on, the idea is being able to compare across different Python implementations which use the same benchmark set... (although that needs other implementations to also post to the data to SpeedTin). Note that uploading the data to SpeedTin should be pretty straightforward (by using https://github.com/fabioz/pyspeedtin, so, the main issue would be setting up o machine to run the benchmarks). Best Regards, Fabio

4 years, 10 months

Deleting with setting C API functions

by Serhiy Storchaka

Slots like PyTypeObject.tp_setattr, PySequenceMethods.sq_ass_item, PyMappingMethods.mp_ass_subscript are used not only for setting attribute/item value, but also for deleting attribute/item (if value is NULL). This is not documented and should be. [1] Correspondingly public API functions like PyObject_SetAttr, PyObject_SetItem, PySequence_SetItem, PySequence_SetSlice, PyMapping_SetItemString can be used for deleting. But all these functions have special counterparts for deleting: PyObject_DelAttr etc. The question is wherever deleting ability of Set-functions is intentional, should we document this or deprecate and then delete? [1] http://bugs.python.org/issue25701

4 years, 10 months

Help with a book

by Jacob Zimmerman

Hello Python Developers! I'm writing a book about descriptors, and I'm hoping to make it a comprehensive guide, covering just about everything there is to know about descriptors, including many tips to get past certain knowledge barriers and how to avoid certain pitfalls. I'm hoping for it to become the definitive guide for those who want to really understand descriptors. Raymond's Descriptor HowTo Guide is great, but focused. I want to expand on what that guide teaches. Anyway, I am currently reading through my initial rough draft and making corrections for a revised draft. Once I'm done with that, I'd like a few volunteers to read through it. First, to find spelling, grammatical, or consistency mistakes, though those should be few in number, but also to give input as to whether something seems too repetitive, if some more information should be given in a spot, and if I'm even blatantly wrong about anything (hopefully not). Anyone who helps will be able to receive a free ebook of the final copy as well as mention in the Special Thanks. I appreciate any help anyone can give to assist in making this book as great as it can be. Thanks, Jacob Zimmerman Twitter: @jacobz_20 Blog: http://programmingideaswithjake.wordpress.com

4 years, 10 months

Can not pass configuration on mac os

by maochongzhao

Hi, I am new here wishing to contribute to python. I tried to go through the tutorial for seting up Cpython, while I cannot pass the configuration. My system is Mac OS and I have installed the command tool of Xcode and hg. But on terminal it said that no such file or directory when I type “./configure --with-pydebug”. What was wrong with my action? How can I fix the issue? This may a little question, but thanks for your help and tutoring! Sincerely, Chongzhao Mao

4 years, 10 months

crash bug in weakref_richcompare?

by Luke Deller

Hi I have come across some dubious code in Objects/weakrefobject.c which looks like a bug to me, but wanted to run it past others. This was discovered from looking at crash dumps from a multithreaded python app (using Python 2.7.9, but the same weakref code exists in 3.5 and hg tip). The code that worries me is at the end of the "weakref_richcompare" function: return PyObject_RichCompare(PyWeakref_GET_OBJECT(self), PyWeakref_GET_OBJECT(other), op); At this point the code has established that the referents are still alive, and it is trying to compare the referents. However it has not acquired a strong reference to the referents, so I think it is possible for one of them to be deleted half way through this comparison. This can lead to a crash, because PyObject_RichCompare assumes that the PyObject*'s it was passed will remain usable for the duration of the call. The crashes I have seen involve data corruption consistent with one of these PyObject's being deleted and the memory reused for something else, eg: 00 python27!try_3way_compare+0x15 [objects\object.c @ 712] 01 python27!try_3way_to_rich_compare+0xb [objects\object.c @ 901] 02 python27!do_richcmp+0x2c [objects\object.c @ 935] 03 python27!PyObject_RichCompare+0x99 [objects\object.c @ 982] 04 python27!weakref_richcompare+0x6a [objects\weakrefobject.c @ 212] (In this example v->ob_type was 0x5f637865 which is ASCII "exc_", not a valid pointer at all) Other places in weakrefobject.c seem to have a similar weakness, eg in weakref_hash and weakref_repr. I have not been able to produce a small test case to exhibit this crash, but from this inspection of the code it looks like a bug - am I understanding this correctly? Thanks, Luke. ********************************************************************************************** Important Note This email (including any attachments) contains information which is confidential and may be subject to legal privilege. If you are not the intended recipient you must not use, distribute or copy this email. If you have received this email in error please notify the sender immediately and delete this email. Any views expressed in this email are not necessarily the views of IRESS Limited. It is the duty of the recipient to virus scan and otherwise test the information provided before loading onto any computer system. IRESS Limited does not warrant that the information is free of a virus or any other defect or error. **********************************************************************************************

4 years, 10 months

ACTIVITY SUMMARY (2015-11-20 - 2015-11-27)

by Laura Creighton

My mailer just barfed trying to read that summary. The problem is that the mail comes out with the encoding: Content-Type: text/plain; charset="us-ascii" but then wants to print 'http://bugs.python.org/issue25709 opened by Árpád Kósa' Can we change the encoding to utf-8 ? Laura

4 years, 10 months

Summary of Python tracker Issues

by Python tracker

ACTIVITY SUMMARY (2015-11-20 - 2015-11-27) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 5263 ( +3) closed 32238 (+57) total 37501 (+60) Open issues with patches: 2312 Issues opened (41) ================== #20923: Explain ConfigParser 'valid section name' and .SECTCRE http://bugs.python.org/issue20923 reopened by terry.reedy #25684: ttk.OptionMenu radiobuttons aren't unique between two instance http://bugs.python.org/issue25684 opened by Bryan.Oakley #25685: Inefficiency with SocketHandler - may send log record message http://bugs.python.org/issue25685 opened by Marvin Greenberg #25687: Error during test case and tearDown http://bugs.python.org/issue25687 opened by bennoleslie #25690: Replacement for unittest.mock.mock_open http://bugs.python.org/issue25690 opened by Niv Ben-David #25694: test.libregrtest not installed http://bugs.python.org/issue25694 opened by Arfrever #25696: "make -j9 install" fails because bininstall target requires th http://bugs.python.org/issue25696 opened by haypo #25698: test regressions introduced with the fix for #22995 http://bugs.python.org/issue25698 opened by doko #25699: Easier way to specify reduced globals for doctest http://bugs.python.org/issue25699 opened by John.Mark.Vandenberg #25701: Document that tp_setattro and tp_setattr are used for deleting http://bugs.python.org/issue25701 opened by serhiy.storchaka #25702: Link Time Optimizations support for GCC and CLANG http://bugs.python.org/issue25702 opened by alecsandru.patrascu #25704: Update the devguide to 3.5 http://bugs.python.org/issue25704 opened by matrixise #25707: Add the close method for ElementTree.iterparse() object http://bugs.python.org/issue25707 opened by serhiy.storchaka #25708: runpy hides traceback for some exceptions http://bugs.python.org/issue25708 opened by sleepycal #25709: Problem with string concatenation and utf-8 cache. http://bugs.python.org/issue25709 opened by Árpád Kósa #25710: zipimport is not PEP 3147 or PEP 488 compliant http://bugs.python.org/issue25710 opened by byrnes #25711: Rewrite zipimport from scratch http://bugs.python.org/issue25711 opened by brett.cannon #25713: Setuptools included with 64-bit Windows installer is outdated http://bugs.python.org/issue25713 opened by James.Paget #25714: Consider isinstance(..., numbers.Integral) instead of isinstan http://bugs.python.org/issue25714 opened by posita #25715: Python 3.5.1 installer shows wrong upgrade path http://bugs.python.org/issue25715 opened by steve.dower #25716: typeobject.c call_method & call_maybe can leak references on ' http://bugs.python.org/issue25716 opened by Myron Walker #25717: tempfile.TemporaryFile fails when dir option set to directory http://bugs.python.org/issue25717 opened by Hans Lawrenz #25718: itertools.accumulate __reduce__/__setstate__ bug http://bugs.python.org/issue25718 opened by arigo #25719: Deprecate spitfire benchmark http://bugs.python.org/issue25719 opened by florin.papa #25720: Fix curses module compilation with ncurses6 http://bugs.python.org/issue25720 opened by donmez #25723: ConfigParser should never write broken configurations http://bugs.python.org/issue25723 opened by spaceone #25724: SSLv3 test failure on Ubuntu 16.04 LTS http://bugs.python.org/issue25724 opened by mdeslaur #25726: sys.setprofile / sys.getprofile asymetry http://bugs.python.org/issue25726 opened by stefan #25728: email parser ignores inner multipart boundary when outer messa http://bugs.python.org/issue25728 opened by forest #25729: update pure python datetime.timedelta creation http://bugs.python.org/issue25729 opened by bdkearns #25730: invisible sidebar content with code snippets http://bugs.python.org/issue25730 opened by xwhhsprings #25731: Assigning and deleting __new__ attr on the class does not allo http://bugs.python.org/issue25731 opened by Stanisław Skonieczny (Uosiu) #25732: functools.total_ordering does not correctly implement not equa http://bugs.python.org/issue25732 opened by David Seddon #25733: Idle does not handle non-standard compile errors http://bugs.python.org/issue25733 opened by ppperry #25735: math.factorial doc should mention integer return type http://bugs.python.org/issue25735 opened by John.Yeung #25738: http.server doesn't handle RESET CONTENT status correctly http://bugs.python.org/issue25738 opened by spaceone #25739: Add PAYLOAD_TOO_LARGE / URI_TOO_LONG (new name in RFC 7231) http://bugs.python.org/issue25739 opened by spaceone #25740: multiple issues in http.client http://bugs.python.org/issue25740 opened by spaceone #25741: Usual Installation Directory http://bugs.python.org/issue25741 opened by firatozgul #25742: locale.setlocale does not work with unicode strings http://bugs.python.org/issue25742 opened by tierlieb #25743: Clarify exactly what \w matches in UNICODE mode http://bugs.python.org/issue25743 opened by zwol Most recent 15 issues with no replies (15) ========================================== #25742: locale.setlocale does not work with unicode strings http://bugs.python.org/issue25742 #25735: math.factorial doc should mention integer return type http://bugs.python.org/issue25735 #25733: Idle does not handle non-standard compile errors http://bugs.python.org/issue25733 #25726: sys.setprofile / sys.getprofile asymetry http://bugs.python.org/issue25726 #25724: SSLv3 test failure on Ubuntu 16.04 LTS http://bugs.python.org/issue25724 #25720: Fix curses module compilation with ncurses6 http://bugs.python.org/issue25720 #25713: Setuptools included with 64-bit Windows installer is outdated http://bugs.python.org/issue25713 #25708: runpy hides traceback for some exceptions http://bugs.python.org/issue25708 #25687: Error during test case and tearDown http://bugs.python.org/issue25687 #25685: Inefficiency with SocketHandler - may send log record message http://bugs.python.org/issue25685 #25682: __package__ not set to None under pdb in Python 3 http://bugs.python.org/issue25682 #25675: doc for BaseEventLoop.run_in_executor() says its a coroutine, http://bugs.python.org/issue25675 #25661: tokenize.untokenize does not maintain the order of tabbed inde http://bugs.python.org/issue25661 #25658: PyThread assumes pthread_key_t is an integer, which is against http://bugs.python.org/issue25658 #25653: ctypes+callbacks+fork+selinux = crash http://bugs.python.org/issue25653 Most recent 15 issues waiting for review (15) ============================================= #25740: multiple issues in http.client http://bugs.python.org/issue25740 #25739: Add PAYLOAD_TOO_LARGE / URI_TOO_LONG (new name in RFC 7231) http://bugs.python.org/issue25739 #25738: http.server doesn't handle RESET CONTENT status correctly http://bugs.python.org/issue25738 #25729: update pure python datetime.timedelta creation http://bugs.python.org/issue25729 #25724: SSLv3 test failure on Ubuntu 16.04 LTS http://bugs.python.org/issue25724 #25720: Fix curses module compilation with ncurses6 http://bugs.python.org/issue25720 #25719: Deprecate spitfire benchmark http://bugs.python.org/issue25719 #25718: itertools.accumulate __reduce__/__setstate__ bug http://bugs.python.org/issue25718 #25717: tempfile.TemporaryFile fails when dir option set to directory http://bugs.python.org/issue25717 #25716: typeobject.c call_method & call_maybe can leak references on ' http://bugs.python.org/issue25716 #25715: Python 3.5.1 installer shows wrong upgrade path http://bugs.python.org/issue25715 #25709: Problem with string concatenation and utf-8 cache. http://bugs.python.org/issue25709 #25704: Update the devguide to 3.5 http://bugs.python.org/issue25704 #25702: Link Time Optimizations support for GCC and CLANG http://bugs.python.org/issue25702 #25701: Document that tp_setattro and tp_setattr are used for deleting http://bugs.python.org/issue25701 Top 10 most discussed issues (10) ================================= #25709: Problem with string concatenation and utf-8 cache. http://bugs.python.org/issue25709 24 msgs #25717: tempfile.TemporaryFile fails when dir option set to directory http://bugs.python.org/issue25717 13 msgs #25723: ConfigParser should never write broken configurations http://bugs.python.org/issue25723 11 msgs #20923: Explain ConfigParser 'valid section name' and .SECTCRE http://bugs.python.org/issue20923 10 msgs #25660: tabs don't work correctly in python repl http://bugs.python.org/issue25660 10 msgs #25730: invisible sidebar content with code snippets http://bugs.python.org/issue25730 7 msgs #25677: Syntax error caret confused by indentation http://bugs.python.org/issue25677 6 msgs #25694: test.libregrtest not installed http://bugs.python.org/issue25694 6 msgs #25729: update pure python datetime.timedelta creation http://bugs.python.org/issue25729 6 msgs #15348: IDLE - shell becomes unresponsive if debugger windows is close http://bugs.python.org/issue15348 5 msgs Issues closed (51) ================== #4744: asynchat documentation needs to be more precise http://bugs.python.org/issue4744 closed by r.david.murray #7990: xml.etree.cElementTree lacks full dir() on Element http://bugs.python.org/issue7990 closed by serhiy.storchaka #10131: deepcopying an xml.dom.minidom.Document generates an invalid X http://bugs.python.org/issue10131 closed by serhiy.storchaka #10942: xml.etree.ElementTree.tostring returns type bytes, expected ty http://bugs.python.org/issue10942 closed by serhiy.storchaka #13275: Recommend xml.etree for XML processing http://bugs.python.org/issue13275 closed by serhiy.storchaka #14044: IncompleteRead error with urllib2 or urllib.request -- fine wi http://bugs.python.org/issue14044 closed by martin.panter #14988: _elementtree: Raise ImportError when importing of pyexpat fail http://bugs.python.org/issue14988 closed by serhiy.storchaka #19687: Fixes for elementtree integer overflow http://bugs.python.org/issue19687 closed by serhiy.storchaka #21228: Missing enumeration of HTTPResponse Objects methods of urllib. http://bugs.python.org/issue21228 closed by martin.panter #22989: HTTPResponse.msg not as documented http://bugs.python.org/issue22989 closed by martin.panter #23914: pickle fails with SystemError http://bugs.python.org/issue23914 closed by serhiy.storchaka #24097: Use after free in PyObject_GetState http://bugs.python.org/issue24097 closed by serhiy.storchaka #24455: IDLE debugger causes crash if not quitted properly before next http://bugs.python.org/issue24455 closed by terry.reedy #24731: Incorrect assert in str_subtype_new http://bugs.python.org/issue24731 closed by serhiy.storchaka #24858: python3 -m test -ugui -v test_tk gives 3 failures under Debian http://bugs.python.org/issue24858 closed by serhiy.storchaka #25508: LogRecord attributes are not tuple, when logging only dict http://bugs.python.org/issue25508 closed by python-dev #25576: Remove “Content-Type: application/x-www-form-urlencoded; cha http://bugs.python.org/issue25576 closed by martin.panter #25594: enum instance attribute access possible http://bugs.python.org/issue25594 closed by python-dev #25616: Extract OrderedDict tests into separate file http://bugs.python.org/issue25616 closed by serhiy.storchaka #25622: Enable ctypes.test.test_values.Win_ValuesTestCase for non-Wind http://bugs.python.org/issue25622 closed by martin.panter #25623: Keep the link to Python implementation of OrderedDict http://bugs.python.org/issue25623 closed by serhiy.storchaka #25624: shutil.make_archive makes invalid directory entries http://bugs.python.org/issue25624 closed by serhiy.storchaka #25625: "chdir" Contex manager for pathlib http://bugs.python.org/issue25625 closed by serhiy.storchaka #25626: Gzip fails for file over 2**32 bytes http://bugs.python.org/issue25626 closed by martin.panter #25646: Distutils and Windows SDK 7.1 http://bugs.python.org/issue25646 closed by JGoutin #25656: multiprocessing.dummy: pool.map hangs on empty list http://bugs.python.org/issue25656 closed by ebarry #25657: virtualenv's activate does not update LD_LIBRARY_PATH http://bugs.python.org/issue25657 closed by serge-sans-paille #25663: Make rlcompleter avoid duplicate global names http://bugs.python.org/issue25663 closed by martin.panter #25668: Deadlock in logging caused by a possible race condition with " http://bugs.python.org/issue25668 closed by vinay.sajip #25669: unittest.assertEqual() on un-equal types inheriting from colle http://bugs.python.org/issue25669 closed by michael.foord #25678: int() from a buffer reads past the buffer boundaries http://bugs.python.org/issue25678 closed by serhiy.storchaka #25686: Don't use distutils in test_shutil http://bugs.python.org/issue25686 closed by serhiy.storchaka #25688: File leak in ElementTree.iterparse() http://bugs.python.org/issue25688 closed by serhiy.storchaka #25689: ftplib docs language fix http://bugs.python.org/issue25689 closed by martin.panter #25691: Crash on deleting Element attribute http://bugs.python.org/issue25691 closed by serhiy.storchaka #25692: input function outputs prompt to stderr http://bugs.python.org/issue25692 closed by martin.panter #25693: test_asyncio prints some messages http://bugs.python.org/issue25693 closed by martin.panter #25695: test___all__ and test_support alter execution environment http://bugs.python.org/issue25695 closed by martin.panter #25697: Fix rough alphabetical order in Misc/ACKS http://bugs.python.org/issue25697 closed by serhiy.storchaka #25700: namedtuple documentation http://bugs.python.org/issue25700 closed by Laur Joost #25703: test_sys is failed if standard stream is redirected in 2.7 http://bugs.python.org/issue25703 closed by serhiy.storchaka #25705: Fix regex_compile benchmark crash http://bugs.python.org/issue25705 closed by zach.ware #25706: problems in library/base64.rst http://bugs.python.org/issue25706 closed by serhiy.storchaka #25712: Dead link in the PEP-3147 http://bugs.python.org/issue25712 closed by haypo #25721: Fix pybench always_display error http://bugs.python.org/issue25721 closed by haypo #25722: Lib/ssl.py breaks certificate validation for wildcard domains, http://bugs.python.org/issue25722 closed by christian.heimes #25725: Memory leak on unpickling bogus data http://bugs.python.org/issue25725 closed by serhiy.storchaka #25727: os.startfile implementation for other OS'es besides Windows http://bugs.python.org/issue25727 closed by r.david.murray #25734: fnmatch regular expression can be improved http://bugs.python.org/issue25734 closed by r.david.murray #25736: smtplib can't send 8bit encoded utf-8 message http://bugs.python.org/issue25736 closed by r.david.murray #25737: array is not a Sequence http://bugs.python.org/issue25737 closed by eryksun

4 years, 10 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Python-Dev November 2015