[issue12169] Factor out common code for d2 commands register, upload and upload_docs

Éric Araujo added the comment: > Hi, I'm wondering why this branch was never merged in? It was, see the comment before with the changeset link. > AFIAK, it's roundabout here - > http://hg.python.org/cpython/log/28e4cd8fd864/Lib/packaging/command/upload.py I don’t understand what you mean. >

[issue20641] Python installer needs elevated rights to install pip

Martin v. Löwis added the comment: I cannot reproduce the problem. It works fine for me. -- ___ Python tracker ___ ___ Python-bugs-lis

[issue20710] Make pydoc consistent about bound methods

Yury Selivanov added the comment: With this patch 'help' now correctly renders classmethods, yay -- ___ Python tracker ___ ___ Python-

[issue20710] Make pydoc consistent about bound methods

Changes by Larry Hastings : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue20716] 3.4 cherry-pick: 5e73bb72662e pydoc shouldn't display "self" for bound methods

Changes by Larry Hastings : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue20716] 3.4 cherry-pick: 5e73bb72662e pydoc shouldn't display "self" for bound methods

New submission from Larry Hastings: 5e73bb72662e -- assignee: larry components: Library (Lib) messages: 211817 nosy: larry priority: release blocker severity: normal status: open title: 3.4 cherry-pick: 5e73bb72662e pydoc shouldn't display "self" for bound methods versions: Python 3.4

[issue20710] Make pydoc consistent about bound methods

Roundup Robot added the comment: New changeset 5e73bb72662e by Larry Hastings in branch 'default': Issue #20710: The pydoc summary line no longer displays the "self" parameter http://hg.python.org/cpython/rev/5e73bb72662e -- nosy: +python-dev ___ Pyth

[issue20710] Make pydoc consistent about bound methods

Yury Selivanov added the comment: Looks good to me. Those unit tests give some confidence ;) -- ___ Python tracker ___ ___ Python-bugs

[issue20710] Make pydoc consistent about bound methods

Larry Hastings added the comment: You're right, that was the exact same test ;-) So what I did was: move the other tests down into that test class, as that's a better fit, and keep the new version of the test. -- Added file: http://bugs.python.org/file34172/larry.fix.help.on.bound.met

[issue20710] Make pydoc consistent about bound methods

Larry Hastings added the comment: I went ahead and added tests for os.stat, and the unbound versions of the two class methods. Total of five new tests now. -- Added file: http://bugs.python.org/file34171/larry.fix.help.on.bound.methods.7.diff ___ P

[issue20679] 3.4 cherry-pick: 587fd4b91120 improve Enum subclass behavior

Larry Hastings added the comment: We still have a couple of weeks left. Ethan, can you start a discussion in python-dev about cherry-picking this for 3.4? -- ___ Python tracker ___

[issue20710] Make pydoc consistent about bound methods

Larry Hastings added the comment: Updated with tests. And I built without docstrings and it still passed. And if I revert the change to Lib/pydoc.py the tests fail. -- Added file: http://bugs.python.org/file34170/larry.fix.help.on.bound.methods.6.diff ___

[issue20715] 3.4 cherry-pick: 2000c27ebe80 inspect: Fix getfullargspec to support builtin module-level functions

Changes by Yury Selivanov : -- keywords: -3.4regression ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue20715] 3.4 cherry-pick: 2000c27ebe80 inspect: Fix getfullargspec to support builtin module-level functions

New submission from Yury Selivanov: Larry, please consider cherry-picking 2000c27ebe80. Another bug in newly renovated 'inspect.getfullargspec()', this time with module-level builtins. Would be great if it supports them well in 3.4. changeset: 89314:2000c27ebe80 tag: tip user:

[issue20711] inspect.getfullargspec does not correctly work with builtin module-level functions

Yury Selivanov added the comment: Thanks Larry! > I bet you want this cherry-picked Very much so! I'll create a new issue. -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue20711] inspect.getfullargspec does not correctly work with builtin module-level functions

Roundup Robot added the comment: New changeset 2000c27ebe80 by Yury Selivanov in branch 'default': inspect: Fix getfullargspec to support builtin module-level functions. Issue #20711 http://hg.python.org/cpython/rev/2000c27ebe80 -- nosy: +python-dev

[issue20679] 3.4 cherry-pick: 587fd4b91120 improve Enum subclass behavior

Larry Hastings added the comment: If you've committed something already, and want to change it, then please request both revisions be cherry-picked. -- ___ Python tracker ___ __

[issue20711] inspect.getfullargspec does not correctly work with builtin module-level functions

Larry Hastings added the comment: I bet you want this cherry-picked; please create a separate issue for that. -- ___ Python tracker ___ __

[issue20679] 3.4 cherry-pick: 587fd4b91120 improve Enum subclass behavior

Ethan Furman added the comment: Can we do that? If a doc change can make it so we're not locked in to supporting __getnewargs__ I could live with that. Although, to be honest, I'd rather get the change in *and* have a doc warning that pickling specifics are subject to change in 3.5. Really,

[issue20653] Pickle enums by name

Ethan Furman added the comment: Thanks for your comments, Eli, I'll work on getting better comments in the code. The qualname comment is partially related to the pickling changes as it's necessary for protocol 4 (I forgot to put that comment in on the previous pickling change that addressed th

[issue20679] 3.4 cherry-pick: 587fd4b91120 improve Enum subclass behavior

Eli Bendersky added the comment: The discussion in #20653 is ongoing but I have to say I don't feel confident about this issue at all. If anything, I'd prefer to explicitly mark "advanced pickling support" for enums as provisional in 3.4 - this is a simple documentation fix Larry should have

[issue20711] inspect.getfullargspec does not correctly work with builtin module-level functions

Yury Selivanov added the comment: Updated patch. The entire test suite pass. -- Added file: http://bugs.python.org/file34169/sig_bound_02.patch ___ Python tracker ___ ___

[issue20679] 3.4 cherry-pick: 587fd4b91120 improve Enum subclass behavior

Ethan Furman added the comment: Larry, If I make changes to the patch, should I reverse the original and then commit one new one so you only have one to merge in, or do you mind having two to do? -- ___ Python tracker

[issue20457] Use partition and enumerate make getopt easier

dongwm added the comment: I have signed the contributor agreement form. The new version of the official web site seem some css style display problems. -- ___ Python tracker ___

[issue20457] Use partition and enumerate make getopt easier

dongwm added the comment: Yes, it has tests. I just modified do_longs and short_has_arg. In Lib/test/test_getopt.py, test_do_longs and test_short_has_arg can do it. -- ___ Python tracker __

[issue20653] Pickle enums by name

Eli Bendersky added the comment: If you were enlightened about how to use the pickle protocols, please explains this better in the code. Currently the code says: # check for a supported pickle protocols, and if not present sabotage +# pickling, since it won't work anyway. +

[issue20653] Pickle enums by name

Ethan Furman added the comment: More explanation: __getnewargs__ is not used by pickle protocol 0 and 1; to support those protocols we need __reduce_ex__. Since __reduce_ex__ works for 0, 1, 2, 3, 4, ... there's no reason to have both __reduce_ex__ *and* __getnewargs__. -- _

[issue12169] Factor out common code for d2 commands register, upload and upload_docs

Matthew Iversen added the comment: Hi, I'm wondering why this branch was never merged in? AFIAK, it's roundabout here - http://hg.python.org/cpython/log/28e4cd8fd864/Lib/packaging/command/upload.py It'd be great to have distutils submit forms that are compliant with the MIME spec (in my use c

[issue19748] test_time failures on AIX

David Edelsohn added the comment: With the latest patch, test_time passes. >>> time.mktime((-100, 1, 10) + (0,)*6) Traceback (most recent call last): File "", line 1, in OverflowError: mktime argument out of range >>> time.mktime((-100, 1, 10) + (0,)*6) Traceback (most recent call last): Fi

[issue20710] Make pydoc consistent about bound methods

Larry Hastings added the comment: An even slighter tweak to the patch, just using De Morgan's law to make the code easier to read. -- Added file: http://bugs.python.org/file34168/larry.fix.help.on.bound.methods.5.diff ___ Python tracker

[issue20653] Pickle enums by name

Ethan Furman added the comment: When I implemented pickle support I did not have a complete understanding of the pickle protocols nor how to best use them. As a result, I picked __getnewargs__ and only supported protocols 2 and 3 (4 didn't exist yet). Serhiy came along and explained a bunch o

[issue20679] 3.4 cherry-pick: 587fd4b91120 improve Enum subclass behavior

Ethan Furman added the comment: When I implemented pickle support I did not have a complete understanding of the pickle protocols nor how to best use them. As a result, I picked __getnewargs__ and only supported protocols 2 and 3 (4 didn't exist yet). Serhiy came along and explained a bunch o

[issue20679] 3.4 cherry-pick: 587fd4b91120 improve Enum subclass behavior

Changes by Ethan Furman : -- Removed message: http://bugs.python.org/msg211739 ___ Python tracker ___ ___ Python-bugs-list mailing lis

[issue20714] Please allow for ]]> in CDATA in minidom.py

New submission from Artur R. Czechowski: Current support for ]]> inside CDATA is to raise an Exception. However, it could be solved by dividing the ]]> to two strings: - ]] - > and each one is a separate CDATA inside elemement. So, to put ]]> inside CDATA one can write: -- component

[issue20713] 3.4 cherry-pick: d57df3f72715 Upgrade pip to 1.5.3

Larry Hastings added the comment: ok. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.or

[issue20713] 3.4 cherry-pick: d57df3f72715 Upgrade pip to 1.5.3

Changes by Larry Hastings : -- resolution: -> fixed stage: -> committed/rejected status: open -> closed ___ Python tracker ___ ___ P

[issue20053] venv and ensurepip are affected by default pip config file

Donald Stufft added the comment: pip 1.5.3 is released and I've requested larry cherry-pick it into 3.4.0 with issue20713 -- ___ Python tracker ___ _

[issue20570] Bundle pip 1.5.3 in Python 3.4rc2

Donald Stufft added the comment: I created issue20713 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:

[issue20713] 3.4 cherry-pick: d57df3f72715 Upgrade pip to 1.5.3

New submission from Donald Stufft: Please pull in the upgrade from pip 1.5.2 to 1.5.3 into CPython 3.4.0, the revision is d57df3f72715 -- assignee: larry messages: 211787 nosy: dstufft, larry, ncoghlan priority: release blocker severity: normal status: open title: 3.4 cherry-pick: d57df

[issue20710] Make pydoc consistent about bound methods

Larry Hastings added the comment: A slight tweak to the patch. Previously I was just using truth testing on the value I got from "__self__", but that's wrong if the object is considered false (e.g. ''.zfill). (Yury got this right in #20711, and I copied from him!) -- Added file: htt

[issue20710] Make pydoc consistent about bound methods

Changes by Larry Hastings : Added file: http://bugs.python.org/file34165/larry.fix.help.on.bound.methods.3.diff ___ Python tracker ___ ___ Py

[issue20710] Make pydoc consistent about bound methods

Larry Hastings added the comment: Here's a revised patch that doesn't modify inspect. -- ___ Python tracker ___ ___ Python-bugs-list m

[issue20710] Make pydoc consistent about bound methods

Yury Selivanov added the comment: > I think that's a bad API, it should be agnostic about the implementation > language. Agree. Re #20711: Please take a look at the patch I wrote. It's your code I modified, you know it and the __text_signature__ quirks better than anyone. -- ___

[issue20712] Make inspect agnostic about whether functions are implemented in Python or C

New submission from Larry Hastings: Some of the methods on the inspect module behave differently depending on whether the callable passed in was implemented in C or in Python. For example, ismethod() only returns True for bound methods implemented in Python. I assert that the interface presen

[issue20710] Make pydoc consistent about bound methods

Larry Hastings added the comment: Okay, that's a fair point. I checked, and the documentation specifically says that ismethod only returns true on bound methods implemented in Python. I think that's a bad API, it should be agnostic about the implementation language. But I'll remove the chan

[issue20648] 3.4 cherry-pick: multiple changesets for asyncio

Yury Selivanov added the comment: Last bit of documentation from me. I, personally, don't have any more changes in mind, so this one is probably the last from me on the asyncio front in this thread. changeset: 89312:ec3a70ef759d tag: tip user:Yury Selivanov date:Thu

[issue20694] asyncio.docs: Document subprocess_exec and subprocess_shell

Changes by Yury Selivanov : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue20694] asyncio.docs: Document subprocess_exec and subprocess_shell

Roundup Robot added the comment: New changeset ec3a70ef759d by Yury Selivanov in branch 'default': asyncio.docs: Document subprocess_exec and subprocess_shell. Issue #20694. http://hg.python.org/cpython/rev/ec3a70ef759d -- nosy: +python-dev ___ Python

[issue20711] inspect.getfullargspec does not correctly work with builtin module-level functions

Changes by Yury Selivanov : -- stage: -> patch review ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://

[issue20710] Make inspect and pydoc consistent about bound methods

Yury Selivanov added the comment: > So why is it necessary (and a release blocker) to fix a bug in > inspect._signature_fromstr, but a terrible idea to fix a bug in > inspect.ismethod? I was actually writing a comment, when I received this on my email ;) Let me explain my point of view. > An

[issue20710] Make inspect and pydoc consistent about bound methods

Larry Hastings added the comment: So why is it necessary (and a release blocker) to fix a bug in inspect._signature_fromstr, but a terrible idea to fix a bug in inspect.ismethod? -- ___ Python tracker ___

[issue20710] Make inspect and pydoc consistent about bound methods

Yury Selivanov added the comment: Indeed, here it is: #20711 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20711] inspect.getfullargspec does not correctly work with builtin module-level functions

New submission from Yury Selivanov: current behaviour: >>> import inspect >>> import os >>> inspect.getfullargspec(os.stat) FullArgSpec(args=['module', 'path'], varargs=None, varkw=None, defaults=None, kwonlyargs=['dir_fd', 'follow_symlinks'], kwonlydefaults={'dir_fd': None, 'follow_symlinks

[issue20710] Make inspect and pydoc consistent about bound methods

Yury Selivanov added the comment: > Rather, I'm proposing to fix a bug in ismethod. Oh, sorry, that's what I meant. I don't think it's good to fix it either. But please hold on, I think I found a bug in inspect.signature. -- ___ Python tracker

[issue20710] Make inspect and pydoc consistent about bound methods

Larry Hastings added the comment: I'm not proposing to modify isbuiltin. Rather, I'm proposing to fix a bug in ismethod. -- ___ Python tracker ___ _

[issue20710] Make inspect and pydoc consistent about bound methods

Yury Selivanov added the comment: I don't think we should touch 'inspect.isbuiltin' at this stage. Please consider my proposal instead. -- ___ Python tracker ___

[issue20710] Make inspect and pydoc consistent about bound methods

Larry Hastings added the comment: We discussed it in python-dev: https://mail.python.org/pipermail/python-dev/2014-January/132051.html And the overwhelming majority voted +1 for "don't show self for bound methods". So I'd like to change it for 3.4. (I meant to get it in earlier but lacked

[issue20710] Make inspect and pydoc consistent about bound methods

Larry Hastings added the comment: Whoops, the test suite hadn't finished when I posted that, and it had an error. Here's an updated patch that fixes the tests. Also, there's one more minor fix in the patch. pydoc has cut-and-pasted code for HTML versus text rendering, and they had fallen out

[issue20710] Make inspect and pydoc consistent about bound methods

Yury Selivanov added the comment: (The thing with my proposal, is that pydoc will handle everything that 'inspect.signature' supports + it's behaviour won't change at all) -- ___ Python tracker ___

[issue20710] Make inspect and pydoc consistent about bound methods

Yury Selivanov added the comment: Larry, I think you can use undocumented and private (but still heavily tested) 'inspect._signature_internal(skip_bound_arg=False)', instead of signature. That will give you a Signature object with 'self' parameter always included. And in 3.5 we'll probably ma

[issue20710] Make inspect and pydoc consistent about bound methods

New submission from Larry Hastings: inspect has a bug: * inspect.ismethod() returns False for bound methods on builtins. If I fix that, that exposes a bug in pydoc: * pydoc's two docroutine() functions assume that bound methods have a __func__; bound builtins do not. The only reason pydoc ass

[issue20710] Make inspect and pydoc consistent about bound methods

Changes by Larry Hastings : -- stage: -> patch review type: -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue20694] asyncio.docs: Document subprocess_exec and subprocess_shell

Changes by Yury Selivanov : Added file: http://bugs.python.org/file34161/asyncio_subp_docs_03.patch ___ Python tracker ___ ___ Python-bugs-lis

[issue20694] asyncio.docs: Document subprocess_exec and subprocess_shell

Changes by Yury Selivanov : Added file: http://bugs.python.org/file34160/asyncio_subp_docs_02.patch ___ Python tracker ___ ___ Python-bugs-lis

[issue20669] OpenBSD: socket.recvmsg tests fail with OSError: [Errno 40] Message too long

STINNER Victor added the comment: For failing "FD pass" tests, see issue #12958: these tests are also skipped on Mac OS X. We should maybe also skip these tests on OpenBSD. -- ___ Python tracker __

[issue20639] pathlib.PurePath.with_suffix() does not allow removing the suffix

Antoine Pitrou added the comment: Thank you! Unfortunately, it is too late for 3.4, but I will make sure the fix is included in 3.4.1 (and 3.5). -- nosy: +serhiy.storchaka stage: -> patch review ___ Python tracker

[issue20685] 3.4 cherry pick: 9f76adbac8b7 better handling of missing SSL/TLS in ensurepip

Larry Hastings added the comment: ok. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mail

[issue20682] test_create_ssl_unix_connection() of test_asyncio failed on "x86 Tiger 3.x"

STINNER Victor added the comment: Oh, AIX has the same issue. I propose broken_unix_getsockname.patch to skip also the check on 'sockname' extra info on AIX. The fix can wait Python 3.4.1. http://buildbot.python.org/all/builders/PPC64%20AIX%203.x/builds/1757/steps/test/logs/stdio

[issue20707] 3.4 cherry-pick: bf413a97f1a9 fix conflicting hypot definition with VS 2010

Larry Hastings added the comment: ok. it's a low-risk fix. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue20707] 3.4 cherry-pick: bf413a97f1a9 fix conflicting hypot definition with VS 2010

Changes by Larry Hastings : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue20669] OpenBSD: socket.recvmsg tests fail with OSError: [Errno 40] Message too long

STINNER Victor added the comment: recvmsg_trunc_emsgsize.patch: modify recvmsg() tests checking for truncated data to ignore the test on OSError(EMSGSIZE). -- keywords: +patch Added file: http://bugs.python.org/file34158/recvmsg_trunc_emsgsize.patch

[issue20709] os.utime(path_to_directory): wrong documentation for Windows.

Changes by STINNER Victor : -- nosy: +larry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python

[issue20708] commands has no "RANDOM" environment?

STINNER Victor added the comment: I'm not sure that commands.getstatusoutput() will use the same shell than your shell. Try to display $SHELL environment variable to know your shell. -- nosy: +haypo ___ Python tracker

[issue20709] os.utime(path_to_directory): wrong documentation for Windows.

New submission from Jan-Philip Gehrcke: The os.utime() docs for Python 2 (http://docs.python.org/2/library/os.html#os.utime) and 3 (http://docs.python.org/3/library/os.html#os.utime) both contain the sentence "Whether a directory can be given for path depends on whether the operating system i

[issue20708] commands has no "RANDOM" environment?

New submission from Yanming Xiao: I saw this issue on Python 2.7.3 running on FreeBSD 9.1-64 and ubuntu 12.04-64. All under BASH. It seems that the shell for the external script does not have the access to RANDOM environment variable. If I run the script directly, the results are OK. # py

[issue20694] asyncio.docs: Document subprocess_exec and subprocess_shell

Yury Selivanov added the comment: Patch is attached, please review. -- keywords: +patch Added file: http://bugs.python.org/file34156/asyncio_subp_docs_01.patch ___ Python tracker ___

[issue20669] OpenBSD: socket.recvmsg tests fail with OSError: [Errno 40] Message too long

STINNER Victor added the comment: Extract of the POSIX standard for recvmsg(): http://pubs.opengroup.org/onlinepubs/009695399/functions/recvmsg.html """ DESCRIPTION (...) The recvmsg() function shall return the total length of the message. (...) If a message is too long to fit in the supplied

[issue20694] asyncio.docs: Document subprocess_exec and subprocess_shell

Changes by Yury Selivanov : -- nosy: +asvetlov ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue20707] 3.4 cherry-pick: bf413a97f1a9 fix conflicting hypot definition with VS 2010

New submission from Zachary Ware: PC/pyconfig.h does "#define hypot _hypot", but VS 2010 and above already define a hypot function (implemented by _hypot), which results in a warning if you have warning 4211 enabled (which warning level 4 does) or a recursive definition which results in a cras

[issue20221] #define hypot _hypot conflicts with existing definition

Zachary Ware added the comment: Fixed, thanks for the report and patch! -- assignee: -> zach.ware resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker _

[issue20221] #define hypot _hypot conflicts with existing definition

Roundup Robot added the comment: New changeset 9aedb876c2d7 by Zachary Ware in branch '3.3': Issue #20221: Removed conflicting (or circular) hypot definition http://hg.python.org/cpython/rev/9aedb876c2d7 New changeset bf413a97f1a9 by Zachary Ware in branch 'default': Issue #20221: Removed confli

[issue20648] 3.4 cherry-pick: multiple changesets for asyncio

Yury Selivanov added the comment: Hopefully, the last one from me ;) Again, some documentation updates. Thank you, Larry, for accepting these last minute fixes. changeset: 89308:cd23d0c3f850 tag: tip user:Yury Selivanov date:Thu Feb 20 16:20:44 2014 -0500 files:

[issue20706] asyncio.docs: Fix wording in 'this method returns a coroutine object'

Roundup Robot added the comment: New changeset cd23d0c3f850 by Yury Selivanov in branch 'default': asyncio.docs: Improve wordings; add a note to the Coroutines section. Issue #20706 http://hg.python.org/cpython/rev/cd23d0c3f850 -- nosy: +python-dev _

[issue20706] asyncio.docs: Fix wording in 'this method returns a coroutine object'

New submission from Yury Selivanov: Codereview: https://codereview.appspot.com/66430046/ -- assignee: yselivanov messages: 211751 nosy: gvanrossum, haypo, yselivanov priority: normal severity: normal status: open title: asyncio.docs: Fix wording in 'this method returns a coroutine object

[issue20706] asyncio.docs: Fix wording in 'this method returns a coroutine object'

Changes by Yury Selivanov : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue20648] 3.4 cherry-pick: multiple changesets for asyncio

Larry Hastings added the comment: I finished the second preview of rc2 just before you posted 96e078663083. That'll go in the third preview. Also, I found another revision you forgot about (something about improving debug info). With that, and the other revisions I mentioned, asyncio in the

[issue20648] 3.4 cherry-pick: multiple changesets for asyncio

STINNER Victor added the comment: changeset: 89307:96e078663083 tag: tip user:Victor Stinner date:Thu Feb 20 21:59:38 2014 +0100 files: Lib/asyncio/base_events.py Lib/test/test_asyncio/test_events.py description: asyncio: _check_resolved_address() must also accept

[issue20687] Change in expectedFailure breaks testtools

Larry Hastings added the comment: Then I'm marking this as 3.5 and clearing the regression keyword. From here we can either fix it in 3.5 or not bother (and just close this issue as wontfix). -- keywords: -3.4regression priority: high -> normal versions: +Python 3.5 -Python 3.4 _

[issue20628] csv.DictReader

Changes by Sean Rodman : Removed file: http://bugs.python.org/file34141/DictReader_DictWriter_python2_NewWording.patch ___ Python tracker ___ ___

[issue20628] csv.DictReader

Sean Rodman added the comment: Great! Thank you for the reference name. I have changed the patch to use a ref link. Here is the new patch. -- Added file: http://bugs.python.org/file34155/DictReader_DictWriter_python2_ref.patch ___ Python tracker

[issue20221] #define hypot _hypot conflicts with existing definition

Zachary Ware added the comment: Ok, I had missed that the warnings in your two separate cases were in fact different. I still don't understand why VC++ sees the two cases so differently (throwing different warnings), but it at least explains the different results in your two cases. I don't s

[issue20648] 3.4 cherry-pick: multiple changesets for asyncio

Yury Selivanov added the comment: Again, documentation update. changeset: 89306:1c35d3114ea1 tag: tip user:Yury Selivanov date:Thu Feb 20 14:10:02 2014 -0500 files: Doc/library/asyncio-stream.rst description: asyncio.docs: Improve documentation of Streams. Issue

[issue20696] asyncio.docs: Document StreamReader an other streams module APIs

Changes by Yury Selivanov : -- resolution: -> fixed stage: patch review -> committed/rejected status: open -> closed ___ Python tracker ___ _

[issue20696] asyncio.docs: Document StreamReader an other streams module APIs

Roundup Robot added the comment: New changeset 1c35d3114ea1 by Yury Selivanov in branch 'default': asyncio.docs: Improve documentation of Streams. Issue #20696. http://hg.python.org/cpython/rev/1c35d3114ea1 -- nosy: +python-dev ___ Python tracker

[issue20705] distutils.extension.Extension with empty 'sources' list

New submission from Rémi Rampin: While this is obviously a programming error, distutils currently has no check for the 'sources' list being empty, which might or might not result in a self-explanatory error message once the CCompiler's link() method is called (the exact error depends on the su

[issue20704] asyncio: Implement debug API

Yury Selivanov added the comment: Relevant commits: 549f451aa4c3 and dbf13a7d3987 -- ___ Python tracker ___ ___ Python-bugs-list maili

[issue20648] 3.4 cherry-pick: multiple changesets for asyncio

Yury Selivanov added the comment: NEWS updates: changeset: 89305:db749f0c6567 tag: tip user:Yury Selivanov date:Thu Feb 20 13:59:14 2014 -0500 files: Misc/NEWS description: Misc/NEWS: Add some missing news items re asyncio. -- __

[issue20704] asyncio: Implement debug API

Changes by Yury Selivanov : -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list U

[issue20704] asyncio: Implement debug API

New submission from Yury Selivanov: This is a proxy issue for https://code.google.com/p/tulip/issues/detail?id=136 -- assignee: haypo messages: 211740 nosy: gvanrossum, haypo, yselivanov priority: normal severity: normal stage: committed/rejected status: open title: asyncio: Implement de

[issue20679] 3.4 cherry-pick: 587fd4b91120 improve Enum subclass behavior

Ethan Furman added the comment: When I implemented pickle support I did not have a complete understanding of the pickle protocols nor how to best use them. As a result, I picked __getnewargs__ and only supported protocols 2 and 3 (4 didn't exist yet). Serhiy came along and explained a bunch o

  1   2   >