Mailman 3 May 2015 - Python-Dev

3.5 doc warnings
by Terry Reedy May 23, 2015

May 23, 2015

35\Doc\whatsnew\3.5.rst:686: ERROR: Unknown interpreted text role "module". 35\Doc\library\typing.rst:: WARNING: document isn't included in any toctree from building html docs just now -- Terry Jan Reedy

2 1

Fwd: Re: [python-committers] Reminder: Python 3.5 beta 1 will be tagged tomorrow
by Larry Hastings May 23, 2015

May 23, 2015

Whoops, didn't send my reply to both lists. Forwarded, below. -------- Forwarded Message -------- Subject: Re: [python-committers] [Python-Dev] Reminder: Python 3.5 beta 1 will be tagged tomorrow Date: Sat, 23 May 2015 12:23:09 -0700 From: Larry Hastings <larry(a)hastings.org> To: python-committers(a)python.org On 05/23/2015 06:25 AM, Nick Coghlan wrote: > I filedhttp://bugs.python.org/issue24270 to track this, but there's a > fair bit of work to be done to integrate the changes into the existing > math module's code, tests and documentation. I'm willing to consider a feature freeze exception for this, as long as * it doesn't make invasive changes (it looks like it will literally add one new entry point, which is acceptable) * it's cleaned up in the way the core devs are proposing (integrate it into the math module, including tests and documentation) * it's done before beta 2 Somebody, please take that as an encouragement to get this cleaned up and ready for checkin. //arry/ p.s. Would it make sense to add a form of isclose to unittest?

1 0

Can we clean up the buildbots please?
by Larry Hastings May 23, 2015

May 23, 2015

Right now we have eight online buildbots for Python trunk. Of those, currently *six* are reporting errors in either the compile or test phases. http://buildbot.python.org/all/waterfall?category=3.x.stable There's one platform ("AMD64 Snow Leop") where the failures are sporadic "stack overflow" errors encountered during the test suite. But the other five platforms have consistent failures, build after build. Those platforms: AMD64 OpenIndiana AMD64 Windows7 SP1 x86 Windows Server 2003 [SB] x86 Windows7 x86 XP-4 That includes *all* of the Windows buildbots. Gosh, it sure would be nice if Beta 1 didn't fail on Windows, wouldn't it? Could some Windows core devs take a look at the failures and see about cleaning them up? Naturally the OpenIndiana and OS X devs are invited to fix the errors on those platforms too, //arry/ p.s. My apologies for not bringing attention to this sooner. But, well, we still have a day left, right?

4 8

PEP 484 (Type Hints) announcement
by Mark Shannon May 23, 2015

May 23, 2015

Hello all, I am pleased to announce that I am accepting PEP 484 (Type Hints). Given the proximity of the beta release I thought I would get this announcement out now, even though there are some (very) minor details to iron out. (If you want to know the details, it's all at https://github.com/ambv/typehinting) I hope that PEP 484 will be a benefit to all users of Python. I think the proposed annotation semantics and accompanying module are technically sound and I hope that they are socially acceptable to the Python community. I have long been aware that as well as a powerful, sophisticated and "production quality" language, Python is also used by many casual programmers, and as a language to introduce children to programming. I also realise that this PEP does not look like it will be any help to the part-time programmer or beginner. However, I am convinced that it will enable significant improvements to IDEs (hopefully including IDLE), static checkers and other tools. These tools will then help us all, beginners included. This PEP has been a huge amount of work, involving a lot of people. So thank you to everyone involved. If I were to list names I would inevitably miss someone out. You know who you are. Finally, if you are worried that this will make Python ugly and turn it into some sort of inferior Java, then I share you concerns, but I would like to remind you of another potential ugliness; operator overloading. C++, Perl and Haskell have operator overloading and it gets abused something rotten to produce "concise" (a.k.a. line noise) code. Python also has operator overloading and it is used sensibly, as it should be. Why? It's a cultural issue; readability matters. Python is your language, please use type-hints responsibly :) Cheers, Mark.

4 3

Hello, I am André Freitas :)
by André Freitas May 22, 2015

May 22, 2015

Hi there, My name is André Freitas, I'm 22 years old and I live in Portugal (Porto). I'm currently finishing my Masters in Informatics and Computer Science with a thesis in Mining Software Repositories, where I am able to predict defects in Software components: https://github.com/andrefreitas/schwa I'm a Python developer with 4 years of experience and as a Speaker, did a lot of Python workshops in Engineering Universities. I'm always learning new things and I really love Python (it's my religion)! I have skills in Security, Tests and Quality, Devops, Software Architecture and Engineering, UI/UX and Compilers. I am reading your guidelines and just checking around to see how this mailing list works. Hope to send some patches soon and share some ideas. Feel free to follow me on Github https://github.com/andrefreitas Best regards, André Freitas.

2 1

Accepting PEP 489 (Multi-phase extension module initialization)
by Eric Snow May 22, 2015

May 22, 2015

Hi all, After extended discussion over the last several months on import-sig, the resulting proposal for multi-phase (PEP 451) extension module initialization has finalized. The resulting PEP provides a clean, straight-forward, and backward-compatible way to import extension modules using ModuleSpecs. With that in mind and given the improvement it provides, PEP 489 is now accepted. I want to thank Petr, Nick, and Stefan for the time, thought, and effort they put into the proposal (and implementation). It was a disappointment to me when, at the time, we couldn't find a good way to apply PEP 451 to builtins and extension modules. So thanks for easing my anxiety! -eric

5 4

How shall we conduct the Python 3.5 beta and rc periods? (Please vote!)
by Larry Hastings May 22, 2015

May 22, 2015

Python 3.5 beta 1 is coming up soon. After beta is rc; after rc is 3.5.0 final. During the beta and rc periods the Python developer workflow changes a little--what sorts of checkins are permissible, and how to get something accepted and merged generally becomes more complicated. I was the release manager for Python 3.4, and the way I ran the rc period for 3.4 was miserable. Everyone hated it--and that includes me. I'm absolutely not doing it that way for 3.5. But that leads one to the question: okay, how *am* I going to run it? I have three ideas for workflows for the beta and rc periods for 3.5, below. But first let's talk about what I/we hope to achieve. Traditionally during the beta and rc periods, development of new features stops completely. Obviously, after feature freeze no new features can go into the beta / rc releases. But why can't people develop new features for the *next* release? The reason given is that we're trying to guide the core dev community in the right direction--they should concentrate on fixing bugs in the new release. I suspect the real reason for this is that back in the bad old days of Subversion (and CVS!) branching and merging were painful. This social engineering policy is a justification after-the-fact. But Mercurial makes branching and merging nearly effortless. Mercurial also makes it painless to develop new features in private. So consider: anyone who wants to work on new features during beta and rc can easily do so. All our "no new features during beta and rc" policy really does is drive such development away out of public view. I think it's time we experimented with lifting that policy. The trick is finding a good place for us to check in the work. You see, during the 3.5 rc period, we arguably want to accept checkins for *three* different revisions: 3.5.0 3.5.1 3.6 3.5.1? Yep. During the rc period for 3.4--and particularly after the last rc was tagged--there were a lot of minor fixes that were desirable, but I didn't want to accept into 3.4 just to avoid destabilizing the release. I still wanted those checkins, I just didn't want them in 3.4.0. So the way it worked was, developers would check those bugfixes in to trunk, then I'd cherry-pick the revisions I wanted into the rc branch. In other words, during the rc period for 3.4, trunk effectively represented 3.4.1. This was valuable and I absolutely want to do it again. So here are the workflows. Workflow 0 most resembles what we've done in the past. Workflow 1 is my favorite and the most ambitious. All three give us a public place to put revisions for 3.5.0 and 3.5.1; Workflow 1 also gives us a place to check in work for 3.6 during the beta and rc periods for 3.5. Workflow 2 is a less ambitious compromise. Workflow 0 ========== When I ship beta 1, trunk remains 3.5. When I ship rc 1, trunk becomes 3.5.1. I create a publically visible read-only repo that represents 3.5.0, and any checkins that I want to accept into 3.5.0 I must manually cherry-pick from trunk. When I ship Python 3.5.0 final, we branch 3.5, and trunk becomes 3.6. Workflow 1 ========== When I ship beta 1, we create the 3.5 branch. trunk become 3.6. When I ship rc 1, the 3.5 branch becomes 3.5.1. I maintain a publically visible repo /on bitbucket/ for 3.5.0, and we use bitbucket "pull requests" for cherry-picks from 3.5.1 into 3.5.0. This gives us a pilot project to try out a web GUI for merging. It makes my workflow easier, as I can push a button to accept cherry-picks. (If they don't apply cleanly I can tell the author to go fix the conflict and resubmit it.) The downside: it requires core devs to have and use bitbucket accounts. Workflow 2 ========== When I ship beta 1, trunk remains 3.5. When I ship rc 1, we create the 3.5 branch. The 3.5 branch is 3.5.0 and trunk is 3.5.1. Only blessed stuff gets cherry-picked from 3.5.1 back into 3.5.0. What do you think? My votes are as follows: Workflow 0: -0.5 Workflow 1: +1 Workflow 2: +0.5 Please cast your votes, //arry/

11 18

Reminder: Python 3.5 beta 1 will be tagged tomorrow
by Larry Hastings May 22, 2015

May 22, 2015

Howdy howdy. It's-a me, Larry, your friendly neighborhood Python 3.5 Release Manager. Somewhere around 2 or 3pm tomorrow I expect to tag Python 3.5 beta 1. We'll actually release beta 1 on Sunday, once the binary installers are all built. Beta 1 is also feature-freeze, meaning no new features may be added to 3.5 without my permission. Since it seems useful to have a specific cutoff time, please stop adding features at ** 8pm Saturday UTC **. (That's 1pm Pacific Daylight Time. It's also almost exactly 24 hours from... now.) I remind you that this time we're trying something new: we're going to create the 3.5 branch when we release beta 1, allowing feature development (for 3.6) to continue in trunk. At the point that I check in and push beta 1, I'll also merge all checkins from trunk back into the 3.5 branch. After that it'll be responsibility of the person checking in to check their bug fixes in to the appropriate place. So please keep in mind: once the 3.5 branch becomes generally available on Sunday, the usual rules for a release branch will apply: bug fixes for 3.5 should be checked in to the 3.5 branch and get merged forward into trunk. If you have new features you want to ship with Python 3.5, please check them in as soon as possible! Thank you for helping to make Python better, //arry/

1 0

Re: [Python-Dev] Status of PEP 484 and the typing module
by Guido van Rossum May 22, 2015

May 22, 2015

Hi Mark, We're down to the last few items here. I'm CC'ing python-dev so folks can see how close we are. I'll answer point by point. On Thu, May 21, 2015 at 6:24 AM, Mark Shannon <mark(a)hotpy.org> wrote: > Hi, > > The PEP itself is looking fairly good. > I hope you'll accept it at least provisionally so we can iterate over the finer points while a prototype of typing.py in in beta 1. > However, I don't think that typing.py is ready yet, for a number of > reasons: > > 1. > As I've said before, there needs to be a distinction between classes and > types. > They is no need for Any, Generic, Generic's subtypes, or Union to subclass > builtins.type. > I strongly disagree. They can appear in many positions where real classes are acceptable, in particular annotations can have classes (e.g. int) or types (e.g. Union[int, str]). > Playing around with typing.py, it has also become clear to me that it > is also important to distinguish type constructors from types. > > What do I mean by a type constructor? > A type constructor makes types. > "List" is an example of a type constructor. It constructs types such as > List[T] and List[int]. > Saying that something is a List (as opposed to a list) should be rejected. > The PEP actually says that plain List (etc.) is equivalent to List[Any]. (Well, at least that's the intention; it's implied by the section about the equivalence between Node() and Node[Any](). > 2. > Usability of typing as it stands: > > Let's try to make a class that implements a mutable mapping. > > >>> import typing as tp > #Make some variables. > >>> T = tp.TypeVar('T') > >>> K = tp.TypeVar('K') > >>> V = tp.TypeVar('V') > > #Then make our class: > > >>> class MM(tp.MutableMapping): pass > ... > #Oh that worked, but it shouldn't. MutableMapping is a type constructor. > It means MutableMapping[Any]. > #Let's make one > >>> MM() > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/home/mark/repositories/typehinting/prototyping/typing.py", line > 1095, in __new__ > if _gorg(c) is Generic: > File "/home/mark/repositories/typehinting/prototyping/typing.py", line > 887, in _gorg > while a.__origin__ is not None: > AttributeError: type object 'Sized' has no attribute '__origin__' > > # ??? > Sorry, that's a bug I introduced in literally the last change to typing.py. I will fix it. The expected behavior is TypeError: Can't instantiate abstract class MM with abstract methods __len__ > #Well let's try using type variables. > class MM2(tp.MutableMapping[K, V]): pass > ... > >>> MM2() > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File "/home/mark/repositories/typehinting/prototyping/typing.py", line > 1095, in __new__ > if _gorg(c) is Generic: > File "/home/mark/repositories/typehinting/prototyping/typing.py", line > 887, in _gorg > while a.__origin__ is not None: > AttributeError: type object 'Sized' has no attribute '__origin__' > Ditto, and sorry. > > At this point, we have to resort to using 'Dict', which forces us to > subclass 'dict' which may not be what we want as it may cause metaclass > conflicts. > > 3. > Memory consumption is also a worry. There is no caching, which means every > time I use "List[int]" as an annotation, a new class object is created. > Each class may only be a few KB, but collectively this could easily add up > to several MBs. > This should be easy to fix. > I can work on this after the beta-1 release. Until then, type aliases can be used to avoid redundant type creation (and often they are clearer anyway :-). > 4. > PY2, etc. really need to go. > Assuming that this code type checks OK: > > if typing.PY2: > type_safe_under_py2_only() > else: > type_safe_under_py3_only() > > Is the checker supposed to pass this: > > if sys.hexversion < 0x03000000: > type_safe_under_py2_only() > else: > type_safe_under_py3_only() > > If it should pass, then why have PY2, etc. at all. > If it should fail, well that is just stupid and annoying. > > Pylint already understands version checks, as does our (Semmle's) checker. > I suspect most IDEs do as well. > I have to negotiate this with Jukka but I think he'll agree. > 5. > Removing isinstance() support: > > As I said before, this is the job of a checker not typing.py. > > It also introduces some strange situations: > D = tp.Dict[str,int] > d = {} > assert isinstance(d, D) > d["x"] = None > assert isinstance(d, D) > > In the above case the first check passes, and the second fails. > But d is either of type D or it isn't. It can't be both, as types > are static properties of programs, unlike classes. > Well, isinstance() is a dynamic function. The type checker has no authority over its behavior beyond its signature. > And it's broken anyway: > >>> D = tp.Dict[str,'D'] > >>> d = {"x": {}} > >>> isinstance(d, D) > False > That's because _ForwardRef doesn't implement __instancheck__ or __subclasscheck__. It's easily fixed. > > Realistically, I don't see typing.py being ready in time for 3.5. > I'd be happy to be proved wrong. > > Cheers, > Mark. > > > P.S. > I am worried by the lack of formal specification. It all seems a bit > hand-waving. A formal spec reduces the likelihood of some unforeseen corner > case being a permanent wart. > Formal specs are not my cup of tea. :-( (I'm not proud of this, but it just is a fact -- see how terrible a job I've done of the Python reference manual.) The best I could come up with is PEP 483. > Take the recursive type above. There is no mention of recursive types in > the PEP and they are clearly possible. Are they allowed? > They should be allowed. I imagine you could create one for which a naive isinstance() imeplementation ends up in an infinite loop. That can be fixed too (we fixed this for printing self-referential lists and dicts). > I'm guessing that Jukka's thesis should cover a lot of this. > Has it been published yet? > Hopefully Jukka can answer that. :-) -- --Guido van Rossum (python.org/~guido)

3 6

Summary of Python tracker Issues
by Python tracker May 22, 2015

May 22, 2015

ACTIVITY SUMMARY (2015-05-15 - 2015-05-22) 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 4833 ( -7) closed 31194 (+71) total 36027 (+64) Open issues with patches: 2219 Issues opened (40) ================== #24147: Dialect class defaults are not documented. http://bugs.python.org/issue24147 reopened by r.david.murray #24203: Depreciate threading.Thread.isDaemon etc http://bugs.python.org/issue24203 opened by anon #24204: string.strip() documentation is misleading http://bugs.python.org/issue24204 opened by PhoenixofMT #24206: Issues with equality of inspect objects http://bugs.python.org/issue24206 opened by serhiy.storchaka #24207: Argument Clinic doesn't mangle conflicting names http://bugs.python.org/issue24207 opened by serhiy.storchaka #24209: Allow IPv6 bind in http.server http://bugs.python.org/issue24209 opened by Link Mauve #24212: Idle, 2.7, backport idlelib.__main__, enable py -m idlelib http://bugs.python.org/issue24212 opened by terry.reedy #24214: Exception with utf-8, surrogatepass and incremental decoding http://bugs.python.org/issue24214 opened by RalfM #24215: test_trace uses test_pprint http://bugs.python.org/issue24215 opened by serhiy.storchaka #24217: O_RDWR undefined in mmapmodule.c http://bugs.python.org/issue24217 opened by Jeffrey.Armstrong #24219: Repeated integer in Lexical analysis/Integer literals section http://bugs.python.org/issue24219 opened by vlth #24224: test_msilib is inadequate http://bugs.python.org/issue24224 opened by zach.ware #24225: Idlelib: changing file names http://bugs.python.org/issue24225 opened by Al.Sweigart #24228: Interpreter triggers segmentation fault at the starting http://bugs.python.org/issue24228 opened by mdootb #24229: pathlib.Path should have a copy() method http://bugs.python.org/issue24229 opened by jshholland #24230: tempfile.mkdtemp() doesn't work with bytes paths http://bugs.python.org/issue24230 opened by durin42 #24231: os.makedirs('/', exist_ok=True) fails on Darwin http://bugs.python.org/issue24231 opened by mew #24234: Should we define complex.__complex__ and bytes.__bytes__? http://bugs.python.org/issue24234 opened by gvanrossum #24235: ABCs don't fail metaclass instantiation http://bugs.python.org/issue24235 opened by Devin Jeanpierre #24238: Avoid entity expansion attacks in Element Tree http://bugs.python.org/issue24238 opened by vadmium #24239: Allow to configure which gpg to use in distutils upload http://bugs.python.org/issue24239 opened by ced #24241: webbrowser default browser detection and/or public API for _tr http://bugs.python.org/issue24241 opened by daves #24243: behavior for finding an empty string is inconsistent with docu http://bugs.python.org/issue24243 opened by swanson #24244: Python exception on strftime with %f on Python 3 and Python 2 http://bugs.python.org/issue24244 opened by MajeedArni #24247: "unittest discover" does modify sys.path http://bugs.python.org/issue24247 opened by redixin #24249: unittest API for detecting test failure in cleanup/teardown http://bugs.python.org/issue24249 opened by r.david.murray #24251: Different behavior for argparse between 2.7.8 and 2.7.9 when a http://bugs.python.org/issue24251 opened by hhuang #24252: IDLE removes elements from tracebacks. http://bugs.python.org/issue24252 opened by ppperry #24253: pydoc for namespace packages indicates FILE as built-in http://bugs.python.org/issue24253 opened by Antony.Lee #24254: Make class definition namespace ordered by default http://bugs.python.org/issue24254 opened by eric.snow #24255: Replace debuglevel-related logic with logging http://bugs.python.org/issue24255 opened by demian.brecht #24256: threading.Timer is not a class http://bugs.python.org/issue24256 opened by jrunyon #24258: BZ2File objects do not have name attribute http://bugs.python.org/issue24258 opened by jojko.sivek #24259: tar.extractall() does not recognize unexpected EOF http://bugs.python.org/issue24259 opened by Thomas Güttler #24260: TabError behavior doesn't match documentation http://bugs.python.org/issue24260 opened by abacabadabacaba #24261: Add a command line flag to suppress default signal handlers http://bugs.python.org/issue24261 opened by abacabadabacaba #24263: Why VALID_MODULE_NAME in unittest/loader.py is r'[_a-z]\w*\.py http://bugs.python.org/issue24263 opened by sih4sing5hong5 #24264: imageop Unsafe Arithmetic http://bugs.python.org/issue24264 opened by JohnLeitch #24265: IDLE produces error message when run with both -s and -c. http://bugs.python.org/issue24265 opened by ppperry #24266: raw_input function (with readline): Ctrl+C (during search mode http://bugs.python.org/issue24266 opened by sping Most recent 15 issues with no replies (15) ========================================== #24266: raw_input function (with readline): Ctrl+C (during search mode http://bugs.python.org/issue24266 #24265: IDLE produces error message when run with both -s and -c. http://bugs.python.org/issue24265 #24264: imageop Unsafe Arithmetic http://bugs.python.org/issue24264 #24263: Why VALID_MODULE_NAME in unittest/loader.py is r'[_a-z]\w*\.py http://bugs.python.org/issue24263 #24260: TabError behavior doesn't match documentation http://bugs.python.org/issue24260 #24259: tar.extractall() does not recognize unexpected EOF http://bugs.python.org/issue24259 #24258: BZ2File objects do not have name attribute http://bugs.python.org/issue24258 #24253: pydoc for namespace packages indicates FILE as built-in http://bugs.python.org/issue24253 #24247: "unittest discover" does modify sys.path http://bugs.python.org/issue24247 #24239: Allow to configure which gpg to use in distutils upload http://bugs.python.org/issue24239 #24238: Avoid entity expansion attacks in Element Tree http://bugs.python.org/issue24238 #24235: ABCs don't fail metaclass instantiation http://bugs.python.org/issue24235 #24234: Should we define complex.__complex__ and bytes.__bytes__? http://bugs.python.org/issue24234 #24224: test_msilib is inadequate http://bugs.python.org/issue24224 #24214: Exception with utf-8, surrogatepass and incremental decoding http://bugs.python.org/issue24214 Most recent 15 issues waiting for review (15) ============================================= #24254: Make class definition namespace ordered by default http://bugs.python.org/issue24254 #24244: Python exception on strftime with %f on Python 3 and Python 2 http://bugs.python.org/issue24244 #24238: Avoid entity expansion attacks in Element Tree http://bugs.python.org/issue24238 #24230: tempfile.mkdtemp() doesn't work with bytes paths http://bugs.python.org/issue24230 #24225: Idlelib: changing file names http://bugs.python.org/issue24225 #24219: Repeated integer in Lexical analysis/Integer literals section http://bugs.python.org/issue24219 #24217: O_RDWR undefined in mmapmodule.c http://bugs.python.org/issue24217 #24215: test_trace uses test_pprint http://bugs.python.org/issue24215 #24209: Allow IPv6 bind in http.server http://bugs.python.org/issue24209 #24206: Issues with equality of inspect objects http://bugs.python.org/issue24206 #24204: string.strip() documentation is misleading http://bugs.python.org/issue24204 #24198: please align the platform tag for windows http://bugs.python.org/issue24198 #24195: Add `Executor.filter` to concurrent.futures http://bugs.python.org/issue24195 #24165: Free list for single-digits ints http://bugs.python.org/issue24165 #24164: Support pickling objects with __new__ with keyword arguments w http://bugs.python.org/issue24164 Top 10 most discussed issues (10) ================================= #16991: Add OrderedDict written in C http://bugs.python.org/issue16991 22 msgs #4709: Mingw-w64 and python on windows x64 http://bugs.python.org/issue4709 18 msgs #24230: tempfile.mkdtemp() doesn't work with bytes paths http://bugs.python.org/issue24230 16 msgs #24244: Python exception on strftime with %f on Python 3 and Python 2 http://bugs.python.org/issue24244 12 msgs #24195: Add `Executor.filter` to concurrent.futures http://bugs.python.org/issue24195 10 msgs #12319: [http.client] HTTPConnection.request not support "chunked" Tra http://bugs.python.org/issue12319 9 msgs #24225: Idlelib: changing file names http://bugs.python.org/issue24225 9 msgs #23699: Add a macro to ease writing rich comparisons http://bugs.python.org/issue23699 8 msgs #24215: test_trace uses test_pprint http://bugs.python.org/issue24215 8 msgs #6598: calling email.utils.make_msgid frequently has a non-trivial pr http://bugs.python.org/issue6598 7 msgs Issues closed (61) ================== #4254: _cursesmodule.c callable update_lines_cols() http://bugs.python.org/issue4254 closed by r.david.murray #9858: Python and C implementations of io are out of sync http://bugs.python.org/issue9858 closed by pitrou #10170: Relationship between turtle speed setting and actual speed is http://bugs.python.org/issue10170 closed by terry.reedy #15267: tempfile.TemporaryFile and httplib incompatibility http://bugs.python.org/issue15267 closed by serhiy.storchaka #15836: unittest assertRaises should verify excClass is actually a Bas http://bugs.python.org/issue15836 closed by serhiy.storchaka #16261: Fix bare excepts in various places in std lib http://bugs.python.org/issue16261 closed by serhiy.storchaka #18682: [PATCH] remove bogus codepath from pprint._safe_repr http://bugs.python.org/issue18682 closed by serhiy.storchaka #18986: Add a case-insensitive case-preserving dict http://bugs.python.org/issue18986 closed by serhiy.storchaka #20098: email policy needs a mangle_from setting http://bugs.python.org/issue20098 closed by r.david.murray #20438: inspect: Deprecate getfullargspec? http://bugs.python.org/issue20438 closed by yselivanov #20596: Support for alternate wcstok syntax for Windows compilers http://bugs.python.org/issue20596 closed by Jeffrey.Armstrong #20691: inspect.signature: Consider exposing 'follow_wrapper_chains' o http://bugs.python.org/issue20691 closed by yselivanov #21083: Add get_content_disposition() to email.message.Message http://bugs.python.org/issue21083 closed by r.david.murray #21800: Implement RFC 6855 (IMAP Support for UTF-8) in imaplib. http://bugs.python.org/issue21800 closed by r.david.murray #21804: Implement thr UTF8 command (RFC 6856) in poplib. http://bugs.python.org/issue21804 closed by r.david.murray #21931: Nonsense errors reported by msilib.FCICreate for bad argument http://bugs.python.org/issue21931 closed by python-dev #22027: RFC 6531 (SMTPUTF8) support in smtplib http://bugs.python.org/issue22027 closed by r.david.murray #22107: tempfile module misinterprets access denied error on Windows http://bugs.python.org/issue22107 closed by serhiy.storchaka #22155: Out of date code example for tkinter's createfilehandler http://bugs.python.org/issue22155 closed by terry.reedy #22804: Can't run Idle in Windows 8 or windows 64 http://bugs.python.org/issue22804 closed by terry.reedy #23184: Unused imports, variables, file in IDLE http://bugs.python.org/issue23184 closed by terry.reedy #23780: Surprising behaviour when passing list to os.path.join. http://bugs.python.org/issue23780 closed by serhiy.storchaka #23889: Speedup inspect.Signature.bind http://bugs.python.org/issue23889 closed by yselivanov #23898: inspect() changes in Python3.4 are not compatible with objects http://bugs.python.org/issue23898 closed by yselivanov #23964: Update README documentation for IDLE tests. http://bugs.python.org/issue23964 closed by terry.reedy #23985: Crash when deleting slices from duplicated bytearray http://bugs.python.org/issue23985 closed by pitrou #24004: avoid explicit generator type check in asyncio http://bugs.python.org/issue24004 closed by yselivanov #24091: Use after free in Element.extend (1) http://bugs.python.org/issue24091 closed by serhiy.storchaka #24102: Multiple type confusions in unicode error handlers http://bugs.python.org/issue24102 closed by serhiy.storchaka #24127: Fatal error in launcher: Job information querying failed http://bugs.python.org/issue24127 closed by paul.moore #24162: [2.7 regression] test_asynchat test failure on i586-linux-gnu http://bugs.python.org/issue24162 closed by python-dev #24176: Incorrect parsing of unpacked expressions in call http://bugs.python.org/issue24176 closed by python-dev #24180: PEP 492: Documentation http://bugs.python.org/issue24180 closed by yselivanov #24190: BoundArguments facility to inject defaults http://bugs.python.org/issue24190 closed by yselivanov #24192: unexpected system error with pep420 style namespace packages http://bugs.python.org/issue24192 closed by eric.snow #24200: Redundant id in informative reprs http://bugs.python.org/issue24200 closed by yselivanov #24205: signature.bind error messages are sub-optimal http://bugs.python.org/issue24205 closed by yselivanov #24208: test_inspect leaks temporary directory http://bugs.python.org/issue24208 closed by serhiy.storchaka #24210: Tests failed with -Werror http://bugs.python.org/issue24210 closed by berker.peksag #24211: Add RFC 6532 support to the email library http://bugs.python.org/issue24211 closed by r.david.murray #24213: ProcessPoolExecutor().map() fails following an identical map() http://bugs.python.org/issue24213 closed by ned.deily #24216: Typo in bytes.join/bytearray.join documentation http://bugs.python.org/issue24216 closed by r.david.murray #24218: Also support SMTPUTF8 in smtplib's send_message method. http://bugs.python.org/issue24218 closed by r.david.murray #24220: ast.Call signature changed http://bugs.python.org/issue24220 closed by willingc #24221: Clean-up and optimization for heapq siftup() and siftdown() http://bugs.python.org/issue24221 closed by rhettinger #24222: Idle 2.7 -c, -r compile with print as function. http://bugs.python.org/issue24222 closed by terry.reedy #24223: argparse parsing (mingling --option and optional positional ar http://bugs.python.org/issue24223 closed by vadmium #24226: [3.5 Regression] unable to byte-compile the attached IN.py http://bugs.python.org/issue24226 closed by yselivanov #24227: IndentationError caused by async / await changes in parser http://bugs.python.org/issue24227 closed by zach.ware #24232: Speling fixes http://bugs.python.org/issue24232 closed by berker.peksag #24233: Link to getfqdn rather than "see above" http://bugs.python.org/issue24233 closed by berker.peksag #24236: TestNG results to Junit results conversion http://bugs.python.org/issue24236 closed by tusharm #24237: PEP 479: missing DeprecationWarning when generator_stop is not http://bugs.python.org/issue24237 closed by yselivanov #24240: PEP 448: Update the language reference http://bugs.python.org/issue24240 closed by benjamin.peterson #24242: property performance regression http://bugs.python.org/issue24242 closed by rhettinger #24245: Eliminate do-nothing exception handlers http://bugs.python.org/issue24245 closed by serhiy.storchaka #24246: mimetypes.guess_extension returns different values when init() http://bugs.python.org/issue24246 closed by r.david.murray #24248: Deprecate inspect.Signature.from_function and from_builtin http://bugs.python.org/issue24248 closed by yselivanov #24250: Optimization for strcpy(..., "") in file 'install.c' http://bugs.python.org/issue24250 closed by benjamin.peterson #24257: Incorrect use of PyObject_IsInstance http://bugs.python.org/issue24257 closed by serhiy.storchaka #24262: logging.FileHandler.close() is not thread-safe http://bugs.python.org/issue24262 closed by dubglan

1 0